Start from the app when available
If your Kavach360 app account includes an account deletion option, use that in-app path first. It helps verify the signed-in account and route the request correctly.
Data deletion
Delete account and associated data
Last updated: June 24, 2026. This page is the public Kavach360 data deletion URL for app users, web users, website visitors, residents, customer admins, and support contacts.
Start a deletion request.
To request deletion, open the contact route and use the subject or message line Account and data deletion request. If your request relates to a live society or property account, include the relevant account context so the request can be routed to the correct customer admin or support owner.
Contact us to request deletionHow deletion requests work
Use this public web route
If you no longer have the app, cannot sign in, or need a website-accessible deletion URL for Google Play or App Store review, use the contact route linked below.
We verify before deleting
We may verify your email, phone number, account, society, property, unit, role, or customer admin authority before changing or deleting records.
We confirm the outcome
After review, we explain what was deleted, what could not be deleted, and what must be retained for legal, financial, security, audit, dispute, or customer-governance reasons.
What you can ask us to delete
- Kavach360 app account identifiers and profile data that are controlled by Kavach360.
- Website contact, demo, lead, support, marketing, and communication records linked to the verified requester, where retention is no longer needed.
- Device tokens, notification preferences, app diagnostic identifiers, and optional marketing preferences associated with the account where technically feasible.
- User-submitted content or attachments that are not required for an active customer workflow, legal record, payment record, incident record, or community governance record.
What may be retained
Deleting an app account does not always erase every record that mentions a person. Some data must remain where it is controlled by a customer, required for community operations, or needed for legal, payment, accounting, security, audit, dispute, or compliance reasons.
- Invoices, receipts, tax records, payment references, refund records, chargeback context, accounting records, and payment provider records that must be retained.
- Security logs, abuse-prevention records, incident records, audit trails, admin actions, and access logs needed to protect the service and users.
- Community operations records controlled by a society, property operator, builder, employer, or customer admin, such as dues, notices, approvals, visitor logs, complaints, vendor records, governance records, and service history.
- Records connected to unresolved support requests, legal claims, disputes, fraud reviews, regulatory requests, or contractual obligations.
- Backup copies that age out on the normal backup cycle, and aggregated or de-identified analytics that no longer identify a person.
What to include in your request
- Full name, email address, and phone number used with Kavach360.
- Whether the account was used on Android, iOS, web dashboard, or the public website.
- Society, property, organisation, unit, or customer account context if relevant.
- Whether you want to delete the app account and associated data, only website/contact data, only marketing records, or a specific operational record.
- Any request ID, payment reference, or support ticket number that helps identify the record. Do not send passwords, OTPs, UPI PINs, card PINs, or sensitive documents unless we specifically ask for verification through a secure channel.
Timing
We aim to acknowledge deletion requests within 7 days and complete verified requests within 30 days where feasible. More time may be needed when a request involves customer-controlled society records, payment records, identity verification, legal retention, security investigation, or third-party processors.
Customer-controlled records
If your data is part of a society, property, builder, employer, vendor, or managed portfolio account, the customer may control whether the record can be changed or deleted. In those cases, Kavach360 may forward or coordinate the request with the relevant customer admin while still helping you understand the process.
Related policies
See the Privacy Policy for broader handling of personal data and the Terms of Service for account, payment, operational, and customer-data responsibilities.