1. Who we are
Dialt provides a hosted voice engine. Our customer decides what conversation data to send to Dialt and why. We process that data for the customer. We decide how to use the account and billing data that we collect directly.
2. What we record
Dialt currently records every session. We do not yet offer a setting that turns recording or storage off. We are working to add zero data retention, but it is not available today. Contact us before sending live traffic if you need it.
EEA and UK customers may evaluate Dialt with their own voice, synthetic data or non-personal data. Do not send personal data about your callers, employees, customers or other people until Dialt publishes the required customer data-processing and international-transfer terms.
A session record can include the caller's audio, the assistant's audio, transcripts, tool calls and results, timing and turn-taking events, technical information about the client, and feedback or error reports. We store a short fingerprint of the system prompt instead of the prompt itself. We do not record a model's private reasoning.
Customer voice conditioning is no longer offered. For voices created before its retirement, we retain the historical Dialt voice mapping and the speech processing subprocessor may retain source material or a derived voice artifact. Dialt did not retain the uploaded conditioning recording.
For accounts, we collect an email address, a name if provided, sign-in information, roles, API key labels and billing records. API keys and passwords are stored as hashes. Stripe handles payment card details. We do not see card numbers. We do not use advertising cookies or advertising trackers.
3. How we use data
We use data to run the service, show sessions and evaluations, measure usage, bill accounts, prevent abuse, answer support requests, fix problems and improve quality.
Where European or UK data protection law applies to account and website data, we rely on our contract, our legitimate interests in operating and securing the service, consent where we ask for it, and legal obligations. For conversation content, the customer decides the purpose and legal basis and Dialt acts as its service provider.
Authorized Dialt staff may review retained sessions and replay them in quality tests. A useful failure may become a test case while the source session is still retained. It remains customer data and stays linked to the source for deletion requests.
4. Service providers
The providers used for a session or evaluation depend on the feature and route. We use or may use the following providers:
| Provider | What it does |
|---|---|
| Meta, Cartesia, ElevenLabs and Inworld | Speech recognition, speech generation, transcription and evaluation |
| OpenRouter | Routes conversation responses and optional web search to approved providers |
| Google, OpenAI and Anthropic | Language-model processing for product features, evaluation, development and support |
| Microsoft Azure, Together AI, Baseten, CoreWeave, Modal, ModelRun and Fireworks | Hosting for selected conversation models |
| Cloudflare R2 | Session storage |
| PlanetScale | Account, billing and session database |
| Hetzner | Service hosting |
| Stripe | Payments |
| Google and GitHub | Optional sign-in |
| Grafana Cloud | Service monitoring |
These providers receive only the data needed for their part of the service. Some are based in the United States or process data there. We will update this list before a new provider receives conversation content. Contact us before sending data that requires a particular processing region or international-transfer arrangement.
5. Retention and deletion
Dialt does not currently offer a customer-selected retention period. Conversation data may be retained for the life of the account or until we verify a deletion request. Some stored artifacts may be deleted earlier under operational storage lifecycle rules.
Conversation data used in a quality test remains customer data. Service providers may retain data under their own terms and legal obligations. We will support verified deletion requests using the controls available to us.
The conditioned-voice creation and deletion API has been retired. Contact us for verified deletion of historical voice resources. Removing the API does not delete those resources automatically.
We may keep usage, cost, latency, error and service-health measurements that do not include conversation content and cannot be used to reconstruct it.
6. Model training
We do not train shared models on customer conversations, traces or personal data. We do not ask for rights to a person's voice, likeness or identity, and we do not use recordings from customer sessions, including caller or assistant audio, as training data.
We may train on our own synthetic examples and Dialt-generated text after removing personal data and links to a customer session. Any broader use of customer data would require a separate written agreement and a change to this policy.
We may use feedback about Dialt to improve our models and services as described in our Terms of Service, subject to these training limits and this policy's privacy, retention and deletion protections.
7. Access and security
A user can see sessions in their personal account and in any organisation where they are a current member. Authorized Dialt staff can access session data when they need it to run, support or improve the service.
Traffic is encrypted in transit. Recordings live in a dedicated bucket and are served only through signed links that expire in ten minutes. Passwords and API keys are stored as hashes. We hold no SOC 2 or ISO 27001 certification.
8. Your choices and rights
You may have the right to access, correct, export, delete or restrict your personal data. If you spoke to a Dialt-powered application, its operator is your first contact and we will support them.
Where European or UK data protection law applies, you may also object to processing, withdraw consent where processing relies on it, and complain to your local supervisory authority, including the UK Information Commissioner's Office.
Deletion requests are handled manually today. Email legal@dialt.com with the account email and any session IDs so we can verify and process the request. We keep records when the law requires it.
9. Children
Dialt is not directed at children and we do not knowingly collect their data. If your application may be used by children, disclosure and consent are your responsibility.
10. Changes
We will update this page and its date when the service changes, and give notice before any change that materially reduces protection takes effect.
11. Contact
For privacy questions, email legal@dialt.com.