Privacy and data handling.

Setup requests and support messages.

The setup request form asks for your name, work email, team and industry, expected operator count, and optional notes about your current workflow or a question for us. Submitting it sends a request through the website's inbound endpoint and Amazon Simple Email Service (SES) for delivery to the setup team's inbox. The message includes the form fields you provide. We use that information to respond, answer your questions and arrange or support the requested setup.

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 the public setup request form or an ordinary support message.

A received setup request is not an active account or a paid subscription. We provision a workspace and email access when a plan is paid and the workspace is ready. Information you send in a request is distinct from any operational data later placed in a paid 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.

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.

Payments and the merchant name.

Paid checkout is hosted by Stripe. The DialBreeze website requests a checkout session for the selected plan and directs you to Stripe to enter payment information. The setup request form does not collect card numbers. Stripe processes the payment and sends the receipt under the merchant name MIRA, DialBreeze's parent company. Your card statement shows DIALBREEZE.

Billing information needed to identify and support a subscription can include the billing email, selected plan, payment or receipt reference and subscription status. For a missing receipt, cancellation or other billing question, contact our support address using the billing email. Do not send the full card number. Stripe's checkout and related services have their own privacy information; review it on the payment surface before submitting.

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. The after-call AI workflow processes recorded content to produce a transcript, fixed structured fields and summary. 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. Bringing your own Telnyx account does not mean that the application's lead database, recordings and AI outputs are all stored in that carrier account or on hardware you own.

AI and data processing.

On Pro and Team, recorded calls are processed after the call ends. Here is where that processing happens:

• Transcription runs on our own servers, using a self-hosted speech model. If the local model is unavailable, a third-party speech provider, Deepgram, transcribes the recording instead.
• Summaries and structured fields are produced by a language model running on our infrastructure.
• Recordings are stored on our servers in the United States.
• Retention is not configurable yet. To delete data, email brayden@themilnerteamfl.com and we delete it on request.

Processors.

These companies process data on our behalf, or on yours in Telnyx's case:

• Stripe: billing and payments.
• Amazon SES: email delivery.
• Cloudflare: network delivery and protection.
• Telnyx: calls, numbers and carrier services, under your own Telnyx account.
• Deepgram: fallback transcription, used only when our self-hosted speech model is unavailable.

Your carrier account and credentials.

Production telephony uses your own Telnyx account, numbers and authorized caller ID. Telnyx handles carrier services and the associated carrier data under your separate account relationship. You retain responsibility for that account's users, credentials, service settings and billing decisions.

Use the connection process provided during onboarding. Do not paste an API key or password into the public setup request form, a screenshot or an ordinary support note. Your own account ownership is not a technical claim that an integration never needs access to a credential while carrying out an authorized action. 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. Recording is enabled at the workspace level by our team, not switched per call; ask us to turn it on or off for your workspace.

The product's internal DNC, per-lead quiet hours and attempt caps help you run your compliance program; they do not establish consent or 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. Do not use an AI summary as proof of consent, identity, insurance eligibility or a person's exact commitment. 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.

Cancellation of the DialBreeze subscription and closure of your carrier account are separate actions. Canceling one does not, by itself, instruct the other provider to release numbers or remove its records. Read the subscription terms and coordinate the relevant requests with each service.

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 brayden@themilnerteamfl.com. Include a way to reach you and the specific issue, and leave credentials and unrelated personal information out of the message.