Privacy and data handling.
Last updated: September 26, 2026
This notice separates the public DialBreeze website from the operational data used by a provisioned calling account. DialBreeze is built by the team behind the Milner Team in Cape Coral, Florida. Send privacy and data-handling questions to brayden@themilnerteamfl.com. Use that address to confirm the arrangements required for your account before uploading production lists or recordings.
Trial requests and support messages.
The trial form asks for your name, work email, team and industry, expected operator count, and optional notes about the workflow you would like to evaluate. 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, arrange the evaluation and 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 trial form or an ordinary support message.
A received trial request is not an active account or a paid subscription. Our team provisions the sandbox and emails access when it is ready. The trial uses test numbers rather than your real calling lists. Information you send to arrange it is distinct from any operational data later placed in a paid environment.
Website delivery and technical requests.
The public site is delivered through Cloudflare and loads a Cloudflare Web Analytics script from static.cloudflareinsights.com. That analytics integration is a separate third-party request, not just local page rendering. The pages also load the Barlow Semi Condensed and Manrope typefaces from Google Fonts. Visiting the site therefore involves requests to infrastructure beyond the local website server. Those requests carry the technical information normally needed to deliver a web resource, such as the requesting network address and browser request information.
The site should not be described as involving no third parties or no technical data simply because a form has not been submitted. Website delivery, font loading, email delivery and billing are separate processing activities. Your browser's network and privacy controls can help you inspect or restrict third-party requests, although restrictions may affect font display or other functionality.
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 trial form does not collect card numbers. Stripe processes the payment and sends the receipt under the parent team's account, whose business name is MIRA. It is the same team that builds 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, structured score 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.
Before uploading production data, confirm the operational environment, recording storage, AI-processing arrangement, access controls and any required processor information with the setup team. This notice does not identify an unverified provider as the host of your recordings, claim a particular geographic storage region, or promise a data-processing agreement that has not been established for the account.
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 trial 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, consent and sensitive information.
Your business determines which calls may be made and recorded, what notices or permissions apply, and which information operators should collect. The product's internal DNC, per-lead quiet hours and attempt caps support the configured calling policy; they do not establish consent or perform the customer's federal-registry scrub.
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 legal commitment. Review important details against the source and involve the appropriate responsible professional where needed. 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.
Confirm the export format and practical retention or deletion process before ending service or relying on a particular storage period. This page does not promise an unverified self-service export tool, unlimited recording retention, immediate removal from every backup or a fixed deletion deadline. 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.
Use the no-card sandbox to inspect the workflow with test data. Bring your storage, access, processor and retention requirements to onboarding before moving real lists into a production environment. 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.