How AssetSort handles your data

Every organisation's data is isolated by the API's authorization layer: every request is checked against your live membership and, for MSP staff, your live client scope, before any data is read or written. That scope is re-derived on each request rather than baked into a session, so revoking someone's access to a client takes effect immediately — including on any calendar feed they'd subscribed to. The isolation rules are covered by an automated test suite rather than resting on policy alone. All data is encrypted in transit and at rest. No Microsoft 365 passwords or tokens are stored for your tenant: AssetSort keeps only your tenant ID, and its own app secret lives in Google Secret Manager, never in the application database. Calendar feed links are stored only in hashed form, and sign-in tokens and link secrets are masked in our application logs. When an MSP hands a client over, the client becomes standalone the moment the hand-over completes (straight away when it's handed to one of the client's own admins, or when an invited new owner accepts) — its data stays intact, the MSP's staff lose access at that moment, and the client stops inheriting the MSP's plan. An archived client is read-only for 30 days and then permanently deleted. For current backup and retention commitments, ask us via the contact details in "How to reach support" — we'd rather give you the live figure than an out-of-date one here. The formal terms are in the Privacy Policy (/privacy), the data processing agreement (/legal/dpa), the sub-processor list (/legal/subprocessors) and the data portability statement (/legal/data-portability).