Start a request
Use the Kavach360 contact path and choose or describe a data-deletion request. Include the community or workspace name, your relationship to it, the person or records involved, and the action you are asking us to take.
Do not send sensitive records in the first message. We will ask for only the information needed to verify authority and locate the correct workspace or record.
What happens next
Verify authority
We confirm that the requester is the person, administrator, or organization authorized to request the action.
Scope the request
We identify whether the request covers a workspace, person, record type, or a narrower set of information.
Review dependencies
We check whether a record must be retained for security, legal, billing, dispute, or other documented reasons.
Complete and confirm
We carry out the approved action and communicate completion or the reason a limited part must remain.
Scope and exceptions
Deletion can mean different things: removing access, deleting a workspace, removing a person’s information, or deleting a specific record. We will describe the action we can take rather than treating every request as the same operation.
- A community administrator may need to approve changes to shared workspace records.
- Some information may need to remain for legal, security, fraud-prevention, billing, or dispute-resolution reasons.
- Backups and system logs may have a separate lifecycle and may not disappear immediately from every copy.
- Removing a record from Kavach360 does not remove copies a community exported or stored elsewhere.
Before you delete
Make sure the request is intentional, the right administrator is involved, and any record needed for an open issue has been preserved through the appropriate process. If you only need to stop someone’s access, an access change may be safer than deleting their history.
For the broader controls behind this process, read Privacy & data controls.