Rings gaiiarings.com →

Privacy Policy

Rings · Last updated: November 6, 2026

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.

"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

Location and technical connection information

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

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

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.