Word Peach

Privacy Policy

Last updated 17 November 2026

This policy explains what personal data Word Peach handles, why, who else receives it, how long it’s kept, and your rights. It’s written to meet the EU General Data Protection Regulation (GDPR).

1. Who is responsible

The controller is Sanaz Kazemi Gharahche, Wittenberger Str. 44, 12689 Berlin, Germany (“we”, “us”). Email: [email protected]. We haven’t appointed a data protection officer, since we aren’t required to.

2. The short version

  • We don’t sell your data or show ads, and we have no advertising SDKs in the app. Google Analytics runs only if you allow it (section 3).
  • We don’t store your email address or password on our server. Google’s Firebase service holds them.
  • Your game data, chats and uploads are on our server in Germany.
  • Private chat isn’t end-to-end encrypted, and we can read it.
  • Deleting your account doesn’t delete everything. Most of what stays goes after a year, and purchase records go 10 years after the purchase. Support tickets are kept with no end date. Section 7 lists them.
  • Other players can see your name, avatar and level, and your activity in places like leaderboards and matches.
  • Word Peach is a game of skill played for fun and entertainment, not gambling. Coins and gems have no real-world value and can’t be exchanged for money, so we never collect payout or bank details (Terms sections 5 and 6).

3. What we process and why

The legal bases are from Art. 6(1) GDPR: (b) performing our contract with you, (c) a legal duty, (f) our legitimate interests (named below), (a) your consent.

Purpose Data Legal basis
Account and sign-in Account ID, username, display name, avatar and frame, account type, creation date, last seen date; a hash of your device credential; Google or Apple’s account identifier; the Firebase user ID (not your email address); session token hashes (b)
Checking whether an email address has an account The address you enter, passed to Firebase and not stored by us (b)
Playing the game Levels, stars, words found, hints, timings, XP, level, stats, daily puzzle results, match history and results, leaderboard scores (b)
Offline play A random install ID; a log of your offline actions, with times (b); (f) keeping play fair
Coins, gems and purchases Balances and a complete history of changes; Google order ID or Apple transaction IDs, product, time and refund status of each purchase; VIP status and, for a VIP subscription, its state in the store (active, in a grace period, on hold, cancelled or ended), its tier, renewal date and a token that identifies it in Google Play or the App Store (not your card or payment details) (b), (c) for tax and accounting records
Friends and social features Friends, requests, blocks, invite codes and who invited whom, gifts of VIP, nudges, online status, watch history (b)
Private chat Text, photos and voice notes, in readable form; read positions; your emoji reactions to messages (b); (f) safety and enforcing our rules
Public chat Your messages, with name, avatar, frame, level, VIP flag and game admin flag; your emoji reactions to messages; the game’s own notices about you: a ban notice, and a card for each private room without a password that you host (b); (f) safety, and helping players find a match
Moderation Reports, what was reported and by whom, bans and reasons, custom avatar reviews, audit records of operator changes. A banned player is shown the reason for an account ban; the reason for a ban on a phone is given on request. If a ban closes your report, we send you a push notification saying that a player you reported has been banned, without naming them. In the app, you can silence it only by pausing all notifications (f) a safe, lawful service; (c) our duties for illegal content
Notifications Push token, platform, app version, permission state, your category choices, a log of what was sent (b); (a) for marketing
Device bans A device identifier for the phone you play on: on Android, a one-way hash of the phone’s Android ID (the ID itself never leaves the phone); on iOS, a random ID the app keeps in the phone’s keychain. It’s recorded with each sign-in session, with which accounts have signed in on that phone and when, and with a support ticket you open. If we ban a phone, we keep its identifier, the reason and when (f) enforcing bans, so a banned player can’t simply sign in with another account, and protecting other players
Security and abuse IP address, kept briefly for rate limits; a salted hash of it while you’re in the matchmaking queue and joining a match; patterns such as repeat opponents; offline verification flags; application logs with account IDs (f) protecting the service and players
Diagnostics Crash reports through Firebase Crashlytics: stack traces, device model, OS and app version, and Crashlytics and installation IDs (f) keeping the app working
Usage measurement, only if you allow usage statistics Google Analytics for Firebase, automatic collection only, such as screens opened and session length, with an app instance ID. We don’t send it custom events or your account ID (a) your consent
Support tickets in the app What you write to support, with photos and voice notes; replies you quote; when you opened, read and sent each message; the app version and store you use, and whether your account or your phone was banned when you opened the ticket, and the identifier of the phone you opened it from. A banned account can still write to support (b) or (f) answering you, reviewing bans and disputes, and keeping a record of them; (c) for legal requests
Emails you send us Your address and what you write (b) or (f) answering you; (c) for legal requests

What you have to provide. A username and display name are needed to register, and playing online needs the data above. Nothing else is required by law. Without a required item, the feature it supports can’t work. Photos, voice notes, support tickets, notifications and email or social sign-in are optional.

Usage statistics are off until you agree. The app asks once, and you can change your answer at any time in Settings › Usage statistics. Saying no changes nothing else in the game.

Marketing notifications are opt-in, and you can turn them off at any time. Other notifications, like daily puzzle reminders, friend progress and a player waiting for an opponent, are on by default but need your phone’s notification permission, and each can be turned off in Settings. The notice to reporters, under “Moderation” above, and the notice that support replied to your ticket can’t be turned off on its own. A banned account gets only the support notice.

4. On your device

We store some information on your device because it’s needed for the service you asked for (§ 25(2) TDDDG):

  • Sign-in: your device credential and install ID, in the system’s secure storage.
  • Device identifier: on iOS, a random ID in the keychain, which stays when you reinstall the app. On Android, the app reads the phone’s Android ID, which the system gives each app, and sends only a one-way hash of it. Either is sent each time you sign in, so that a ban on a phone applies whichever account signs in on it (section 3).
  • Email address: kept locally for the “Change password” option. It isn’t sent to our server for storage. It may be included in your device’s backup, if you use one.
  • Game data: the campaign bundle, your offline action log until it syncs, and a cached profile.
  • Settings: sound, theme, your usage statistics choice and similar.

Usage statistics store an app instance ID on your device only with your consent (§ 25(1) TDDDG). Without it, Google Analytics stores and sends nothing.

Permissions, each asked for only when needed:

  • Camera and photos to set an avatar or send a photo in chat. On Android, the system picker gives us only what you choose.
  • Microphone to record voice notes, in chat or to support.
  • Notifications for push messages.

We don’t ask for your location or contacts. The Firebase Analytics library can also declare a permission for the install referrer on Android.

5. Who can see what

Other players

  • Profile and search: registered players can find you by username or display name and open your profile, which shows those names, your avatar, frame, level, XP and three game stats. If you’re a guest, this page doesn’t exist, and other players see you as “Guest”. Your guest username and account ID are still sent to other players’ apps with leaderboard data, although they aren’t shown.
  • Leaderboards: your name, avatar, frame, level and score, to anyone signed in. Daily puzzle boards also show your solve time.
  • Matches and rooms: your opponent and spectators see your name, avatar, frame, level, VIP status, entry value, connection status and progress. Spectators can include any signed-in player, even in a private room with a password. There’s no way to opt out, though you can see a spectator count.
  • Public chat: everyone in the game can read your messages, and can scroll back through every one still kept, however old (section 7). Your reactions to messages show only in each emoji’s count, not with your name. If we make your account a game admin, your messages show an “Admin” badge. The game also posts there itself:
    • Ban notices: when we ban an account, public chat shows that the player was banned, with their name as it was at the time (“Guest” for a guest), how many times they’ve been banned and for how long. Lifting the ban doesn’t remove the notice.
    • Room cards: a private room without a password is announced with the host’s name, avatar, frame, level, VIP status, the room code and the entry, and follows the room until it starts or closes. A room with a password is never announced.
  • Friends: your online status, progress on the campaign map, and when you’ve been away.
  • Notifications: some name you to other players, for example a friend request, passing a friend on the map, or a search for an opponent. That last one can reach players you don’t know.
  • Avatars: avatar image files are served at unguessable web addresses that need no login.

The operator. Only the operator has access to production data, and can see:

  • all private conversations, including text, photos and voice notes, and including messages the sender deleted and media that has expired for players, until they’re removed (section 7). Reading them isn’t logged;
  • your support tickets, with their photos and voice notes, your account’s ban state and the details captured when you opened each one. Support replies are signed “Word Peach Support”, whoever sent them, and support can see when you have read them. Closing or reopening a ticket, deleting an attachment and blocking an account from support are recorded in the audit log;
  • the words and progress in a live match;
  • reports, public chat, players’ balances, purchases, progress and sign-in types;
  • which phones an account has signed in on (shown by platform and the last few characters of the identifier), the other accounts that signed in on the same phone, and whether a phone is banned;
  • who is online and playing. The operator can also get a push notification when a player looks for an opponent.

We use this to moderate, handle reports and support, and investigate abuse.

The operator can also mark a registered player’s account as a game admin, then post, reply and react in public chat as that account. Messages from a game admin show an “Admin” badge, whether the player or the operator sent them, and each post the operator makes is recorded in the audit log.

6. Recipients and transfers outside the EU

Our own server is in Germany, so if you play from elsewhere, your data is sent there. We use these providers:

Provider Purpose Where and on what basis
Google Firebase Authentication Email and password sign-in, verification and reset emails; holds your address, password, IP address and user agent US only. Keeps logged IPs a few weeks. Google is our processor
Google Firebase Cloud Messaging; Apple Push Notification service on iOS Delivering notifications. Their content can include other players’ names and account IDs, and, if you choose the “full” preview, up to 80 characters of a message and a link to a chat photo that works for 15 minutes Global
Google Firebase Crashlytics Crash reports Global. Google keeps them for 90 days
Google Analytics for Firebase Usage measurement, only with your consent Under Google’s separate Analytics terms. Google’s documents we reviewed don’t state its location
Google Sign-In; Sign in with Apple Sign-in, under their own policies. We keep only their account identifier Google and Apple
Google Play; Apple App Store Payments, subscriptions and checking purchases. We ask them to confirm purchases, and they tell us about renewals, cancellations and refunds. Google and Apple act under their own terms and privacy policies, and they are processors for the checking and notifications we exchange with them Google and Apple
The browser push service of the operator’s own device Telling the operator that a named player is looking for an opponent, if switched on. Encrypted in transit Depends on the browser’s provider
Cloudflare All traffic between you and our server passes through its network, including your IP address Global

Google says it also uses some service data from Firebase, such as for Cloud Messaging and Crashlytics, to maintain and protect its services, under its own privacy policy.

Transfers. Transfers from the EU to the US rely on the EU-US Data Privacy Framework for certified companies, including Google LLC, and on the European Commission’s standard contractual clauses otherwise (Art. 45 and 46 GDPR). You can ask us for a copy of the safeguards.

We don’t otherwise share your data, except where the law requires it or it’s needed to establish or defend legal claims. If you share an invite, you choose the app it goes to.

7. How long we keep data

Data How long
Chat text, public chat messages Until 1 year after the sender’s account is deleted, even if the sender deleted the message earlier. There’s no time limit while that account exists. A ban notice or room card about a player counts as that player’s message
Chat photos and voice notes Hidden from players after 48 hours and 7 days. The file is removed 1 year after that, even if the message or the account was deleted
Inactive guest accounts Deleted as described below after 90 days without a login. A guest with an active VIP subscription isn’t deleted, and the 90 days count from the end of the subscription
Subscription records While the subscription can still renew, and 10 years after it ends
Purchase records 10 years from the purchase, on every account. A live account’s balance history then keeps the entry without its order ID, so the balance still adds up
Balances, XP, level, other coin and gem history, frame ownership, invite code Until 1 year after the account is deleted
Match history, invites, gifts of VIP, nudges Until 1 year after the account is deleted, or longer while the other player’s account exists (see below)
Custom avatars The image in use is deleted with your account. A replaced or declined image, and the record of its review, go up to 1 year after it stopped being used
Support tickets: messages, photos, voice notes, and the details captured when a ticket is opened No end date. They’re kept after the ticket is closed and after the account is deleted, to handle your request, follow it up, review appeals and disputes, and for audits. After an account is deleted, its name and avatar no longer show with them; the account ID stays. We may delete a single photo or voice note by hand, keeping a record of who deleted it and when
Reports, bans, operator audit records Until 1 year after the reported, banned or audited account is deleted. There’s no time limit while that account exists. Audit records of operator changes can name an account’s old username and display name, and stay in readable form until then
Offline action log 90 days on the server; removed from the device once synced
Offline sync records and flags, watch history Until 1 year after the account is deleted
Which offline rules an install was given: install ID, rules version, time first served No end date. Nothing links it to an account after that account’s offline sync records go
Leaderboard scores 7, 56 or 366 days after a daily, weekly or monthly period ends, so a monthly score can stay up to about a month past the 1-year mark
Notification log 120 days
Push tokens Until you sign out, the token is rejected, you’re banned, or the account is deleted
Session records, with the device identifier they were signed in on Valid 24 hours; removed 90 days after they expire
Which phones an account signed in on Until 1 year after the account is deleted
A banned phone’s identifier, the reason and when Until we lift the ban, whatever happens to the accounts that used the phone
IP address in rate limits About an hour; online status about a minute
Application logs Rotated by size (5 files of 50 MB), so there’s no fixed time
Backups 14 days. They include the database, avatars, chat files and support attachments
Firebase user Until you delete your account or remove the user; Google then clears it from its systems within 180 days. An email sign-up that’s never verified goes after 30 days (see below)

While an account exists, including a banned one, its records stay unless the table gives a shorter limit. So a message you delete stays until a year after your account is deleted. A daily job removes data once its date has passed. Each run has a limit, so a backlog can take some days longer.

When you delete your account, or a guest account is removed:

  • Deleted straight away: sign-in links, progress, stats, VIP, friends, requests, blocks, daily puzzle results, activity days, your offline action log, push tokens and preferences, your current custom avatar, and your Firebase user.
  • Anonymized straight away: your account record loses its username, display name, avatar and frame, but keeps its ID, type, dates and ban status. An avatar waiting for review is declined, and can’t be approved afterwards.
  • Kept for 1 year, still linked to that account ID: balances, XP, level and their history, match history, messages you sent, public chat messages, your reactions to messages, reports and bans against you, audit records, invite code and invites, gifts and nudges, watch history, frame ownership, offline sync records and the phones you signed in on.
  • Kept on their own schedule, as in the table: purchase records, chat photos and voice notes, replaced or declined avatars, sent notification and session logs, and leaderboard scores, which are hidden from players.
  • Kept with no end date: your support tickets, with their photos and voice notes and the identifier of the phone each was opened from.
  • Not affected: a ban on a phone you used stays until we lift it. Open tickets are closed when the account is deleted.

After that year, your account record stays, empty, because other records point at it. It holds only its ID, type and dates, and has no end date. If it has purchases inside their 10 years, those rows stay and keep the account ID. An account in a live match, or with an open report against it, is held until that ends. A message or file under an open report isn’t removed until the report is closed.

Chat. A deleted account can’t receive new messages. The other person keeps seeing the conversation until messages are removed, and removed messages show as deleted. Public chat messages from deleted accounts are hidden from players, and so are ban notices and room cards about them. A removed message’s row stays, with its sender’s ID and time but no text or file, and a private conversation’s record keeps both account IDs. These have no end date. The other person’s own messages follow the dates of their account.

Records shared by two players. Matches, invites, gifts of VIP and nudges stay while the other player’s account exists, because that player’s history, rewards and once-only limits depend on them. Your ID in them then points to the empty account record. They go once both accounts are past their date. A report you made stays until the reported account’s date, with your ID in the same way.

Deleted data can stay in backups until they expire, and restoring a backup could bring it back for a time. When you delete an Apple-linked account in the iOS app, the app asks Apple for a one-time code and we use it to revoke your Sign in with Apple grant. We don’t store Apple’s tokens. If Apple’s sheet fails, or the account is deleted another way, the grant stays. We don’t revoke a Google sign-in grant. You can remove either in that account’s settings.

Firebase. If deleting your Firebase user fails, we queue a retry, which runs once a day for up to 30 attempts and keeps only the user ID. If you’ve signed back in with that address, the user is in use again and we stop. If all 30 attempts fail, we give up and keep no record of which user it was, so your address can stay at Firebase. If you think that has happened, email us, and we may need you to tell us the address. Someone who signs up with an email address and never verifies it has no account with us, and we delete that Firebase user 30 days after the sign-up, unless an account signs in as that user by then. Someone who verifies their address but never signs in to the game also has no account with us, and that Firebase user has no end date. You can email us to have it removed.

8. Automated decisions

We don’t make decisions with legal or similarly significant effects solely by automated means (Art. 22 GDPR), in our view. For transparency:

  • Our server verifies offline play and can automatically void the rewards in a batch that fails, with a report to you and a flag that we can review.
  • Inactive guest accounts are removed automatically after 90 days. A guest with an active VIP subscription isn’t removed, and the 90 days count from the end of the subscription.
  • Players for “opponent waiting” notifications are picked automatically, using last activity, level and gem balance, with friends first.

Bans are decided by a person.

9. Your rights

Under the GDPR you have the right to:

  • access your data and receive a copy (Art. 15);
  • have it corrected (Art. 16);
  • have it deleted (Art. 17), subject to what we must or may keep;
  • restrict processing (Art. 18);
  • receive data you gave us in a portable form (Art. 20);
  • object to processing based on legitimate interests (Art. 21);
  • withdraw consent at any time, with effect for the future (Art. 7(3)), such as by turning off usage statistics in Settings.

To use them, email [email protected]. You can also delete your account in the app, unless you’re banned, when you need to email us. We answer within one month. To protect your account, we need to confirm it’s yours, by signing in or by verifying its email address. A guest account without its device can’t be tied to you, so we usually can’t act on it, and it’s removed after 90 days of inactivity (counted from the end of a VIP subscription, if it has one).

Right to complain. You can complain to any data protection authority, including where you live. Ours is the Berlin Commissioner for Data Protection and Freedom of Information (Berliner Beauftragte für Datenschutz und Informationsfreiheit), Alt-Moabit 59-61, 10555 Berlin, Germany.

If you live elsewhere. The rights above are available to all players. You may have further rights under local law, such as in the UK, Switzerland, Brazil or certain US states, including California. Depending on where you live, these can include knowing what’s collected, deleting or correcting it, and not being discriminated against for using your rights. We don’t sell personal data or share it for cross-context behavioural advertising as those laws define it. Email us, and we’ll respond as your law requires.

10. Children

Word Peach isn’t directed at anyone under 18, and the terms require players to be 18 or older. We don’t check age. If you believe a child is using the game, email us and we’ll delete the account as described in section 7.

11. Security

Traffic to our server is encrypted in transit, device credentials and sessions are stored as hashes, and only the operator has access to production data. But chats aren’t end-to-end encrypted, and everything runs on a single server with backups on the same machine. No system is fully secure, and we’ll tell you and the authorities about a data breach where the law requires it.

12. This website

The site uses no cookies, no analytics and no third-party content. If you choose a theme, your browser remembers it in local storage, and it’s never sent to us. The demo wheel runs entirely in your browser. Our server doesn’t keep access logs of your visits, but your request passes through Cloudflare, which processes your IP address to deliver and protect the site (Art. 6(1)(f) GDPR).

13. Changes

We’ll update this page when our handling of data changes, and tell you in the app about material changes. The date at the top shows the current version.

© 2026 Sanaz Kazemi Gharahche
Terms of ServicePrivacy PolicyDelete accountImpressum

Apple, the Apple logo and App Store are trademarks of Apple Inc., registered in the U.S. and other countries. Google Play and the Google Play logo are trademarks of Google LLC.