WordCracker is a free word game. To run the game we store your progress, your display name and your online matches, and we record how the game is played. That record is linked to a random account ID, not to your real identity unless you sign in. We do not sell your data, show ads, or use advertising IDs, and we do not track you across other apps or websites.
WordCracker is operated as an independent project. The game is hosted at wordcracker.net and runs in your browser and as apps for iOS and Android. Contact: privacy@wordcracker.net.
When you first open the game we create a random identifier called a playerToken and a Firebase account ID. The account ID is anonymous unless you sign in. We use these identifiers to:
Our analytics provider also uses its own app-instance identifier. On iOS this is Apple's per-developer "identifier for vendor". On the web and Android it is a first-party Google Analytics cookie. If you turn on notifications, we store your device's push token so we can tell you when it's your move. We never collect advertising IDs.
Most of your progress lives in your browser's or app's local storage:
Some of it also goes to our servers: your Daily Puzzle results (with your display name) for the daily stats every player sees, your rating and leaderboard entry, and, if you sign in, your full Quest save and replays. Details are in the next section.
The following are stored in Firebase Realtime Database (operated by Google):
Your display name is public: other players see it in matches, on leaderboards and in invite links you share.
If you sign in with Google or Apple, we receive your name and email address through Firebase Authentication. Apple may give us a private relay address instead of your real one. We use your first name to suggest a display name, and your email address to identify your account. If you turn on Email me when it's my move in Settings, we also use your email to tell you when a match is waiting on you. Those emails are sent through Resend, an email-delivery service, and you can turn them off in Settings at any time. Sign-in is optional; every game mode works without an account.
We use Google Analytics for Firebase to understand how the game is played. The events we record include:
Events are linked to your account ID. Google Analytics also records your device type, operating system, language and approximate location (city or region, derived from your IP address). The letters on the board are gameplay data, not personal data. We never send your display name, your email address or anything you type into a report or bug report to analytics. Analytics is not used for advertising and is not shared with advertisers. There is no in-app switch to turn analytics off. You can ask us to delete your analytics data at any time (see Your rights).
If your device is set to a European time zone, analytics is switched off entirely.
Separately from Google Analytics, the game sends a tiny anonymous signal when the app opens, when a match starts, when a round ends, and when an invite is opened or joined. It contains only the kind of event and the platform (iOS, Android or web). It carries no player ID or token, and nothing is stored on or read from your device for it. Our server adds the country your connection comes from, then increases a daily per-country total. Your IP address is not stored or logged. We keep only those totals, such as "40 rounds played in Brazil today", which can't be linked to you or to any individual. Because no identifier is involved, these counts are collected in every region, including Europe.
We use Sentry for crash reporting on the website and in the apps. When an error happens, Sentry receives:
playerTokenSentry does not receive form values, the contents of your local storage, or text you've typed. Crash reporting is switched off for devices set to a European time zone.
If you submit a bug report or feedback through the in-game form, we receive what you wrote and the email address if you give one. We also receive a snapshot to help us reproduce the issue: app version, current screen and mode, screen size, time zone, browser or device, your playerToken and the last few errors. Reports are emailed to the operator through Resend.
When you look up a word that isn't in our built-in definitions, the word is sent to the free Dictionary API (dictionaryapi.dev). Like any website, it can see your IP address.
The website is hosted by Vercel, which keeps standard server logs (including IP addresses) for security and reliability. On Android, the app reads Google Play's install referrer once, on first launch, only to tell whether you arrived through a friend's invite. Apple and Google also process data under their own policies when you download the app or sign in with them.
These service providers process data for us:
By using WordCracker, you consent to your data being processed in the United States.
Depending on where you live, you may have some or all of the following rights regarding your personal data:
To exercise any of these, email privacy@wordcracker.net. We'll respond within 30 days. If you're in the EU/UK and we can't resolve a concern, you also have the right to file a complaint with your local data-protection authority.
California residents have the rights listed above and additionally the right to know what personal information we collect and the right to opt out of the "sale" or "sharing" of personal information. WordCracker does not sell or share personal information for cross-context behavioral advertising. You may still email privacy@wordcracker.net to exercise any other right.
WordCracker is intended for users 13 years of age and older. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe your child under 13 has provided us with personal information, please contact privacy@wordcracker.net and we will delete it.
The website uses first-party cookies:
We also use localStorage and IndexedDB to store your game on your device. Sign-in providers (Google, Apple) may set their own cookies while you sign in. You can clear all of these by clearing your browser's site data for wordcracker.net, or by clearing the app's data.
We use HTTPS for all traffic. Firebase data is access-controlled via security rules so users can only read their own private data. Despite this, no system is perfectly secure — please don't use WordCracker to store information you'd be devastated to lose.
We may update this policy from time to time. The "Effective" date at the top of the page reflects the latest version. We don't currently have a way to notify users of changes; please check back occasionally if it matters to you.
Privacy questions, data requests, or concerns: privacy@wordcracker.net.