Privacy Policy
The short version: Rings shows two people who meet the contacts they have in common — a feature we call Crosscon. Matching uses hashes of phone numbers. These remain personal data because phone numbers can be guessed. After you both accept a connection, each of you sees only the contacts you have in common, under the name the other person saved them. Chat messages, files and shared locations are end-to-end encrypted with the Signal protocol. Call media uses WebRTC encryption; we cannot read the content of either. Call transcription runs entirely on your iPhone. No ads, no trackers, no selling of data.
Who we are
Rings (listed on the App Store as "Rings: Mutual Contacts") is operated by GAIIA PRODUCTIONS LLC-FZ ("we", "us"). "Crosscon" is the name of the Rings feature that matches two people's contacts; it is not a separate app or service. Contact: privacy@gaiiafoundation.com.
What we collect and why
Everything in this section leaves your phone, is stored on servers we operate, is linked to your account and is used only to make Rings work. None of it is used for advertising or tracking.
- Display name — the name you enter in your profile (pre-filled from your Apple ID name if Apple shares it). It is shown to people you connect with, in the notifications they receive about your requests, and to participants of a temporary call you join.
- Own phone number — Rings asks for your number when you create your profile. When you request or check a verification code, your full international phone number is sent to our server. If SMS verification is enabled, the configured provider, Vonage Verify or Twilio Verify, receives that number to send and check the code. Our server stores a short-lived verification record containing the number, request times, attempts and the provider's request reference. Scheduled cleanup removes records more than 24 hours old; deleting this installation's account also removes its verification records. If SMS verification is unavailable, the app can continue with the number marked unverified; no code is sent and ownership has not been confirmed. A SHA-256 hash of the number is stored with your installation until you change it or delete its account. People who already have your number in their address book can see that you are on Rings, may get a notification when you join, and can send you a Crosscon request. The number does not recover another installation's chat history. Mo, when enabled, can share a balance between devices that have verified the same number, as described below.
- Profile avatar (optional) — the colour and style you choose for your avatar, and, if you choose a photo, that photo. The photo is re-encoded by our server (location and other metadata are removed), stored on servers we operate, and shown only to the people you are connected with. It is not end-to-end encrypted. Kept until you remove or replace it or delete your account.
- Contacts (hashed) — while "Share contacts for matching" is on (it is on by default once you allow Contacts access, and you can turn it off in Settings), Rings uploads SHA-256 hashes of the phone numbers in your address book, except contacts you hide from Crosscon. Hashes are pseudonymous, not anonymous. Our server reveals only the overlap between two people, and only after both accept the connection; a block stops further access. For each contact you have in common, the name you saved them under is uploaded and shown to that one person. When you start a Crosscon with, or invite, a specific contact, the hash of that contact's number is stored with the request. Hashes and names are kept until you turn sharing off or delete your account.
- Connections and groups — who is connected with whom, and which group chats you belong to. Kept until you delete your account.
- Account and device identifiers — a random account identifier issued by our server when you register (it is not your advertising ID), and the Apple push tokens (APNs and VoIP) used to deliver messages and to ring your phone for calls. Kept until you delete your account.
- "About you" and professional field (optional) — described in the next section.
- Temporary call rooms — adding a person to a call creates short-lived routing metadata, not a group chat. Room participants can see each other’s account identifiers and display names to understand who is joining. The server records the room’s participants and original call identifier to authorize encrypted signaling and key exchange. No messages or files are stored in this room. Room metadata is removed when the last participant leaves, the creator cancels, or an account in the room is deleted. Authorization expires after ten minutes without call presence; a cleanup task runs every minute and removes expired metadata. The routing lease is renewed while the call remains active.
- Call log — for each call: the two account identifiers, start and end time, audio or video, and the outcome (for example answered or missed). Never the audio, video or anything said. Kept until you delete your account.
- Message delivery metadata — sender and recipient account identifiers, times, and whether a message was delivered and read. Kept together with the encrypted message: up to 7 days after delivery, or 30 days if it is never delivered.
- Abuse reports — when you report someone: both account identifiers, the reason you choose and the text you write, and — if you report from a group chat or a specific message — the group and an identifier of that message (not its content, which stays end-to-end encrypted). Our team reviews reports and may suspend or permanently ban an account; the decision, its reason and which team member made it are kept as a moderation record. For a permanent ban we keep the hash of the account's phone number, if one was entered, so the same number cannot register again. Kept for safety and moderation.
- Support messages — when you write to Rings Support from the app, your messages and our replies are stored on our server with your account identifier. If you choose "Email us instead" and provide a reply-to email address, that address is stored with the message and can be sent to our support mailbox through Resend when email delivery is enabled. These messages are not end-to-end encrypted: our support team reads them to help you, so please do not send passwords or codes. Messages on the Rings server are kept until you delete your account; deleting them does not recall email already delivered to a mailbox.
"About you" (optional)
You can tell your connections what you do: a professional field you pick from a fixed list and a short "About you" text. If you fill either of them in — during setup or later in Settings › About you — it is uploaded to our servers and shown only to people you have accepted as connections. The "About you" text is never used in search. Interest tags picked in an earlier version of the app are kept with it. The job title you type to find your field stays on your iPhone. "About you" is not end-to-end encrypted, so that a reported profile can be moderated. You can change or clear it at any time in Settings › About you; our server keeps only the latest version, and all of it is deleted with your account.
Professional search and introductions (optional)
In Contacts, "Find a professional" lets you search a fixed professional field, such as Design. Search words are matched to the field on your device using a local synonym list; only the selected field and search filters reach our server.
If you enable discovery participation in Settings, we store counts of contacts by professional category, not the names or numbers behind those counts. Your accepted connections can use these counts to ask you for an introduction. You decide whether to pass the request along. Turn participation off to remove these counts.
Searching introduction routes requires a separate consent screen before your existing accepted-connection graph is used for that purpose. Your professional field becomes searchable only if you also turn on "Find me by my profession"; allowing requests to pass through you is a separate switch. Saving a professional field alone does not make you discoverable. These choices can be changed in Settings.
Routes cover two to six connections. Search results identify your own first contact and the number of steps, while other people's identities remain hidden. People already in your saved address book or accepted Rings connections are excluded as introduction targets. Country and, for shorter routes, city may appear; interest overlap is shown as a count. We store these optional self-described fields with your profile.
When you request an introduction, our server stores the route, its participants, decisions and request status so the request can progress. Each intermediary decides whether to pass it on; the target sees who is requesting the introduction and can accept or decline. The introduction request message is stored on our server and is not end-to-end encrypted; it is not shown to intermediate contacts. Pending requests expire, and you can cancel a request before completion. Blocks and suspended accounts restrict routing. Profiles, published counts and introduction records are removed when you delete your account.
Mo allowance (when enabled)
Mo is an earned allowance for professional introductions, with no cash value. It is available only when the service is enabled and your number is verified. Our server links a Mo account to the hash of that verified number. Devices that verify the same number share the balance, earned total and available introduction reach; this does not share their chat history or encryption keys.
We store the balance, amounts reserved for requests, changes to those amounts, the type and time of each event, invitation records, and records that prevent repeated rewards. When you organise a contact, the app sends an opaque event identifier for a classification reward. It does not send that contact's name, phone number, address-book identifier, rating, notes or category for this event. Contact matching and optional professional-category counts remain separate, as described above.
Mo request records connect an allowance reservation to an introduction and its outcome. A request can reserve Mo; acceptance spends the reservation, while a declined, cancelled, unavailable or expired request returns it. These records enforce the balance and reward limits; they are not used for advertising or tracking.
Deleting an installation's account removes its invitation records and releases affected pending reservations. For the number currently verified by that installation, the shared Mo account, its balance, event history and reward records are deleted if no other verified installation with that number remains. While another verified installation remains, the shared records remain available to it. Changing a verified number ends this installation's membership of the previous number's Mo account. Pending Mo introductions involving that membership expire and affected reservations are returned. If no other verified installation with the previous number remains, that number's shared Mo account, balance, event history and reward records are deleted as part of the change. Otherwise, those shared records remain available to the other verified installations.
End-to-end encrypted: we store or relay it, but cannot read it
Chat message text, photos, voice messages, files and their names, locations you share in a chat, group names, reactions and replies, and call summaries you choose to send are end-to-end encrypted with the Signal protocol (libsignal). Call audio and video are encrypted with WebRTC (DTLS-SRTP), and call signaling — the messages that set up a call — is encrypted and authenticated with libsignal, so a call can be set up only with the person you expect. You can compare an eight-emoji handshake with the other person to check that nobody is in the middle.
Our server holds encrypted messages only for delivery: for up to 7 days after delivery, or 30 days if undelivered. Encrypted files are kept for 30 days. When a direct connection is not possible, calls are relayed through our TURN server, which sees only encrypted media.
Stays on your iPhone
- Call transcription (beta, off by default) — if you turn it on in Settings and tap Record during a one-to-one call, both phones show "Recording on" and the other phone plays a chime. Speech is transcribed on your iPhone by Apple's on-device speech recognition; on iOS 26 with Apple Intelligence, the summary of what was agreed is drafted by Apple's on-device model. Call audio and transcripts never leave your iPhone: they are not sent to us, to Apple's servers or to any AI service. A summary leaves your phone only if you tap Send, and then end-to-end encrypted to that chat.
- Task reminders — scheduled as local notifications on your iPhone.
- Your address book — the numbers themselves are never uploaded; only the hashes and common-contact names described above.
- Your own organisation of contacts — individual categories (including ones you create), ratings and notes, and the job title you type. Optional professional-category counts and Mo event identifiers are described above. An avatar photo that you choose to share is uploaded as described under "Profile avatar".
Location and technical connection information
- Location (Shake to Connect only) — when you shake to connect, your coordinates are sent once. Our server matches them in memory against a shake made within 3 seconds and 150 m, and discards them within 10 seconds; they are never stored. Locations you share in a chat are end-to-end encrypted (see above).
- IP address — your IP address necessarily reaches our API and our TURN relay, Google's public STUN server (stun.l.google.com, used during calls to find a network path) and Apple Maps (map previews). Our servers record it in routine technical logs for security and troubleshooting; we do not use it to track or profile you.
Services we rely on
Our API, database, storage for encrypted files and TURN relay run on servers we operate. We also rely on Apple (Sign in with Apple, Apple Push Notification service, Apple Maps and on-device speech recognition) and on Google's public STUN server. When SMS verification is enabled, the configured provider, Vonage Verify or Twilio Verify, sends and checks the one-time code; it receives your own number, not your contacts or messages. Resend can deliver a support message to our team when you choose "Email us instead" and email delivery is enabled. Notifications about new messages carry no message content; notifications about connection requests may include the other person's display name. Rings contains no analytics, advertising or cloud AI services.
What we do NOT do
- No advertising, no trackers, no analytics SDKs, no data brokers.
- No selling of your data and no sharing of it with third parties for their own purposes. What you share inside Rings (your display name, avatar, common-contact names, "About you") is shown only to the people described above — never to anyone outside the app.
- No reading of your private chat messages or calls: they are end-to-end encrypted, and transcription happens on your iPhone. Support and introduction request text are readable as described above.
- No ranking people for money, no promoted placement, no use of any of this data for advertising or profiling.
Sign in with Apple
Rings asks Apple for your name to pre-fill your display name; it does not request email access. Your Apple sign-in identifier is kept in your iPhone's Keychain. Server access uses credentials belonging to your registered installation; an Apple sign-in or phone number does not open another installation's history.
When server-verified Apple sign-in is enabled, the app also sends your Apple identifier, identity token and one-time authorization code to our server to verify your identity and bind the authorization to that installation. A single-use challenge expires after five minutes; expired challenge records are removed by scheduled cleanup. The server stores a keyed identifier linked to your installation and encrypts the token response (identity, access and refresh tokens) at rest. A token response may contain claims Apple previously authorized, including an email address; we do not use these claims for advertising or email marketing. These credentials are used for sign-in verification and revocation, not to recover chat history. They are not end-to-end encrypted from our server.
Stored Apple credentials are kept while the installation's account exists. When you delete it, the server removes the account binding and retains an encrypted token response and minimal retry information only to request revocation from Apple. This queue is separate from your deleted installation record. Revocation is retried if Apple or the network is unavailable; the queued credentials are deleted after successful revocation. Older accounts, or deployments without server-verified Apple sign-in, may not have stored tokens to revoke.
After deleting your Rings account, check its Apple sign-in access. You can remove it in iPhone Settings › your name › Sign in with Apple, select Rings or its developer, then choose Delete or Stop Using and confirm. Older iOS versions list apps under Password & Security › Apps Using Your Apple ID. You can also manage this at account.apple.com › Sign-In & Security › Sign in with Apple. Check the apps listed before confirming: Apple may group several apps under one developer. Apple explains how to manage this access.
Updated Rings versions check the Apple authorization state. A confirmed revocation can start account deletion when Rings detects it; if the server is unreachable, the app keeps data locked while deletion is retried. A missing credential requires sign-in again without erasing your history. A network error alone does not trigger deletion. To initiate deletion directly, use Settings › Delete Account in Rings. Apple's authorization can be shared across installations using the same Apple Account; do not assume that revoking it affects only one iPhone.
Data retention and deletion
- Delete your account — Settings › Delete Account. Our server deletes this installation's account and its data: display name, avatar and its photo, phone-number hash and verification records, contact hashes and common-contact names, connections, group memberships, queued messages and files, encryption keys, "About you", call log, support messages, blocks and the reports you filed. The app then erases its local data and asks you to close and reopen it to finish cleanup. Shared Mo records follow the rule described above. Messages already delivered remain on the other person's device, as with any messenger. Stored files are removed through a deletion queue with retries; download links issued earlier can remain valid until they expire. Reports other people filed about an account are kept for safety. Apple credential storage, automatic revocation when available, and manual removal for older accounts follow the rules above.
- Stop contact matching — turn off Settings › Share contacts for matching. Our server deletes your uploaded contact hashes and the common-contact names exchanged in your connections, and the app stops uploading them until you turn sharing back on. If you are offline, the deletion happens when your iPhone reconnects.
- "About you" — change or clear it in Settings › About you.
- Avatar photo — change it in Settings, or choose initials or a ring instead of a photo; the photo is then deleted from our server.
- Retention periods — encrypted messages and their delivery metadata: up to 7 days after delivery, 30 days if undelivered; encrypted files: 30 days; contact hashes and common-contact names: until you turn sharing off or delete your account; installation account data, avatar, connections, call log and support messages: until you delete that account; encrypted Apple token responses when server-verified sign-in is enabled: while the account exists and, after deletion, only until its revocation request succeeds; phone verification records: removed by scheduled cleanup once more than 24 hours old; shared and previous-number Mo records: as described under "Mo allowance"; temporary call rooms: until closure or expiry as described above; abuse reports, moderation records and banned phone-number hashes: kept for moderation.
You can also ask us to delete your data by writing to privacy@gaiiafoundation.com.
Your rights
Depending on your jurisdiction (including GDPR), you have the right to access, correct, export or erase your personal data. Write to us and we will respond within 30 days.
Changes
We will post any changes to this policy on this page and update the date above.