Privacy Policy
Last updated 24 October 2026. Covers the revised Swiss Federal Act on Data Protection (revFADP) and, for EU players, the GDPR.
Who is responsible
The controller for your personal data — the Verantwortlicher under Art. 5 lit. j revFADP and the controller under Art. 4(7) GDPR — is Marvin Krieg — HelveticLabs (sole proprietorship), 12 Rue Le Corbusier, 1208 Genève, Switzerland. Full operator details are in our Impressum; data-protection questions go to the address at the bottom of this page.
Data we collect
- Account data — email address, hashed password (or the account identifier of Google, Apple, GitHub or HelveticLabs if you sign in with one of them), display name, handle, and date of birth. DOB is collected once at signup solely to enforce our 16+ age requirement and is never shown to other players.
- Technical data — IP address, browser/device info, and connection logs, captured automatically for security, abuse prevention, and debugging.
- Gameplay data — match results, scores, leaderboard rankings, and per-game statistics.
- Chat & messages — chat, direct messages, friend requests, and invites, plus reports filed by or against you.
- Payment data — PRO checkout currently runs in mock mode; no real payment data is collected until a live processor is wired in (this section will name it as a sub-processor when that happens).
- Guest sessions — a temporary, memory-only token, never written to persistent storage and discarded on reload. No account profile is created for guests.
Why we process it
- Performance of a contract (Art. 6(1)(b) GDPR) — account, matchmaking, chat, leaderboards, PRO billing.
- Legitimate interest (Art. 6(1)(f) GDPR) — fraud and abuse prevention, report handling, service security, and enforcing our own 16+ minimum age from the date of birth you give at signup. No Swiss or EU statute imposes that age limit on us; it is our rule, so we rely on legitimate interest for it rather than claiming a legal obligation we do not have.
- Consent (Art. 6(1)(a) GDPR) — optional analytics, and optional marketing notifications; toggle either at any time, analytics in the consent banner and notifications in Settings → Notifications.
- Legal obligation (Art. 6(1)(c) GDPR) — keeping billing records for the ten years Art. 958f of the Swiss Code of Obligations requires, once PRO billing is live.
Under the revFADP a private controller does not need a statutory legal basis to process personal data at all: it must respect the Art. 6 principles — lawfulness, good faith, proportionality, purpose limitation, accuracy, security — and needs an Art. 31 justification only where processing would otherwise breach personality rights under Art. 30. The grounds above are how we meet both regimes at once.
Sub-processors
We use a small number of processors to run the Service — Hetzner (the server our database runs on), Sentry (error tracking), Vercel (hosting), our payment processor, and our email provider. None may use your data for their own purposes. See the full list with purpose and region on our Sub-processors page.
Transfers abroad
Art. 19 para. 4 revFADP requires us to name the destination country and the safeguard, so:
- Switzerland and the EU/EEA — our database (on our own server in Nuremberg), error tracking and payment processing (Ireland) stay here. The EU/EEA is on the Federal Council adequacy list (Annex 1 DPO), so nothing further is needed.
- United States — our hosting provider’s edge network, our email provider and — only if you choose them — the Google, Apple and GitHub sign-in options involve US processing. Those transfers rest on the European Commission Standard Contractual Clauses with the Swiss addendum recognised by the FDPIC (Art. 16 para. 2 lit. d revFADP) and, where the vendor is certified, on the Swiss–US Data Privacy Framework.
Ask us at the address below for a copy of the safeguards we rely on.
Security
We take the measures Art. 8 revFADP and Art. 32 GDPR require: TLS in transit, passwords stored only as hashes, least-privilege access for the small number of operators and moderators who need it, every moderation action logged against the admin who took it, and backups. No system is perfectly secure; if a breach is likely to result in a high risk to your rights we notify the FDPIC as soon as possible (Art. 24 revFADP) and tell you where the law requires it.
Automated moderation
Every chat message and direct message is checked automatically before it is delivered. A message with a slur or a scam link is not sent, and repeats mute the sender's chat for a limited time (from 5 or 30 minutes, doubling with each repeat, at most 30 days). To do this we keep a count of your blocked messages with your account; the blocked text itself is not stored. A mute only limits chat and direct messages for a while; it does not touch your account, purchases or progress.
Reported chat, DMs and profiles also run through an automated screen, which only queues content for a human moderator; a person decides whether to dismiss, delete, mute or ban. You can ask us at the address below to have a person review any automatic block or mute, or any action taken against your account, and to hear your side (Art. 21 revFADP, Art. 22 GDPR).
Retention periods
- Account data — deleted within 30 days of account deletion (Settings → Account → Delete account).
- Gameplay stats & leaderboard entries — deleted on account closure. Match results (score and placement in a match) stay, irreversibly anonymized, so the other players' matches keep their outcome. Anonymized means the account identifier is destroyed, not replaced by a pseudonym we could reverse: once it is done the result is no longer personal data and cannot be traced back to you, which is also why we cannot delete a specific result for you afterwards.
- Chat & direct messages — 12 months from the message date, or until account deletion, whichever is sooner.
- Technical logs — request and error logs sit with our error-monitoring processor for 90 days and are not kept in our own database. The security records we do store (login lockouts, spent verification and reset tokens, in-app notifications) are pruned at 90 days.
- Reports & moderation records — 12 months after resolution.
- Guest sessions — never persisted.
These windows are enforced by the service, not by hand: a retention pass runs on every deployment and can be triggered between deployments, and it deletes exactly what is past the periods above — including a direct-message thread once its last message has aged out, so an empty thread cannot outlive the messages it held. Art. 6 para. 4 revFADP and Art. 5(1)(e) GDPR require data actually to be deleted once its purpose is spent, which is why these periods are wired to code rather than to good intentions.
Your rights
Under revFADP and, where applicable, GDPR, you have the right to:
- Access the data we hold about you (Art. 25 revFADP, Art. 15 GDPR) — download it anytime from Settings, or via
GET /me/export. - Rectification of inaccurate or incomplete data (Art. 32 para. 1 revFADP, Art. 16 GDPR).
- Erasure ("right to be forgotten") (Art. 32 para. 2 revFADP, Art. 17 GDPR), subject to the retention periods above.
- Portability — the data you gave us, in a structured, machine-readable format (Art. 28 revFADP, Art. 20 GDPR). That is exactly what the Settings export produces.
- Objection to processing based on legitimate interest, and withdrawal of consent at any time.
Access, deletion, and export are self-serve in Settings. For rectification or anything else, email us (below); we answer within 30 days (Art. 25 para. 7 revFADP and Art. 18 DPO; one month under Art. 12(3) GDPR). Access is free, and we may ask you to identify yourself before releasing data.
In Switzerland the FDPIC does not decide individual complaints: you can report a matter to it (Art. 49 revFADP) and separately enforce your rights in the civil courts (Art. 32 revFADP). If you are in the EU/EEA you can lodge a complaint with your local supervisory authority. We would rather you came to us first.
EU representative
We are established in Switzerland and offer Playza into the EU/EEA, which engages Art. 3(2)(a) GDPR. Our processing is occasional, involves no special categories at scale, and is unlikely to result in a risk to the rights and freedoms of players, so we rely on the exemption in Art. 27(2)(a) GDPR and have not appointed an EU representative. We will appoint one and name it here if that stops being true. EU players can reach us directly at the address below.
Changes to this policy
The date at the top of this page is the version in force. If we change how we process your data in a way that materially affects you, we will tell you in the app or by email before the change takes effect.
Age requirement
Playza is for players aged 16 and over. We collect your date of birth at signup solely to enforce this minimum age and don't use it for any other purpose.
Contact us
Questions or requests about this policy: support@playza.app