Skip to content

Delete your CallSave account

Terms policy identifier: terms-1.1. Privacy policy identifier: privacy-1.1. Effective date: 2026-09-26 (IST, Asia/Kolkata).

Account deletion information updated 1 November 2026 (IST). This page explains the current request routes and the local and cloud records covered by deletion.

CallSave is operated by Relvo Projects Private Limited, CIN U74909KL2025PTC098789, incorporated 1 December 2025, GSTIN 32AAPCR2517R1ZU. Registered address: Room No. 17/153, Puzhambram, Gramam, Ponnani, Malappuram, Kerala 679577, India. Our verified email-only support, privacy and grievance channel is support@callsave.in.

Request deletion in CallSave

Open Settings, then Account / Delete Account. Choose the account-deletion action, read the confirmation and verify the same Google account when asked. Confirm only if you want the CallSave account deleted. Account deletion and privacy controls remain available after your trial or Pro access expires. A successful acknowledgement means the request was accepted for processing; it does not mean that deletion has finished.

Request assistance after uninstalling

Email support@callsave.in from your CallSave Google account address with the subject “CallSave account deletion”. State that you request deletion of your CallSave account. You do not need to reinstall CallSave to contact support. This website provides a support-operated request route; it is not an automatic sign-in or deletion form.

Support will arrange ownership verification, recent Google authentication and explicit confirmation before an account is deleted. Email delivery alone does not establish ownership or complete deletion. We never ask you to send passwords, OTPs, access tokens or backup recovery keys. Do not include customer contacts, phone numbers, call history, scans or exported files in the email. If verification or processing fails, support will explain how to continue without claiming completion.

What happens after a verified request

CallSave acknowledges acceptance separately from completion. A durable deletion request blocks further ordinary account access while the service processes deletion and retries failures. Our application-controlled target is removal of ordinary account identity and binding, installation, trial, entitlement and associated encrypted cloud-backup records within seven days of a valid verified request, including deletion of the Firebase Authentication account. Support records and attachments associated with that account are also removed through this process.

Cloud-backup ciphertext and related vault, consent, device, upload and snapshot metadata are included. Deletion does not require your recovery key: the service can remove encrypted copies without decrypting their contents. Failed cleanup is retried and is not reported as completed deletion.

Google/Firebase controls residual processor copies. Firebase states that residual Authentication information is removed from its live and backup systems within 180 days after deletion is initiated. That processor period is separate from our seven-day application-controlled target. See https://firebase.google.com/support/privacy.

Completed deletion removes ordinary trial evidence. We retain no indefinite identity or device anti-abuse tombstone to prevent a later trial. Short-lived deletion and retry records support completion and expire under their retention rules. Google Play independently retains purchase and transaction information under its policies; account deletion does not remove those records or alter statutory retention duties.

Local copies and files outside CallSave's service

When an in-app deletion request is accepted, CallSave starts cleanup for that account's local Tasks, Customer Memory, Private Contact Inbox, Missed Call Reminders records, task alarms, local notice settings and stored cloud-backup key and settings on that device. A private local marker blocks renewed access and permits unfinished cleanup to retry when the app runs.

Account deletion does not automatically erase shared local History, Scanned Cards or their images, Android/Google contacts, or files you exported. Use CallSave's local removal controls or Android's Clear storage to remove remaining app-private data on each device. Uninstalling can also erase app-private data. A website or support request cannot remotely wipe an offline device. Deleting a cloud copy does not delete independently saved local files, and deleting local files does not by itself delete existing cloud snapshots.

Delete only cloud backups

Use Cloud Backup's deletion controls to remove a selected device's snapshot or all stored cloud backups without deleting the whole account. These privacy controls remain available after plan expiry. Deleting all cloud backups also disables backup. Disabling backup alone stops transfers and retains stored snapshots. Incomplete uploads expire after 24 hours and become eligible for cleanup; physical cleanup can finish later and may require retries. The Privacy Policy explains the complete backup contents, metadata, limits and retention.

Google Play subscriptions

Deleting CallSave, its cloud backups or its account does not cancel a Google Play subscription. Cancel renewal separately at https://play.google.com/store/account/subscriptions. Android/Google Contacts and your selected export providers manage their own copies and sync settings.