GLUE: Privacy Policy
Effective date: September 27, 2026 · Controller: GLUE (iglued.us), operated by its founder during the open beta · Contact: support@iglued.us (privacy requests: subject “privacy”) · Data protection contact (LGPD encarregado / GDPR): support@iglued.us · EU representative: not yet appointed; contact us directly
This policy explains what GLUE collects when you use the website, the web app, the Telegram mini app and bot, why, with whom it is processed, how long it is kept and what rights you have. GLUE is for people 16 and older.
1. What we collect
| category | what | when |
|---|---|---|
| Account | a random identifier; if you link a sign-in: your email address; the identifier and email address your Google or Apple account provides; or your Telegram user number with your @username (without one, the name on your Telegram account); for each device you sign in from, its browser and system (such as “Chrome, macOS”) and a session token | when you start and when you link a sign-in |
| Conversation | what you write to the Sphere; voice messages and their transcripts; photos you send in the conversation; files the Sphere makes while doing what you ask; the hours of the day when you usually write | when you use the Sphere |
| Portrait | information derived from your conversation about how you live, expressed as structured descriptors, and readiness indicators; your age, city and gender as you mention them or as the Sphere notices them; the path to your portrait shown on About me (the scenes you have played and what is still missing) | continuously while you talk |
| Simulation results | outcomes of comparisons you requested (with public figures, friends, partners or members), and of the one GLUE runs by itself with a friend who came through your link; how closely you fit the members matching compares you with | when you request a comparison, when such a friend reaches their first checkpoint, and while matching searches for you |
| Face check (optional) | a numeric representation (embedding) of your face computed on your device, an age estimate and whether your face matched the photos in your album; no photo of your face is transmitted or stored; the embedding cannot be turned back into a picture but is biometric data | only if you choose to verify |
| Photos (optional) | photos you place in your album; for each, once you have agreed to the face check, the same kind of numeric representation of the face in it, computed on your device, so that the photo can be marked as matching your face check or not; until you agree, your device tells us only whether the photo shows a face | if you add them |
| Payments | purchase and subscription records, amounts, dates and the payment provider's transaction reference; for a stablecoin transfer, the network, the token and the transaction hash, which are public on the blockchain; we never see or store full card numbers | when you pay |
| Technical | IP address, browser and device type, language, time zone, error logs, push-notification subscription (if you allow notifications) | automatically |
| Usage | which pages of the open website you open; product events: the sign-in method you chose and whether you created an account, secured your guest account with a sign-in method or returned to an account you already had, milestones of your conversation and of what the Sphere has gathered, which screens of the app you open (by the screen's name), which public figure you opened, the outcome of the face check, what you started to buy and what you bought with its amount and the way you paid, what you spent karma on and how much; a counting cookie that tells one browser from another; once you are signed in, a pseudonymous account number, so that your visits from different devices count as one person. Page addresses inside the app are reduced to the shape of the route (`/app/chat/:id`) before anything leaves your browser | automatically |
We do not use advertising trackers and we do not sell your data. Cookies and browser storage keep you signed in, remember your settings, count visits and the product events listed under Usage above, and keep on your device the latest turns of your conversation, the list of your conversations and the photos and voice messages you have opened, so that the app opens at once. Signing out clears them from that device.
To count people rather than browsers, counting receives a pseudonymous account number once you are signed in. Our server computes it from your account with a secret key, and it is the same on all your devices, so your phone and your laptop count as one person. It is not your name, your email address or the identifier of your account, and none of them can be worked out from it. Counting never sees your conversation, your portrait, what you write on About me, the addresses of pages inside the app, or the identifier of any other person or of a conversation. Visits from automated browsers and from our own test builds are not counted.
2. Why we process it and on what legal basis
| purpose | basis (GDPR / LGPD) |
|---|---|
| run the Service: the conversation, your portrait, simulations, comparisons, introductions | performance of a contract |
| process sensitive data that is inherent to the Service: your relationships, family, intimacy, health of relatives, and (if you tell us) sexual orientation, religion or ethnicity | your explicit consent, given when you start the conversation: whichever way you came in, the consent line stands under the message field until you send your first message; you can withdraw it by deleting your account |
| face embeddings (of the face check and of your album photos) and age estimate | your explicit, separate consent, given on the check screen before the camera turns on; withdraw by deleting the check in settings (Settings → Account → Delete the face verification), which also deletes the embeddings of your album photos |
| voice recordings and transcripts | consent (you choose to send voice) |
| payments, invoices, fraud prevention | contract and legal obligations |
| security, abuse prevention, debugging | legitimate interests |
| understand how the product is used: counting visits and the product events listed under Usage, and the pseudonymous account number that joins your devices into one person | legitimate interests |
| sign-in codes by email and push notifications you enabled | contract / consent |
3. Who processes your data for us
Your data reaches the service providers and other recipients below. Those that process it for us do so under contract and only on our instructions; for the others (the search service and the public blockchain networks) we say what reaches them:
- AI model providers for the conversation and its analysis: OpenRouter, Inc. and the model providers it routes your requests to. Your messages, including photos you send, are sent to them to generate responses. We do not set any retention or training options on these requests: how long your data is kept there and whether it may be used for training is determined by the policies of OpenRouter and of each model provider.
- Speech: your voice messages are transcribed, and the Sphere's spoken replies are made, by speech services that run on the same machine as our servers and belong to another product on that machine, whose owner lets GLUE use them. Your recordings are not sent to the AI model providers.
- Web search: when the Sphere looks something up on the web, its search queries go to Exa, the search service built into its tools, and the pages it opens receive a request from our servers. The model writes the queries, and they may contain words from your conversation.
- Hosting and storage: servers operated by us, which during the open beta are located outside the EU/EEA, the UK and Brazil; Cloudflare, Inc. (hosting of the website and of our Telegram bot, and a proxy in front of our servers that all traffic between your browser and our servers passes through: it is decrypted there and encrypted again on the way to us; this also gives DDoS protection).
- Sign-in providers you choose: Google, Apple, Telegram; they receive only what is needed to sign you in.
- Payments: Stripe, Inc. for cards and Telegram for Telegram Stars; they process your payment details under their own policies, and Stripe also receives your account identifier with each card payment. A stablecoin transfer is recorded publicly on the Base or Polygon network, and we ask a public node of that network to confirm it.
- Counting: Google LLC and Google Ireland Limited (Google Analytics), for visits to the open website and the product events listed under Usage. They receive the pseudonymous account number described in section 1, which lets them count your devices as one person. They do not receive your name, your email address, your account identifier, the addresses of pages inside the app, your conversation, your portrait or what you write on About me.
- Email delivery: Resend, Inc. for sign-in codes.
- Push notifications: your browser vendor's push service, only if you enable notifications.
Some providers, and our own servers, are outside your country. Where the GDPR or LGPD applies, we rely on standard contractual clauses or equivalent safeguards, and on your explicit consent where the law requires it.
4. What other people see
Your conversation is never shown to anyone. Another member sees only the result of a comparison you both took part in and the shared summary. Cards you choose to share are generated to contain no other person's data beyond what both sides agreed to show. When you share your invite link, the preview of the link shows your main photo to anyone who has the link; it stops being shown with the link when you change or remove that photo, but the picture itself stays at its direct address until your account is erased. Public-figure readings contain only publicly available statements.
5. How long we keep it
| data | retention |
|---|---|
| account, conversation, portrait, results | while your account exists; erased after the 30-day grace period following deletion (signing in during that period cancels the deletion, except when GLUE was closed for age, section 7) |
| recordings of voice messages and photos you send in the conversation | 30 days after they are sent; transcripts stay with your conversation |
| photos in your album | while your account exists; a photo you remove from the album is no longer shown there, but its file stays in our storage until your account is erased |
| files the Sphere makes while doing what you ask | until a year after the Sphere last used them, or until your account is erased |
| face embedding and age estimate of the face check | until you remove the check or delete the account, and never longer than 3 years after your last visit to GLUE |
| face embeddings of your album photos | until you remove the face check or delete the account, and never longer than 3 years after your last visit to GLUE |
| payment records | as long as tax and accounting law requires; after your account is erased, without your account identifier |
| technical logs | our services keep their logs on our servers in a rolling store limited by size (up to about 50 MB per service): newer entries push out older ones, and a service's logs are removed when the service is replaced, which happens with every release, usually within a few days; when a service restarts without being replaced, its previous log stays. We have not set a fixed time limit. Cloudflare keeps its own records of the requests it passes to us under its own policy |
| one-off copies of the database | we do not make regular backups. Before risky maintenance we sometimes save a copy of a database on our own servers; it holds everything that database held at that moment and is deleted within 7 days, and while it exists, deleting your account does not reach it |
| counting data | at Google Analytics, for the retention period set on our account; totals it has already added up stay with Google. We compute the pseudonymous account number from your account identifier with a secret key that we keep. After erasure our payment records keep no account identifier, and where another member's karma history mentions you, the identifier is replaced by a one-way fingerprint; some service records (such as scheduled tasks) still carry it for up to about a month. Records of card payments kept by Stripe carry the identifier for as long as Stripe keeps them, so the number can still be matched to those records |
6. Your rights
Wherever you live, you can: access the data we hold about you, correct it, receive a copy, object to or restrict processing, withdraw consent, and delete your account and data: in the app (Settings → Account → Delete the account and the data) or by writing to support@iglued.us with “delete my data”. We answer within 30 days (15 days under LGPD where required). You can complain to your data protection authority.
European Union / United Kingdom: the rights above under the GDPR / UK GDPR; contact us at support@iglued.us.
Brazil (LGPD): the rights above plus information about public and private entities we shared data with and about the consequences of refusing consent; our data protection officer (encarregado) can be reached at support@iglued.us.
California: you have the right to know, delete, correct and to opt out of “sale” or “sharing” of personal information (we do not sell or share it in the CCPA sense) and to limit the use of sensitive personal information, which we use only to provide the Service you requested. We do not discriminate for exercising rights.
Illinois (BIPA): if you use the face check, we collect a biometric identifier only after you have read this notice and given written (electronic) consent; we do not sell, lease or trade it; we do not disclose it to anyone except the processors above for storage; we destroy it when the purpose is fulfilled, when you remove the check or delete your account, and in any case within 3 years of your last interaction with GLUE.
7. Children
GLUE is for people 16 and older. If you are 16 or 17, GLUE is for friendship only: matching looks only for friends for you, and topics of intimacy stay closed. We do not knowingly collect data from anyone under 16; if we learn we have, we delete it.
What counts is the age you tell the Sphere, not a guess. If you tell the Sphere you are under 16, it first asks your age again, and GLUE closes only if your answer confirms it. Then the conversation does not go on and the rest of GLUE closes too: purchases, comparisons, invitations and your photo album. You can still read your conversation, sign out and delete your account. The account and all its data are erased 30 days later. Signing in during those 30 days does not cancel this, unlike a deletion you ask for yourself (section 5); deleting the account yourself erases it at once. If your age was taken wrongly, write to support@iglued.us: once support lifts the closure, everything opens again and the erasure is cancelled. The age estimate of the optional face check never closes GLUE to anyone: it can only keep a stated age from counting when that age is far below what your face suggests.
8. Security
Data is encrypted in transit; sensitive data is stored on servers we control with restricted access; passwords are not used (sign-in codes and provider sign-ins only); session tokens are stored hashed. No system is perfectly secure; if a breach affects you we will notify you and the authorities as the law requires.
9. Changes
We will post changes here with a new effective date and, for material changes, tell you in the Service.