Keychain
API keys, provider secrets, refresh tokens, and integration keys live in the macOS Keychain. The same vault your Mac uses for everything else.
Security & control
Local by default. Approved by you.
Your workspaces, sessions, and app state are stored on your Mac. Keychain protects your secrets, connected services are your choice, and destructive actions wait for your yes.
Keys in the Keychain, state on your disk
Keys, data, and consent.
Where your data sits, and who may move it, the promise matches the implementation.
The promise and the implementation, side by side.
Secrets live in the macOS Keychain. App state, profiles, memory, sessions, schedules, persists locally as JSON. Approval gates hold destructive tool calls, and sign-in only establishes identity.
Cloud requests follow the provider’s policy.
The four boundaries
Four boundaries, in plain words.
Keychain for secrets, local JSON for app state, approval gates for destructive actions, and a sign-in that proves identity. Nothing more.
Local app data
Profiles, memory, sessions, activity, schedules, workflows, and plugin state persist locally as JSON. Readable files on your disk, not our database.
Approval gates
Destructive direct tool calls are held for user confirmation unless explicitly pre-approved.
Account boundary
Firebase Google sign-in verifies identity and Supabase returns trial and plan state. Sign-in proves who you are, nothing more.
Nothing outward moves without your yes.
Get Attyn
Your Mac. Your keys. Your yes.
Attyn keeps app state on your device and secrets in the Keychain, and holds destructive actions for your approval.
macOS today, Apple silicon. M1 and every M-series chip after it. Windows waitlist open.