Controller and scope
JeoKod is provided by Melihcan Günbay (Bariton). This policy covers the JeoKod iOS and Android apps and the jeokod.bariton.dev website. JeoKod does not create accounts and does not ask for your name, email address, or date of birth.
Information stored on your device
Your selected age group, detailed learning progress, answers and statistics, favourites, sound/haptic/notification preferences, iOS tracking-permission status, and Premium-access status are stored on your device. JeoKod has no user-account server or cross-device sync service.
These local records are not transferred in full to third parties. The limited measurement events described below may include an app launch, the identifier of a completed lesson, an ad impression, and a Premium purchase or restoration status.
Age group and iOS tracking permission
JeoKod does not request a birth date. It asks only whether the user is “12 or under” or “13 or older” to select the appropriate data and advertising behaviour. Changing this choice later does not erase learning progress.
When “12 or under” is selected, Firebase Analytics, Firebase Crashlytics, and Meta App Events remain disabled, and the iOS App Tracking Transparency (ATT) prompt is not shown. Google Mobile Ads and Google UMP receive child-directed/under-age-of-consent signals, ad content is limited to a general-audience rating, and personalised advertising and cross-app tracking are disabled.
iOS users who select “13 or older” are shown the ATT prompt. If permission is denied, Meta App Events and advertising-identifier collection remain disabled. Contextual or non-personalised ads permitted by Google UMP may still be shown. If permission is granted, the advertising identifier may be used for ad personalisation and measurement. Android does not use ATT; the age choice, Google UMP choices, and platform permissions apply.
Firebase Analytics and Firebase Crashlytics
Firebase Analytics is enabled only when “13 or older” is selected and the app is a Release build. It may measure app launches, completed lesson identifiers, interstitial ad impressions, and Premium purchase or restoration events, including product identifier, price, and currency when available. JeoKod does not send Firebase a name, email address, or a developer-created user ID.
Firebase Crashlytics is enabled only for users who select “13 or older” in Release builds. Crash reports may include the app and operating-system version, device model, crash details, and diagnostic information needed to investigate failures. JeoKod’s Analytics, Crashlytics, and Meta measurement service does not run in Debug or Profile test packages.
Meta App Events
Meta App Events is enabled only for users who select “13 or older” on Android and, on iOS, only when ATT permission is also granted. Automatic event logging and advertising-identifier collection start disabled and the required feature is enabled only when these conditions are met.
Meta may receive app activation, completed lesson, ad impression, and Premium purchase or restoration events. A purchase event may include product identifier, price, and currency. This information may be used for analytics, advertising-campaign measurement, and attribution. The Meta SDK may also process a device identifier, limited technical/diagnostic data, and technical information that its privacy manifest categorises as “Other Data Types.”
Google Mobile Ads and Google UMP
Users without Premium access may be shown interstitial ads at appropriate transitions through Google Mobile Ads. When Premium becomes active, new ad requests stop and any loaded ad is disposed of. Google User Messaging Platform (UMP) manages consent information and privacy options where required; the advertising SDK is not initialised unless UMP allows ad requests.
Google’s advertising and consent SDKs may process a device identifier, approximate location inferred from an IP address, advertising and product interaction, performance, crash, and other diagnostic data for ad delivery, frequency management, consent, security, and measurement. JeoKod does not request precise-location permission. On iOS, access to the advertising identifier depends on ATT status; personalisation also depends on ATT, UMP choices, and applicable rules.
Notifications and device permissions
If you enable reminders, JeoKod asks for local-notification permission. Your chosen time, notification status, and device time zone are used to schedule reminders on your device. On Android, restart permission may be used to restore reminders after the device restarts. Notification content is not sent from a server.
In-app purchases
When you purchase Premium access, payment, store-account information, and transaction verification are processed by the Apple App Store or Google Play. JeoKod may receive product, transaction, and verification status to display, complete, or restore a purchase. It cannot access your payment-card details and does not send the store verification receipt to a JeoKod server.
Premium-access status is stored on your device. If the age and permission conditions described above allow measurement, product identifier, purchase or restoration type, price, and currency may be sent to Firebase Analytics and Meta App Events. Retention or deletion of store purchase history is governed by Apple’s or Google’s policies and legal obligations.
Website and technical logs
The JeoKod website does not create accounts, serve ads, or use marketing analytics. The hosting provider may temporarily process standard technical logs such as IP address, browser type, request time, and error details to secure, troubleshoot, and operate the service.
Data security
Local app data is kept in the operating system’s application area assigned to JeoKod and protected by the device’s access controls. Store purchases are handled through Apple or Google infrastructure; web and support connections are protected with HTTPS/TLS where applicable.
Support correspondence is accessed only to respond to support and privacy requests. Because no electronic storage or transmission method can guarantee absolute security, reasonable technical and organisational safeguards appropriate to the nature of the information are used.
Retention, deletion, and your choices
Local information remains on your device until you reset the relevant statistics or preferences in the app, or uninstall it. You can disable reminders in the app or device settings, reopen UMP advertising privacy options where required, and change iOS tracking permission in device settings. JeoKod does not create an account, so there is no JeoKod account to delete.
Measurement and diagnostic data already sent to third-party services is subject to each provider’s retention and deletion rules. Store purchase history is not removed by uninstalling the app. To request access, correction, or deletion regarding support correspondence that JeoKod may hold, contact support@bariton.dev.
Children’s privacy
JeoKod does not request a name, email address, birth date, or account information. When “12 or under” is selected, Analytics, Crashlytics, Meta App Events, personalised advertising, and cross-app tracking remain disabled. Google advertising and consent SDKs may process only the information necessary for ad delivery, consent, security, and limited technical measurement under child-directed/under-age configuration. A parent or guardian may contact us with a privacy concern.
Service providers and store rules
JeoKod uses Firebase Analytics, Firebase Crashlytics, Google Mobile Ads, Google UMP, and Meta App Events within the limits described above. Processing on those providers’ infrastructure is governed by Google’s Privacy Policy, Firebase Privacy and Security information, and Meta’s Privacy Policy.
Distribution and purchase processing are also governed by Apple’s Privacy Policy, Apple App Review Guidelines — Privacy, and the Google Play User Data policy.
Changes
If JeoKod’s data practices change, this policy and its “Last updated” date will be revised. Material changes will be communicated in the app or on this page.