Sokko Docs
Platform API

Data and privacy

Where the conversations of your end users are stored, who can read them, how to delete the data of one end user, and what that call does not remove.

Your end users write to an agent through your product. This page says what the platform stores about them, who can read it, and how you delete it, so that you can answer an access or erasure request.

What is stored, and where

DataWhereUntil
Conversations: each message and answerIn the workspace of the customer the conversation belongs to.You delete the conversation, the end user's data or the workspace.
AttachmentsWith their conversation.The same.
The externalUserIdOn each conversation.The same.
The agent's own session historyIn the agent's private storage.You delete the agent.
Shared memoryIn the workspace, when memory is on. Written by your server and by every agent of the workspace with memory on.You delete the workspace.

The data of one workspace is separate from every other workspace, yours and other accounts' alike. That holds for the shared memory too: workspaces never share a memory. Inside one workspace the memory is shared by all its agents and by everyone who talks to them, so create one workspace per customer. See Who shares a memory.

Use an opaque id as externalUserId, not an email address or a name. The id is stored, and the agent is shown it as an identifier.

Who can read a conversation

Only your platform key. A conversation created through the API is read through the API, with a key of your account.

  • No dashboard shows it. These conversations do not appear in the Sokko dashboard, for anyone: not for the members of your own workspace, and not in any view of your customer's workspace.
  • Your customer cannot read it on Sokko. Your customers have no Sokko login. What they see is what your product shows them.
  • Another account cannot read it. An id of your account answers 404 to every other key.
  • The agent reads it to answer. For each turn the agent is given the conversation it answers in.

Everyone who holds a platform key of your account can read every conversation of every workspace. Keep the number of keys small, and revoke a key that is no longer used.

What leaves the platform

  • Answers to your API calls. Message text and answers travel only in the answer to a call your server made with its key: a turn, a conversation, an event stream.
  • Webhooks hold no content. The data of an event holds ids, status values and amounts. It never holds message text, an answer, instructions or recipe variables. A webhook that is intercepted tells its reader that something happened, not what was said. See Webhooks.
  • Tool events hold names only. tool.updated and the tools of a turn give the name and the state of a tool call, not its input or its result. The name of a built-in tool is given without the platform's own prefix.
  • What the agent does with its tools. An agent that has an MCP server or a connected app sends data to that service when it uses it. That is your configuration: give an agent only the tools its task needs.

The platform's own record of your API calls holds ids and counts, never message text.

Delete the data of one end user

DELETE /workspaces/{workspaceId}/end-users/{externalUserId}
curl -X DELETE https://sokko.ai/api/v1/workspaces/$WORKSPACE/end-users/user_88213 \
  -H "Authorization: Bearer $SOKKO_PLATFORM_KEY"
{
  "conversations": 3,
  "turns": 41,
  "attachments": 2,
  "skipped": 0
}

The call deletes, in this workspace:

  • every conversation whose externalUserId is exactly this id, on every agent, also on agents you already deleted;
  • every message and answer of those conversations;
  • every attachment of those conversations, with its file.
FieldMeaning
conversationsConversations deleted by this call.
turnsTurns deleted with them. A turn is one message and its answer.
attachmentsAttachments deleted with them.
skippedConversations left in place because a turn was still running.

How it runs:

  • A running turn is asked to stop first, and the call waits up to 5 seconds for it. A conversation whose turn still runs after that is skipped.
  • When skipped is above 0, send the call again until it is 0.
  • A second call after a complete one answers zeros. The call is safe to repeat.
  • The call covers one workspace. If the same end user exists in several workspaces, call it once for each.
  • The platform keeps a record that the deletion happened, with the counts. The record holds no content and not the id itself.

Errors: 400 invalid_request (the id is not 1 to 128 letters, digits or . _ : @ -), 404 not_found (no such workspace in your account).

What this call does not remove

Two stores are not covered by this call. Plan for them before you promise your end users an erasure.

  1. The workspace's shared memory. The memory is not kept per end user, so the platform cannot find and remove what came from one person, and the API has no call that deletes one fact. Deleting the workspace deletes its memory. What is in it is what your server saved through the memory calls and what each agent with "memory": true learned from its conversations, whatever its audience. An agent with "memory": false writes nothing to it. If facts about a person are saved there, you cannot erase them per person.
  2. The agent's own session history. The agent keeps a record of its sessions in its private storage, to continue a conversation. This call does not reach it. Deleting the agent removes that storage.

Also outside this call:

  • What the agent already sent to other systems through its tools: a row it wrote through your MCP server, an email it sent through a connected app. Delete it in those systems.
  • Your own copies: what your product stored of the conversation.
  • Records with no content: usage amounts and webhook delivery records (ids and status).

Other deletes

To deleteCall
One conversationDELETE …/agents/{agentId}/conversations/{conversationId}
Everything of one end user in a workspaceDELETE /workspaces/{workspaceId}/end-users/{externalUserId}
An agent, with its files and session historyDELETE /workspaces/{workspaceId}/agents/{agentId}
Everything of one customerDELETE /workspaces/{workspaceId}

Deleting an agent does not erase the stored records of its conversations. They can no longer be read through the API, and they stay until you delete the end user's data or the workspace. To erase an agent's conversations, delete each conversation before you delete the agent, or run the end-user delete for each externalUserId afterwards.

Deleting a workspace removes all of it: agents, conversations, attachments, skills, MCP servers and their tokens, app connections and the shared memory. See Delete a workspace.

A checklist for an erasure request

  1. Find the workspaces where the person has conversations. You hold that mapping: the platform has no search across workspaces by externalUserId.
  2. Call the end-user delete in each workspace until skipped is 0.
  3. If your server or an agent with memory saved facts about the person in the workspace's memory, decide what to do about the memory. The only complete removal is the deletion of the workspace.
  4. Delete what the agent wrote into your own systems and connected apps.
  5. Delete your product's own copies.

For questions about data processing terms, write to support@sokko.ai.

On this page