Privacy Policy for CallMeReminder

Effective Date: 2026-05-14
Service Provider: KODE.V (kode.v.tk@gmail.com)

This privacy policy applies to the CallMeReminder app (hereby referred to as "Application") for mobile devices that was created by KODE.V (hereby referred to as "Service Provider") as a Freemium service. This service is intended for use "AS IS".

What information does the Application obtain and how is it used?

The Application is designed to prioritize your privacy. It does not collect, transmit, or store personally identifiable information on any external servers. Registration is not required to use the Application.

However, the Application requires access to certain sensitive device capabilities to provide its core features. Your voice recordings and contacts remain strictly on your local device and are never uploaded. The Application does transmit limited non-personal data off-device for analytics, crash reporting, and, if you purchase Pro, for purchase verification — see Sections 3–5 below.

1. Microphone Access (`RECORD_AUDIO`)

Why it is needed: The Application requests microphone access so you can record custom voice memos to play during a scheduled fake call.
How data is handled: All audio recordings are saved locally on your device. The Service Provider does not collect, listen to, or upload your voice recordings to any servers.

2. Contacts Access (`READ_CONTACTS`)

Why it is needed: The Application requests access to your contacts so you can quickly pick a real caller name and phone number to display during a simulated incoming call.
How data is handled: The contact data you select is read locally and used exclusively to populate the caller ID screen. Your contacts are never transmitted, shared, or uploaded to the Service Provider or any third parties.

3. Firebase Analytics (App Interactions)

Why it is used: The Application uses Firebase Analytics (a service provided by Google LLC) to understand how users interact with the app. This helps the Service Provider identify which features are most useful, measure onboarding completion, and improve the overall experience.
What is collected:
- Anonymous app interaction events, such as: completing onboarding, creating or deleting a reminder, reaching the free tier limit, opening the upgrade screen, and completing a purchase.
- A randomly generated Firebase Analytics App Instance ID — this is not linked to any personal identity or account.
- Standard device and session metadata provided automatically by the Firebase SDK: OS version, device model, app version, country/region (derived from IP address, not stored), and session duration.
What is NOT collected: Your name, email, phone number, voice recordings, contacts, reminder titles, caller names, or any other personally identifiable information. No PII is ever included in event parameters.
How data is handled: Analytics data is encrypted in transit (HTTPS) and sent to Google Firebase servers. Google Firebase acts as a data subprocessor on behalf of the Service Provider and does not use this data for its own advertising purposes. Data is retained as configured in the Firebase console (default: 14 months).
How to opt out: You may stop all data collection by uninstalling the Application.

4. Crash Reporting (Firebase Crashlytics)

Why it is used: The Application uses Firebase Crashlytics (a service provided by Google LLC) to automatically collect anonymous crash reports. This helps the Service Provider identify, diagnose, and fix stability issues.
What is collected automatically:
- Stack traces at the time of a crash
- Relevant application state (e.g. which screen was active)
- Device metadata: OS version, device model, manufacturer, available memory (point-in-time snapshot)
- A randomly generated Crashlytics Installation UUID and the RevenueCat anonymous app user ID — neither is linked to any personal identity, account, name, or email address. The RevenueCat ID is used solely to correlate a crash report with a user's Pro entitlement status for debugging purposes.
- Non-personal custom diagnostic keys, such as whether the Pro upgrade is active and the number of reminders scheduled.
What is NOT collected: Your name, email, phone number, voice recordings, contacts, or any personally identifiable information.
How data is handled: Crash data is encrypted in transit (HTTPS) and sent to Google Firebase servers. Google Firebase acts as a data subprocessor on behalf of the Service Provider and does not use this data for its own advertising or marketing purposes. Data is retained as configured in the Firebase console.
How to opt out: You may stop all data collection by uninstalling the Application.

5. In-App Purchases — RevenueCat

Why it is used: If you choose to purchase the Pro upgrade, the Application uses RevenueCat (a purchase management service provided by RevenueCat Inc.) to process and verify your Pro entitlement via Google Play.
What is collected: RevenueCat collects your purchase history — specifically transaction identifiers and entitlement status from Google Play. Per RevenueCat's own data safety guidance, this is classified as Financial Info: Purchase History under Google Play's Data Safety program. This data is used solely for verifying your Pro entitlement (App functionality) and aggregate analytics on behalf of the Service Provider. RevenueCat may also collect a device identifier (Google Advertising ID) for purchase attribution — this is not linked to your name, email, or any personal identity.
What is NOT collected: RevenueCat does not collect your name, email address, contacts, voice recordings, location, crash logs, or any other personally identifiable information. The Service Provider does not pass any such information to RevenueCat.
How data is handled: Purchase history is encrypted in transit (HTTPS) and retained on RevenueCat's servers. RevenueCat acts as a data subprocessor on behalf of the Service Provider. This data is not processed ephemerally — it is stored to maintain your entitlement across reinstalls and devices.
Who is affected: Purchase history processing occurs only if you actively make a Pro purchase via Google Play. Free-tier users generate no data with RevenueCat.
Data deletion: To request deletion of your RevenueCat customer record, contact the Service Provider at kode.v.tk@gmail.com. See the RevenueCat Privacy Policy for further details.

6. On-Device Machine Learning (ML Kit & Language Model)

Why it is used: The Application uses Google ML Kit Entity Extraction and an on-device language model (ONNX Runtime) to understand your voice commands. When you speak a reminder (e.g., "Call me in 10 minutes from Mom"), these on-device models parse the date, time, and contact name from your speech without sending anything to a server.
How data is handled: All ML processing — entity extraction, text embedding, and contact matching — is performed entirely on your device. No voice audio, transcribed text, extracted dates/times, contact names, or embedding data is ever transmitted to Google, Microsoft, or any third party. The ML models and vocabulary files are bundled with the Application and run locally.
What is NOT collected: Your voice input, transcriptions, extracted entities, contact data, or any derived ML features are never collected, transmitted, or stored off-device by the Service Provider.

7. Play Integrity Verification

Why it is used: The Application uses Google's Play Integrity API to verify that the app is running on a genuine, unmodified device and that the installation came from the official Google Play Store. This helps prevent fraud, piracy, and unauthorized use of Pro features.
What is collected: At app startup and during purchase attempts, an anonymous integrity token (a cryptographically signed attestation from Google Play Services) is transmitted to a verification server hosted by the Service Provider at play-integrity-worker.kodev.workers.dev. This token contains device-level signals (such as whether the device has a locked bootloader and whether the app was installed from the Play Store) but contains no personal information — no name, email, phone number, contacts, voice recordings, or location data.
How data is handled: The integrity token is encrypted in transit (HTTPS), verified by the Service Provider's server, and immediately discarded. No integrity tokens or derived signals are retained or logged. The verification server is hosted on Cloudflare Workers and does not store any persistent data.
What is NOT collected: The verification server does not collect your IP address, device identifiers, or any other personal information beyond the ephemeral integrity token.

Does the Application collect precise real-time location information of the device?

No. This Application does not collect precise or approximate information about the location of your mobile device.

Do third parties see and/or have access to information obtained by the Application?

Your contacts and voice recordings are never transmitted off-device and are not shared with any third parties.

The Application uses the following third-party subprocessors:

Firebase Analytics (Google LLC): Processes anonymous app interaction events (feature adoption, conversion funnel, free limit hits) and session metadata (device model, OS version, app version, session duration, country/region) on behalf of the Service Provider. No PII is included. Data is encrypted in transit (HTTPS). See the Firebase Privacy and Security documentation for details.
Firebase Crashlytics (Google LLC): Processes anonymous crash reports — stack traces, device metadata, relevant app state, a randomly generated Crashlytics Installation UUID, and the RevenueCat anonymous app user ID (not linked to any personal identity) — on behalf of the Service Provider. Data is encrypted in transit (HTTPS). See the Firebase Privacy and Security documentation for details.
RevenueCat (RevenueCat Inc.): If you make a Pro purchase via Google Play, your purchase history (transaction identifiers and entitlement status) is processed by RevenueCat on behalf of the Service Provider for the sole purpose of verifying your Pro entitlement. RevenueCat may additionally collect a device identifier (Google Advertising ID) for purchase attribution. This data is classified as Financial Info: Purchase History under Google Play's Data Safety guidelines. It is encrypted in transit (HTTPS), retained on RevenueCat's servers, and not used for advertising. Free-tier users are not affected. See the RevenueCat Privacy Policy for details.
Cloudflare Workers (Cloudflare Inc.): The Service Provider operates a lightweight verification endpoint on Cloudflare Workers. When the Application performs an integrity check (at startup and during purchase attempts), an anonymous Play Integrity token is sent to this endpoint for verification. The token is processed in memory and immediately discarded — no persistent data is stored. See the Cloudflare Privacy Policy for details.

What are my opt-out rights?

You can stop all Firebase Analytics and Crashlytics data collection and Play Integrity verification by uninstalling the Application. You may use the standard uninstall processes available as part of your mobile device or via the mobile application marketplace or network. Additionally, you can revoke Microphone and Contact permissions at any time via your device's Settings menu. On-device ML processing (ML Kit and ONNX Runtime) runs locally and transmits no data — no opt-out is needed.

If you have purchased Pro and would like your RevenueCat customer record deleted, please contact the Service Provider at kode.v.tk@gmail.com. Firebase Analytics and Crashlytics data contain no personal identifiers and cannot be individually deleted. Firebase Analytics data will naturally expire per the retention period configured in the Firebase console (default: 14 months).

Children

The Application is not used to knowingly solicit data from or market to children under the age of 13. The Application's features (such as call simulation and audio recording) are not designed for children.

The Service Provider does not knowingly collect personally identifiable information from children. If you have reason to believe that a child has provided personally identifiable information to the Service Provider through the Application, please contact the Service Provider (kode.v.tk@gmail.com) so that necessary actions can be taken. You must also be at least 16 years of age to consent to the processing of your personally identifiable information in your country.

Security

The Service Provider is concerned about safeguarding the confidentiality of your information. Because the Application processes your sensitive data (like voice recordings and contacts) entirely offline and on your device, the risk of data exposure is limited to the physical security of your own device.

Changes

This Privacy Policy may be updated from time to time for any reason. The Service Provider will notify you of any changes to their Privacy Policy by updating this page with the new Privacy Policy. You are advised to consult this Privacy Policy regularly for any changes, as continued use is deemed approval of all changes.

By using the Application, you are consenting to the processing of your information as set forth in this Privacy Policy now and as amended by the Service Provider.

Contact Us

If you have any questions regarding privacy while using the Application, or have questions about our practices, please contact the Service Provider via email at:
kode.v.tk@gmail.com