Security

Encryption. Data is encrypted in transit and at rest. Credentials and provider keys are held in a managed secrets store, not in configuration files.

Hosting. The Service runs on managed cloud infrastructure in the United Kingdom that its provider patches and certifies. Speech recognition and translation are done outside it, by the providers on our sub-processor list, which says where each one processes; other providers we use may also process data outside it, as International transfers, of the Privacy Policy describes. Our own software is rebuilt and redeployed to take security fixes.

Separation. Every record belongs to one customer organisation, and a signed-in person reaches only their own organisation’s records.

Access. Hosts sign in through our own authentication service, and what a host may do is decided by the role they hold in their organisation. Guests do not have accounts: a guest reaches a session with the code issued for it, so who holds the code decides who can read it.

Staff access. The staff who operate and support the Service can view session content, including kept transcripts and guests’ email addresses, in our systems and, while a provider keeps it, in that provider’s console. When we may do so is set out in Processing only on your instructions, of the Data Processing Terms.

Monitoring, backup and restore. Operational logs and alerts tell us when the Service fails or behaves unusually; how long they are kept is in Retention, of the Privacy Policy. Our databases, which hold account, billing and session records and guests’ email addresses, are backed up to storage separate from the Service, and copies age out on the rotation stated on How Parlabase handles data.

A fuller description of our measures is available to customers on request. Report a vulnerability to hello@parlabase.com.