CallSave Privacy Policy
Terms policy identifier: terms-1.1. Privacy policy identifier: privacy-1.1. Effective date: 2026-09-26 (IST, Asia/Kolkata).
The operator and privacy data controller is Relvo Projects Private Limited, CIN U74909KL2025PTC098789, incorporated 1 December 2025. Registered address: Room No. 17/153, Puzhambram, Gramam, Ponnani, Malappuram, Kerala 679577, India. GSTIN: 32AAPCR2517R1ZU. support@callsave.in is the verified email-only support, privacy and grievance channel. Minimum age: 18 years.
Information kept on your device
Contacts, customer phone numbers, generated contact names, CallSave-observed call events, saved history, analytics, scanned-card content, tasks, customer notes and private Inbox entries use app-private storage on your device. CallSave does not upload this local content to its backend unless you explicitly enable and use the optional encrypted cloud backup described below, or explicitly submit content to support. Cloud backup covers selected CallSave records, not your complete Android address book. If you choose to include local information in a support message or screenshot, that explicitly submitted content is handled under the support section below. CallSave does not read the Android system call log. These local records are not authentication or admission payloads.
The app's contact permissions support checking duplicates, saving contacts and explicit contact lookup; phone-state access and the screening role support call/SIM handling. Saving and product tools require a valid trial or Pro entitlement. Expiry pauses those features and alerts without deleting existing records. Account, renewal, help and privacy controls remain available. No ads or call recording is provided.
CallSave disables Android app backup and excludes its app-owned files, databases and preferences from cloud backup and device transfer in its backup rules. Clearing app storage or uninstalling may permanently delete local history, scanned cards and images, tasks, customer notes, private Inbox entries, reminder records and settings. Contacts already saved to Android or Google Contacts remain according to your device's contact-sync settings; that sync is separate from a CallSave backend upload. Files you deliberately export remain with the destination you choose, whose provider may independently store, back up or sync them.
Optional on-device Tools and Scanned Cards
Local tools disclosure updated 1 November 2026 (IST); addendum identifier: local-tools-privacy-1.0. This addendum expands the tools disclosure of 19 October 2026 and describes the local features below where available in your app version. Camera access is requested only when you open Smart Scan. Photo Picker gives access only to the images you choose; Storage Access Framework gives access only to the import/export files and locations you choose. No broad photo-library or storage access is requested.
Bundled on-device text recognition processes visiting cards, screenshots and posters on the device. Recognition itself does not upload the images or text to a server. Original and processed images remain local. If you enable encrypted cloud backup, saved scanned-card text and contact fields can be included in its encrypted payload; source image files and your full Android address book are excluded. Text is read from the clipboard only after you tap Paste, or from content you explicitly share to CallSave. There is no background clipboard monitoring, screen scraping or chat/group scraping.
Review lets you edit and select proposed contacts before any Contacts write. Contacts permission is used to check existing matches, export contacts you choose and save only the contacts you confirm. Duplicate suggestions do not silently merge or delete contacts. Local batch history stores the source, time, result counts and exact identifiers of contacts created by that batch so Undo can skip contacts changed after saving.
When image recognition completes, CallSave saves the original image, a processed copy and thumbnail, recognized text, suggested and edited contact fields, source details and timestamps in the local Scanned Cards library. This happens before you choose whether to save a proposed contact to the phone. Leaving the review or cancelling a later action does not remove a completed scan. Import candidates and unfinished working input are cleared when you finish or leave that flow; original files selected through Android remain with their providers.
You can remove selected stored images while keeping the card's text and contact links, or delete a scanned-card record and its app-owned images. These actions do not delete Android contacts, existing History entries, original provider files or earlier exports. History and local batch records retain saved-contact details, sources, times and available source references or text for search and review. Original-image downloads preserve the source bytes, which can include metadata already present in the chosen file. No captured image or plaintext local contact information is sent to the identity, entitlement or billing endpoints. Optional encrypted cloud backup is a separate flow described below.
The bundled Google ML Kit SDK can send technical diagnostics and usage metadata to Google over HTTPS, including app/device versions, a per-installation identifier, processing latency, input/output sizes, image format/resolution, feature events and error codes. This is separate from captured images, recognized text and contact content, which remain on the device. See https://developers.google.com/ml-kit/android-data-disclosure.
Voice naming
Name by voice requests microphone access only after you tap the microphone. It uses Android's on-device speech recognizer for English on supported devices. If on-device recognition or the language is unavailable, you can type the name; CallSave does not switch this feature to an online recognizer. CallSave receives an editable transcript and audio-level events for the listening animation. It does not save an audio recording or record phone calls.
You review the original and proposed contact name before saving. Saving changes the selected Android contact and matching local call-history names. Voice recognition does not send the name, transcript or audio to CallSave's backend. A name you save into History can later be included in encrypted cloud backup if you enable it. The separate support voice-input feature is described in the support section because its system speech provider can have different processing settings.
Tasks, Customer Memory and Private Contact Inbox
These optional tools store the content you enter and any contact you explicitly link in a separate local database associated with your signed-in account. Tasks store a subject, notes, optional contact name and number, due date, time zone, status and reminder times. Customer Memory stores notes, labels, timestamps and optional contact references. Private Contact Inbox stores manually entered names, numbers, context, status and optional links to phone contacts. Linking keeps a local snapshot; it does not silently replace a person with a same-name contact.
Customer Memory notes are not written into Android contact notes. Inbox records remain private to CallSave until you explicitly choose and confirm Save to Phone. Archiving retains an entry; removing an Inbox entry does not delete a phone contact. These tools do not send invitations or customer messages. Their contents stay local unless you enable encrypted cloud backup; that optional flow includes the current account's Tasks, reminder definitions, Customer Memory and Inbox. These records are not included in the separate local backup ZIP.
Task, note and Inbox records remain until you remove them or clear this app's storage. Plan expiry or logout does not erase them. Access to these tools and task-alert delivery depends on the current trial or Pro entitlement. Accepted in-app account deletion starts local cleanup for that account's tasks, notes, Inbox entries, missed-call tracking records, task alarms, local notice settings and the device's stored backup key and settings on the device making the request. A private local deletion marker prevents renewed access, and unfinished cleanup is retried when the app runs. A website request cannot remotely erase an offline device's local files; use the app's removal controls or Android's Clear storage on each device for local copies.
Missed Call Reminders and optional notifications
Notification disclosure updated 9 November 2026 (IST); addendum identifier: notifications-privacy-1.1. These disclosures apply where the features are available in your installed app version.
Missed Call Reminders tracking starts on for an active trial or Pro account unless you have explicitly turned it off. CallSave uses call events it observes on this device to keep a local pending-call list and related dates, numbers, SIM information and outcomes for your account. It does not read the Android system call log or automatically call or message anyone. Disabling tracking stops new tracking without deleting existing local records. Expired trial or Pro access pauses tracking; existing records remain local. Tracking resumes when valid access returns unless you previously turned it off.
Task reminders, local plan reminders and weekly pending-call summaries have separate controls. Starting with app version 1.17, task reminders, local plan reminders and weekly summaries start on when no choice has been saved for the current account on this device. An existing off choice is respected. Earlier versions start task reminders off. The plan-reminder choice also controls the local trial-ending warning. You can change each choice in Privacy & Notifications. Android notification permission is also required. These local features do not register a cloud messaging token or upload task or pending-call content. They use Android scheduling and separate notification channels. Task reminders may use exact-alarm access if you grant it; otherwise delivery may be approximate. Evening notices use approximate scheduling. Android permission, channel, battery and Do Not Disturb settings can affect delivery.
Local plan reminders are optional promotional messages scheduled around 7 PM when verified account access shows that a trial has not started or that a trial or Pro plan has ended. Active trials and active Pro access are excluded from these promotional reminders. Account verification can use the existing authenticated access-verification service. At most one plan reminder is displayed per account on this device per local day, with duplicate protection between local and cloud plan messages.
Weekly summaries are scheduled around 7 PM only for an active trial, subscription or Lifetime Pro account with Missed Call Reminders tracking enabled and numbers still pending a call back. The first eligible summary is scheduled for the next evening check; later summaries are due seven local calendar days after the preceding summary. The pending-call list and calculated count stay on the device; they are not sent through the cloud notification service.
CallSave does not post new notifications from 10 PM until 8 AM in the device's current time zone. Task reminders that fall in that quiet period wait until 8 AM; a trial-ending warning can also wait until 8 AM if it is still applicable. Plan and weekly notices use their evening schedule. A delayed notification is checked again before display, so delivery can be deferred or suppressed when the allowed time, account access, preferences or permissions no longer match.
Android receives a task's subject, notes and due time to display its notification. CallSave requests private lock-screen visibility with generic public text; what is visible also depends on your Android settings. Local notification settings, account-scoped duplicate receipts, next-check times and recent attempt results are kept in app-private storage for scheduling and the reminder status shown in Settings. They do not contain task text, phone numbers or contact names. You can turn these notices off without deleting your saved records.
Optional cloud notifications
Cloud service notifications and cloud offers/product news have separate, explicit choices and start off. Starting with app version 1.17, an explained setup action can enable the available cloud notification choices together; you can instead choose categories or select Not now. The app saves cloud consent only after your explicit action succeeds with the service. Turning on a local reminder or granting Android notification permission does not turn on either cloud choice. Cloud messaging registration requires an enabled cloud choice and Android notification permission. The app uses Google Firebase Cloud Messaging to deliver these optional messages. You can use account, renewal, help and privacy controls without opting in.
When you opt in, CallSave processes your authenticated account identifier, a random installation reference, Firebase messaging registration token, device time-zone setting and current UTC offset, notification choices and their version/revision, and registration, update, expiry and scheduling timestamps. The time-zone setting and offset are used to schedule in local time; this feature does not request GPS or infer your physical location. Existing verified trial, subscription and Lifetime Pro records are used to choose eligible messages and suppress plan promotions for active access. This use includes reminders to start a trial or consider a subscription or renewal, so the cloud marketing choice is required for those messages.
Firebase receives the routing identifiers and notification payload needed for delivery, including the account identifier, notification identifier, title, body, destination, category, applicable plan-reminder category and issue/expiry times. These messages do not include local contacts, customer phone numbers, call history, pending-call counts, task contents, notes, scans or images. Firebase also processes installation identifiers and technical SDK metadata under its own terms. Its Android data disclosures are at https://firebase.google.com/docs/android/play-data-disclosure and its privacy information is at https://firebase.google.com/support/privacy.
CallSave records limited scheduling and send-attempt information to prevent duplicates and troubleshoot delivery: the reminder category, sequence, local date, attempt/completion times and whether Firebase accepted, rejected or did not confirm a send. Acceptance is not proof that Android displayed a message or that you opened it. Aggregate notification-worker status contains counts and timestamps, not account or device identifiers. Notification enablement does not enable optional app-open or foreground-activity measurement, Google Analytics collection, or Firebase delivery-metrics export.
Device routing registrations and their index become ineligible for use 90 days after their latest registration/update unless refreshed. Account-level plan-notification attempt records become eligible for deletion 90 days after the attempt, and aggregate worker status after 90 days from its latest update. Short-lived request-limit records expire sooner. Notification choices and their revision are retained to honor your preferences until changed or removed through account deletion; they are not all erased on a 90-day timer. Expiring application records are scheduled for automatic database TTL deletion, which runs asynchronously, so physical deletion can finish after the stated expiry. Firebase's own installation and technical-data retention is separate and is not limited by CallSave's application-record periods.
Turning both cloud notification choices off removes the account's registered cloud notification devices when the authenticated preference update reaches the service. The app applies an opt-out locally immediately and retries a pending account-wide withdrawal when it can reconnect. Signing out clears local permission to display that account's cloud messages and attempts to remove the device registration. Accepted account deletion removes associated cloud notification preferences, device registrations and account-level notification state through the account-deletion process below. Aggregate operational status contains no account-linked identifiers. Disabling cloud notifications does not delete Android contacts, local tasks or pending-call records.
Local downloads and external actions
Backup & Download creates a ZIP at the location you choose through Android's file picker. It contains saved History and scanned-card text and metadata, with an option to include available original images. Separate image downloads also create ZIP files. These files are not encrypted by CallSave: anyone with access to a file can read its contents. These local ZIP downloads do not include Tasks, Customer Memory or Private Contact Inbox, and the ZIP format has no automatic in-app restore. Deleting local records or a CallSave account does not remove previously exported copies from your chosen provider.
When you tap a contact's WhatsApp action, CallSave passes that selected international phone number to WhatsApp to open the conversation. It does not send a message automatically. The optional WhatsApp updates-channel link opens the external channel; opening it does not automatically follow or join it. CallSave does not append local contacts, notes, tasks, scans or your CallSave account identifier to the channel URL. WhatsApp or your browser handles the action under its own settings and privacy policy. Dialler and Contacts actions similarly pass the number or contact you selected to the corresponding Android app.
Optional encrypted cloud backup
Cloud backup disclosure updated 1 November 2026 (IST); addendum and consent identifier: cloudbackup-v1.
Cloud backup is optional. After you set up a recovery key, read the in-app cloud disclosure and explicitly enable backup, CallSave can upload an encrypted copy of its saved History and scanned-card text, together with your account's Tasks, reminder definitions, Customer Memory and Private Contact Inbox. This covers records stored by CallSave, not a copy of your complete Android address book. Original images, processed images and thumbnails, private file paths, native contact identifiers, raw call-observation events, Missed Call Reminders records, sign-in tokens and access credentials are excluded.
CallSave encrypts the backup content on your device before upload using a secret recovery key. The key is stored on that device protected by Android Keystore. CallSave's service receives encrypted content and an encrypted key-check value, but does not receive the recovery key. Only a device with the correct key can decrypt that content. Sign-in identifies your account; it does not recover or replace your decryption key. Keep a separate private copy of the recovery key. If the key and every usable local copy are lost, CallSave cannot decrypt those backups for you. Do not send your recovery key in support messages or screenshots.
When you enable automatic backup, CallSave checks for changed records while the app is open and during background work that Android permits. Encrypted uploads can therefore run when the app is not on screen. There is no guaranteed backup interval: network availability, Android scheduling, battery/Doze settings, force-stop, storage limits and current account or plan verification can delay or prevent a copy. Use the backup status and explicit backup action to check that a recent copy completed. Retrieving and restoring a cloud copy require the same verified CallSave account and the correct recovery key. Restore adds missing supported records and preserves records already present in CallSave. It does not automatically create or overwrite Android contacts or restore excluded images or records. Restore preserves this device's task-notification choice. Restored future task reminders may run when that choice is on, the account has active access and Android permits delivery. An existing off choice is retained, and past task reminders are not replayed. This is backup and restore, not continuous two-way synchronization.
The service still processes your account ownership, backup consent/version and timestamp, random vault/installation/upload/snapshot identifiers, encrypted byte lengths and digests, chunk counts, storage-use and daily-upload counters, and server request/update times to authenticate requests, enforce limits, retain snapshots and delete them. Those metadata are not end-to-end encrypted. Existing authentication and cloud-provider technical metadata, including the processing locations described in this policy, also apply.
The service retains the latest completed snapshot for each backed-up device until it is replaced or deleted. Replaced or deleted copies become unavailable for restore and are queued for physical cleanup, which can require retries. Current limits are five active or uploading devices, 4 MiB per encrypted snapshot and 20 MiB of retained, in-progress and pending-cleanup backup data per account. Daily upload limits also apply. Incomplete uploads expire after 24 hours and become eligible for cleanup; physical cleanup can finish later. Subscription or trial expiry pauses uploads and downloads but does not automatically delete existing cloud copies.
You can disable cloud backup or request deletion of stored backups even after plan expiry. Disabling stops further transfer and retains existing cloud snapshots. Deleting all cloud backups also disables backup. Account deletion initiates deletion of associated cloud backup records through the account-deletion process. These actions do not delete Android contacts or independently exported files. A backup deleted from cloud storage cannot restore later local changes unless another usable copy exists.
The optional cloud feature is separate from Download local backup and image ZIP downloads. Those local files are unencrypted and may contain original images if you include them. Your selected file provider may independently store or synchronize exported files under its own settings.
Google authentication and security
After your explicit consent, Google/Firebase processes your Google account identity, including verified email, Firebase account identifier and provider profile metadata, to sign you in. CallSave requests no additional Contacts, Drive or photo scope and does not put profile photos in its account records. Password and alternate-provider login are disabled. Google/Firebase may process technical data such as IP addresses and user agents for authentication and security.
CallSave stores the verified Firebase account identifier, Google email/name when provided, account creation time, accepted Terms/Privacy versions and trusted consent timestamp. Server-side trial records hold activation and expiry timestamps so reinstalling, device changes and local clock changes cannot reset the same account's trial. A random installation reference and request nonce bind signed access verification to the requesting app; these requests never include local contacts, phone numbers, history, analytics or CSV contents.
Firebase maintains the authenticated session. The app stores consent choices and a signed, bounded entitlement locally. Servers verify Google identity, token validity and revoked/disabled-account status before issuing access. Password and alternate-provider access are not enabled. Tokens, identity values and request bodies are not written to application logs. Cloud providers process service/security metadata under their own terms.
Google infrastructure may process information outside India. Firebase describes its processing and retention at https://firebase.google.com/support/privacy. Authentication IP logs are retained by Firebase for a few weeks; Hosting IP metadata may be retained for a few months. These provider periods are separate from our application-controlled records.
Trial, payments and account lifetime
The 72-hour server-controlled trial is limited to the original account's lifetime: reinstalling, data clearing, device changes and clock changes do not reset it. Completed deletion removes ordinary trial evidence; later re-registration may receive a new trial. There is no indefinite anti-abuse identity/device hash or trial-used tombstone.
Optional annual auto-renewing subscriptions use Google Play's localized tax-inclusive price without app-side GST arithmetic. Google Play collects payment details directly; CallSave does not receive card or bank-account details. To verify and acknowledge a purchase and maintain access, CallSave sends the Google Play purchase token to its authenticated backend and stores account-bound purchase verification records, including the product and base plan, subscription state, authoritative start/expiry and verification timestamps, acknowledgement status and retry metadata. A server-derived obfuscated account identifier binds the purchase to the signed-in account. These are identity and billing records, not local contact or OCR contents. Ordinary application-controlled purchase and entitlement records are included in the account-deletion process below; Google Play maintains its own transaction records under its policies. CallSave does not collect a business GSTIN or issue a separate Relvo invoice in this flow.
Optional in-app support and feature requests
Support disclosure updated 21 October 2026 (IST); support addendum identifier: support-privacy-1.0.
Where in-app support is available, when you choose Report a Problem or Request a Feature, CallSave sends the text you submit and, for a problem report, an optional screenshot to CallSave Support. Requests are linked to your signed-in account so you can see private replies, status changes and case history in My Requests. We do not require a verified phone number or OTP. You may voluntarily include another contact method in your message; avoid passwords, backup recovery keys, payment credentials or unnecessary personal information.
You select an optional screenshot using Android Photo Picker. Screenshots are limited to one JPEG, PNG or WebP image of up to 5 MB. The server checks and re-encodes accepted images to remove embedded metadata before storage. Screenshots are private and are served only through authenticated, authorized support requests; they are not public download links. Authorized support administrators can read requests, reply, update status and review attachments.
Voice input for a feature request uses your device's speech-recognition interface only after you choose it. CallSave receives an editable transcript, not an audio recording, and submits only the text you confirm. The chosen system speech provider may process speech according to its own settings and policy.
Screenshot access ends 365 days after submission, or 90 days after case closure if earlier. Images are scheduled for automatic deletion at those limits. Request text, replies and case history become inaccessible and eligible for automatic deletion 365 days after terminal closure. Platform lifecycle and TTL deletion run asynchronously; physical deletion may complete after eligibility. Account deletion initiates deletion of associated support records and screenshots through the existing controlled deletion process. Android drafts and selected screenshot access are cleared when you submit successfully or cancel. Temporary failures retain your draft so you can retry.
Support data is used for answering requests, fixing reported problems and evaluating requested features, not advertising. Existing account, billing and on-device contact-processing disclosures remain unchanged. Contacts, OCR/import content, tasks, notes and private Inbox entries are not automatically attached to a support request. Only the message and optional screenshot you explicitly submit leave the device through this flow.
Deletion, access and correction
Visit https://callsave.in/delete-account, use the in-app account-deletion link, or email support@callsave.in. Requests require ownership verification and recent authentication. We acknowledge receipt separately from completion. Our application-controlled target is removal of ordinary identity, account, installation, trial and entitlement records within seven days of a valid verified request, including requesting Firebase Authentication deletion. Any pre-existing controlled-test identity binding is also removed; revocation alone is not account deletion.
Firebase states that residual Authentication information is removed from its live and backup systems within 180 days after deletion is initiated. Our seven-day target does not promise that every Google-controlled residual copy disappears within seven days.
Deletion does not cancel Google Play subscriptions or erase Android/Google contacts and exported files. Manage renewal at https://play.google.com/store/account/subscriptions. Contact the verified support/privacy/grievance channel for access, correction or deletion assistance. Do not send passwords, backup recovery keys, OTPs, tokens, contacts, phone numbers, history or CSV data. An email by itself is not proof of ownership. Policy changes will use new identifiers and appropriate notice.