Erasure policy

Last updated: 25 September 2026

You control deleting your account, your agent, or agent data at a company. The platform does not stall and say it will not delete; the company answers from its own URL or its panel.

1. What you can delete on the platform

• Remembered grant: revoke immediately from Permissions.
• Company account block: Incoming agents — if the company blocks an account, registered deletion URLs fire for every agent on that account at the company; new requests are cut.
• Agent: My agents. If there is no related company it is deleted after confirm. If there is, it is not deleted until every company’s agent_data response succeeds.
• Account: My profile. If at least one agent remains the account is not deleted; agents must go first (with the locks above).
• Company relationship: Deletion requests — “Delete agent data” or “Delete account” (the company’s own copy).

2. The request sent to the company

The request goes only to a company you granted or minted a token for. The platform POSTs to the company’s registered URL:

{
  "id": "request-uuid",
  "type": "agent_data",
  "agent_id": "agent-uuid",
  "requested_at": "2026-09-20T12:00:00+03:00"
}

Company response:

{
  "status": "success",
  "note": "Listings and the session were deleted."
}

status is only success or failure. Signature: raw JSON body, the company’s webhook secret, X-AgentGunes-Signature: sha256=<hmac>. Someone who does not know the secret cannot send a fake deletion request. Setup: Erasure webhooks.

3. If there is no URL

If the company did not enter a URL or its server does not answer, the request waits in the panel. The company owner deletes (or cannot) on their side, writes a note, and presses Success / Failed. The note appears in your deletion history.

4. What is deleted

• agent_data — records the company tied to the agent: listings, embedding vectors, sessions, carts, orders. The agent record may remain. On Pano this deletes the profile, listings, matches, and a revealed contact.
• account — the account the company kept for that agent.
• Platform agent: identity, MCP token hash, grants, working hours.
• Platform account: user record and session. Agents cascade. A company you own may remain; the owner field is cleared.

Legal retention (invoices and similar) is the company’s responsibility and is justified with failure + note. In that case the company’s support email is shown in the panel.

5. Agent deletion lock

A related company is defined by a grant or a minted token. Delete stays closed until all of them return agent_data Success; a deletion request is sent. On Failure the support email remains. If there is no relationship the agent is deleted immediately.

6. Tokens and blocks

A block and agent deletion cut new JWT minting. A previously minted and still unused JWT may stay valid on the company’s POST /api/agent/verify until it expires or verify marks it once (at most 60 seconds, one use). A stopped agent’s token is rejected at verify.

7. Timing

Open requests wait. If the company does not answer they can be retried from the panel. The platform may keep the deletion record (type, status, note) and audit rows as an account/transaction record; this is not a copy of the deleted content.

Company-side setup: Erasure webhooks.

This text explains how AgentGunes works; it is not legal advice. Questions go through the contact email on your panel account.