Tenant and application isolation
Every application belongs to one developer workspace. Agents, customers, calls, and recordings are scoped to that application and are not shared across tenants.
Security and privacy
Context-aware does not mean context-everywhere.
Applications control the fields they send and which fields agents may see. Customer, agent, and developer access are scoped separately. This page describes the controls in the platform today and the ones still being built.
Controls in place today
Separate identities
Customers, support agents, and developers authenticate through distinct flows with distinct authorization scopes. An agent cannot use a developer console, and a customer cannot enumerate agents.
Short-lived call capabilities
Support tokens and media credentials are issued per call and expire quickly. They cannot be replayed to join an unrelated conversation.
Encrypted media in transit
Call audio uses WebRTC with peer-to-peer media where the network allows and a TURN relay fallback otherwise. Media is encrypted in transit on both paths.
On-device transcription
Speaker tracks are transcribed on the agent's device. Raw audio is not sent to a third-party speech service as part of the default flow.
Private recording storage
Recordings and transcripts are uploaded to private, S3-compatible storage using short-lived, call-scoped URLs, and are readable only by authorized reviewers.
In progress
We publish these as roadmap items rather than claims. Ask us for current status before making a compliance decision.
- Signed webhook delivery with replay protection
- Automatic recording retention and deletion policies
- Customer-owned recording export connectors
- Workspace audit log views
- Data export and deletion self-service workflows
- Published subprocessor list and regional processing options
Recording consent
Consent is a shared responsibility.
RingDesk provides consent-aware recording controls and records only when recording is enabled for the call. You remain responsible for the disclosure language, the legal basis, and the retention rules that apply in the markets you operate in.
Agent performance metrics are provided for operational visibility. They are not designed or marketed as an opaque employee-ranking system.
- Recording is per-call and controllable by the agent
- Customer and agent tracks stay separated
- Transcripts are generated on the agent device
- Recording access is limited to authorized reviewers
What RingDesk does not do
Scope limits are part of the security story.
- No PSTN phone numbers or carrier service
- No outbound sales dialing
- No omnichannel inbox or system of record
- No autonomous AI voice agents
- No calling without an internet connection
Questions about the security model?
Ask for the current architecture review before you build against RingDesk.