Your Code. Your Keys. Your Machine.
Caide is engineered from the ground up as a private, local-first application. We do not operate intermediary servers that read your prompts or store your source code.
Local Storage
All project files, SQLite state stores, and chat threads remain on your hard drive. Nothing is uploaded to a Caide cloud.
Direct Provider Calls
Caide calls OpenRouter, OpenCode Console, DeepSeek, Google, and the ChatGPT/Claude Code account endpoints directly from your local process over secure HTTPS.
Zero Telemetry
No tracking pixels, no event telemetry, and no usage profiling. BYOK turns talk straight to your chosen provider; only Caide Agent passes through Caide's gateway.
What changes when you sign in
Everything above stays true for key users. Signing in with Google on this website adds a Caide account, which stores the minimum needed to run the Caide Agent provider, API keys and billing — and nothing else. API keys are stored hashed (never in plain text) and the desktop keeps your key locally, encrypted at rest.
Profile data
We receive your name, verified email, and profile photo from Google — nothing else. A login cookie keeps you signed in on this site for 30 days. No passwords: Google handles authentication.
Usage metering
Caide Agent requests record aggregate counts only — requests, tokens, and cost per time window. Caide Agent prompts and generated code are proxied to OpenCode Console and never stored by Caide. Billing runs through Lemon Squeezy; card data never touches us.
Retention, export, deletion
Metering aggregates are kept while your account is active. You can request a usage export at any time, and deleting your account revokes all devices and sessions, cancels billing, and anonymizes stored usage. Deleting the app from your machine removes all local data; contact us from your account email for account deletion.