AI Kavach Privacy Policy
About this policy
AI Kavach (com.aikavach.callblocker) is a phone dialer, call-blocking, and optional SMS messaging app published by MANAUNA TECHNOLOGY. This policy describes the app’s handling of information. Effective date: 8 October 2026. Privacy contact: manoj.cs.iu@gmail.com.
Calls, contacts, and device permissions
With your permission, AI Kavach reads contacts to identify callers, reads call history to show recent calls, and uses phone and SIM information to place and manage calls. Default Phone status enables incoming and ongoing call screens. Notifications, full-screen incoming-call display, and optional overlay and system settings access support these features. Contacts and call-history records are processed on the device; the app code does not upload your address book or complete call history to our server. This version does not request microphone-recording permission or upload call audio.
Optional Google sign-in
In versions that offer it, Google sign-in is optional; calling and messaging do not require Google sign-in. Community contributions use an anonymous Firebase account when you have not signed in with Google. If you choose to sign in, Google shares basic profile information with Firebase Authentication. We store your name, email address, profile-photo URL, provider, email-verification status and account timestamps in a private Firestore profile keyed by your Firebase user ID. Only the signed-in account owner and authorized service administrators can access this record. Profile information supports account identification and management and is not copied to Analytics events or used for ad targeting. Google authentication tokens are used only to authenticate with Firebase, not stored in profile documents or event logs. Profiles remain until you delete the account or request deletion. This does not back up your calls, messages or contacts to your account.
Optional Google Drive backup
Backup is optional and starts only when you tap Back up or Restore in Settings → Backup & restore. If you are not signed in, Google sign-in is shown first. The app then asks Google for the limited Drive permission that lets AI Kavach see, create and change only files it creates itself (drive.file); it cannot read your other Drive files. The backup is one file, ai-kavach-backup.json, in an "AI Kavach Backups" folder in your own Google Drive. It contains your blocked and allowed numbers with their labels, blocking patterns, schedules, SMS sender block rules and app settings such as region, theme and screening switches. It does not contain call history, contacts, SMS/MMS messages, OTPs, recordings, Google account details or purchase information. The file is sent directly between your device and Google Drive over encrypted HTTPS; it is not sent to our servers, Firebase, analytics or advertising services, and we cannot access it. Restoring reads that file and adds missing items to the app; it does not remove anything already on the phone. The Drive access token is used only for that request and is not stored by the app. The backup stays in your Google Drive until you delete it there; you can also remove AI Kavach's Drive access in your Google Account's third-party connections. Google Drive's storage, retention and security are governed by Google's terms and privacy policy. AI Kavach's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.
Optional SMS and MMS messaging
The SMS tab accesses messages only after you choose AI Kavach as your default SMS app and grant SMS permissions. It reads sender and recipient numbers, message text, dates, read/send status, and SIM identifiers needed to display, search, receive, and send messages. Inbox search and message display are processed on the device. AI Kavach does not upload SMS/MMS content, message searches, or OTPs to Firebase, our servers, analytics, or advertising services, and does not use message content for ad targeting. When you explicitly send or reply, your message and recipient number are transmitted through your mobile carrier to the recipient. Carrier charges may apply. MMS downloads use your carrier connection and may use mobile data; opening an attachment in another app is your choice. SMS/MMS are not end-to-end encrypted by AI Kavach and are subject to carrier security and retention practices. While AI Kavach is your default SMS app, incoming message handling can run in the background to save messages and notify you. You can change the default SMS app or revoke permissions at any time; calling does not require enabling SMS. Conversation grouping, category suggestions, sender blocking, OTP detection, and link or suspicious-message warnings are processed on your device. Warnings are heuristic cautions, not verified fraud findings, and links are not automatically opened or checked online. Copy OTP puts the selected code on the Android clipboard only when you tap the button; it is marked as sensitive. Read aloud passes only the message you select to an installed offline text-to-speech voice on your device; playback stops when you stop it or leave the foreground. A supported offline voice must be installed. SIM phone numbers are displayed locally when Android provides them and you grant the optional phone-number permission. Blocked SMS are retained in the system message database and shown in Spam without incoming-message notifications; blocking does not erase messages or prevent carrier delivery. When you attach a photo, video, audio file, PDF, or other document, Android’s system file picker grants access only to the items you select. Selected files are copied to app-private storage for MMS preparation and retry, and are transmitted with your message through your chosen mobile carrier when you tap Send. They are not uploaded to our servers, Firebase, analytics, or advertising services. Carrier size and format limits apply; recipients and their messaging apps may not support every attachment type.
Information stored on your device
The app stores call records, local activity summaries, blocked and allowed numbers, blocking patterns, schedules, settings, and cached community spam information. Android backup may retain app preferences according to your device backup settings; the app database is excluded from configured Android backups. SMS/MMS messages are stored in Android’s system messaging database. Pending incoming SMS may be staged temporarily in private app storage until saved, and downloaded MMS data may be cached locally. Those app-private message files are excluded from AI Kavach’s configured app backup. Device/carrier backups of the system message database are governed by their own settings. SMS category choices and sender/pattern block rules are stored in app-private preferences. If you use Google Drive backup, a copy of your block lists, patterns, schedules, SMS block rules and settings is also kept in your own Google Drive, as described above.
Community spam reports
In versions with community reporting, reporting or blocking an exact phone number sends that number and your selected report category or block status to Cloud Firestore. A private contribution is linked to your Firebase account; an anonymous account is created when needed, without requiring Google sign-in. Each account has one active report and one block status per number. Public records contain the number, aggregate report and block counts, category totals and update time. Optional report notes are private to your account and authorized administrators, not displayed to other callers. Do not include names, passwords or message contents in notes. Counts represent accounts, not verified unique people. Personal blocking is separate from a spam or fraud allegation, and community warnings are unverified. Unblocking withdraws your block contribution. Patterns and hidden or invalid numbers are not expanded into cloud reports. Incoming-call screening may send the individual caller number to Firestore to retrieve these aggregates, with a short timeout and a bounded local cache; it does not upload your address book, message contents or complete call history. Pending block updates are stored privately on your device for network retry. Optional Google sign-in links or merges your community contributions. Earlier app versions use a separate community report collection without account-linked deletion; email us for correction or removal requests.
Diagnostics, usage measurement, and notifications
The app uses Firebase Analytics to measure screen visits, onboarding, screening outcomes, spam reports, message feature usage, sending outcomes, purchases and optional account actions. Events may include app version/build type, Android version, language, selected theme and SMS category, permission and default-role state, notification availability, attachment count and a coarse message-length range. Message bodies, search terms, phone numbers, contact names, OTPs, attachment names/content, Google profile names, email addresses, photos, authentication tokens and FCM tokens are not sent as app Analytics event parameters. Sign-in events contain only provider, outcome and non-identifying flags such as whether a name/photo exists and whether Google verified the email. Firebase Crashlytics processes crash and ANR diagnostics, device and app information, and installation identifiers. Firebase Cloud Messaging uses an installation registration token to deliver notifications; the app can subscribe to a public app-update topic. Tokens remain in app-private storage and the messaging service, not Analytics events. Notification events record fixed message type and handling/opening outcomes, not notification text. Firebase Remote Config retrieves app configuration. These services may process IP addresses, device or installation identifiers, and technical information under Google's policies. When a Google or anonymous community account exists, Analytics uses the internal, randomly assigned Firebase account ID to associate usage across your devices. This is not your email address or Google account identifier. The app clears this Analytics user ID when you sign out or delete the account.
Advertising and purchases
App versions with advertising enabled use Google AdMob. Its SDK may collect device identifiers, IP-derived approximate location, ad interactions, and diagnostic data for advertising, fraud prevention, and measurement. Some internal testing builds disable advertising. Optional purchases are processed through Google Play Billing. AI Kavach processes purchase and entitlement information; it does not receive your full payment-card details. Store and device settings provide additional advertising and payment controls. In versions with privacy choices, Google’s User Messaging Platform requests consent where required before ads are requested. Open Settings → Data & privacy → Ad privacy choices to give, refuse or withdraw consent and change vendor choices where applicable. Refusing consent does not disable calling or messaging; Google determines whether limited ads can be served under your choices. The privacy control is shown where Google requires it, or when a consent check needs to be retried.
How information is used and shared
Information is used to provide calling, caller identification, blocking, community protection, diagnostics, notifications, optional advertising, and purchase entitlements. Community reports are shared as described above. Google/Firebase, Google AdMob, and Google Play process information to provide their respective services. Information may also be disclosed when legally required. We do not claim that app operation is entirely offline or that no information leaves the device.
Retention and security
Local call history follows the retention period selected in Settings; the default is 90 days, and cleanup runs periodically. You can delete local call records in the app. Community reports remain in the shared database until removed or corrected by the operator. Firebase and advertising diagnostic retention is managed under the relevant provider settings and policies; clearing app storage does not itself erase previously transmitted provider data. Connections to our Firebase services use encrypted HTTPS. Carrier SMS/MMS transport uses the carrier’s security practices and is not covered by an app-level end-to-end encryption promise. No storage or transmission method is guaranteed to be completely secure.
Your choices and deletion
You can revoke permissions in Android Settings, change the default phone app, delete local call records, clear app storage, or uninstall. In versions that offer optional Google sign-in, you can delete your AI Kavach account in Settings → Google account → Account options (three dots) → Delete account. Confirm the same Google account to remove your Firebase Authentication account, private Firestore profile and account-linked community contributions. Signing out, clearing storage or uninstalling does not delete a cloud account. Versions without sign-in do not create an AI Kavach account. To request deletion or correction of a community number entry or other identifiable data, use the instructions at /data-deletion. We may need limited information to verify your request and locate the relevant record. Certain information may be retained where legally required or necessary to prevent abuse; we will explain applicable limitations in our response. Clearing AI Kavach app storage does not delete SMS/MMS in Android’s shared messaging database. Use your chosen default messaging app’s deletion controls to remove those messages. In versions with Google privacy choices, Analytics collection follows the Google consent flow where required. Analytics remains disabled while consent is unknown or denied and can operate where Google reports consent is not required. Reopen Settings → Data & privacy → Ad privacy choices to change applicable choices. We use Firebase Crashlytics for technical crash diagnosis and app reliability, without a separate in-app switch. An explicit opt-out recorded by a previous version remains respected. Withdrawal does not retrospectively erase data already sent; contact us for deletion or privacy requests.
Children and changes
AI Kavach is a general-purpose communications utility and is not designed specifically for children. If you believe a child has provided personal information through the app, contact us. We may update this policy when app behavior or service providers change; the effective date will be updated.
Contact and service-provider policies
Contact manoj.cs.iu@gmail.com for privacy questions. See Google Privacy Policy (https://policies.google.com/privacy), Firebase privacy information (https://firebase.google.com/support/privacy), and Google advertising information (https://policies.google.com/technologies/ads).