Privacy

Who we are

Unmet is run by Saleh Fayyaz (individual controller, pilot), based in Barcelona, Spain. That person is the data controller.

For any privacy question, or to use any of your rights, write to unmet.app@gmail.com.

What we collect

Only what you type or say, plus what happens at the table:

• Your university email (that's how you log in, and how we know your campus).
• Your answers: name, department, year, the languages you'd lunch in, and the three things you told us — something you're into, something you'd do more of on campus, something a stranger should know about you — and one tap on how you show up at a table (starts it, keeps it going, asks, listens). If you spoke them, your browser's own dictation (Apple or Google, depending on your device) turned your voice into text: we receive only the text, never any audio.
• The start times you tick — any of 12:00, 12:30, 13:00, 13:30 and 14:00: your usual ones, and any change you make for one week.
• If you choose to tell us: your gender, and whether you'd like a women-only table.
• Your language for the app and emails.
• Which weeks you said "I'm in", which table you sat at, its time and colour, and the one line we wrote about it.
• Your "How was it?" answers: whether you made it, who was there, who you'd lunch with again, and any note — and what your tablemates answer about the same lunch, which can mention you (more below).
• Events you post or say you're going to.
• A 6-digit login code that stops working after 10 minutes, the poster tag you scanned (if any), timestamps — and your IP address, kept in memory only (never on disk) to limit abuse, until the app restarts.
• If you report a problem at a table: what you wrote, who it was about, and whether you asked never to be seated with them again.
• Two cookies: one keeps you logged in (60 days), one remembers your language (1 year). No analytics cookies.
• Plan and table messages: what you write in the thread of a plan you're going to or posted, or in the chat of your lunch table, and when. If you report someone's message, we keep that you did. It's never shown to anyone, only counted.

No photos, no location, no tracking pixels, no analytics scripts. The only places you write to other members are the short thread on a plan you're going to and the chat of your lunch table.

To seat you we need your email, name, department, year, languages and the three answers — without them we can't form your table. The show-up tap only helps us mix the table. Gender and women-only are optional.

What we do with it

• Seat you at a table of three to five (usually four) with people from other departments and years, in a language you share. Your start times are used only to prefer people who ticked one in common with you: that never keeps you out of a table, and if your table has none in common, you agree a time in its chat.
• Write one line about why your table might click, from what each of you wrote. An AI (Claude) drafts it; Saleh reads every line, and can rewrite it, before any email goes.
• Propose a few small events on campus, from what members wrote they'd do more of. The AI drafts the ideas; Saleh approves each one. They may echo members' words, never with a name.
• Email you: your login code, a note when lunches on your campus start, your table the day before, a note if a tablemate can't make it (or is coming after all), "How was it?" the evening of the lunch, and a note if a week didn't form.
• Show your plan messages to the people going to that plan, and your table messages to the people at your table, and to no one else. They are never sent to the AI, never put in an email, and never used to seat you.
• Keep plan threads and table chats safe. Anyone in a thread or chat can report a message. Saleh looks at reported messages, can put one back or delete it, and can remove a member from Events, which also takes them out of plan threads and table chats (their lunches stay as they are). We keep a mark on that account saying so, until the account is deleted.
• If you enter your code but don't finish your answers: at most two reminder emails — the evening after, and before the next lunch closes. Each has a link that stops them, and your mail app's Unsubscribe works too.

We don't advertise, sell data, or build profiles for anyone else.

Nothing important about you is decided by a machine alone. Tables are formed by fixed rules a person wrote — mix departments and years, share a language, keep women-only tables women-only, never seat two people together if one asked not to be — and Saleh checks every table before any email goes. One more fixed rule does run on its own: a plan or table message that two different people report is hidden until Saleh looks at it. That's a rule in the code, not a judgement about you, and Saleh can put the message back or delete it.

Who sees what

• Your tablemates see your first name, your department, your year, the line about your table — which may use your own words, never your full answers — and whether you told them you can't make it. They see your table's time, never the start times you ticked.
• Everyone on your campus sees the events posted — the text, the first name of who posted it, and the first names of who's going.
• Nobody sees your email, your full answers, your gender, or your feedback except the person running Unmet, who reads full profiles to form and check the tables.
• A report is read only by the person running Unmet. The person it is about is never told, but if you asked never to sit with them again, we keep that so the tables respect it.
• The people going to a plan, and whoever posted it, see each other's messages in that plan's thread, with first names. Nobody else on campus can open it. Saleh doesn't browse threads: he reads a message only after someone has reported it.
• Reporting a message is anonymous: its author isn't told who reported it, and Saleh sees only how many people did. A message that two different people report is hidden from everyone except its author straight away, who sees a note in its place saying it's hidden until Saleh has looked.
• When you report a problem at a table, Saleh may email you one line to say he read it, and may decide you two are never put at the same table. He also sees how many different people have reported or blocked the same member: just the number. The person you report is still never told anything.
• Your table chat is read by the people seated at your table, with first names, and by no one else. It opens at 11:00 on the day of the lunch and closes a day after. Saleh doesn't browse chats: he reads a message only after someone has reported it. Like any chat, what you write can be copied by the people who can read it, and we can't delete those copies.

How was it?

After each lunch you can tell us — in the app from an hour after, and by email that evening — whether you went, who was there, who you'd lunch with again, and a note. You can change your answers any time. Your tablemates answer the same about you.

Only Saleh reads the answers, to count which tables worked and to spot problems. They are never shown to your tablemates, never sent to the AI, and never used to seat you. 90 days after each lunch the notes and the names ticked are deleted; only "I was there" stays, because it counts your lunches. Legal basis: legitimate interest. Don't want your tablemates' answers about you kept? Write to unmet.app@gmail.com.

Who helps us run it

These companies run parts of Unmet for us, under contract, and only for what we ask:

• Fly.io — hosts the app and the database in Paris (EU). A US company, certified under the EU–US Data Privacy Framework. It keeps automatic copies of the database (snapshots) for 5 days.
• Resend — delivers the emails. A US company: each email is stored in the United States for 30 days, under the EU Standard Contractual Clauses and the EU–US Data Privacy Framework.
• Anthropic (Claude, the AI) — reads the three things you wrote, tagged by department and year only, to draft your table's line and event ideas. Your name and email are never sent. Processed in the United States under the EU Standard Contractual Clauses. Anthropic doesn't train on this data and deletes it within 30 days (up to 2 years if its safety systems flag misuse).
• Google (Gmail) — our support inbox, unmet.app@gmail.com, is a Gmail account: what you write to us is stored by Google, a US company.

The safeguards for the US: the EU Standard Contractual Clauses and the EU–US Data Privacy Framework. For a copy of our contracts, write to unmet.app@gmail.com. We use no other service: no analytics, no ads, and we serve our own fonts.

Legal basis

Each use has one legal basis under the GDPR:

• Our contract with you (the Terms, Art. 6(1)(b)) — your account and login codes, seating you, and the emails about your table, a week that didn't form, or lunches starting.
• Our legitimate interest (Art. 6(1)(f)) in making the tables work, keeping them safe and keeping Unmet free of abuse — for the AI-drafted line and event ideas, the "How was it?" email and answers (including what tablemates say about each other), events and plans (your first name is visible on campus), plan and table messages, and keeping them safe, reports and blocks, and limiting abuse by IP address. You can object to any of these (see Your rights).
• Your consent (Art. 6(1)(a)) — for your gender and women-only choice. Withdraw it any time by clearing them in You.
• Your explicit consent (Art. 9(2)(a)) — only if you give it, with the separate tick in You → Account — for anything sensitive you mention about yourself (health, religion, sexuality, ethnicity, politics) to be used to write your table's line. Better still, leave those out: we don't need them, and the line never mentions them. Untick it any time.

How long we keep it

• Your account, answers (your start times too) and lunches: until you delete your account. An account whose answers were never finished goes sooner: see the last line.
• Notes and ticked names in "How was it?": 90 days after each lunch.
• Login codes: they stop working after 10 minutes and are deleted within the hour.
• Plan and table messages: in a plan's thread you can write until a day after the plan, and in your table chat from 11:00 on the day of the lunch until a day after it. They are deleted 30 days after the plan or the lunch. A message that has been reported waits for Saleh to look at it, for at most 180 days after, so a serious case isn't wiped before it can be dealt with.
• Copies at the companies above: emails at Resend 30 days; requests at Anthropic 30 days (up to 2 years if flagged for misuse); Fly.io's database snapshots 5 days; our own backups, when we take one, 7 days.
• An account whose answers were never finished (and never entered for a lunch): deleted 30 days after our last reminder, or after you stopped them.

Can't log in any more (say you've lost your university email)? Write to unmet.app@gmail.com from another address. We'll check it's you, then delete your account.

Your rights

• Download my data — in You, one tap gives you everything you gave us, as a file. What tablemates told us about you isn't in it: ask unmet.app@gmail.com and we'll tell you, without saying who said it.
• Delete account — in You. We erase your profile, your answers, your lunches, your feedback and your plan and table messages right away — and every message in a plan you posted — and remove your first name and id from your tablemates' records and from your tables' lines, and your first name from other people's plan and table messages.
• Object to the AI — write to unmet.app@gmail.com and your answers will never be sent to the AI again. Your table's line is then written from your tablemates' answers, or quotes your own words.
• Object to anything we do on legitimate interest — including keeping your tablemates' "How was it?" answers about you — by writing to unmet.app@gmail.com. We stop unless we have a strong reason that outweighs yours, like keeping a table safe.
• Withdraw consent any time, in You: clear your gender or women-only choice, or untick the sensitive-details box. It doesn't change what we did before.
• See, correct or restrict your data, or anything else — write to unmet.app@gmail.com. We answer within a month.
• Complain to the Spanish data protection authority (AEPD) at www.aepd.es.

Changes

If this page changes in a way that matters, we email you before it applies.