Security
Every organisation on RALPH has a database of its own, in the UK or the EU, locked to that organisation, and every change to your records is recorded with who made it, people and AI agents alike.
A database of its own
Every organisation runs in a database of its own. Your records never share a table with another organisation’s. Alongside them, a shared database holds what RALPH needs to run the service around them, such as sign-in and subscription records.
In the UK or the EU
RALPH keeps each organisation’s data in the UK or the EU. Today that means the UK: every organisation’s database, RALPH’s servers and the shared database run there. An organisation’s region is set when it is set up, and can’t be changed from within RALPH.
Locked to your organisation
Your records are locked to your organisation. The database enforces it, not just the application.
Secrets encrypted at rest
The credentials RALPH uses to reach your organisation’s data are encrypted at rest.
Sign-in and sessions
- Sign in with Google. RALPH asks Google for your basic profile, keeps only your name, your email address and Google’s id for your account, stores no password, and keeps no Google token after you sign in.
- Sign in with Email. Every sign-in needs a code sent to your email address and a second step, such as an authenticator app. RALPH stores no password.
- Sessions are protected. Your browser holds a session cookie that means nothing on its own and goes only to RALPH. Signing in also sets a cookie that tells this website only that your browser has signed in, so it can take you straight to the app; it names no one and signs no one in.
- Sessions end. After 7 days unused, or 30 days at most, you sign in again. You can see your sessions and end any of them, and signing out clears what the browser holds.
Connected apps and agents
Access keys for agents and scripts carry only the permissions they’re given, and every key has an expiry date, a year ahead unless set otherwise. Apps you connect, such as Claude or ChatGPT, act only with access you grant, and that access ends on its own after 90 days at most.
Encrypted in transit
All traffic to RALPH is encrypted in transit.
Every change on record
Every change to your organisation’s records is recorded: who made it, with which credential, for whom, and when, agents included. The record can’t be edited, and your organisation’s admins can read who made each change, for whom and when.
Questions, answered
- Does RALPH share one database between customers?
- No. Your organisation’s records live in a database of its own. Alongside them, a shared database holds what RALPH needs to run the service around them, such as sign-in and subscription records.
- Where is our data kept?
- In the UK. Every organisation’s database, RALPH’s servers and the shared database run there today. RALPH keeps your data in the UK or the EU.
- Does RALPH send our records to an AI model?
- RALPH’s own servers use AI models to read photos of tech-log pages and to map spreadsheets an admin imports. What we send to them can include personal data. Otherwise agents work through the AI assistant you connect, such as Claude or ChatGPT, under your own account, and see only what your permissions allow.