Data handling and hosting
Current architecture scope and unresolved service facts,3 October2026. Request an accountable data/service review for the intended country and Workspace before relying on contractual or residency assumptions.
Keep business data and account administration distinct
Current architecture scope and unresolved service facts,3 October2026. Request an accountable data/service review for the intended country and Workspace before relying on contractual or residency assumptions.
| Record / decision | Filled example and next owner |
|---|---|
| Workspace business data | A subscribed Workspace has its own database and filestore for business records and attachments. Multiple databases may share one runtime;this architecture alone does not certify tenant isolation. |
| Account / subscription data | Manager holds service account,subscription,entitlement and billing records. The business customer owns its operational data decisions;service/legal responsibilities belong in the approved agreement. |
| Needs approved deployment facts | Hosting location,controller/processors,retention,deletion,backup location,export assistance and support access require named responsibility and approved documents. Independent security,isolation and recovery review remains unpassed. |
Record the exact service,market,source date,accountable owner and approved document for each commitment. Keep unresolved review gates explicit.
Questions for the service order
Confirm the hosting region, legal provider, data categories, access roles, processors, retention, export path, deletion process and backup location for the chosen plan. Ask whether custom integrations transfer data to another system and who manages keys. Validate any country-specific residency or accounting requirement separately before signing.
A buyer should receive written terms reflecting the actual deployment. Review continuity and discuss your data requirements.