Tenant access
Authenticated resources are checked against the active organization and workspace. Access changes advance a shared authorization generation, which invalidates cached grants and outstanding WebSocket tickets.
SECURITY · DATA HANDLING
The controls behind Staso's launch path.
This page describes controls covered by current code and tests. It is not a certification, compliance guarantee, or customer-specific security commitment.
Browser credentials
Access and refresh credentials stay in server-managed HttpOnly cookies behind a same-origin proxy. OAuth redirects use a short-lived, single-use handoff code. WebSocket URLs contain no credential. Connections use a short-lived, consume-once ticket bound to the principal, tenant, resource, and authorization generation.
Capture controls
The Python SDK has independent controls for request content, system prompts, tool schemas, tool arguments, and output. Disabled categories are omitted before SDK serialization and backend Redis enqueue. Retained content is sanitized for recognized protected values before Redis. This is defense in depth, not complete PII or secret discovery.
API keys
New API keys default to the active workspace, traces:write, and a 90-day expiry. Broader scope or no expiry requires an explicit choice. Keys support rotation, permanent revocation, and last-used visibility. Replacement secrets are shown once.
Delivery and retention
A successful ingest response means the complete request was durably queued. Persistence then reaches ClickHouse or a durable dead-letter queue. Trace retention is 7 days on Personal and 30 days on Team. Internal retention and operator-requested tenant deletion use checkpointed jobs across documented stores. Staso does not promise public account export, self-service account closure, or a universal deletion timeline.
Guard availability
Guard runs inline, and latency depends on enabled rules, model calls, and network conditions. Evaluation failures are classified. Fail-open is the default, and fail-closed can be configured. A degraded result reports which mode selected the effective allow or block action.
What this page does not claim
Staso does not claim an external security certification, regulatory compliance, exhaustive redaction, universal encryption coverage, an organization audit-log product, SSO, self-hosting, or a contractual SLA for the general launch product.
Need to verify a specific control?
Email [email protected] with the data you expect to send and the control you need to verify.
Email a security question