Security
The safest data is the data we never hold. Here is what we do with the little we do.
Encrypted on the device
The local database on each computer is encrypted at rest, with its key held in the operating system’s secure key store.
Sign-ins kept on the device
Mailbox, calendar and chat tokens are stored in the secure key store of the computer that uses them, never on our servers.
Scores-only cloud
By default our cloud holds workspace settings, members and the results that sync: scores, reasons, next steps, revenue figures. A workspace admin can opt in to cloud analysis (text read and not kept) or a cloud workspace (content stored, encrypted per workspace); every change is in the audit log.
Roles and isolation
Each workspace is isolated in the database with row-level security. Roles decide who sees revenue; message content reaches only the people assigned to a client, and a person’s own call figures only that person.
Audit log
Sign-ins, invitations, role changes and connections are recorded in an audit log owners and admins can read.
Encrypted in transit
Every connection to rltnship and to the services it reads from uses TLS.
Where we are
- Hosting
- EU by default; any region on Scale
- Single sign-on
- On the Scale plan
- SOC 2
- Planned, not yet started
- Penetration test
- Planned before public launch
Report a vulnerability
Email security@rltnship.ai. We reply within two working days.
Hear about the next lost client while you can still keep them
We are working with a small group of design-partner agencies through the beta. Partners get the product free during the beta, a direct line to the team, and launch pricing locked in.