Skip to main content
Two paths, same effect: a hosted manage page for the user, and a purge endpoint for your backend. Both are idempotent, so deleting an already-deleted user succeeds with zero counts.

What deletion does

For every affected connection:
  1. The encryption key of the stored session credential is destroyed. The credential becomes unreadable, including to Verso.
  2. The hosted browser profile of the connection is deleted.
  3. Every conversation and every stored attachment file of the connection is deleted.
  4. The connection is kept as a record with status revoked and no credential, so GET /api/connections keeps reporting it, with zero conversations.
Deletion is immediate and cannot be undone. To use Verso again, the user goes through the connect flow from scratch.

The manage page

Sign a link with purpose: "manage" and open it for the user.
The page shows the user’s connections in your app, with provider, status, conversation count and last sync date, and a Delete all my data button behind a confirmation. Like connect links, a manage link lasts 15 minutes and works once; it is consumed when the page loads. After deletion you receive data.deleted:

The purge endpoint

POST /api/purge deletes from your backend, for example when the user closes their account with you.
A user purge sends data.deleted; a connection purge sends connection.deleted. Full parameters and errors are in the API reference.

After deletion