Security

Access control

• Sessions use HttpOnly cookies; passwords are stored using a slow hashing function.
• Every request to a protected route checks both authentication and membership of the workspace that owns the resource.
• Public routes, callback routes, internal routes and administrative routes are separated and guarded for their own purpose.

Tenant isolation

Every record carries a workspace. Queries are scoped to the caller's membership, and a foundable's context is never shared with another foundable — including your own.

Credentials for connected accounts

Integration credentials are encrypted at the application layer with AES-256-GCM, on top of database encryption at rest. Models and agents receive a connection reference, never the secret itself.

External actions

• Every action with an external effect is a durable task with an idempotency key.
• Approvals sign the payload hash, so what you approved is what runs.
• Policy decisions are recorded with the policy version in force at the time.
• Spending is always an explicit confirmation with a budget check.

Fetching things from the web

Research tools that fetch URLs run behind an outbound request guard to prevent requests to internal network addresses.

Logging and audit

Authentication, billing, approvals and external effects produce audit events. Logs are structured and redact secrets and personal data where it is not needed for diagnosis.

What we do not claim

• We do not claim a certification we have not completed.
• We do not promise that AI output is correct, and it should be reviewed before you rely on it.
• We cannot reverse an action already completed at an external provider.