The app
Intertakt is an interval-training cue app for Android: it plays timed audio cues over your own music so you can train without watching a screen. It is offline-first — every feature (plans, sessions, your music, settings) works without any network connection, and all app data is stored only on your device. No account is required to install, use, or unlock premium features.
Nothing is collected before you agree
On first launch the app shows a consent dialog: “Help make Intertakt better: allow anonymous usage statistics and automatic crash reports. No account and no personal data. You can change your choice in Settings at any time.”
Until you explicitly tap Send, the app collects and sends nothing, and performs no network requests at all. This is guaranteed by the app’s architecture, not just by good behavior: the analytics and crash-reporting components are only initialized after consent is granted, and a build compiled without the developer’s project keys cannot transmit anything even if consent is given. If you tap Don’t send, the refusal is remembered and the question is never asked again — though you can change your choice in Settings at any time.
What is sent if you consent
With your consent, the app sends exactly two kinds of data:
- Anonymous usage statistics — the complete inventory of 11 event types below, nothing more.
- Automatic crash reports — sent by the crash reporter only when the app crashes; it deliberately runs with session tracking, performance tracing, and default personal-data collection disabled.
The complete event inventory (11 events)
| Event | Meaning |
|---|
session_started | a training session began |
preset_selected | you picked a preset training plan |
session_completed | a session finished naturally (carries the planned and missed cue counts) |
cue_missed | a cue was missed during a session |
session_resumed_after_interruption | you accepted the restore offer after an interruption |
paywall_viewed | the premium paywall was opened |
purchase_started | you tapped Buy (carries the product identifier) |
purchase_completed | a purchase granted premium (carries the product identifier) |
purchase_failed | an error ended the purchase flow (carries the product identifier and a masked, stable error code) |
purchase_canceled | you closed the store sheet without buying (carries the product identifier) |
restore_completed | a restore re-granted premium (carries the product identifier) |
Event properties carry only counts, sources, product identifiers (such as productId), and masked stable error codes — never names, contacts, or anything else identifying you. Each event also carries a timestamp of when it occurred on your device.
Who processes the data (the complete list)
Exactly three parties are ever involved, and only the first two receive any telemetry:
- PostHog (analytics) — the app uses the developer’s own minimal PostHog capture client, hosted in the United States, reached only over HTTPS. It receives the usage-statistics events above.
- Sentry (crash reports) — the official Sentry service receives automatic crash reports only, from the crash-reporting component described above.
- Google Play Billing (purchases) — if you buy premium, the payment is processed by Google under Google’s own privacy policy for Google Play purchases. The app itself only learns a local premium entitlement (granted or not) and never sees your payment credentials.
There are no other processors, no advertising SDKs, and no analytics or ad networks beyond the list above.
The anonymous device identifier
Analytics events are tied to an anonymous identifier: a random UUID generated locally on your device (one per installation, created when you first grant consent). It is not derived from any personal data, is not based on your Google account, phone number, or device serial, and contains no personal data. It exists only to distinguish one installation from another in aggregate statistics.
Encryption
All telemetry is transmitted over HTTPS (TLS). Data stored by the app itself never leaves your device.
No selling, no sharing
Your data is never sold. It is never shared with third parties beyond the processors named above, and those processors act only on the developer’s instructions as service providers — they do not use the data for their own purposes such as advertising.
Changing your mind
You can change your choice in Settings at any time (Settings → Privacy → Anonymous statistics). Turning it off stops all collection immediately: the analytics and crash-reporting components are shut down and any not-yet-sent queued events are dropped. Because there is no account, there is no account-deletion surface; if you want data already delivered to the processors deleted, contact the developer (below), who can request deletion in the PostHog and Sentry projects.
Retention
How long delivered statistics and crash reports are kept is configured in the developer’s PostHog and Sentry project settings.
Final values (verified 2026-09-15 from the plan defaults): anonymous analytics events are kept for
1 year (PostHog Cloud, free plan default); crash reports are kept for
30 days (Sentry, Developer plan default). Requesting deletion removes them sooner —
see the data-deletion page.
Children
The app is a general-audience sports tool, is not directed at children, and requires no account — so it collects nothing from children that it does not collect from anyone else: nothing at all without consent, and only the anonymous data described above with it.
Changes to this policy
If the app’s data practices ever change, this policy will be updated and the “Last updated” date above will change with it. The event inventory is deliberately pinned: an automated check compares this policy against the app’s actual code on every release, so the two cannot silently drift apart.