Privacy Policy — Crush Sort
Effective date: 17 October 2026
Version: 1
1. Who we are
Crush Sort ("the app", "the game") is published by TEZZVO ("we", "us"). We are the controller of the personal data described here (LGPD, Lei 13.709/2018; and, for users in the EEA/UK, the GDPR).
Contact for privacy questions and requests: privacy@tezzvo.com, a monitored mailbox. Write to it for any request under this policy, wherever you live; we answer within one month.
Data protection officer (encarregado, LGPD art. 41; DPO, GDPR art. 37): not appointed. The game processes no special-category data and carries out no large-scale systematic monitoring, so the GDPR does not require one; privacy@tezzvo.com is the channel for data-subject requests. We do not name an EU/EEA representative: the contact address works from anywhere.
2. The short version
- You can play Crush Sort without an account and without giving us your name, e-mail, phone number or location.
- Your game progress, settings and streaks are stored on your device.
- We collect anonymous usage events and crash reports, under a random install id that is not your device id, advertising id or name. You can switch this off in Settings.
- If you turn on cloud backup, a small save (your progress) is stored with Google Firebase under an anonymous account. You can delete it in the app.
- Ads (rewarded, shown only when you choose to watch one) are served by Google AdMob.
- Purchases are made through Google Play. We never see or store your card number.
- The game is not directed at children. We know minors may play it; see section 9.
3. What we collect, why, and on what legal basis
"Basis" is the legal ground we rely on: LGPD art. 7 (and art. 14 for children), and GDPR art. 6.
| # | Data | Where it comes from | Purpose | Basis |
|---|---|---|---|---|
| 1 | Game data on your device: progress, level results, stars, settings (sound, haptics, speed, reduced motion, theme), daily streak, calm-mode stats, hints used, whether you opted out of analytics or cloud backup, the daily-reminder time you chose, ad frequency counters, a local log of purchase attempts | You, by playing | Run the game, remember your progress | Not sent to us. Stored in app storage on your device. Deleting the app data erases it |
| 2 | Random install id (a 128-bit random value generated by the app on first run and kept on the device) | The app | Count players without knowing who they are; join one install's events together | Legitimate interest (LGPD art. 7 IX; GDPR 6(1)(f)) |
| 3 | Usage events: app opened or backgrounded, session start, levels started/finished and their outcome, calm-mode sessions, store opened, which product was viewed or bought and the outcome, ad shown/rewarded/skipped/failed, cloud-backup and sign-in steps (success or failure code), app start time, local-storage failure counts. No text you type, no name, no e-mail | The app, sent to PostHog | Understand whether the game works and where players get stuck; improve it | Legitimate interest; you can object by switching analytics off (section 6) |
| 4 | Device and app information that the analytics and crash SDKs may attach automatically, such as app version, operating system and version, device model, language, screen size, and the IP address of the request (used for connection handling and approximate country) | Your device | Make events and crashes comparable and diagnosable | Legitimate interest |
| 5 | Crash and error reports: stack trace, app version/build, device model and OS, a short trail of recent app actions, session start/end | The app, sent to Sentry | Find and fix crashes | Legitimate interest |
| 6 | Cloud backup (only if the build has it and you leave it on): an anonymous Firebase user id, and one small save document (your progress counter and a progress marker, timestamps). Level progress, streaks, settings and purchase records are not uploaded | The app, sent to Google Firebase (Authentication, Firestore) | Keep your progress across reinstalls or a new phone | Performance of the service you asked for (LGPD art. 7 V; GDPR 6(1)(b)) |
| 7 | Optional sign-in to back up with Google (Android) or Apple (iOS): the provider's account identifier and, depending on the provider, your e-mail address, held by Firebase Authentication. We do not read your contacts, name or profile for any other purpose | You, if you choose to link | Let you restore the same save on another device | Your consent (LGPD art. 7 I; GDPR 6(1)(a)), withdrawable by signing out or deleting the account |
| 8 | Ad data (when ads are on): the Google Mobile Ads SDK, run by Google, may process your Android advertising id, IP address, device and app information and ad interaction data to serve and measure ads and prevent fraud. In the EEA/UK, and in some other places, Google's consent form (UMP) is shown first | Your device, to Google AdMob | Show rewarded ads that fund the game | Your consent through the Google consent form where required; otherwise legitimate interest in non-personalised advertising |
| 9 | Purchase data: when you buy, Google Play processes the payment. Our purchase service RevenueCat receives the purchase receipt/token and an anonymous RevenueCat user id, to confirm what you own (for example "ads removed") and to let you restore purchases. We never receive your card, bank or Google Pay details | Google Play, RevenueCat | Deliver and restore what you bought | Performance of the contract (LGPD art. 7 V; GDPR 6(1)(b)); legal obligations for accounting and tax records (LGPD art. 7 II) |
| 10 | Daily reminder: a notification scheduled on your device at the time you choose. No push token is created and nothing is sent to us | You | Remind you to play | Your choice (consent); switch it off in Settings or in system settings |
| 11 | Sharing: if you tap share, the app builds a result card or text on your device and hands it to the sharing sheet you pick. We do not receive it | You | Let you share a result | Your action |
| 12 | Messages you send us (e-mail to the privacy contact or support): your e-mail address and what you write | You | Answer you | Legitimate interest; legal obligation where it applies |
What we do not collect: your name, phone number, contacts, photos, files, microphone, camera, precise location or any health data. The app does not read your device's advertising id itself: only Google's ads SDK does, and only when ads are on. The app has no friends list, chat, user-generated content or public leaderboard in this version. If a feature that shares data between players is added, this policy will be updated before it ships.
Playtest builds distributed to invited testers can keep a gameplay log on the device and let the tester export it by hand. It is not sent automatically and is not in the store build.
4. Who receives data (processors) and where it goes
| Service | What it receives | Role | Where |
|---|---|---|---|
| PostHog | Items 2, 3, 4 | Processor (analytics) | United States (PostHog US cloud, us.i.posthog.com) |
| Sentry | Items 4, 5 | Processor (crash reports) | European Union (Sentry EU region) |
| Google Firebase (Authentication, Firestore) | Items 6, 7 | Processor | United States (Google Cloud multi-region nam5) |
| Google AdMob / Google Mobile Ads, Google UMP | Item 8 | Google acts under its own terms, normally as an independent controller for ads | Google's global infrastructure |
| Google Play (Billing) | Item 9 payment | Independent controller for the payment | |
| RevenueCat | Item 9 | Processor | United States |
| Apple (Sign in with Apple, iOS only) | Item 7 | Independent controller for the sign-in | Apple |
We do not sell personal data. We do not use it for profiling or targeted advertising of individual users.
International transfers (LGPD art. 33; GDPR chapter V). Several of these providers are in or process data in the United States and elsewhere. We rely on the providers' contractual safeguards (data-processing terms and, where applicable, standard contractual clauses).
5. How long we keep it
| Data | Retention |
|---|---|
| On-device data | Until you uninstall the app or clear its data |
| Analytics events and install id (PostHog) | 30 days, then deleted or aggregated; this is the retention the PostHog plan applies, not a window we chose |
| Crash reports (Sentry) | 90 days, Sentry's standard error retention, then deleted |
| Cloud backup (Firebase) | Until you delete it in the app, or until you ask us to. We do not currently delete saves of inactive users automatically |
| Purchase records (Google Play, RevenueCat) | As long as needed to deliver and restore purchases and to meet accounting and tax obligations. Fiscal records in Brazil are commonly kept for five years |
| E-mails you send us | Up to 24 months after the matter is closed |
6. Your choices and rights
In the app (Settings):
- Share anonymous usage data switch. On a fresh install analytics is on until you switch it off. When you switch it off, we stop collecting new events and crash reports, shut the analytics and crash software down for the session, and discard any events still waiting to be sent. An event already on its way at the moment you tap can still arrive.
- Delete my cloud data / Delete my account (shown when cloud backup is available in your build): deletes your save and your Firebase user, signs you out and turns cloud backup off on that device so nothing is re-created. If you linked a Google/Apple sign-in, you may be asked to sign in again to confirm.
- Without the app: the page https://tezzvo.com/games/crush-sort/delete explains how to delete your cloud data, in the app or by e-mail to privacy@tezzvo.com.
- Privacy policy and Your data rows: the policy link, your analytics id and the address for deletion or export requests.
- Daily reminder switch.
- Ads: you choose each rewarded ad; in the EEA/UK and some other regions Google's consent form lets you change your ad choices. You can also reset your advertising id or opt out of ad personalisation in your Android settings.
By e-mail to privacy@tezzvo.com you may ask, as LGPD art. 18 and (in the EEA/UK) GDPR arts. 15-22 provide: confirmation that we process your data; access; correction; anonymisation, blocking or deletion; portability; information about sharing; withdrawal of consent; and objection to processing based on legitimate interest. We confirm within one month of a request (extendable by two months for a complex one, as the law allows).
How we find "your" data: analytics and crash data are tied to a random install id, not to you. Settings > Your data shows that id (while analytics is on) with a copy button; give it to us in your request and we can locate the data. We cannot search by name or e-mail. Switching analytics off forgets the id on your device: events sent earlier stay under the old id, and switching it on again creates a new one. Uninstalling or clearing the app data also creates a new id.
Export: the app has no in-app data export yet (Settings > Your data tells you where to write). On request we can export your cloud save document (a small progress record) by e-mail.
You may also complain to the Brazilian data protection authority (ANPD, www.gov.br/anpd) or, if you are in the EEA/UK, to your local supervisory authority.
7. Consent, in plain words
Analytics and crash reporting follow a three-state switch inside the app:
- Not yet known (the first moments after launch, before the app has read your saved choice): anything the app would report is held in a small buffer in memory and not sent.
- On: the held items are sent, in order, and new ones follow. The analytics and crash software is started only now.
- Off: the held items are thrown away unsent, the analytics and crash software is not started (or is shut down), and its queue of unsent events is deleted.
If the app cannot read your saved choice (for example a storage error), it treats that as off.
8. Ads and purchases
- Rewarded ads only at first. Ads appear only after you tap to watch one in return for a reward. We may later add short full-screen ads between levels, never at the start of a level or on exit; this policy will say so before they ship.
- Non-personalised. Every ad request the game makes asks Google for non-personalised ads only (not based on a profile of your interests) and for content rated G at most. Google may still use limited data (for example IP address and the ad id) for delivery, frequency capping, measurement and fraud prevention.
- Remove ads and any other items are bought through Google Play Billing. Items are not random: you always know what you get before you pay (no loot boxes, no mystery packs). Refunds follow Google Play's policy.
9. Children and minors
Crush Sort is not directed at children: it is not directed to children under 13 (or the applicable age of digital consent in your country, up to 16 in parts of the EEA); the game is meant for players 13 and older and we do not knowingly collect personal data from them. We recognise, however, that a colourful casual game may be played by minors, so we apply the strictest settings we can to everyone: probable access by minors is assumed. That means: rewarded-only, non-personalised ads; no random paid items; no behavioural profiling for advertising; no social features or chat; no collection of name, contacts or location; and no use of reward mechanics to push excessive play.
Brazil's Digital Statute of the Child and Adolescent (ECA Digital, Lei 15.211/2025, in force 2026-03-17) applies to services directed at minors or with probable access by them.
If you are a parent or guardian and believe a child has given us personal data, write to privacy@tezzvo.com and we will delete it.
10. Security
Data in transit to the services above uses HTTPS/TLS. Access to the Firebase project is limited to people who work for TEZZVO. The cloud save is readable and writable only by its own anonymous account (enforced by Firestore Security Rules). No system is perfectly secure; if an incident puts your data at risk we will notify you and the ANPD as the law requires.
11. Changes to this policy
We will post changes at https://tezzvo.com/games/crush-sort/privacy and change the date above. For a material change that affects what we collect we will say so in the app before it applies.
12. Contact
TEZZVO - privacy@tezzvo.com