Our principles
- Least access. People and systems get only the access they need, for as long as they need it.
- Separation. Each customer's data is kept logically separate and is never shared with or visible to other customers.
- Defence in depth. We layer protections so no single failure exposes customer data.
- Brand privacy. Customer-facing links, emails and call recordings are delivered through Orra's own domains wherever possible.
Data protection
- All traffic between users, callers' systems and Orra is encrypted in transit using current TLS.
- Stored data, including recordings, transcripts and databases, is encrypted at rest by our infrastructure providers.
- Recordings and transcripts are accessed through authenticated access rather than public pages.
- Retention periods are applied to stored data, and deleted data is removed from backups within 35 days.
Access control
- Customer dashboards use individual logins for each user, with roles controlling what each person can see. Access rules are enforced in the database itself, so one business can't read another's records, even through the API, and this is tested automatically.
- Staff and contractor access to production systems uses individual accounts with multi-factor authentication where supported, is granted on a need-to-know basis, and is removed promptly when no longer needed.
- Orra HQ administration needs a separate admin role and a completed two-step sign-in, checked on the server, not just on screen. Sensitive actions are written to an append-only audit log.
Secure development
- Changes are tested before release.
- Secrets and API keys are kept out of source code and stored in protected environment configuration.
- Dependencies and systems are kept up to date with security patches.
- Source code is kept in private, access-controlled repositories with off-site backup.
Abuse and fraud prevention
- Public voice demos are protected by rate limits, call-length limits and automated detection of abusive, bot or time-wasting callers, with repeat offenders blocked.
- Trial sign-ups are checked to prevent multiple or fraudulent accounts.
- Outbound calling is subject to time-window controls and authorisation rules set by each customer.
Availability and resilience
- The platform runs on established cloud infrastructure with redundancy.
- Customers can set a fallback number so calls reach a person if an Agent is unavailable.
- Backups are taken regularly.
- Usage and credit levels with key providers are monitored, with alerts before limits are reached.
Incident response
We have a documented process to detect, contain, investigate and recover from security incidents. Where an incident affects customer personal data, we notify affected customers without undue delay, within the timescales set out in our Data Processing Agreement, and support them in meeting their own obligations.
People and suppliers
- Everyone with access to customer data is bound by written confidentiality obligations.
- Suppliers that process customer data are assessed before engagement and bound by data protection terms. See Sub-processors.
Reporting a vulnerability
If you believe you have found a security vulnerability in Orra, please email hello@orrahq.com with the subject line “Security”. Please give us reasonable time to investigate and fix the issue before telling anyone else, do not access or change other people's data, and do not run tests that could disrupt the service. We will acknowledge your report within 3 Working Days and will not take legal action against good-faith research that follows these rules.
