P 3 R 1 I 1 V 4 A 1 C 3 Y 4

What we collect

What Tile Crack holds about you depends on whether you've signed up. As a guest you give us essentially nothing. With an account we store the basics needed to authenticate you, sync your preferences, and manage your subscription.

When you sign up for an account

• Sign-in identity — email and password, or your Google / Facebook OAuth identifier.
• Profile — display name, optional phone number, optional avatar image, account creation date, last sign-in timestamp.
• Synced preferences — your chosen dictionary, theme, and other app settings tied to your profile.
• Saved progress — anything Tile Crack syncs to your user ID (for example, favourite words and lookups across devices).

When you subscribe to Premium

• Subscription status — whether you have an active Premium entitlement, managed for us by RevenueCat. We never see your card number; Apple and Google handle that.
• Receipt identifiers — the App Store / Play Store transaction identifiers needed to validate the purchase.

On your device only

• Search history, racks, recent words. Stored locally in the app's sandbox. Not sent to our servers unless you have an account that syncs them.
• Offline dictionary files. Bundled with the app or downloaded once. Lookups never leave the device.

Collected automatically

• Crash diagnostics from Expo / Apple / Google, when you've left system-level crash reporting on. These are anonymised before they reach us.
• Aggregate install counts from the App Store and Play Store dashboards — supplied by Apple and Google, not collected by us, and not tied to you personally.
• Advertising identifiers in the free tier, used by Google AdMob to show ads (see Ads & advertising IDs below).

How we use it

We use the data above strictly to run the service:

1. Authenticating you — verifying your email/OAuth identity so the right profile loads on the right device.
2. Syncing your preferences and progress across the devices you sign in on.
3. Managing your subscription — checking your Premium entitlement with RevenueCat so the right features unlock and ads turn off.
4. Showing ads to free-tier users via Google AdMob.
5. Fixing crashes when an anonymised report from your device tells us a screen broke.
6. Responding to support requests you send to impelatek.apps@gmail.com.

We do not profile you, build behavioural models, or sell access to your data.

Ads & advertising IDs

Tile Crack's free tier shows ads served by Google AdMob. Subscribing to Premium removes all ads — once your Premium entitlement is active, the ad SDK is not asked to load anything.

What AdMob receives

• On iOS, your App Tracking Transparency choice controls whether the IDFA can be shared. We respect your choice.
• On Android, AdMob uses the Advertising ID, which you can reset or limit from your device settings.
• Approximate technical context — device model, OS version, screen size, coarse locale — needed to render a suitable ad.

Turning ads off

• Subscribe to Premium — the cleanest opt-out. No ad SDK requests are made.
• iOS: Settings → Privacy & Security → Tracking → toggle Tile Crack off, and/or Settings → Privacy & Security → Apple Advertising → turn off Personalised Ads.
• Android: Settings → Google → Ads → Delete advertising ID (or opt out of personalisation).

Who we share with

We rely on a small set of processors to actually run the app. We have data-processing agreements with each of them, and we share with no one else.

We do not sell, rent, license, or otherwise share your data with advertisers, data brokers, or affiliates beyond what is strictly necessary to run the service.

Storage & retention

Your profile and synced preferences live in our Supabase project. Avatar files live in a Supabase storage bucket. Subscription receipts and entitlement state live with RevenueCat and the relevant app store.

How long we keep things

• Profile, preferences, avatar, saved progress — kept while your account is active; removed when you tap Delete Account.
• Subscription receipts — kept as long as required by Apple, Google, and our accounting obligations.
• Crash reports — stripped of identifiers and kept for 90 days.
• Support emails — kept for the lifetime of the conversation, plus 12 months.
• On-device data — lives on your phone until you uninstall the app or clear its storage.

Your rights & controls

Under the GDPR, the UK GDPR, the CCPA, and other modern privacy laws, you have the right to access, correct, and delete the personal data we hold about you. Most of these you can exercise directly inside the app.

• Delete your account. Profile → Delete Account. See the How to delete your account page for the full walkthrough.
• Edit your profile. Update display name, phone and avatar from the Profile screen.
• Cancel Premium. Cancel through the App Store or Play Store at any time.
• Request a copy of your data by emailing impelatek.apps@gmail.com with subject Data request.
• Object to a specific kind of processing by emailing us — we will explain what we can and can't do.

Children's privacy

Tile Crack is rated suitable for ages 4+ on the App Store and Everyone on Google Play, but accounts and Premium subscriptions are not aimed at children. We do not knowingly collect personal data from children under the age required by your local law (13 in the US, 16 in much of the EU). If you believe a child has created an account, contact us and we will delete it.

International data transfers

Our processors operate in multiple regions, including the EU and the US. Where data leaves your region we rely on the legal mechanisms our processors provide (for example, the EU Standard Contractual Clauses for transfers out of the EEA, and Apple's and Google's own transfer frameworks).

Changes to this policy

When this policy changes in any meaningful way, we will update the effective date at the top of this page and surface a short summary in the app. Material changes (new processors, new categories of data) will require you to re-acknowledge before continuing.

Contact

A real person reads every message and aims to reply within two business days. For data-deletion requests, please put Data request in the subject so it routes to the right queue.