SecureRing · Effective: October 1, 2026 · Version 2.3
SecureRing is operated by an individual doing business as SecureRing, located in California ("SecureRing," "we," "us," or "our"). This Privacy Policy describes the information we collect through the SecureRing application and the secure-ring.com website, how we use and retain that information, the third-party services involved in operating SecureRing, and your privacy rights.
This Privacy Policy accompanies our Terms of Service, which govern your use of SecureRing.
Depending on the version of the application and authentication method available to you, you may provide information such as your display name and email address when creating or maintaining a SecureRing account. If phone-based authentication is offered and you choose to use it, a phone number may also be collected.
When you first install or use the application, SecureRing may create a temporary identifier associated with your device or installation. That identifier may subsequently be associated with your SecureRing account or circle membership.
If you create or join a Trusted Circle, SecureRing processes information necessary to operate the circle, including your display name, circle membership, invitations, member identifiers, and information provided by you or another circle member for calling, verification, or alert functionality.
If you or another circle member provide a phone number or emergency-contact information for a circle member, SecureRing processes that information for the feature for which it was provided.
SecureRing generates an Ed25519 cryptographic keypair on your device.
The private key is generated on your device and is not transmitted to SecureRing's servers. The corresponding public key is shared with SecureRing so that the verification system can associate a verified device with the relevant SecureRing membership.
On iOS, cryptographic key material may be backed up through your own iCloud Keychain. iCloud Keychain is operated by Apple and is not accessible to SecureRing.
If you use AI Scam Check, you may submit text that you type, paste, or dictate, an image or screenshot, and a general source label such as "SMS," "email," or another category.
SecureRing does not maintain a user-visible history of your Scam Check submissions or results. We do retain the limited usage information and aggregate statistics described below.
If you choose to report a scam or suspicious communication, SecureRing may store the report type, your written description, an optional phone number, the associated area code, and an internal identifier linking the report to your account so that you can view its status through features such as "My Reports."
If you send an alert or check-in notification through SecureRing, the message content is delivered to the circle members designated to receive it.
SecureRing uses device, member, account, and circle identifiers as necessary to operate the service, bind cryptographic verification to the appropriate device or membership, maintain sessions, enforce quotas, and protect the service against abuse.
SecureRing processes push-notification tokens for Apple Push Notification service (APNs) and Firebase Cloud Messaging (FCM), together with associated platform information and other technical information necessary to deliver notifications.
When a SecureRing call is placed, we may record metadata such as participating member identifiers, room or call identifiers, start and end times, duration, and the outcome of the applicable verification process.
SecureRing does not record or store the audio or video content of calls.
SecureRing maintains usage counters associated with Scam Check to enforce feature quotas and prevent abuse. These counters do not contain the submitted message or screenshot.
SecureRing may also maintain aggregate, non-user-identified statistics regarding Scam Check risk results.
Our cloud infrastructure may generate operational and security logs that can include technical information such as IP addresses, timestamps, request paths, device or service identifiers, and other information necessary to operate and secure the service.
We may also retain records of failed authentication attempts and notification-delivery events for security, abuse prevention, troubleshooting, and service operation.
If you voluntarily join an email waitlist through secure-ring.com, we may collect your email address, a source tag, and your IP address where necessary to prevent duplicate or abusive submissions.
The SecureRing website uses strictly necessary cookies or similar technologies required for website hosting, security, and operation.
The website does not currently use advertising cookies or analytics cookies for behavioral advertising. Because we do not currently use non-essential advertising or analytics cookies, we do not currently use a cookie-consent banner for those purposes.
SecureRing does not currently request or collect through the application's active user flows:
The in-app Call History displays SecureRing call activity and is not the same as the native phone's call history.
SecureRing does not currently use an advertising SDK, behavioral analytics SDK, or crash-reporting service in the application. Firebase Cloud Messaging is used for Android push notifications and not for advertising analytics.
Certain information is visible to members of your Trusted Circle because it is necessary for the service to function. This may include your display name, circle membership, verification requests, incoming-call information, and alerts you send.
Incoming-call notifications may display the caller's SecureRing display name.
Rotating Safe Words are generated and used as part of SecureRing's verification system. The underlying shared secret is distributed to authorized circle members and is stored by SecureRing in encrypted form so that verification can continue to operate across supported devices.
SecureRing servers may decrypt this material when necessary to operate the verification system.
Safe Words should be treated as circle-confidential information. Anyone who is shown or told a Safe Word may be able to use that information to impersonate the expected verification signal.
SecureRing calls are carried through LiveKit Cloud, a third-party communications service.
During an active call, audio and video streams travel through LiveKit's infrastructure between participants. SecureRing's application backend does not receive or store the call's audio or video content.
When you connect to a call, LiveKit receives a short-lived access token and the technical connection information necessary to carry the call, which may include IP address and network information.
SecureRing does not use LiveKit's recording functionality.
SecureRing stores call metadata necessary to operate the service, such as room identifiers, participant member identifiers, start and end times, duration, and verification results.
When you use AI Scam Check, the content you submit is transmitted to SecureRing's backend and forwarded to Anthropic, PBC, currently using a Claude AI model, for analysis.
The request sent to Anthropic contains the submitted content and general source information necessary for the analysis. SecureRing does not send your SecureRing account identifier, device identifier, or IP address to Anthropic as part of the model request.
Anthropic processes API submissions under its applicable commercial API terms and policies.
Under Anthropic's applicable commercial API terms, API inputs and outputs are not used to train Anthropic's models by default. Under the standard applicable retention terms, API content is subject to limited retention, currently generally up to 30 days, with possible longer retention in circumstances such as trust-and-safety review.
SecureRing does not control Anthropic's independent processing practices.
SecureRing does not maintain a user-visible history of submitted Scam Check messages, screenshots, or results.
SecureRing may retain:
If you dictate content for Scam Check, speech recognition is performed using your device's operating-system speech-recognition functionality.
Depending on your device, operating-system settings, and service configuration, speech recognition may be processed by Apple, Google, or another operating-system provider. SecureRing does not receive the original audio as part of the normal Scam Check text-submission process.
Only the resulting transcribed text is submitted to SecureRing for Scam Check.
A message or screenshot submitted to Scam Check may contain another person's information, such as a scammer's phone number, email address, name, or a request for sensitive information.
SecureRing processes submitted content to provide the requested risk assessment and does not maintain a user-visible history of that content.
You should avoid submitting passwords, authentication codes, payment-card numbers, government identification numbers, or other sensitive credentials because they are unnecessary for Scam Check.
If you submit a scam report, SecureRing may retain the report type, your written description, an optional phone number, the associated area code, and an internal identifier linking the report to your account so that you can view its status through the "My Reports" feature. My Reports shows moderation status information only — not your stored report content.
Every report is reviewed by a human moderator before any publication decision. Nothing is published automatically.
Your account identity and reporter identifier are not published with a Community Report.
If a report is approved, SecureRing may publish a redacted version containing information such as the description of the reported activity and, where appropriate, an area code. Reports that are approved for publication may be redacted, anonymized, or otherwise modified to remove unnecessary personal information before being made available to other users.
Credential-like information, including passwords, authentication codes, payment-card numbers, and similar sensitive information, is removed or redacted before publication where detected.
A reporter's full phone number is not published.
Pending reports that are never reviewed expire automatically, generally after 30 days, and are then treated the same as rejected reports for retention purposes.
If a report is approved and published, the redacted version may be retained only for as long as reasonably necessary to operate, maintain, improve, and secure the Community Reports feature, subject to applicable law.
If a report is rejected or is not selected for publication, its submitted content (including any phone number and the report description) is deleted or anonymized no later than two (2) years after the review decision. Until then, such reports may be retained for purposes such as moderation, abuse prevention, security investigations, handling disputes, and demonstrating compliance with our policies. After that point, only non-identifying moderation metadata (such as the report type, area code, status, and relevant dates) is retained, unless a longer retention period is reasonably necessary for legal obligations, legal claims, fraud prevention, security, or other legitimate purposes permitted by applicable law.
Where technically and legally appropriate, information contained in reports may be aggregated, de-identified, or anonymized so that it is no longer reasonably associated with an identifiable individual. Anonymized information may be retained for longer periods for security, research, analytics, or product-improvement purposes.
We do not intentionally publish unnecessary personal information contained in submitted reports. Users should avoid submitting sensitive personal information that is not relevant to identifying or understanding a suspected scam.
You may request deletion of your own report by contacting [email protected]. Deletion requests are subject to applicable legal, security, moderation, and record-retention requirements.
Subscriptions are purchased through the Apple App Store or Google Play.
SecureRing does not receive or store your payment-card number.
Apple or Google processes payment information according to its applicable policies.
SecureRing may receive and store information necessary to administer subscriptions, such as transaction identifiers, product identifiers, purchase dates, expiration dates, and subscription status.
SecureRing uses information as reasonably necessary to:
SecureRing does not sell personal information.
SecureRing does not use personal information for cross-context behavioral advertising.
Scam Check uses automated processing to analyze submitted content and provide an informational risk assessment. These results are not used by SecureRing to make decisions that produce legal or similarly significant effects about you.
When you delete your account through an available account-deletion mechanism, SecureRing will delete or de-associate account and service data that is eligible for deletion, subject to the retention exceptions described below.
Depending on your role and the applicable data involved, this may include your member profile, circle memberships associated with your account, invitations, verification requests, push tokens, training activity, and other account-associated service data.
If you own a Trusted Circle, account deletion may also remove your ownership and participation in that circle. Information belonging to other members is not treated as your personal data solely because you were the circle owner.
To comply with law, resolve disputes, maintain security, prevent abuse, administer purchases, and maintain service integrity, SecureRing may retain certain information after account deletion, including:
Community Reports that are published do not identify the reporter.
SecureRing retains personal information only for as long as reasonably necessary for the purposes described in this Privacy Policy, to comply with applicable legal obligations, or to establish, exercise, or defend legal claims.
SecureRing uses reasonable administrative, technical, and organizational measures designed to protect information.
Data is encrypted in transit and at rest where supported by the applicable service infrastructure.
Private cryptographic keys are generated on your device and are not transmitted to SecureRing's servers. On iOS, supported cryptographic material may be backed up through your own iCloud Keychain.
Server-held secrets, including cryptographic material used for Safe Word verification, are stored using encryption and access controls.
SecureRing uses scoped credentials and access controls for its infrastructure.
No method of transmission or storage is completely secure. If SecureRing becomes aware of a security incident involving personal information, we will provide notices required by applicable law.
SecureRing uses third-party providers to operate portions of the service, including:
These providers may have their own privacy policies and terms governing their services.
SecureRing may add or replace service providers as necessary to operate the service. Material changes that materially affect the processing of personal information will be communicated through an appropriate notice where required.
SecureRing may also disclose information when required by law, legal process, or governmental request, or as reasonably necessary to protect the rights, safety, property, or security of SecureRing, its users, or others.
SecureRing is not intended for children under 13, and use by children under 13 is prohibited.
SecureRing does not knowingly collect personal information from children under 13.
If we learn that a child under 13 has provided personal information, we will take reasonable steps to delete it.
Use by individuals aged 13–17 requires express parental or guardian consent as described in the Terms of Service.
If you believe a child under 13 has provided personal information to SecureRing, contact [email protected].
Depending on where you live and subject to applicable law, you may have rights to:
You may submit a privacy request by contacting [email protected].
We may require reasonable information necessary to verify a request before acting on it.
California residents may have rights under the California Consumer Privacy Act, as amended by the California Privacy Rights Act ("CCPA/CPRA"), including rights to know, delete, correct, and obtain certain personal information, and the right not to receive discriminatory treatment for exercising privacy rights.
SecureRing does not sell personal information and does not share personal information for cross-context behavioral advertising.
If our practices change in a way that creates an applicable opt-out right, SecureRing will provide the required mechanism and honor applicable opt-out preference signals, including Global Privacy Control where legally required.
We generally respond to verifiable California privacy requests within 45 days, with an additional 45-day extension where reasonably necessary and permitted by law.
Residents of states with applicable comprehensive consumer privacy laws may have rights to access, correct, delete, or port personal information and to opt out of targeted advertising, sale of personal information, or certain profiling.
SecureRing does not currently engage in targeted advertising or sale of personal information.
Residents of the European Economic Area and United Kingdom may have rights under applicable data-protection laws, including rights of access, rectification, erasure, portability, objection, and restriction of processing.
Where applicable, SecureRing may process account and circle information as necessary to perform a contract with you.
SecureRing may process information necessary to maintain security, prevent abuse, and operate the service based on legitimate interests where permitted by applicable law.
Where you voluntarily submit information through features such as Scam Check or Community Reports, SecureRing processes that information as necessary to provide the feature you request. Where applicable law requires consent for a particular processing activity, SecureRing will obtain consent separately.
You may lodge a complaint with the data-protection authority applicable to your location.
SecureRing operates from the United States.
Our service providers may process information in the United States and other countries where they operate.
If you use SecureRing outside the United States, your information may therefore be transferred to and processed in the United States.
Where required by applicable law, SecureRing will rely on appropriate safeguards for international transfers.
We may update this Privacy Policy periodically.
The effective date and version number identify the current version.
If we make material changes, we will provide an appropriate notice, including an in-app notice where appropriate.
Your continued use of SecureRing after an updated Privacy Policy becomes effective constitutes acceptance of the updated policy to the extent permitted by applicable law.
Questions about this Privacy Policy or privacy-rights requests may be directed to:
SecureRing is operated by an individual doing business as SecureRing, located in California, and is not a corporation, LLC, or other formal legal entity.