> For the complete documentation index, see [llms.txt](https://docs.sesori.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sesori.com/get-started/security-and-privacy.md). # Security and privacy Sesori is local-first: your code, repositories, assistant processes, and terminal commands stay on your computer. The mobile app reaches them through the Sesori Bridge. This page explains the technical boundary in plain language. The [Sesori Privacy Policy](https://sesori.com/privacy/) is the authoritative source for personal-data processing, retention, rights, and sub-processors. ## Ordinary session traffic The phone and Bridge establish an encrypted application channel using X25519 key exchange and XChaCha20-Poly1305 authenticated encryption. Ordinary session payloads pass through the relay as opaque encrypted frames, so the relay does not ordinarily have plaintext access to prompts, responses, or file content in transit. The relay still processes information needed to operate the service, including account identity, connection and routing metadata, session and project identifiers, timestamps, delivery status, and limited device or app metadata. {% hint style="warning" %} The relay delivers the public keys used to establish the encrypted channel. That key delivery currently trusts Sesori's relay infrastructure and is not independently authenticated out of band. A compromised relay could attempt a man-in-the-middle attack. End-to-end encryption protects ordinary payloads from passive relay access; it does not remove the relay from the trust model. {% endhint %} ## Features with a different data path Some features cannot remain entirely inside the ordinary encrypted relay channel: * **Push notifications:** Sesori stores push tokens and sends notification payloads through Apple or Google. Depending on your settings, a notification can include limited session metadata or a partial snippet and may appear on the lock screen. * **Voice input:** Recorded audio is sent to Sesori and a transcription provider. The generated text is returned to the prompt field for review. The current policy says audio and transcripts are not retained after processing, except where limited retention is needed for operations, abuse prevention, security, incident response, or law. * **Short text features:** Invoked features such as session-title or branch naming can send limited readable text to Sesori and a configured processor. * **Support and diagnostics:** Logs, screenshots, attachments, crash data, or other details you submit or that supported diagnostics collect can be readable by Sesori and its service providers. Review the [Privacy Policy](https://sesori.com/privacy/) for the current provider list and retention details. ## Your assistant and model provider Sesori's phone-to-Bridge encryption covers the Sesori connection. It does not replace the security, permission, or privacy model of your selected AI coding assistant or model provider. The assistant runs with whatever local access and approval configuration you give it. Prompts, source code, tool output, or other context may be sent by that assistant to its configured model provider. Review the provider's terms and configure the assistant's sandbox and permissions for your risk level. {% hint style="danger" %} **YOLO mode** in Sesori tells the Bridge to approve permission requests automatically. It can let an assistant run consequential tools without waiting for you. Use it only in an isolated environment or on a project and computer where you accept that risk. Assistant-specific bypass modes may apply independently. {% endhint %} ## Practical safeguards * Keep the Bridge and mobile app updated. * Use trusted projects and review project-local assistant configuration before opening them. * Prefer the assistant's sandbox and approval controls over unrestricted modes. * Hide sensitive notification previews at the operating-system level. * Review a session's [local changes](/user-guide/reviewing-changes.md) before committing or merging them. * Stop the Bridge with `Ctrl+C` when you no longer want remote access to that computer. ## Privacy rights Sesori does not currently provide self-serve account deletion in the app. To request deletion or exercise another privacy right, follow [Delete your account](/user-guide/delete-account.md). Requests are handled by email after identity verification. --- # 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://docs.sesori.com/get-started/security-and-privacy.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.