How Dialtone protects the pilot
See what Dialtone knows—and what it does not.
Dialtone keeps user permissions, practice rules, provider information, and human decisions separate. Missing, failed, and unknown information is shown clearly; it is not treated as permission or success.
This is a factual description of the current product controls. It is not a security certification, a lawyer-reviewed calling policy, or a compliance guarantee.
Who can see what
Cloudflare Access protects the service. The server uses the signed-in person’s verified identity to decide what they may see and do. A browser cannot grant itself owner access. Owners may see the practice; callers see only the leads, numbers, and controls assigned to them.
One user-controlled call at a time
Every call starts with the same review. The user sees the lead and starts the call. Dialtone blocks a second live call from the app. If the carrier’s status is unclear, Dialtone shows that uncertainty instead of assuming the call ended. The pilot does not provide parallel, predictive, prerecorded, ringless-voicemail, or autonomous AI calling.
Caller ID and calling-provider status
Before a number can be used, the provider must confirm it, an owner must assign it to the caller, and it must be active. The server decides which numbers that caller may use and which one is the default. A local area-code guess cannot add a number. If the browser, provider, or assignment is not ready, Dialtone names the problem instead of showing a generic success badge.
What Dialtone shows before a call
Dialtone shows the reason for the call, local time, do-not-call evidence, practice stop-contact status, consent information, caller ID, recording status, warnings, and acknowledgements as separate facts. Required information that is missing or out of date is named. No badge is presented as permission to call or legal advice.
Recording
Recording remains off when the practice’s rule requires it or the rule is unknown. If a practice enables recording, Dialtone requires the configured decision, the consent information shown for that call, and a saved server record. Transcription and AI coaching remain off unless separately enabled.
Saving work and recovering from errors
Dialtone gives each save a unique identifier so retrying does not quietly create a duplicate. The result, note, stage, callback, and next step are saved together. If a save is waiting, refused, failed, or needs manual help, the app says so. When data is permanently deleted, Dialtone states which audit history remains; it does not describe the deleted data as recoverable.
Where data is stored
Practice records stay in the protected Dialtone service. A user’s device keeps only limited preferences and unsent retry information. Practice mode uses fictional data stored separately from live records. Credentials are excluded from exports and public website files. See the private-pilot privacy notice for categories, purposes, providers, and request routes.
This public site
The marketing site uses no analytics, advertising pixels, outside scripts, or lead form. The readiness check calculates its result in the browser and does not send the answers anywhere. Cloudflare may still keep ordinary request and security logs needed to host and protect the site.