Legal Policies

How call data is handled

Voice AI raises data questions that ordinary software does not, because a phone call produces a recording, a transcript, and a set of extracted personal details all at once. Our position across every deployment model is the same on the essentials: encryption in transit and at rest, configurable retention windows with automatic expiry, role-based access that separates reading a call summary from replaying the audio, and a full access log behind both.

• Recording consent. Consent prompting can be configured per jurisdiction to reflect one-party and two-party consent rules, and the prompt is delivered consistently on every call rather than left to an agent's memory.
• Redaction. Payment card data and other sensitive identifiers can be masked in stored transcripts and muted in recordings, so staff reviewing a call never see data they have no reason to see.
• Data-subject requests. Deletion, export, and rectification cover the summary, transcript, and recording together, and the deletion itself is recorded — which is the artefact an auditor actually asks for.
• Outbound calling rules. Do Not Call scrubbing runs before the dial, calling windows follow the recipient's local time zone, and an opt-out spoken on any call propagates across every active campaign.
• Data residency. On a self-hosted deployment, the application, database, recordings, and transcripts live entirely inside your own infrastructure and never transit a Ringlyn-hosted production system.

Licensing agreements for self-hosted and white-label deployments

The policies above govern use of the hosted platform. Two additional commercial arrangements are covered by their own written agreements, issued before purchase and reviewed on the call rather than clicked through:

Comparing the two, or unsure which applies? See the white-label overview or contact us and we will send the relevant agreement before any commitment.