This privacy policy covers Odak ("the app", "we", "us"), a self-control / commitment tool that helps you limit your own use of apps you choose. It applies to the Android version distributed through Google Play and to the iOS version distributed through the Apple App Store. Where the two platforms differ, the difference is stated explicitly below. Questions or requests can be sent any time to odakapp@ome-marketing.com.
What Odak stores on your device
- The list of apps you chose to lock, and your lock/break settings.
- Your wait-escalation state (how many times you have opened a locked app today).
- App-usage statistics that Odak reads with your permission to show you how long you use your apps, including a per-hour and per-app breakdown that Odak computes entirely on your device. These numbers are shown to you on your device and are not sent anywhere.
- Your Focus programs (scheduled locks), if you set any: each program's times, days and which apps it covers. Stored on your device only.
- A passive "time saved" counter: wall-clock timestamps of when your locks are active, kept in the app's local preferences, used only to show you how much time you've protected.
- A local record of your own activity in Odak (deterrent attempts, breaks, and any skip purchases — including each skip's price and currency, exactly as shown by the store at the time of purchase) used to show you your statistics.
Odak has no servers and no account system. Apart from the private device backup and payment-verification data described below, there is nothing of yours stored anywhere except on your own device, in the app's private storage, which the operating system shields from other apps. We do not run a backend, we do not receive your app data, and we have no crash-reporting or analytics service watching the app in the field — if it crashes for you, we only find out if you tell us.
Device backup and reinstall
If device backup is enabled, your platform may include Odak's safe, durable data in your private device backup: your mountain journey, statistics, locked-app list, Focus programs, settings, and the current day's wait-escalation counter. The operating system controls when a backup runs and whether it is available during reinstall or device transfer; a restore can be delayed, unavailable or older than the data that was on the device when you uninstalled. Odak cannot see, trigger or guarantee it.
Odak deliberately excludes active break/session grants and pending unlock handoffs from backup. A reinstall must never restore a currently open break or a half-completed gate. When a recent backup exists, reinstalling will generally restore your journey and the backed-up same-day escalation state. Without an available backup, Odak starts fresh. This backup improves retention; it does not prevent uninstalling or make the app unbreakable.
What Odak does NOT do
- No login, and no collection of your name, email address or phone number.
- No collection of advertising identifiers or location, and no collection of device identifiers for advertising or tracking. Odak does not track you across apps or websites owned by other companies. A pseudonymous RevenueCat app user ID is used only when you make or restore a purchase, as described in Payments.
- No advertising of any kind.
- No analytics or tracking SDKs, no crash reporting, no behavioural profiling.
- No selling of your data, no sharing of your data, and no use of your data for any purpose other than showing it back to you — Odak does not transmit your app-usage data or your list of locked apps anywhere. There is nowhere for it to go.
- On Android, the optional Accessibility service does not inspect screen text, typed input, controls or descriptions and does not take screenshots or perform actions. Android grants interactive-window capability, which Odak limits in code to foreground package/window identity metadata.
- On Android, if you switch on the optional notification tidying described below, Android hands Odak the full text of notifications from your locked apps. That is how the permission works and no app can ask for less. Odak uses only which app sent it; the words are never saved, never transmitted, and never seen by us.
Permissions Odak uses, and why
Each of these is requested in the app with an explanation before the system shows you the permission dialog, and each is used only for the purpose stated here. Revoking any of them is always possible through system settings and never requires contacting us.
On iOS
- Screen Time / Family Controls authorization: Odak uses Apple's Screen Time APIs (
FamilyControls,ManagedSettings,DeviceActivity) to shield the apps you chose and to show Odak's own block screen when you open one. You grant this explicitly in the system authorization prompt, and can withdraw it at any time in iOS Settings → Screen Time. - What Apple's design means for your privacy: the apps you select are handed to Odak as opaque, privacy-preserving tokens issued by the system, not as a readable list of your installed apps. Activity and shield events are processed on-device by app extensions; none of it is transmitted to us.
- Notifications (optional): to show gentle reminders and to tell you when a break has ended.
On Android
- Usage Access (PACKAGE_USAGE_STATS): to detect when a locked app is opened and to show your usage statistics, including a per-hour and per-app breakdown that Odak computes entirely on your device by walking the system's usage events. Read on-device only; never transmitted. You can revoke it at any time in Android Settings → Special app access → Usage access (Odak's blocking and statistics stop working without it).
- Display over other apps (SYSTEM_ALERT_WINDOW): to show the block screen over a locked app. The overlay is only ever Odak's own block/wait screen — it never covers system navigation or the Settings app, and it carries no ads.
- Notifications (POST_NOTIFICATIONS): to show the ongoing protection notification and gentle reminders.
- Run at startup (RECEIVE_BOOT_COMPLETED): to resume protection after you restart your device. It restarts only Odak's own service.
- Foreground service (special use): to keep enforcement running so the block screen can appear the moment you open a locked app.
- Accessibility service (optional, off by default): Odak offers an optional accessibility service that closes one specific bypass: returning to an already-open locked app through the Recents screen, which the Usage Access permission alone cannot detect reliably. If you choose to enable it in Android Settings → Accessibility, Android grants access to interactive-window information. Odak uses only foreground package/window ID, type, active and focused state. It does not inspect accessibility nodes, screen text, typed input, controls or descriptions; take screenshots; or perform gestures/actions. The information is processed on-device solely to show or hide the lock and is never transmitted. You can turn the service off at any time; Odak then reports reliable protection as inactive. UsageStats may continue for statistics but cannot attach the blocking overlay.
- Notification access (optional, off by default): if you turn this on, Odak quietens notifications from apps you've locked, so a locked app can't buzz you while you're staying out of it. Android hands the full text of every notification to any listener that's turned on — that is how the permission works, and no app can ask for less — but Odak reads only which app posted the notification, to decide whether to dismiss it. Notification text/content is never read, stored or transmitted. Odak's own protection notification, and notifications from a call or navigation, are never touched. You can turn this off at any time in Android Settings → Apps → Special app access → Notification access.
- Internet (INTERNET): required for Google Play billing and RevenueCat's payment-verification SDK. When you make or restore a purchase, the SDK sends a purchase token and pseudonymous app user ID to RevenueCat to verify that entitlement. Nothing in "What Odak stores on your device" — including your locked-app list and app-usage data — is transmitted.
Payments
If you choose to pay to skip a wait, the payment is processed by the platform's own store (Apple App Store or Google Play) under its own terms and privacy policy. Odak never sees or stores your card details, billing address or store account information; it records the completed skip only in your local statistics, together with its price and currency exactly as shown by the store at the time of purchase. That record — like the rest of your statistics — stays on your device and is never transmitted.
The skip fee is flat: it does not rise with repeated use. Odak never hardcodes a price — it displays the store's own localized price string, so what you are shown is what the store charges.
If you purchase or restore Odak Premium — an optional auto-renewing subscription that adds extra features on top of the free core, and never weakens the lock or creates a free bypass — the store processes the payment and RevenueCat acts as our payment-verification processor. RevenueCat receives the store purchase token and a pseudonymous app user ID so it can tell Odak whether the premium entitlement is active. RevenueCat does not receive your locked-app list, usage statistics, contacts, messages, location or payment-card details. We do not use this information for advertising, profiling or tracking. RevenueCat's handling of this processor data is also governed by its privacy policy. You can manage or cancel a subscription at any time in your store account settings.
Other than the platform stores for purchases and RevenueCat for entitlement verification, Odak shares data with no third parties, embeds no analytics or advertising SDKs, and has no parent, subsidiary or partner with access to your app-usage data.
Honesty about blocking
Odak is a commitment aid, not an unbreakable lock. Because it runs as a normal app, blocking depends on the operating system and can be bypassed (for example by force-stopping, restarting, or uninstalling Odak, or by withdrawing its permissions). We do not prevent you from removing the app or changing its permissions through normal system settings, and we never will — that is your device, not ours.
If you reinstall Odak, the system may restore your backed-up journey and same-day wait-escalation state as described above. Because device backup is controlled by the operating system and is not guaranteed to be current or available, reinstalling can still produce an older counter or a fresh start. Completely preventing that would require a separate server-side anti-circumvention system, which Odak does not operate.
Data security
Your locked-app, usage and settings data is protected in the app's private storage area, which the operating system isolates from other apps. If device backup is enabled, selected durable data may also be held in your own private device backup and protected under the platform's backup security and privacy practices. Purchase verification is sent over the network to the platform store and to RevenueCat; those providers apply their own security and privacy practices to that data.
Data retention and deletion
Uninstalling Odak immediately deletes the app and its local private storage from that device. If device backup is enabled, selected durable data may remain in your private device backup and may be restored later. You control that backup through your Apple or Google account backup settings; Odak cannot inspect or delete it for you. There is no Odak-operated server copy or Odak account to close. Your purchase history with the app store is held by the store under its own policy. RevenueCat's purchase-verification data is retained under RevenueCat's privacy policy; contact us at the address below if you need help exercising a privacy right concerning that processing.
Your privacy rights (GDPR, KVKK, CCPA and others)
Privacy laws such as the EU/UK GDPR, Turkey's KVKK, and the California CCPA/CPRA give you rights over personal data an organisation holds about you — access, correction, deletion, portability, objection, and the right to withdraw consent. Odak's local data can be deleted by uninstalling the app and permissions can be revoked in system settings; any remaining device backup is managed through your Apple or Google account backup settings. For payment-verification data processed by RevenueCat, contact us at the address below and we will assist with your request. We do not sell personal information or share it for cross-context behavioural advertising as those terms are defined in the CCPA/CPRA, and we make no automated decisions about you. If you believe we hold any data about you, or have any privacy question or complaint, email odakapp@ome-marketing.com and we will respond; you also have the right to complain to your local data-protection authority.
Children
Odak is a self-control tool intended for adults and is not directed at children under 13 (or the equivalent minimum age in your country). We do not knowingly collect personal information from anyone, children included — the app has no means of collecting it apart from the payment-verification data generated if a purchase is made.
Changes to this policy
If we change how Odak handles data (for example, if a future version adds any network feature), we will update this policy, move the "Last updated" date at the top, and update the Google Play Data Safety section and the Apple privacy label before that version ships. A version of the app described by this policy will never silently start collecting data.
Contact
Odak's developer can be reached at odakapp@ome-marketing.com.
Publisher: OME Marketing.