Mindful Speaker (Call Manager) — Privacy Policy & Account Deletion
Krishnam Raju Datla ("Owner," "we," "us," or "our") operates the Mindful Speaker mobile application. In some package names, repository paths, and older documents, the app may still be referred to as Call Manager. This Privacy Policy explains how we collect, use, store, protect, and delete your information when you use the app.
Your privacy is a core product principle. Mindful Speaker is designed to keep core contact, call-timer, and caller-matching data on your device by default. Optional cloud features, ads, analytics, and crash reporting are described explicitly below.1. Information We Collect1.1 Information You Provide Directly
Google account email, display name, and photo URL: Collected when you sign in with Google. Used for authentication, account identification, and optional sync/backup features.
Contact group assignments, custom durations, premium group names, and timer settings: Collected when you configure the app. Used for core call-timer functionality.
Optional backup connection details (WebDAV server URL, username, password, and remote folder): Collected when you connect your own backup destination. Used to connect to your selected backup provider and perform backup/restore.
1.2 Information Collected Automatically in the App
Device contacts (such as name and phone number): Synced from device contacts with your permission. Used to match callers to your contact groups. Stored on your device only.
Call state (ringing, active, idle): Accessed via READ_PHONE_STATE permission. Used to detect when calls start and end for timers and reminders. Stored on your device only.
Call duration: Calculated from call state changes. Used to track call time against your limits. Stored on your device only.
Active cellular caller number or identity: Accessed via Android Call Screening / Caller ID role on supported devices. Used to identify GSM callers without reading call history. Stored on your device only.
Foreground app during calls: Accessed via PACKAGE_USAGE_STATS special access. Used to detect supported VoIP or meeting apps and decide how the timer should behave. Stored on your device only.
Supported VoIP caller text or caller name: Accessed via Notification listener access. Used to identify VoIP callers such as WhatsApp or Telegram callers. Stored on your device only.
Call history records generated by the app: Built from app events and timer state. Used for analytics, insights, communication score, and backup/export features. Stored on your device unless you back it up.
1.3 Information Sent to Third-Party Services
Firebase Authentication: Sends Google sign-in token and account identifier. Used for sign-in and account management. [Google Privacy Policy]
Firebase Analytics: Sends usage events, screen views, and device metadata. Used for app improvement and aggregate analytics. [Google Privacy Policy]
Firebase Crashlytics: Sends crash reports and stack traces. Used for stability monitoring and bug fixing. [Google Privacy Policy]
Firebase Remote Config: Sends configuration requests and metadata. Used for feature flags and rollout control. [Google Privacy Policy]
Google AdMob / User Messaging Platform: Sends Advertising ID, consent status, and ad interaction telemetry. Used for consent management and advertisement delivery in the free tier. [Google Ads Privacy]
RevenueCat: Sends anonymous app user ID and purchase state. Used for subscription and paywall management. [RevenueCat Privacy]
1.4 Information We Do NOT Collect
We do NOT record, listen to, intercept, or store call audio.
We do NOT request or use microphone access for call recording.
We do NOT read call logs or call history from the system phone app.
We do NOT read SMS, chat messages, or email content.
We do NOT collect location data.
We do NOT use default-dialer privileges.
We do NOT access your photos, camera, or general files except when you intentionally import, export, or share backup files.
We do NOT sell or rent your personal data to advertisers or data brokers.
2. How We Use Your Information
Core call timer functionality: Uses call state, duration, and caller identity. (Basis: Contract performance / legitimate interest).
Contact group matching: Uses contacts and group assignments. (Basis: Consent).
VoIP caller identification: Uses notification listener data. (Basis: Consent / legitimate interest).
Analytics and communication score: Uses app-generated call history. (Basis: Legitimate interest).
App improvement and bug fixing: Uses analytics events and crash reports. (Basis: Legitimate interest).
Advertising in the free tier: Uses AdMob telemetry and consent status. (Basis: Consent where required).
Subscription management: Uses anonymous app user ID and purchase state. (Basis: Contract performance).
Optional backup and restore: Uses settings, history, and provider credentials. (Basis: Consent).
Optional cloud sync: Uses account-linked settings in Firestore. (Basis: Consent).
3. Data Storage and Security3.1 Local Storage (Your Device)
Contacts, call history, and app settings are primarily stored locally in app-managed storage (Hive databases).
Sensitive connection details (WebDAV credentials/tokens) are stored using platform-secured storage.
Secure-storage entries for sensitive backup secrets are excluded from Android automatic cloud backup and device-transfer rules.
3.2 Cloud Storage and External Storage (Optional)
Google Drive backup: Uses the drive.file scope (limited to files created by this app).
Other backup destinations: Backup archives stored on OneDrive, Dropbox, iCloud, or WebDAV are governed by the privacy model of that provider.
Firebase Firestore sync: Settings are stored under users/{your-uid}/app_data/settings.
4. Data Sharing
We do NOT sell your personal data. We share data only for:
Google (Firebase/AdMob): For analytics, stability, and ads.
RevenueCat: For subscription management.
Chosen Backup Providers: To perform your initiated backup/restore.
Law Enforcement: Only if required by valid legal process.
5. Your Rights
Universal Rights: You have the right to Access, Export (via backup), and Delete your account, and control permissions via device settings.
EEA (GDPR): Rights to rectification, restriction, and portability. Data Controller: Krishnam Raju Datla, Hyderabad, India. Contact: dkrishnamraju@gmail.com.
California (CCPA): Right to know, delete, and correct. We do NOT sell your information.
India (DPDP) / Brazil (LGPD): We comply with local erasure and grievance redressal requirements.
6. Account and Data Deletion8.1 What the in-app deletion flow does:
When you request deletion via Settings > Account > Delete Account, the app attempts to:
Delete your Firebase Authentication user account.
Delete your Firestore cloud-sync document.
Delete app-created Google Drive backup folders/files.
Disconnect the Google sign-in session.
8.2 What is NOT automatically deleted:
On-device data: You must uninstall the app or clear storage in your device settings.
External backups: You must manually delete backups from OneDrive, Dropbox, or WebDAV.
Subscriptions: You must cancel active subscriptions via Google Play or the Apple App Store.
7. Data Retention
On-device data: Retained until you clear app storage or uninstall.
Firebase Auth/Firestore: Retained until account deletion.
Google Drive Backups: Retained until deleted by user or in-app deletion flow.
Analytics/Crash Reports: 90 days to 14 months (service provider defaults).
8. Permissions Explained
Phone State: To detect call starts/ends for timers.
Caller ID Role: To identify callers without reading system logs.
Contacts: To match callers to your custom groups.
Notification Listener: To identify VoIP callers (WhatsApp, etc.).
Display Over Other Apps: To show the timer overlay during calls.
Usage Access: To detect meeting apps (Zoom/Teams) and skip timers.
Post Notifications: To show alerts and reminders.
9. Contact Us
For privacy, data access, or deletion questions, email: dkrishnamraju@gmail.com