Sudoku Sensei Privacy Policy
Last updated: 17 November 2026
Sudoku Sensei ("the app") is published by Indhumathi Palanisamy, trading as AppachiTech, Bengaluru, India. Contact: support@appachi.tech.
The short version
- The game itself works fully offline. Your games, progress, ratings and settings are stored only on your device. We don't run servers that receive them, and there are no accounts.
- If you use the free version, the app shows ads provided by Google AdMob. Ads need an internet connection, and AdMob processes some data to serve and measure them (see below). There is no paid ad-free option at present.
- Crash reports and a few usage events (Firebase, also Google) help us fix problems and see what is used. Where the law requires it they only start after you agree, and you can change your mind in Settings → Privacy choices.
What stays on your device
Saved games and move history, your private rating, streaks and calendar, technique progress, and settings. They're stored in the app's private storage and deleted when you uninstall the app. We can't see them.
Advertising (free version)
We use Google AdMob to show ads. To serve, limit and measure ads, AdMob may collect your device's advertising ID (Android advertising ID, or iOS IDFA only if you allow tracking), IP address, approximate location derived from it, and information about how you interact with ads. We need this to show ads and to be paid for them. See Google's policy: https://policies.google.com/technologies/partner-sites
- Consent. In the EU, EEA and UK, and wherever else the law requires it, Google's consent form (UMP) asks you before ads use your data. You can change your answer at any time in Settings → Privacy choices (shown where the form applies to you). On iOS, Apple's App Tracking Transparency prompt also applies; if you decline, ads are not personalised using the IDFA.
- If we offer a paid ad-free option later, buying it will remove ads.
Purchases
The app sells nothing at present. If we offer a purchase later (such as removing ads), Google Play or the Apple App Store will handle it: we will receive only confirmation of the purchase, never payment details.
Crash reports and usage analytics
We use Google Firebase for two things.
- Crash reports (Crashlytics): when the app crashes or hits an error, the crash log (stack trace), device model, OS version, app version and a random installation ID are sent so we can fix it. Why: to keep the app stable.
- Usage analytics (Analytics): only these events, with no screen-by-screen tracking:
- a puzzle was started or completed (puzzle type, difficulty level, whether it was the daily puzzle; on completion also a rough duration range, number of mistakes and hints used);
- a daily puzzle was completed;
- a hint was used (which hint step);
- something was shared (from which place in the app, and what kind).
None of this includes your name, email or puzzle contents, and we don't link it to who you are. Your games stay on your device.
Consent. Where the law requires consent (EU, EEA, UK and similar), none of this is collected until you agree in the consent form. You can withdraw at any time in Settings → Privacy choices; collection then stops. Elsewhere, collection is on by default.
Retention and deletion. Google keeps the data under its own retention settings: Analytics event data is kept for 2 months, and Crashlytics data is kept for 90 days. To ask for your data to be deleted, contact support@appachi.tech with your app-instance ID or advertising ID; uninstalling the app and resetting your advertising ID also stops it being linked to you.
Google acts for us as a processor for this data under its terms: https://firebase.google.com/support/privacy
Children
The app is a general-audience puzzle game and is not directed at children under 13. We don't knowingly collect data from children.
Your choices
- Change ad, analytics and crash-report consent in Settings → Privacy choices (where it applies to you).
- Reset your advertising ID or limit ad tracking in your device settings.
- Delete all app data by uninstalling the app.
Changes
We'll update this page if anything changes and revise the date above.