Privacy Policy & Account Deletion
Call Timer: Call Time Limits (formerly Mindful Speaker) · Package: com.callmanager.call_manager
Last updated: 3 November 2026
Krishnam Raju Datla (“Owner,” “we,” “us,” or “our”) operates the Call Timer: Call Time Limits mobile application. This Privacy Policy explains how we collect, use, store, protect, and delete your information. It is written to support Google Play privacy, ads, and account-deletion requirements.
Your privacy is a core product principle. Call Timer: Call Time Limits keeps core contact, call-timer, and caller-matching data on your device by default. Optional cloud features, ads, analytics, and crash reporting are described below.
1. Information we collect
1.1 Information you provide
- Google account email, display name, and photo URL when you sign in with Google — for authentication and optional sync/backup.
- Contact group assignments, durations, premium group names, and timer settings — for core call-timer features.
- Optional backup connection details (e.g. WebDAV URL, username, password, folder) — only when you connect your own backup destination.
1.2 Information collected on-device
- Device contacts (with permission) — to match callers to groups; stored on device only.
- Call state (ringing, active, idle) via phone state permission — for timers; stored on device only.
- Call duration derived from state changes — stored on device only.
- Active cellular caller identity via Caller ID / call screening role where supported — on device only.
- Foreground app during calls (usage access) — to detect supported VoIP/meeting apps; on device only.
- Supported VoIP caller text via notification listener — on device only.
- App-generated call history for insights and backup/export — on device unless you back it up.
- Ending a call (ANSWER_PHONE_CALLS permission) — used only when you turn on optional auto-end for a group, to end a call when its time limit is reached. Never used for internet (VoIP) calls, emergency, hidden or unknown numbers, No Timer contacts, or while a second call is waiting.
- Repeat-call handling via the Caller ID & spam (call screening) role — only if you turn on Stop repeated calls, to silence or decline a caller who rings back within a short period you choose; the third attempt always rings. The list of recent callers and silence timers is stored on device only.
1.3 Third-party services
- Firebase Authentication — Google sign-in token / account identifier.
- Firebase Analytics — usage events and device metadata for product improvement.
- Firebase Crashlytics — crash reports and stack traces.
- Firebase Remote Config — feature flags and configuration.
- Google AdMob / User Messaging Platform — Advertising ID, consent status, and ad telemetry for free-tier ads.
- RevenueCat — anonymous app user ID and purchase state for subscriptions.
See Google Privacy Policy, Google advertising, and RevenueCat Privacy.
1.4 We do NOT collect
- Call audio (no recording, listening, or interception)
- Microphone access for call recording
- System call logs / SMS / chat / email content
- Location data
- Default-dialer privileges
- Photos/camera/files except when you intentionally import, export, or share backups
- We do not sell or rent personal data to advertisers or data brokers
2. How we use information
- Core call timer and contact matching
- VoIP caller identification (with consent where required)
- Analytics, communication score, stability, and bug fixing
- Advertising in the free tier (consent where required)
- Subscription management
- Optional backup/restore and optional cloud sync
3. Storage and security
Contacts, call history, and settings are primarily stored locally (e.g. Hive). Sensitive backup credentials use platform secure storage and are excluded from Android auto-backup where applicable. Optional Google Drive backups use drive.file. Optional Firestore sync stores settings under your user ID.
4. Data sharing
We do not sell your personal data. We share data only with Google (Firebase/AdMob), RevenueCat, backup providers you choose, and law enforcement when required by valid legal process.
5. Your rights
You may access, export (via backup), and delete your account, and control permissions in device settings. EEA/California/India/Brazil rights apply as required by local law. Data controller: Krishnam Raju Datla, Hyderabad, India · dkrishnamraju@gmail.com.
6. Account and data deletion
In-app: Settings → Account → Delete Account attempts to delete your Firebase Auth user, Firestore sync document, app-created Google Drive backup files (when connected), and disconnect Google sign-in.
Not automatic: on-device data (uninstall/clear storage), backups on OneDrive/Dropbox/WebDAV, and store subscriptions (cancel in Google Play / App Store).
You may also use our deletion request form:
Request account & data deletion
7. Retention
- On-device data — until you clear storage or uninstall
- Firebase Auth/Firestore — until account deletion
- Google Drive backups — until you or the in-app flow deletes them
- Analytics/crash reports — per Google’s retention defaults
8. Permissions (summary)
Phone state, Caller ID role, contacts, notification listener, display over other apps, usage access, answer/end phone calls (optional auto-end only), and notifications — each used only for the features described above.