Trust and compliance
What we promise, in writing.
A phone service touches emergency calling, consent law and other people's data. This page collects every notice and policy we publish, and says what the product does today rather than what a badge would imply.
911
Registered address per number, limits stated plainly.
47 CFR 9.11
SMS consent
STOP and HELP enforced by the server before every send.
Recorded per contact
Recording
Off by default; a tone plays when a workspace turns it on.
Consent beep
Your data
Tenant-scoped, audit-logged, never used for training.
CPNI
Six topics
How each part works.
Emergency calling
VoIP 911 routes by registered address and fails without power or internet. We say so plainly, require an address per number, and record each acknowledgment.
Read the 911 NoticeText messaging
Consent recorded per number, STOP and HELP enforced by the server before every send, a published program description and sample messages.
SMS ProgramCall recording
Off by default. When a workspace turns it on, callers hear a tone. Recordings stay in that workspace and are served through short-lived links.
Recording termsAI receptionist
Answers only from knowledge the business published, introduces itself as an AI, and never dials out. Conversation content is not used for training.
AI in the Privacy PolicyYour data
Tenant-scoped storage, role-based access with an audit log, and deletion you control. Call records are treated as CPNI.
Privacy PolicyNetwork conduct
No spam, no unlawful robocalls, no caller-ID misuse. We watch traffic patterns, not conversations, and act on abuse.
Acceptable Use PolicyNo badges
What we do not claim.
We hold no third-party security certification today and do not display badges we have not earned. We run on a carrier-grade US network, and the carrier obligations that apply to our service are being registered with the FCC and state authorities as we launch commercially.
Ready when you are.
Questions about 911, consent or data before you sign up are welcome. Ask them in the form.