Security & Data Handling
This page summarises how iCura handles data and access at a technical level. For the full list of security controls, see the Security page.
Data residency
All data is hosted and processed within UK sovereign infrastructure, on Microsoft Azure. See Microsoft Azure for the specific services involved.
Tenant isolation
Each organisation's data is logically isolated from every other organisation on the platform. There is no scenario in which one customer's data is visible to another, regardless of role or permission configuration.
Access control
Access follows a role-based model:
- Every user is assigned one or more roles.
- Each role defines exactly which records, actions and reports are visible.
- Permissions are enforced at the data layer — not just hidden in the interface — so a restricted user cannot access restricted data through the API, exports, or the AI layer either.
- Multi-factor authentication is required for all accounts.
Encryption
Data is encrypted in transit (TLS) and at rest. Secrets, keys and certificates are managed through Azure Key Vault rather than stored in application code or configuration files.
Audit trails
Every action taken in iCura — by a user or by the AI layer — is recorded in an immutable audit trail. These records cannot be edited or deleted, including by administrators, and form the basis of the evidence packs generated by iCura 360.
AI-specific controls
AI actions follow the same permission boundaries as human users: the AI layer never surfaces data a given user isn't already entitled to see. Actions above a defined risk threshold — safeguarding concerns, compliance gaps, financial changes — are routed to a human for approval before taking effect. See AI Governance for the full model.
Questions during procurement
If your information governance or IT team has specific questions not covered here — data processing agreements, sub-processor lists, penetration testing history — get in touch and we'll provide what's needed directly.