Privacy notice.

This Notice describes personal information processed through the SaferRing website, account registration, beta enrollment, and call-screening service, including information about beta participants and people who call enrolled phone lines. SaferRing is operated by SaferRing Inc., a Delaware corporation. References to “SaferRing,” “we,” and “us” mean that operator.

This Notice explains information practices; it does not waive anyone’s legal rights or replace a consent that must be obtained separately. The Beta Participation Terms describe the service’s contractual terms.

Accounts: name, email, mobile number, password verifier, account identifiers, authentication and recovery information, sessions, consent, settings, and security events. Security notices can include browser/device information and the network address used to sign in.

Calls: caller and destination numbers, time, duration, delivery status, technical identifiers, caller-provided name and reason, screening transcript, risk indicators and outcome. Voicemail includes the recording, transcript when available, caller metadata and listened/deleted state. Optional synced contact numbers are represented by protected account-linked fingerprints for known-caller matching. Contact display names stay on your device; the sync does not upload address-book names, photos, emails or notes.

Support: submitted messages, topic, reply email, account identifier, receipt reference and submission time. Diagnostics include push tokens, device/session associations, call-registration and delivery results, errors and request timings needed to operate and secure the service. When billing is enabled, we process subscription identifiers, plan, payment outcome, entitlement and cancellation status; hosted Stripe checkout handles card entry, rather than our app receiving full card numbers.

A risk score is a caution indicator, not a statistical probability, proof of wrongdoing or verification of a caller’s identity. Carrier forwarding determines which calls reach SaferRing; we cannot screen a call that never reaches us.

Website analytics: where you allow optional analytics cookies, we use Google Analytics 4 to understand website activity, including page views, referral sources, device and browser information, and approximate location. Google uses cookies and similar identifiers for this measurement. This website integration is configured for page views, with enhanced measurement disabled. It is not configured to collect beta signup field values, contacts, or call recordings.

You can decline optional analytics through “Decline all” or “Manage cookies” in the cookie banner, and change your choice through “Cookie Preferences” on the website. Learn how Google uses information from sites that use its services and read Google’s Privacy Policy.

If you choose Google or Apple sign-in, we receive the provider account identifier, email address and basic profile information supplied for sign-in. Apple may supply a private relay address. SaferRing does not receive your Google or Apple password; these sign-in options do not request Gmail messages or Google Contacts.

New accounts must complete SaferRing email-code and mobile-number verification before activating calling. We send your saved number to Twilio Verify to deliver the requested verification text and process the result. Proof is retained for the same saved number; changing it requires a new ownership check. Text messages are not offered as a two-step sign-in method. Optional two-step methods include email codes and an authenticator; user-verified passkeys are also available for sign-in and supported security confirmations.

If you add a passkey, SaferRing stores its public key, credential identifier, label, creation and last-use timestamps and basic capability metadata. Your private key and device unlock or biometric data are not sent to SaferRing. Your credential provider controls passkey storage and synchronization.

Contact sync is optional. If you grant Contacts permission and choose sync, selected phone numbers are submitted for known-caller matching and represented by protected fingerprints on the service. These fingerprints are account-linked information, not anonymous data. Contact display names remain on your device. Sync does not authorize marketing to your contacts or selling your address book.

You can remove synced contacts using the app. Revoking Contacts permission stops future device access but does not erase already synced information. Use the service’s removal controls or contact support for removal. You must have authority to share the numbers you choose; your authorization does not waive another person’s rights or separately required recording consent.

Microphone permission lets you speak during app calls. Notification permission controls ordinary alerts such as saved voicemail. Carrier forwarding is configured separately. Removing the app or turning screening off does not turn off carrier forwarding, cancel a subscription or delete an account.

SaferRing processes speech during the AI screening interaction to produce a transcript and risk assessment. The screening opener says the call is screened and recorded before asking for the caller’s name and reason. Voicemail has a separate recording notice before the tone, and voicemail messages are recorded and may be transcribed. The current service does not record full connected conversations.

Do not provide passwords, verification codes or other unnecessary sensitive information to the screener. A caller who does not wish to continue can end the call. A participant’s enrollment consent does not substitute for another person’s legally required consent. Where applicable law requires additional consent, the notice alone is not a substitute. Processing must comply with applicable caller-consent requirements.

Any future full-conversation recording feature requires a separate opt-in, appropriate notice, retention disclosures and all legally required consents before recording begins. Joining the beta does not authorize full-conversation recording by default.

We use information to enroll and support beta participants; operate, route, screen, block, and troubleshoot calls; apply enabled contact-based preferences; detect abuse and security threats; evaluate and improve screening performance; communicate service and safety information; enforce our terms; and comply with legal obligations.

Beta participation does not grant blanket permission to publish identifiable caller audio, transcripts, or contact information in advertising or social media. Any such promotional use requires an appropriate separate permission and review of the affected people’s rights. Anonymization must be assessed for the actual content, not assumed merely because a phone number is removed.

We use providers to operate the service: Twilio and telecom networks for phone numbers, call transport, speech recognition and voicemail; AWS for account databases and backups; Netlify for calling APIs and scoped call/contact/rule state; OpenAI API for screening-text analysis and voicemail transcription when enabled; Apple for app distribution and call/push delivery; Google Workspace/SMTP for account and support email; Squarespace for the website and forms; Google Analytics for optional website measurement; and Stripe for hosted billing when enabled.

Restricted company support and operations tools can display account-linked call details and transcripts to investigate service issues. These records are not described as accessible only to the account holder. Approved generalized fraud patterns may be retained after removal of their account association; raw personal call transcripts are not public company-library entries.

OpenAI API data is not used for model training by default. Our screening requests use store:false, but provider-specific processing and retention still apply; this is not a zero-retention promise. Calls and transcripts are not end-to-end encrypted between callers and recipients through SaferRing.

Provider access must be appropriate to its service and governed by applicable data-protection obligations. We may disclose information where legally required, to protect people or the service, or in a merger, financing, acquisition or asset transfer subject to applicable obligations. This notice does not authorize unrestricted unrelated use by providers.

Google and Apple process requested sign-in under their own privacy terms. Twilio Verify processes initial or changed-number verification texts. Email security codes use our configured mail provider. SaferRing retains linked provider identifiers, and an encrypted Apple authorization reference needed to revoke Apple authorization when deleting an account. These exchanges do not grant access to unrelated Google or Apple services.

Account records are stored in our account service on AWS. Website form submissions, where used, are handled by Squarespace. Calling and voicemail data also pass through the providers described above. Active account information is retained for service operation until removed through available controls or account deletion; there is no blanket automatic call-history expiration. Voicemail expires after 30 days or is hidden when deleted, with provider cleanup retried before clearing retained content. In-app support records expire after 30 days; separately delivered support email is a mailbox record with separate retention.

In app versions that include account deletion, open Settings → Delete account, review the carrier-forwarding notice, confirm your identity using the supported account-security method and existing second factor where required, and confirm. The request blocks further account use immediately. Cleanup cancels owned subscriptions, retires the assigned route, deletes owned service content and voicemail media, and removes account credentials, sessions, push registrations, synced contacts, history, support records and settings. A request reference is shown, and completion email is sent after cleanup succeeds. Provider outages can delay completion; failed cleanup is not reported as completed deletion. Privacy requests can also be sent to support@saferring.com.

Deletion does not change your carrier’s forwarding settings. Turn off conditional forwarding using your carrier’s instructions before deleting your account, or contact the carrier. Calls still forwarded to a retired number will not be screened or delivered to you by SaferRing. Retired numbers are quarantined rather than immediately reassigned. Account deletion does not automatically issue a refund.

Restricted deletion references, account-hash tombstones and retired-route records prevent deleted accounts from being restored or reassigned. Pending cleanup instructions are encrypted; completed cleanup payloads are cleared. Rolling account backups are configured hourly with 168 retained snapshots, approximately seven days when backups run successfully. This is not a promise that manual archives, server snapshots, logs or delivered email expire in seven days. Those copies remain subject to restricted access, documented retention and applicable legal exceptions. Deletion safeguards must be applied before a backup is restored to active use.

Twilio may retain recording metadata for 40 days after recording deletion; the deleted audio cannot be retrieved through that recording resource. Financial providers may retain required transaction/history records. Legal, security or dispute-related exceptions remain limited to their necessary purpose. Ending beta participation does not erase every separate provider or mailbox record immediately.

Telecom providers may retain required technical or billing records and can take additional time to propagate removal from their active call logs. Deletion does not promise that every provider copy disappears immediately.

Account deletion removes SaferRing passkey public records and initiates revocation of stored Apple authorizations before final account erasure. Removing a saved passkey from your device credential manager is a separate device action. An authorization-provider outage can delay cleanup and is not reported as completed deletion.

SaferRing uses reasonable administrative, technical, and organizational safeguards appropriate to the information it processes. No service can guarantee absolute security, uninterrupted availability, or prevention of every unauthorized disclosure. This statement does not limit duties imposed by applicable law.

Do not submit passwords, one-time codes, complete payment-card details, government-identification numbers, or sensitive medical or financial information through beta signup or feedback. Call screening is not a secure channel for exchanging those details. Report suspected misuse or a privacy concern to support@saferring.com.

Participants and callers may contact support@saferring.com to ask about their information, request access or correction, request deletion, withdraw optional permissions, or raise a privacy concern. Depending on your location and the law’s applicability, you may have additional rights concerning copies, portability, restriction, objection, opt-outs, authorized agents, or appeals. We will handle applicable requests within the time and on the terms required by law.

We may reasonably verify identity or authority before disclosing or changing records. Please do not send sensitive identity documents unless we explain why they are needed and provide an appropriate method. Some requests may be limited by legal exceptions or the rights of other people; where required, we will explain a refusal and available review or appeal options.

You may withdraw from the beta or withdraw screening-recording consent by contacting support. Withdrawal does not undo processing already lawfully completed and may prevent provision of a feature that depends on that processing. A caller may decline recording without agreeing to the participant’s contract.

We may send requested onboarding, operational, support, and safety communications. Optional automated or AI-voice calls, texts, or nonessential updates require the appropriate separate permission where required by law. Optional communication consent is not a condition of purchasing anything or joining the waitlist.

You may revoke optional communication consent by contacting support@saferring.com or using any other reasonable method recognized by applicable law, including an opt-out method offered in the message. Ordinary service emails or other legally permitted essential notices may continue. Message and data rates may apply to texts or calls.

Beta enrollment is limited to adults aged 18 or older. SaferRing does not knowingly collect beta enrollment information from children. This enrollment rule does not mean that every incoming caller is an adult. If you believe a child’s information has been improperly collected, contact support so the issue can be assessed and handled under applicable law.

Information may be processed in the United States and other places where SaferRing’s providers operate. Protections can differ between locations. Any legally required transfer safeguards or location-specific disclosures must be provided when applicable; this Notice is not a waiver of those requirements.

We may update this Notice as the beta changes. A published revision will identify its effective date. Material changes require appropriate notice, and any new consent required for a new processing purpose must be obtained before that processing begins. A revised Notice does not retroactively authorize a materially different use of information where fresh consent or another legal requirement applies.

Questions, privacy requests, or withdrawal requests may be sent to support@saferring.com. SaferRing is operated by SaferRing Inc., a Delaware corporation. Contact us at support@saferring.com.