Security and data
Only what the product's code confirms. If something is not on this list, we don't promise it.
A practice workspace with step-by-step guidance and result checks. No sign-up or account changes.
How it works
Passwords are stored only as an argon2 hash. A session is a short-lived access token plus a refresh token stored hashed — in the Keychain on iPhone. A password reset ends every session.
Permissions are checked on the server for every request. The interface only shows what is allowed.
Stored provider, MCP and GitHub secrets are encrypted; ordinary settings responses show a mask. A newly created personal access key is shown on creation; save it securely.
Approval for ordinary agent writes depends on policy and is required by default. Privileged actions always require approval. Audit logs and run history help inspect executed operations.
Why it helps
- An agent cannot bypass the space's permissions.
- Stored secrets are not returned by ordinary settings responses.
- Run history helps inspect agent actions and errors.
Get started
- 1
Grant the smallest role that works: start with viewer or member.
- 2
Enable only the tools an agent needs.
- 3
Share a provider key at project level instead of personal keys.
- 4
To delete your account, email support with the subject “Delete my account”.
Where to find it
Space → Settings → Member accessApprovalsSupport
Details
Not available yet
- Two-factor authentication and passkey sign-in.
- Single sign-on (SSO).
- Self-service account deletion and a full data export — support handles these. Databases can be exported to CSV, XLSX and JSON.
Write to support and we will reply by email. Or just try it: your personal space is ready right after sign-up.
Checked against the code on 4 November 2026