Security and data

Where data is processed and stored

Aethis processes governed traffic at the Cloudflare edge and stores control-plane and evidence data in Supabase PostgreSQL, with Upstash Redis used for low-latency policy/cache state.

Aethis doesn’t make a geographic data-residency commitment.

What is recorded

For each governed action, the Action Record holds the Agent, Connection, tool, resource, an arguments summary, the policy version and decision, any approval and reviewer reason, and the outcome. Turn on the Agent’s redaction controls (PII redaction, Payment data redaction, Secrets redaction) to mask sensitive values before they leave for a provider or tool.

Retention

Action Records are kept for your plan’s retention period and then removed:

Plan	Retention
Developer	30 days
Pro	90 days
Scale	365 days or custom

Deleting an Agent or a Connection doesn’t delete its existing records; they follow the same retention period.

Record integrity

Action Records are tamper-evident:

• Append-only storage. Records are written once and not edited in place.
• HMAC hash-chaining. Each record’s Chain hash is computed with HMAC and chains to the previous record, so a change or a missing record shows up as a break in the chain.

Use Verify Chain in Activity to check record consistency for a scope. Each record’s Integrity tab shows its link status.

See Verify a governance boundary for the verification workflow and how to respond to Delayed, Degraded, Gap and Unverified results.

Agent credentials

• Each Agent has one Aethis MCP endpoint, https://mcp.aethis.io/v1/agents/{agent_id}/mcp, and its own Aethis access key: a scoped Agent credential your client sends as Authorization: Bearer <aethis_agent_token>.
• The endpoint URL isn’t a secret. The access key is what authenticates the Agent.
• The key is shown in full once, when the Agent is created or rotated. Afterwards the dashboard shows only its fingerprint.
• Rotate Key replaces the key. Rotating, pausing and deleting an Agent each require a typed confirmation.
• Keep keys in a secret manager. Never put them in source control, screenshots or support tickets.

Access control

Organization roles (Owner, Organization Admin, Reviewer, Member and custom roles) control who can manage Agents, publish policy and review approvals. Workspaces separate environments, and Agents can only use Connections in their own workspace. See Organizations and workspaces.

Trust Center

For Aethis’s security program, architecture and disclosure policy, see the Trust Center.