Phase 1 — running on Factory-1 LAN

Legal

Privacy Policy

How Ringly collects, uses, and protects your information.

Effective 2026-01-01 · Last updated 2026-06-30

Information We Collect

Account profile (name, business name, address, email, phone), billing details (Stripe-tokenized — Ringly never sees card numbers), call detail records (numbers, duration, cost), recordings if you enable them, voicemails, transcripts, and platform usage logs.

How We Use It

To provide and bill for the service, route your calls, surface call analytics, fulfill legal obligations (CALEA, subpoena response, lawful intercept), and detect fraud. We do not sell customer data.

CPNI (Customer Proprietary Network Information)

Your call records and usage data are CPNI under 47 CFR Part 64. We disclose CPNI only with your consent, as required by law, or as necessary to bill and provide the service. See our CPNI Notice for details.

Data Retention

Call detail records are retained for 5 years (industry standard, supports billing disputes, fraud investigation, and CALEA). Recordings are retained per your account's configured policy. Personal account data is retained for the life of the account plus 3 years.

Your Rights

California (CCPA/CPRA), Virginia (CDPA), Colorado (CPA), Connecticut (CTDPA), Texas (TDPSA), EU (GDPR), and UK GDPR residents can request access, correction, deletion, portability, and opt-out via [email protected].

Security

TLS 1.3 in transit, AES-256 at rest, SRTP for media, role-based access control, MFA for admin, audit logging on every sensitive action. Annual SOC 2 Type II audit on the Phase-2 roadmap.

Children's Privacy

Ringly is a business-to-business service. We do not knowingly collect data from anyone under 13.

International Data Transfers

EU and UK data may be processed in the United States subject to Standard Contractual Clauses. We will sign a DPA with any customer who requests one.

Changes

We will notify you of material changes via email and a 30-day notice posted on the site before they take effect.

Questions about this document? Contact [email protected] or visit /legal/compliance for our full regulatory posture.