Security & privacy
A plain-language rundown of how your data is stored, who can see what, and what happens when you share.
Accounts & authentication
- Sign up and sign in with email + password or Google Sign-In.
- Chat requires an account; guests can try community skills, view shared chats/artifacts, and test skills — but can't save work.
- You can log out of all devices from Settings → Data.
Where your data lives
- Conversations are stored per user account. Idle conversations (14+ days) archive to cold storage and rehydrate when you open them.
- Artifacts (generated files) are saved to your account's gallery.
- Skills you create are personal unless you publish them to the community library.
- We use your connected Google account only for what you ask (send email, read calendar, save/read Drive files) via scoped OAuth.
Sharing model
- Private by default. Nothing you build is visible to anyone else until you explicitly share it.
- Public link: anyone with the URL can view a read-only copy. Treat it like any public URL.
- Password-protected link: adds a password layer on top.
- Community skills: publishing makes the skill public with your author attribution — that's the point of the library.
Code execution
The harness runs generated code on server-side, sandboxed compute — it never runs on your machine. Scripts execute in a contained environment and only produce the file artifacts you see. As with any AI system, treat AI-generated code like code you didn't write: review it before trusting it with anything sensitive, and don't ask it to process data you aren't comfortable having processed by the service.
Third-party services
- DeepSeek — the model provider that processes conversation content to generate responses.
- Google — for search results (Serper) and for Gmail/Calendar/Drive when you connect an account.
- AWS — hosting, storage, and the serverless execution engine.
See the Privacy Policy and Terms of Service for the full legal picture.
Your controls
- Settings → Data: export your data, delete all chats, manage shared links, log out of all devices.
- Settings → API Keys: manage your own DeepSeek key (BYOK).
- Report a bug: any concern, in-product.