A control boundary, not a blanket claim.
Hosting, storage location, backup, key management, subprocessors, and deletion requirements are confirmed for the selected product and written deployment scope. Bank programmes receive a separate architecture and assurance review.
Controls in the current operating path.
| Control | Current boundary |
|---|---|
| Tenant isolation | Authenticated organization scope is enforced in the API and database policies. |
| Authorization | Roles gate administration, review, reporting, and platform-operator actions. |
| Provenance | Source batch links persist through alerts, cases, reports, decisions, and exports. |
| Payment access | Workspace entitlement, row allowance, seat limit, status, and retention are server controlled. |
| AI assistance | Model output is kept separate from deterministic rule results and requires human review. |
Data lifecycle follows the commercial term.
Review Pack workspaces close after 30 days. Continuous workspaces remain available while active and preserve export access for 30 days after cancellation before scheduled deletion. A refund revokes paid access; retained evidence follows the recorded disposition workflow.
AI output remains advisory.
Narrative assistance receives bounded case facts through the configured model path. It does not alter rule evaluation, create hidden evidence, approve a case, or file a report. Reviewers must validate the generated text against attached evidence.
Need a bank security review?
Define the boundary →