Privacy Policy for Thumka

TL;DR

Thumka does not ask you to create an account, does not collect your name, email, or any other personal information, and never sends the list of apps you choose to block off your device. The only data that leaves your phone is fully anonymous product analytics (bucketed counts, no identifiers that can be traced to you) and, if you tap "Send feedback," whatever you voluntarily type into the feedback form.

Who we are

Thumka is an iOS app that helps you spend less time on apps by requiring a short movement ("dance to unlock") before a chosen set of apps becomes usable for a grace period. This privacy policy applies to the Thumka app published on the Apple App Store.

Data we do NOT collect

We want to be explicit about what Thumka does NOT collect, because the short version matters more than the long one:

• We do not ask for your name, email, phone number, or any account.
• We do not access your location (no GPS, no Wi-Fi scanning).
• We do not access your contacts, photos, camera, microphone, or health data.
• We do not use IDFA (Apple's advertising identifier).
• We do not track you across other apps or websites.
• We do not sell data to anyone.
• We do not store, transmit, or log the list of apps and categories you have chosen to block. That selection is held in an encrypted token blob provided by Apple's Family Controls framework and stays on your device.
• We do not store or transmit raw motion-sensor data. The "dance to unlock" detector reads the gyroscope and accelerometer in memory at 30 Hz while the unlock screen is open and discards the data as soon as the screen closes. Nothing is written to disk, and nothing is sent anywhere.

Data we do collect

1. Anonymous product analytics

Thumka sends anonymous usage events to a third-party analytics provider so we can understand which features are used, find bugs, and decide what to build next. Events are tied to an anonymous per-install identifier — we never attach your name, email, device ID, IDFA, or IP-based profile.

Events contain only coarse, bucketed information (such as app version, iOS major version, device class, install cohort week, and usage counts expressed as ranges like "5-19" rather than exact numbers) so no individual user can be fingerprinted.

2. Feedback (only when you submit it)

If you tap "Send feedback" inside the app, Thumka submits an anonymous form to a public Google Form with your star rating (1 to 5) and the optional message you typed. No user ID, no email, no device information is attached. The submission is handled by Google Forms and stored in the form's response sheet, which only the developer can read.

3. Purchases (Apple StoreKit)

If you ever purchase the optional Thumka Pro upgrade, the transaction is handled entirely by Apple's StoreKit. Thumka has no server of its own — Pro entitlement is verified directly against Apple on your device. Thumka does not receive your payment details, Apple ID, or email. (Note: as of this policy's date, the Pro tier is not sold in the App Store.)

Data stored only on your device

The following information is saved locally on your iPhone or iPad (using Apple's standard UserDefaults and App Group storage) and is never transmitted anywhere:

• Your unlock streak, lifetime unlock count, and daily unlock count.
• The grace-period duration you configured (for example, 30 minutes).
• The encrypted token blob representing which apps and categories you chose to block (from Apple's FamilyActivitySelection — Thumka itself never sees the underlying app list in plain text).
• Per-day and per-hour unlock time used to render the charts in the app.
• Your last-seen dance video name and various onboarding flags.

Uninstalling Thumka removes all of this.

Permissions and why we ask

Thumka requests two iOS permissions. Both are optional in the sense that you can deny them, though the core feature of the app requires Screen Time authorization.

• Motion & Fitness — used by the "dance to unlock" screen to read the gyroscope and accelerometer. As stated above, the data is processed in memory and never written or uploaded.
• Screen Time (Family Controls) — required for Thumka to actually block the apps you select. The heavy lifting is performed by Apple's system frameworks; Thumka only stores the opaque selection token.

Thumka never asks for: camera, microphone, location, contacts, photos, Bluetooth, or HealthKit.

Third parties with whom data is shared

Thumka shares limited data with a small number of third-party services. There are no advertising SDKs, attribution SDKs, or data brokers.

• An analytics provider — receives the anonymous, bucketed events described above.
• Google (Forms) — receives your star rating and optional message when you explicitly submit feedback. Privacy policy.
• Apple — receives purchase transactions (via StoreKit) and enforces app shielding (via Family Controls). Privacy policy.

Data retention

• Local data persists on your device until you delete the app, or reset your device.
• Analytics events are retained on the analytics provider's servers according to its default retention settings.
• Feedback submissions live in a Google Forms response sheet that only the developer can read; they will be cleared periodically.

Children

Thumka is a general-audience productivity app. It is not directed to children under 13, it does not contain kid-targeted content, and we do not knowingly collect information from children.

Your rights

Because Thumka does not collect personal information — no account, no email, no name, no persistent device identifier — there is no user-specific record to access, correct, export, or delete on request. The effective way to remove everything is to delete the app, which wipes all on-device data. The analytics events we send are anonymous and bucketed, and cannot be traced back to a specific person.

International users

If you are located outside the United States, note that the anonymous analytics events and any feedback you submit may be processed on servers in the United States and other countries. By using Thumka, you understand that this transfer takes place. Because no personal data is collected, GDPR and CCPA obligations around access, portability, and erasure are not triggered — there is simply no personal data to act on.

Changes to this policy

If this policy ever changes in a material way, the effective date at the top will be bumped and the app's release notes will call out the change.

Questions or concerns

Use the same feedback form the app uses — it reaches us directly. Submissions are anonymous. Rate one star and tell us what's wrong, or five stars and tell us what we should build next.