{"slug":"security-and-governance/privacy","title":"Privacy in SpineWorkspace","section":"security-and-governance","sectionLabel":"Security & Governance","status":"unclassified","type":"document","path":"security-and-governance/privacy.mdx","bytes":960,"description":"SpineWorkspace treats customer data with strict privacy controls: scoped access, minimum-necessary retrieval, and configurable retention and residency.","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nPrivacy in SpineWorkspace is enforced at the platform layer. Customer data lives inside the tenant boundary, connectors declare scopes upfront, and Twin and agents read only what a capability authorizes.\n\n## Privacy Principles\n\n- **Tenant isolation** — customer data stays inside the tenant boundary.\n- **Minimum-necessary access** — connectors and capabilities declare scope explicitly.\n- **Configurable retention** — organizations control how long context is retained.\n- **Configurable residency** — data lives in the region the organization selects.\n\n## Related\n\n- [Security](/security-and-governance/security)\n- [Governance](/security-and-governance/governance)\n- [Compliance](/security-and-governance/compliance)"}