Effective 18 August 2026
Privacy Policy
ME3T is run by GLOBL. It puts three compatible people in a room together. That takes knowing something about you, so this page says exactly what we hold, why, and what it takes to get rid of it — in the order you would actually ask.
The short version: we collect what you type into your profile and what you do in the app. We do not track you across other apps or websites, we run no advertising, we sell nothing, and there is not a single third-party analytics or advertising SDK in ME3T.
What we collect
Things you give us
| What | When | Why |
|---|---|---|
| Email address and name | When you join a community with an access code | Your identity, your sign-in, and how another member knows who they met |
| Access code | At join | Puts you in the right community and event |
| Profile: your archetype, role, company, industry, city (and an optional second city), interests, what you're working toward, what you can help with, what you want help with, who you want to meet | Whenever you edit your profile | Matching, and giving the other two people something real to work with |
| Profile links: LinkedIn, and an intro video or media link | Optional, whenever you add them | Shown only after a ME3T is revealed — see reveal |
| Photo | Optional | Recognising each other in a room. Stored as a file, not in the database |
| Phone number | Optional, and off by default | Only shared if you switch sharing on, and only after a reveal |
| Answers to an organizer's event questions | At an event, if the organizer set questions | Better matches inside that event; the organizer can see them |
| A voice memo, if you record one | After a ME3T | Your own note about what happened. Stored as a file |
Things the app records as you use it
- When you say you're open to meeting, in which mode and city, and what you want out of it.
- The ME3Ts you were offered, whether you accepted, and who was at the table.
- Messages you send in a ME3T group chat.
- Your rating of a ME3T, whether you followed up, and what came of it.
- Poll votes at an event, and which days you marked the daily tip as read.
- Your ME3T Me connect code, and the connections it made.
- People you blocked, and reports you filed or that were filed about you.
- Your sign-in codes — as a one-way hash, never the code itself, so reading our database cannot sign anyone in.
Things we deliberately do not collect
- No device location. Never GPS, never background location, never an IP-derived position. See below.
- No password. There isn't one to steal — signing in is a six-digit code emailed to you.
- No contacts, photos library, calendar, microphone-in-the-background, or health data.
- No advertising identifier, and no payment details. Members pay us nothing.
- No tracking cookies. ME3T sets no cookies at all. Your sign-in token is kept in your browser's local storage, alongside your event code — it is what keeps you signed in, and clearing your browser data signs you out.
Location
ME3T is about meeting in person, so it has to know roughly where you are. It asks. You pick a metro area from a list — Los Angeles, not a coordinate — and you can pick a second one if you genuinely split your time. That city is the whole of the location data we hold about you, and it is a word you typed, not a reading taken from your device.
Your city is used to build matching pools and is shown to the other two members of a ME3T. Venues suggested for a meet-up are places an organizer added to their community, not places we detected near you.
Who can see what
This is the part ME3T is strictest about, because a networking app that leaks identity is worse than no app.
- Before a ME3T is revealed — the other two people see your archetype, role, industry, city, what you're working toward and what you can help with. They do not see your name, your photo, your email, your phone, your LinkedIn or your media link. Nothing in the pre-reveal view is meant to add up to a name.
- After all three accept — your name, photo, LinkedIn and media link are shown to those two people, and only those two.
- Your email and phone are different. They are contact details, and being revealed to someone is not the same as agreeing to be contacted by them, so each has its own switch and both start off. Nobody gets them unless you turn them on.
- Your community's organizer can see the member list for their own community — name, email, role, industry, city, event answers — plus aggregate numbers, open reports, and a leaderboard. They cannot see your ME3T chat messages or your private notes.
- Members of other communities see nothing of you. Communities are separate, and a membership in one is not a membership in another.
How ME3T uses AI
Once a ME3T is formed, one AI call writes the two lines of introduction at the top of it: a short note on why these three people fit, and an opening question for the table. That is the only place ME3T uses AI.
The matching itself is not AI. It is a published compatibility framework and a scoring function — the same three people, given the same inputs, are matched the same way every time, and we can tell you exactly why.
What is sent, and what is not
| Sent to the model | Never sent |
|---|---|
| Archetype name, role title, industry, your stated goal, interests, what you can help with, what you want help with, who you want to meet, and your answers to the event's questions | Your name, email address, phone number, photo, LinkedIn, media link, city, or member id |
The model is Claude, run by Anthropic as a processor for us. Under Anthropic's commercial API terms, what we send is not used to train their models. If the call fails or is switched off, ME3T falls back to a fixed template — the app works identically without it.
No profile is scored, ranked, accepted or rejected by AI. No decision about you is made by a model.
Who else touches your data
We sell nothing and share nothing for advertising. These are the companies that process data to run ME3T:
| Who | What they get | Where |
|---|---|---|
| Vercel | Hosts the app and the API; stores photos and voice memos | United States |
| Supabase | Runs the Postgres database everything else lives in | United States (AWS us-east-1) |
| Resend | Sends the sign-in code emails — your address and the message | United States |
| Anthropic | The AI introduction described above | United States |
| Google Workspace | Holds GLOBL's nightly encrypted database backups | United States |
One more, and it is opt-in per community: a community can connect ME3T to its own system, and if it does, we send that system a notification when a ME3T is proposed and when it fills — including the email addresses of the three members. Only communities that set this up receive it, and only about their own members. If you want to know whether your community has one, ask its organizer, or ask us.
We will also hand over data if the law actually requires it, and if GLOBL is ever acquired, ME3T data would move with it under this same policy.
How long we keep it
- Your account and everything attached to it: until you delete it. We do not expire accounts, and we do not quietly purge inactive members.
- Expired sign-in codes: deleted daily. A scheduled job sweeps them — they are single-use and short-lived, and the code itself was only ever stored as a hash.
- Proposed ME3Ts that nobody completed: expired daily, and the members go back into the pool.
- Safety reports: kept. A record that disappears the moment an account does is not a safety record. Once the member is deleted, the ids in a report no longer resolve to a person.
- When you delete your account: immediately, and for good. No grace period, no thirty-day shadow copy — the delete runs as one transaction while you wait.
- Backups: up to 30 days. The database is backed up nightly, encrypted at rest, and those copies age out on their own. They exist to bring the service back after a failure and are never used to restore one person's account. A deletion cannot reach into a backup taken before it, so for up to 30 days a copy of your data survives there, and then it does not.
The details of what is deleted and what survives are set out on Your Data.
Your rights
- See it — most of it is on your profile screen. Ask us for the rest and we will send it.
- Fix it — edit your profile at any time.
- Delete it — in the app, yourself, under Your account → Delete my account. You do not have to ask us and we cannot make you wait.
- Take it with you — ask and we will send your data in a machine-readable file.
- Be left out — set yourself to Invisible and you enter no matching pool. Block anyone, and the matching engine will never seat you with them.
- Object, or withdraw consent — turn off email or phone sharing, leave a community, or delete the account.
If you are in the UK or EU: our lawful basis is the contract between us for the profile and activity data that makes ME3T work, consent for the optional bits you switch on yourself, and legitimate interest for keeping safety reports. If you are in California: we do not sell or share personal information as those terms are defined, and we will not discriminate against you for exercising any of the above.
Any of these: email privacy@me3t.app. We answer within 30 days.
Security
- Everything travels over HTTPS.
- There are no passwords to breach. Sign-in codes are short-lived, single-use, attempt-limited, and stored only as hashes.
- Sessions are signed tokens that expire after 30 days.
- Communities are isolated from each other at the query level, and an organizer's key can only ever act on their own community.
No system is perfect. If you find something wrong with ours, email privacy@me3t.app and we will take it seriously.
Children
ME3T is for working professionals and is not for anyone under 18. We do not knowingly collect anything from children. If a member turns out to be under 18, tell us and the account goes.
Changes
If we change this in a way that matters, we will say so in the app before it takes effect. The date at the top is the date of the current version, and every page in this set carries the same one.