> For the complete documentation index, see [llms.txt](https://salesa.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://salesa.gitbook.io/docs/support/security.md). # Security Salesa is built with security as a core part of its design.\ Every connection, message, and data update is handled safely using trusted Google authentication and encrypted communication. ### **Authentication and Access** Salesa uses **Google OAuth 2.0** for all Gmail and Google Sheets connections.\ This means Salesa never sees or stores your passwords.\ All access is granted and controlled directly through your Google Account. When you connect Gmail or Google Sheets, the system requests only the permissions needed for reading and updating deal-related data.\ You can revoke this access at any time from your Google Account or inside the Salesa integrations page. ### **Data Encryption** All communication between your browser, Salesa servers, and Google APIs is encrypted using **HTTPS and TLS 1.2+**.\ This ensures that your email metadata, Sheet data, and AI-generated insights cannot be intercepted or read by unauthorized parties. Stored data such as organization information and configuration settings is encrypted at rest using industry-standard encryption. ### **Data Handling and Privacy** Salesa does not permanently store your emails or message content.\ Only the metadata needed to detect deal intent is processed temporarily and used to update your Google Sheet.\ No personal or unrelated messages are stored, shared, or used for training AI models. Your Google Sheets remain in your own Google Drive.\ Salesa only accesses them during sync operations and never makes a copy outside your account. ### **Organization Controls** Admins can manage team access and integrations at any time.\ If a member is removed from the organization, their Gmail connection and access are revoked automatically.\ You can also delete your entire organization and all related data through the settings page. ### **Compliance** Salesa follows standard data protection principles aligned with **GDPR** and **Google Workspace Security Policies**.\ No customer data is shared with third parties except for secure API communication with Google services. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://salesa.gitbook.io/docs/support/security.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.