Data deletion

1. Delete data in Reva

Where a deletion control is available in the product, use it first. Retained source files and approved memories have their own deletion controls. Completing an ephemeral work session removes its uploaded working data under the displayed retention policy.

A workspace administrator can also remove a member's access. Disconnecting a provider stops new capture but does not by itself decide whether already retained records should be deleted.

2. Request account or workspace deletion

Send a request from the email address associated with your Reva access. Use the subject Reva data deletion request and include:

• Your name and organization name.
• The email address used for Reva.
• Whether you want a source, connected channel, user account, or entire organization workspace deleted.
• For a WhatsApp connection, only the last four digits of the business number and its displayed connection name.
• Any record that must be preserved for another authorized teammate, with the reason.

Email a deletion request. Do not send passwords, access tokens, full phone numbers, customer exports, or message histories.

3. Meta and WhatsApp-connected data

The same request path applies to data received through an authorized Meta or WhatsApp Business connection. After verification, Reva will scope the request to the correct organization and connection, stop new processing where requested, revoke or remove Reva-held connection credentials, and delete the applicable retained content and derived records.

Customer-owned WhatsApp assets, WhatsApp Manager access, billing records, and data retained by Meta are controlled separately by the customer and Meta. Removing Reva access does not delete a customer's Meta business portfolio or WhatsApp account.

4. What happens next

1. Reva acknowledges the request, normally within seven days.
2. We verify the requester and the organization or record in scope.
3. We explain any impact on shared business records before deletion.
4. Verified deletion is completed within 30 days unless law, security, fraud prevention, dispute handling, or a technically necessary backup schedule requires a limited delay.
5. We send confirmation when the active-system deletion is complete.

5. Records that may remain

Reva may keep a minimal, access-restricted audit receipt showing that a deletion occurred, without preserving the deleted message or source payload. Limited security, billing, legal, or backup records may remain for the required period and are not restored to ordinary product use.

If a raw source is deleted while an approved case fact, commitment, or action remains, the retained record keeps its provenance and deletion boundary and is never presented as a verbatim copy of deleted content.

6. Questions or unresolved requests

Reply to the acknowledgement email if the request is incomplete or the result is unclear. You may also raise a privacy concern using the contact address above and review the privacy policy for other access, correction, export, or restriction requests.