Security
How your data is protected.
This page states what the platform does today. Where something is not yet in place, it says so.
Built into the product
| Separation between organisations | Every record belongs to one organisation, and the rule is applied where data is read, not only on the screen. A white-label sign-in page admits only that organisation's people. |
|---|---|
| Roles and permissions | Access is granted by role, down to department level. External auditors see only the engagement they are scoped to and can never edit a record. |
| Separation of duties | A control is marked compliant only when a reviewer from another department accepts it. Nobody can approve their own work. |
| Evidence integrity | Each evidence file is fingerprinted with SHA-256 when it arrives and earlier versions are kept, so a change after the fact is detectable. |
| Activity history | Changes, approvals and AI-assisted actions are recorded with who did them and when. |
| AI use | AI is optional and the product works fully without it. It reads only your own organisation's records and never approves, closes or decides anything. |
| Your data stays yours | You can export your organisation's data at any time. |
Hosting and operations
| Encryption in transit | All traffic is served over HTTPS. |
|---|
Ask us for the current hosting region, backup schedule and recovery objectives and we will send them in writing: contact us.
Our own certifications
Radiatus does not yet hold an independent SOC 2 or ISO 27001 certification for this platform.
We will publish the report here when we do. Until then we answer security questionnaires directly — send us yours.
Reporting a vulnerability
If you believe you have found a security issue, write to info@radiatus.com. Please give us the chance to fix it before you disclose it.