Privacy and data handling.
Last updated: October 27, 2026
This notice separates the public DialBreeze website from the operational data used by a provisioned calling account. Send privacy and data-handling questions to support@dialbreeze.com. Use that address to confirm the arrangements required for your account before uploading production lists or recordings.
Payments, support messages and account data.
After checkout, we receive the order result needed to open your workspace: your plan, seat count, amount and signup email. We email a set-password email to that address.
A support email may contain your contact information, billing email, plan, the problem reported and any record references or attachments you choose to send. Include the minimum information needed to investigate. Do not put payment-card details, passwords, carrier credentials, complete prospect lists or unnecessary health information into an ordinary support message.
Checkout opens your software subscription. Calling credit is optional at checkout, but you need credit to dial; add it any time from your dashboard. Each plan includes phone numbers (Basic 1, Breeze 3, Jetstream 5 per seat), and extra numbers are $5/month each. Support messages are distinct from operational data in your workspace.
Website delivery and technical requests.
The public site is delivered through Cloudflare. Like any web request, a page visit sends Cloudflare and our server the technical information needed to deliver it, such as your network address and browser details. Fonts and images are served from this site, not from a third-party font service.
Google Analytics (measurement ID G-QRSK6E18GH) records page views and checkout steps (plan, seats, price) so we can see which pages and ads bring customers. It does not load when your browser sends Global Privacy Control or Do Not Track. Outside the EEA, UK and Switzerland, Google can receive advertising signals (ad storage, ad user data, ad personalization) so we can measure which ads bring customers; in those regions they stay off. IP addresses are anonymized. Turn off analytics for this browser.
Website delivery, email delivery and billing are separate processing activities, each listed under processors below. Your browser's network and privacy controls can help you inspect or restrict requests.
This notice does not promise that infrastructure logs contain no identifying information or that every record disappears as soon as a browsing session ends. Ask the team for the current logging and retention arrangement if it is material to your use. We do not use a general statement about the website to describe the privacy behavior of every third-party service.
First-party attribution.
We store a first-party cookie named db_attr_v1 for up to 90 days. It holds the landing path, the referring site name, campaign tags, ad click identifiers, a creator referral code, a random visitor id, and both the first visit and the latest visit that brought a new click identifier, campaign tag, or creator referral code. A separate cookie, db_vid, holds a random visitor id for 90 days. When a Google Analytics client id is already present, we copy that id into the same record. These cookies do not hold your name, email address, or the full referring address. We do not set them when your browser sends Global Privacy Control or Do Not Track, or after you turn off analytics for this browser.
Payments.
We do not collect full payment details on this website. For a missing receipt, cancellation or billing question, contact support from your billing email. Do not send full payment details.
Leads, calls and after-call processing.
A production calling workflow can involve lead and list records, phone numbers, call attempts and timestamps, dispositions, operator notes, follow-up tasks and available recordings. Those outputs may repeat details spoken during a conversation; they should be handled with the same care as the underlying record.
Your operational data belongs to you. Ownership is different from physical storage location, a particular hosting architecture or a guarantee that no provider processes the data.
Call processing and data.
- Call recording is optional. When it is on, the audio is saved to DialBreeze servers so you can play it back from your account. Our calling carrier may hold a short-lived temporary copy while a recording is processed.
- On Breeze and Jetstream, transcription runs after the call ends, not during it. A speech-to-text service turns the audio into text, and the transcript and AI notes are stored in your account.
- After the call ends, the transcript (never the audio) is used to write AI notes, stored in your account. Breeze and Jetstream only.
- Retention in your workspace is not configurable yet. To delete data, email support@dialbreeze.com and we delete it on request.
Processors.
These companies process data on our behalf, or on yours when you load calling credit:
- PayPal: billing and payments.
- Amazon SES: email delivery.
- Cloudflare: network delivery and protection.
- Google: Google Analytics page measurement and ad measurement. It does not load when Global Privacy Control or Do Not Track is on. Advertising signals are off in the EEA, UK and Switzerland.
- Calling carrier: calls, numbers and carrier services from our calling carrier, which may use its own sub-processors; and, on Breeze and Jetstream, a speech-to-text service and the language models that write call notes from the transcript.
Our carrier partner and credentials.
Production telephony runs on DialBreeze's numbers through our carrier partner, which handles carrier services and the associated carrier data for those numbers. You remain responsible for your workspace's users, passwords and calling decisions.
Do not paste a password into email, a screenshot or an ordinary support note. Ask for the current credential-handling details when assessing your security requirements.
Recording and consent.
You are responsible for giving any notice and getting any consent that recording a call requires under federal and state law. Some states require the consent of every party to a call, so a notice that works in one state may not be enough in another. Call recording is off unless you turn it on in Settings and confirm you have consent.
The product's internal DNC, calling hours and attempt limits help you run your compliance program. DialBreeze does not collect, verify or store proof of consent, and it does not perform the federal-registry scrub. The responsibility table shows what DialBreeze does and what you must do.
Minimize unnecessary personal information in notes and recordings. Review important details against the recording. The calling controls page is educational and is not legal advice.
Access, correction, export and deletion.
Contact support to discuss access to your operational records, a correction, an export or a deletion request. Identify the account and the scope of the request without sending an entire dataset in the first message. The team may need to confirm that the requester is authorized before disclosing or changing account data.
Deletion is by request: email support and we delete the data you identify. There is no configurable retention period yet, and no self-service export tool. Confirm the export format before ending service. Billing, security and operational records can involve different handling requirements; resolve any required written terms before uploading data.
Canceling the DialBreeze subscription ends access to the numbers we provide. Read the subscription terms and contact support for any records request.
Questions before you start.
Bring your storage, access, processor and retention requirements to onboarding, before you move real lists into your workspace. A privacy requirement should be resolved explicitly, not inferred from a plan name or a claim about who owns the phone number.
For questions about this notice or your account's data, email support@dialbreeze.com. Include a way to reach you and the specific issue, and leave credentials and unrelated personal information out of the message.