How we protect your risk data
Risk Companion is hosted in the European Union. This page sets out the controls we operate, and what we do not claim.
Encryption in Transit
Traffic is encrypted at every external boundary. Requests made without encryption are redirected rather than served.
Encryption at Rest
Databases, object storage and the file system holding uploaded documents are encrypted at rest. Backups inherit that encryption.
A Database per Customer
Each customer environment has its own database and its own credential, scoped to that database alone. The environment a request belongs to is resolved server-side and cannot be supplied by the user.
EU Hosting
The application, its databases, file storage and backups run inside the European Economic Area. One exception is set out below.
Single Sign-On
Users sign in with a password or through your own identity provider using single sign-on. Passwords are stored hashed, and sign-in attempts are rate-limited.
Role-Based Access Control
Roles determine what each user can do. Access to an individual project is checked at the point of each request, not only at sign-in.
Backups and Tested Restores
Customer databases are backed up on a regular schedule, and restores are tested rather than assumed.
No Standing Access to Your Data
We hold no standing access to your environment, and the product has no user-impersonation facility. Where support access is needed it is granted explicitly: read-only, time-limited, requiring a recorded reason, logged, and notified to you.
A Sub-processor Register
Every third party that processes your data is named in a register we maintain and review, with what it processes and where. It is available to customers.
What is in your contract
Risk Companion is the processor for the data your users hold in the service, and you remain the controller. The points below are obligations we take on in our data processing terms, not statements of intent.
We act as your processor under signed data processing terms, with EU hosting and a maintained sub-processor register.
Our processes are aligned with ISO 27001 and mapped against Annex A. Risk Companion is not certified, and we do not present alignment as certification.
Artificial intelligence
Your data is not used to train or fine-tune any model. Where an AI feature retrieves data it does so under the permissions of the user who asked for it, checked at each access rather than once at the start.
In-product suggestions send a narrow set of fields that is fixed in code. No uploaded documents, no account details, and no data from any other customer. Every output is a suggestion, and nothing is written to your environment without an explicit action by one of your users.
That suggestion traffic currently reaches the model provider outside the European Economic Area, which is the one exception to the residency statement above. The path is being moved to EU-region inference. Until it is, the provider is named in our sub-processor register, and we seek your authorisation through that register.
What we do not claim
Risk Companion is not certified under ISO/IEC 27001 or SOC 2. We align our processes with ISO 27001 and map them against Annex A, which is a different thing, and we would rather say so than let the two be read as the same. The infrastructure we run on is certified in its own right, and we distinguish the controls we operate from the ones we inherit.
We do not publish an uptime service level agreement, and we have not published a recovery time or recovery point objective. Where availability commitments matter to you, we would rather agree them with you than advertise a number.
We keep a register of the gaps we know about, with an owner and a target date against each, and we give it to customers rather than waiting to be asked. It comes with a detailed security pack. Write to [email protected] and we will send both under our confidentiality terms.