Your number, your plans and — if you allow it — your address book. Here is where that lives, who else touches it, and what we will not build with it.
wya is made by two people, Lars Schlageter and Clément Hamada, working from Konstanz, Germany. There is no growth team, no data team, and nobody whose job is to keep you in the app.
The person legally responsible for your data is named in the privacy policy — with a street address, not a mailbox company. Mail to us is read and answered by one of the two of us.
On one server we run ourselves, running software we wrote ourselves.
wya runs on a single small server in France that we operate ourselves. The backend is our own code, written so that we would not have to hand your data to a platform to get the features. It is small because we are small; we intend to grow it as wya grows, and to keep it in Europe when we do.
Venues and organisers additionally get email from us and can sign in with Google. Section 6 of the privacy policy lists every processor, in binding words.
None of it is end-to-end encrypted, and we do not claim it is. What we claim is narrower: it sits on a machine we run ourselves, in the EU, and it is not for sale.
Your phone book is the one thing on wya that belongs to people who never signed up. Here is exactly what we do with it.
If you allow it, the app reads the phone numbers in your address book — not the names, those never leave your phone — and sends them to our server over an encrypted connection, so we can tell you who is already on wya. Then the numbers are gone: what the server keeps is a keyed hash of each one (HMAC-SHA256 under a key that exists only on our server) and its country code. That holds for every number in your book, including the ones that belong to nobody on wya.
A plain hash would not be honest here: there are few enough phone numbers that anyone could try them all. The key is what makes the stored hashes worthless on their own — a copy of our database could not be turned back into numbers without it. We need the hashes for exactly one thing: when someone from your address book signs up later, we recognise their number and connect the two of you.
Public events come from venues and organisers, not from users. Before one can publish, a person has checked that it is real.
A venue or organiser signs up on the web with an email address or a Google account and can edit its profile — but not its address. The address is set only through verification: they search for it, drop the pin on the map, and attach a document that shows the organisation operates there — a business registration or a hospitality licence, for instance. Without the document the request cannot be sent.
One of us reads every request and accepts it or rejects it with a reason. Acceptance is what makes the organisation verified and ties the address to it; the proof document is deleted at that moment, because it was only ever needed for the review. Renaming a verified organisation revokes the verification, so a badge cannot quietly change hands.
AI helps us build wya. The ideas, the decisions and the final say are ours — and we do not use it on you.
Every idea in wya comes from us — from the evenings we plan and the group chats that never quite converge. AI is part of the toolchain that turns those ideas into a product: it writes code alongside us, drafts the German and French, and helps with copy like this page. That is how two people get a product of this size out the door.
It does not lower the bar. Everything that ships is read, run and tested by one of us first: code is reviewed by a person, translations are checked by the native speaker on the team, and every feature runs on our own phones before it goes out.
And nothing gets added that is not, in our eyes, perfect. If a feature is not there yet, it waits. We would rather ship less than ship something we have not checked.
What wya does, and what it refuses to do, comes from the two of us and the evenings we plan. No tool decided what this app should be.
Code, translations, copy. A tool, used by two people who know what it should say.
Nothing reaches your phone that one of us has not read, run and tested.
No AI and no algorithm decides anything about you inside the app. Nothing ranks your friends, nothing scores your posts, nothing scans your photos. Your feed is your people, and only your people.
There are enough apps on your phone built to keep you on it. This one is built to be closed.
The landing page says the app should end. This is what that costs us — the things every other social app has and this one will not get.
We could not measure how long you spend in wya even if we wanted to. Our server records only that you used the app on a given day — one entry per person per day, never how many times you opened it or for how long. A product cannot optimise a number it does not have.
Success is you closing wya and being somewhere. This page is what makes that sentence true.
We would rather say this here than let the sections above imply more than is there. wya is run by two people.
If something here is unclear, or you think it is wrong, write to us. The answer comes from one of the two of us.
Write to usNo. There are no ads and no data buyers, so there is nothing it would be sold for. The privacy policy says so in binding words.
Technically, yes: messages are not end-to-end encrypted, and they sit on our server. We do not read them, and we act on reports — the child safety standards say the same, for the same reason.
Block them from their profile: you disappear from each other, and they are not told. If what they posted breaks the rules, report it from the same place — a profile, a story or an event — with one of five reasons, and a person reads it. And there is no way for a stranger to find you on wya in the first place, which is what the child safety standards explain.
In France. We do not name the hosting company on a public page; ask us and we will tell you.
Not the numbers. We keep a keyed hash of each one so we can connect you when they sign up, and the key never leaves our server. We do not message them, we create nothing for them, and withdrawing the contacts permission deletes the hashes. Section 2.1 of the privacy policy is the binding version.
Because there are two of us. The ideas are ours; AI helps turn them into code and copy that would otherwise need a team. The bar stays where it is: a person reads, runs and tests everything before it ships, and nothing goes in that we are not happy with.