Security overview
In progressRINADS is designed so AI assistance operates inside organisation context, permissions, and human approval where required.
Security
RINADS is designed so assistance, recommendations, and supported actions stay inside organisation context, permissions, and human approval where required.
RINADS is designed so AI assistance operates inside organisation context, permissions, and human approval where required.
Organisation membership and authenticated sessions gate product access.
Business data access is organised around organisation context rather than a shared global workspace.
Product actions are intended to respect the same authorization boundaries as the operating system.
Sensitive or meaningful actions can be held for review instead of treating AI output as automatic authority.
Event and audit primitives exist so important system activity can remain traceable.
Data handling practices will be published in counsel-approved privacy and DPA materials.
Model provider use depends on deployment configuration. No blanket retention or training claim is published here.
Transport encryption is used for public HTTPS surfaces. Broader encryption claims require verified inventory.
Backup and recovery posture depends on the deployed environment and is not published as a universal SLA here.
Secure development practices are evolving with the platform. Formal programme claims are not published yet.
Incident response process will be published when counsel-approved and operationally ready.
See /legal/subprocessors when the counsel-approved list is published.
No SOC 2, ISO 27001, GDPR, DPDP, or HIPAA compliance certification is claimed on this page unless explicitly verified and approved.
Report suspected vulnerabilities through the security contact channel below.
Use /contact?intent=security or the company contact path for security questions.
Questions about security posture or subprocessors? Contact the team or review subprocessors.