TokST
Privacy at TokST
TokST is designed around explicit memory storage, workspace-scoped access, and user-controlled collaboration.
Data scope
Cloud memory includes the Markdown content and metadata you create, attached files, Atlases, workspaces, Agent identities, API key metadata, OAuth connection records, and audit events. These records belong to the account and workspace that create them.
Access and collaboration
A workspace is the access boundary. Owner, admin, and member roles govern shared resources. A memory retains its creator and lifecycle details. Team owners and administrators manage memberships, roles, invitations, and shared governance.
Connected Runtime and automatic memory
Automatic memory processes connected Agent session material on the device, removes sensitive patterns before compilation, and sends only resulting cloud records and required audit metadata.
Connected Agent
Automatic memory uses the connected ACP Agent in an isolated compilation session. The Agent's existing authorization remains with that Agent; TokST receives the resulting Markdown memory and Session metadata needed for workspace review.
Retention and lifecycle
Archiving removes a memory from normal views while preserving its history. Deleting a memory follows its resource lifecycle and permission rules. Session candidates, checkpoints, and audit records preserve the review trail required to understand how durable knowledge was created.
Your controls
Users can archive or restore memories, manually clear archived content, revoke API keys and OAuth connections, leave workspaces, and control automatic memory. Teams can manage members, roles, invitations, and shared resources. Use [email protected] for privacy questions.
Data minimization and safe use
Store confirmed, durable knowledge. Keep secrets, credentials, private keys, full chat transcripts, raw reasoning, and short-lived tool output outside durable memory. Automatic memory applies local redaction before compilation.