> ## Documentation Index > Fetch the complete documentation index at: https://docs.maximem.ai/llms.txt > Use this file to discover all available pages before exploring further. # Security & Trust > How Synap handles encryption, isolation, data residency, deletion, and compliance. This page covers everything an enterprise security review will ask about. If your specific question isn't answered here, email **[security@maximem.ai](mailto:security@maximem.ai)**. ## Encryption | Layer | Mechanism | | ------------------------- | ------------------------------------------------------------------------------------------------------- | | In transit | TLS 1.3 on every SDK connection. | | At rest: application data | AES-256 at rest for vector store and graph store. | | At rest: credentials | API keys are hashed with SHA-256 before storage. Plaintext keys are never persisted on the server side. | | Backups | Encrypted with separate keys; backup-restore is audited. | All traffic between SDK and Synap Cloud is verified against pinned certificates. The SDK never falls back to plaintext if TLS negotiation fails. ## Isolation model Synap enforces isolation at three boundaries: 1. **Instance isolation**: each Instance has its own logical storage namespace across vector and graph stores. Memories from one Instance are never queryable from another, even by accident, because every query is scoped to an Instance ID resolved server-side from your API key. 2. **Scope isolation**: within an Instance, every memory is tagged with USER → CUSTOMER → CLIENT → WORLD scope. A user-scoped retrieval never returns memories from a different user, regardless of similarity. See [Memory Scopes](/concepts/memory-scopes). 3. **Network isolation**: Synap Cloud is network-isolated per region. Customer data never crosses regions. ## Data residency | Region | Location | Status | | ------------- | --------- | --------------------------------------------------------------- | | US East | Virginia | Available | | EU Central | Frankfurt | Available | | Other regions | n/a | On request, contact [sales@maximem.ai](mailto:sales@maximem.ai) | You pick the region at Client creation. Memories stay in that region for their entire lifecycle, including backups and replicas. Cross-region replication is not done automatically. ## Deployment options | Option | Availability | | --------------------------- | ---------------------------------- | | Synap Cloud (fully managed) | All plans | | Private / VPC deployment | Enterprise | | Self-hosted / on-premise | Enterprise (self-hosted licensing) | Synap is offered as a fully managed cloud service, and, on Enterprise, as a private/VPC deployment or a self-hosted/on-premise install for teams with strict data-residency or air-gap requirements. The open-source SDK ([github.com/maximem-ai/maximem\_synap\_sdk](https://github.com/maximem-ai/maximem_synap_sdk)) is available independently of the managed platform. ## Enterprise access controls | Control | Availability | | ---------------------------------------------- | ------------------------------------------------------------------------------------ | | SSO / SAML | Enterprise | | Role-based access control (RBAC) | Enterprise (configurable) | | Bring-your-own-key (BYOK) for the LLM pipeline | Pro and above (see [Pricing → BYOK](/resources/pricing#byok-bring-your-own-llm-key)) | | Custom SLAs & dedicated customer success | Enterprise | Contact **[sales@maximem.ai](mailto:sales@maximem.ai)** to enable SSO/SAML, RBAC, VPC/private deployment, or self-hosting. ## Deletion guarantees Synap supports per-memory, per-conversation, per-user, per-customer, and per-instance deletion. * **Soft delete** (default): the memory is removed from retrieval results immediately and purged from active stores within 24 hours. The deletion is logged to the audit trail. * **Hard delete** (on request): removes the memory from backups as well, within 30 days. Use this for GDPR Right-to-be-Forgotten and CCPA Right-to-Delete requests. Contact **[privacy@maximem.ai](mailto:privacy@maximem.ai)** to initiate. Deletion cascades through the entity graph: when a user is deleted, any entities exclusively referenced by their memories are also removed. Entities co-referenced by other users (e.g., a shared product entity) are retained. ## Compliance posture | Framework | Status | | ------------- | ----------------------------------------------------------------------------------------- | | SOC 2 Type II | In progress, target audit completion Q3 2026 | | GDPR | Compliant. DPA available on request from **[legal@maximem.ai](mailto:legal@maximem.ai)**. | | CCPA | Compliant. | | HIPAA | Not currently certified. Do not send PHI to Synap. | | ISO 27001 | On roadmap (2026). | Synap maintains a vendor security questionnaire (CAIQ + Lite SIG). Request via **[security@maximem.ai](mailto:security@maximem.ai)**. ## Sub-processors Synap maintains a public sub-processor list. See the Synap [sub-processor disclosure](https://maximem.ai/subprocessors) for the current list. ## Audit logs Every dashboard and SDK action is logged with `correlation_id`, principal (user / API key), timestamp, action, and resource. Audit logs are retained for 90 days by default and can be exported from the Dashboard (on Enterprise plans). ## Reporting a vulnerability Email **[security@maximem.ai](mailto:security@maximem.ai)** with reproduction steps. We acknowledge within 24 hours and aim to issue a patch within 7 days for critical vulnerabilities. We do not currently run a public bug bounty but will reward responsibly-disclosed issues. ## What we do NOT do Stated explicitly so there are no surprises in your security review: * **We do not train models on customer data.** * **We do not share customer data with sub-processors beyond what is listed above.** * **We do not allow Synap engineers to query customer data without a documented support ticket from the customer.** All such access is logged. * **We do not retain deleted memories.** Once a hard delete completes, the data is gone, including from backups within the 30-day window.