Trust & compliance
Dialfyne is usage-based sales software: AI roleplay, a human-led power dialer, and email with review controls. You own the list. We give you calling hours, suppressions, recording controls, logs, and contracts so the team can run outbound with a process.
Start with the DPA and the subprocessor list when you need vendor detail. Here is how each product runs.
Turn these on in your workspace. They are the same switches your team uses on a normal outbound day.
Set when outbound dials are allowed for the workspace, including timezone-aware hours.
Keep an internal do-not-call / do-not-email list. A stop on one channel can stop the other where the products are connected.
Recording is a workspace choice. Optional beep at start. Default retention is described in the Privacy Policy (typically 12 months for recordings).
Human-led dialing is the standard path. Optional AI-voice outbound checks the customer-supplied consent record when the session is created and again at dial time; the customer still determines whether the consent is legally sufficient.
Generated email is meant to be reviewed by a human before it leaves. Managed Outbound keeps that review step.
Customer data stays in that Customer’s workspace. Product stats we use internally are aggregated so they are not tied back to your accounts.
Recordings, transcripts, email bodies, and roleplay audio are Customer Data used to provide the Services. We encrypt in transit (TLS 1.2+) and at rest on the primary database, isolate workspaces, and notify Customers of a personal data breach affecting their data within 72 hours of becoming aware, as set out in the DPA.
Gemini, Anthropic, OpenAI, and optional other models run inference on bounded prompts for transcription, scoring, drafts, and coaching.
Some research paths can call Moonshot (Kimi). That path is optional; location is listed with the other subprocessors.
Calling data, recordings, and email live in your workspace. Product-level stats we keep are aggregated.
These documents are part of how you buy and use Dialfyne. The DPA is included when you accept the Terms.
Dial is a human-led power dialer. A real rep is on the call. Your workspace sets calling hours, DNC and suppressions, and recording. You control calling and email settings. Platform Email supports manual review or automatic approval for campaigns, with quality and send-time checks.
Dial, Email, and Managed Outbound support cold B2B workflows. Your team owns the list, offer, consent basis, calling windows, suppression policy, and the federal and state rules that apply. On Managed Outbound, Dialfyne operators work from your approved brief. Product controls do not replace legal review.
A human places the standard live sales call. Models transcribe, score, draft, and coach. Roleplay uses AI buyers for practice. Email uses company research tied to your offer and follows your campaign review settings.
TLS 1.2+ in transit, encryption at rest on the primary database, workspace isolation, and vendor terms with subprocessors. Infrastructure providers publish their own audit reports. We notify you of a personal data breach affecting your Customer Personal Data within 72 hours of becoming aware, as set out in the DPA.
Third-party models process data to provide the feature you asked for. Subprocessors are contractually limited to that use. You can email [email protected] if you want Dialfyne to keep your recordings and transcripts out of our own product-improvement work.
You choose whether Dial records, and an optional beep can play when recording starts. Recording and disclosure rules vary by jurisdiction; your team is responsible for the notice and consent required for each call. Default retention is described in the Privacy Policy.
Primary storage is in the United States. The Data Processing Addendum at dialfyne.com/dpa is part of the Terms. Subprocessors are listed at dialfyne.com/subprocessors. EEA, UK, and Swiss transfers use Standard Contractual Clauses.
Privacy and data-subject requests go to privacy@. Contract and DPA countersign requests go to legal@.