> For the complete documentation index, see [llms.txt](https://docs.crew.you/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crew.you/security-and-privacy/overview.md). # Overview Crew is built with security and privacy as core principles. We understand that connecting your email, calendar, and files to an AI agent requires trust — and we take that responsibility seriously. ## Google CASA Certification Crew has passed Google's **Cloud Application Security Assessment (CASA)** with an excellent score. CASA is a rigorous third-party security audit program managed by Google, where an independent security firm evaluates the application's architecture, data handling, authentication, and vulnerability management. This certification means Google has formally approved Crew to access user data through Google Workspace APIs (Gmail, Calendar, Drive, Contacts) after verifying that our security practices meet their standards. ## Your Data Is Never Used for AI Training **We do not use your data to train AI models — period.** * Your conversations, emails, files, and calendar data are never used for AI training * We use commercial AI APIs (such as Anthropic's Claude) that explicitly guarantee your data is not used for model training * Your data is processed only to provide the service to you — nothing more ## Data Access Principle Crew only accesses your data when you explicitly ask it to. For example: * Crew reads your email **only when you ask** it to check your inbox * Crew accesses your calendar **only when you ask** about your schedule * Crew reads your Google Drive files **only when you ask** about a document Your agent never proactively accesses your personal data unless you've explicitly enabled a feature that requires it (such as Proactive Intelligence modules, which you opt into individually). ## Encryption ### OAuth Tokens All OAuth tokens (Google, Microsoft, GitHub, Notion, Slack, etc.) are encrypted at rest using **AES-256-GCM** encryption before being stored in our database. Even in the unlikely event of a database breach, your tokens would be unusable without the separate encryption key. ### Workspace & Drive Files Files in My Files are encrypted at rest using per-user encryption keys derived via **HKDF** (HMAC-based Key Derivation Function). Each user's files are fully isolated — cross-tenant data access is architecturally impossible. ### Data in Transit All data transmitted between your browser and Crew's servers is encrypted using **TLS 1.2+** (HTTPS). This includes chat messages, file uploads, API calls, and webhook communications. ## Isolation ### Per-User Sandboxing When Crew runs code or processes files, it uses isolated sandbox environments. Each user gets their own sandboxed workspace — there is no shared file system between users. ### Multi-Tenant Architecture While Crew operates as a shared platform, each user's data is strictly isolated at the application level. Database queries are scoped to the authenticated user, and there are no administrative backdoors that bypass this isolation. ## Payment Security All payments are processed through **Stripe**, a PCI-DSS Level 1 certified payment processor. Crew never stores your full credit card number or payment details on our servers. All payment interactions happen directly between your browser and Stripe's secure infrastructure. ## Third-Party Data Sharing Crew does not sell, rent, or share your personal data with third parties for marketing or advertising purposes. Data is shared with third-party services only as necessary to provide the service: * **AI providers** (e.g., Anthropic) — to process your requests (your data is not used for training) * **Payment processor** (Stripe) — to handle subscriptions and payments * **Connected services** (Google, Microsoft, etc.) — only the data you explicitly authorize through OAuth ## Location Sharing Crew can use your device's location to enhance features like weather forecasts, nearby place searches, and transit directions. Location sharing works as follows: * **Opt-in by default**: Crew asks for your permission before accessing your location * **Easy opt-out**: Go to **Settings → General** to disable location sharing at any time * **No tracking**: Your location is used only to process your request in real-time — it is not stored or tracked over time If location sharing is disabled, location-dependent tools will still work but may ask you to specify your location manually. ## Account Deletion You can permanently delete your Crew account and all associated data at any time from **Settings → Danger Zone**. When you delete your account: * All conversations and chat history are permanently erased * All connected service tokens are revoked and deleted * All files in My Files are permanently deleted * All memories, preferences, and agent customizations are removed * Your subscription (if any) is cancelled * This action is irreversible For details on how to delete your account, see [Account Deletion](/security-and-privacy/account-deletion.md). ## Responsible Disclosure If you discover a security vulnerability in Crew, please contact us at ****. We take all security reports seriously and will respond promptly. ## Additional Resources * [Privacy Policy](https://crew.you/privacy) — Full legal privacy policy * [Terms of Service](https://crew.you/terms) — Terms governing the use of Crew