Trust & compliance
Dialfyne is usage-based sales software: AI roleplay, a human-led power dialer, and approval-first email. 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. When you enable AI-first outbound, documented consent is checked when the session is created and again at dial time.
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 initiate every call, email, or SMS sent through the Services, including sequences you configure to send automatically. Those controls are there so your team can run outbound with a clear process.
Yes. Cold outbound is a core use of Dial, Email, and Managed Outbound. Your team owns the list, the offer, and the outreach laws that apply. On Managed Outbound, Dialfyne operators work from your instructions.
A human places the live sales call. Models transcribe, score, draft, and coach. Optional AI-first outbound, when you enable it, checks documented consent when the session is created and again at dial time. Third-party models run inference on bounded prompts so we can deliver those features.
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. An optional beep can play when recording starts. In all-party consent states, including California, your team handles disclosure before the conversation continues. Default retention is 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@.