Privacy Policy

OvTracker, developed by Inidam Leader

Overview

OvTracker is an ad-supported ovulation and menstrual-cycle tracking app. This policy describes data that the app processes, why it is used, and the choices available to you. OvTracker does not sell the cycle information that you enter.

Account information and sign-in

You can use OvTracker without an account. If you choose to sign in, the app offers Email/Password sign-in and Google Sign-In through Firebase Authentication. Depending on the selected provider, Firebase Authentication and the app process your Firebase user ID, email address, display name, and profile-photo URL when those values are available.

The app stores the available display name, email address, and profile-photo URL in local app preferences and in the signed-in user's Firebase Firestore profile document. The profile-photo URL may be used to load and display the account picture in the app. These details identify the account and support sign-in, backup, restoration, and synchronization across devices.

Cycle and reproductive information

OvTracker stores cycle start dates, cycle length, period length, optional day notes, and counts of protected and unprotected intercourse that you choose to record. It calculates estimated period, fertile-window, and ovulation dates from that information. The app does not collect precise location and does not request location permissions.

Cycle information is stored locally in the app's Room database. It remains on the device unless you sign in and use the cloud backup/synchronization features. For a signed-in account, the app stores cycle data in that account's Firebase Firestore cycles document. Sign-in can create the initial cloud backup, and later backups can update it.

OvTracker does not send cycle entries, notes, intercourse counts, or derived cycle timing to advertising SDKs or Firebase Analytics. Cycle data is sent to Firebase Firestore only when you sign in and use cloud backup/synchronization.

Feedback you choose to send

If you submit feedback, the app sends the feedback text, submission date, device locale, whether you are signed in, and an email address when one is supplied. This is stored in a separate Firebase Firestore feedbacks collection so that we can read and respond to feedback and improve OvTracker. Feedback is not automatically deleted when an account is deleted.

Technical, analytics, crash, consent, and advertising data

OvTracker uses Firebase Remote Config at startup to obtain app configuration, including ad-network waterfall settings. Remote Config and Firebase Installations process technical configuration information such as country code, language, time zone, platform and OS version, application/version identifiers, and a Firebase installation ID as described in Firebase documentation.

Firebase Analytics and Firebase Crashlytics are disabled by default in the Android manifest. After the Google User Messaging Platform (UMP) consent flow, the app enables or keeps them disabled according to the resolved analytics-storage consent. Where enabled, Analytics records non-health app events such as sign-in, backup, account deletion, ratings, sharing, biometric-setting enablement, and feedback-flow choices. Crashlytics receives crash reports, non-fatal exceptions, stack traces, technical device/app context, and fixed diagnostic labels identifying the source file and function.

The app requests ads only after UMP reports that ads may be requested. It can load banner and native ads using Google Mobile Ads/AdMob, AppLovin MAX, and Meta Audience Network. The app also includes Vungle/Liftoff mediation adapters; whether they serve an ad in a particular session depends on the live mediation configuration. Advertising providers may process IP-derived approximate location, advertising and app/device identifiers, ad and app interactions, and diagnostic information to provide, measure, secure, and personalize or limit advertising according to consent, regional rules, and provider configuration.

UMP provides a Privacy & Consent option when Google requires one. Consent affects Analytics and Crashlytics collection and provides consent signals to advertising providers; it does not mean that all advertising-related technical processing stops when ads are eligible for limited or non-personalized delivery.

Service providers

OvTracker uses these providers for the purposes described above:

These providers have their own terms and privacy documentation. Their processing can vary by provider, region, device, consent status, and live advertising configuration.

Storage and security

Local cycle data is stored in the app's local database. This version of OvTracker does not add application-level encryption to that local database. Firebase and Google Mobile Ads document TLS encryption for their SDK traffic; other providers protect traffic according to their own SDK and service documentation. No transmission or storage method can be guaranteed completely secure.

Account and data deletion

You can request deletion of your account and its associated cloud profile and cycle documents in the app or on the OvTracker account-management page. Sign in, then choose Delete account and associated cloud data. Recent sign-in may be required before Firebase can complete the request.

When the request completes, OvTracker deletes the Firebase Authentication account and the Firestore users and cycles documents for that account. The action does not erase local data already stored on a device; remove that data by clearing OvTracker's app storage or uninstalling the app from that device.

Account deletion deletes the account and its associated cloud data, but OvTracker does not currently provide a separate data-deletion request mechanism that lets you keep the account while requesting deletion of some or all data. Separately stored feedback is not automatically deleted by account deletion. For support questions, contact gladiatorkilo@gmail.com.

Children's privacy

OvTracker is not intended for children under 13. We do not knowingly collect personal information from children under 13.

Changes to this policy

We may update this Privacy Policy from time to time. Changes take effect when posted on this page.