wemeo (“wemeo”, “we”, “us”) helps you discover communities, places and events in the cities we cover (Romania first, and the markets we have opened since), save the ones you like, and get a reminder before they start. This policy explains what we collect, how we use it, and your choices. By using wemeo you agree to this policy.
Who we are
The controller of your personal data is the operator of wemeo, based in Romania and reachable at hello@wemeo.com. Write there for anything in this policy, including the rights described below. Company registration is in progress; the registered name, registration number and registered office will be listed here as soon as it completes.
Information we collect
- Sign-in details. You sign in with Apple, Google or an email code. With Apple we receive the name and email address you choose to share (including Apple’s private relay address if you use “Hide My Email”); with Google we receive your name, email address and profile picture; with email sign-in we receive your email address.
- Profile. An optional display name, city and language; a profile picture if you upload one; and light, optional fun: your “city animal” quiz result and things you’d like to try (sidequests). If you signed in with Google we also check whether the picture Google sent is a real photograph or one of the coloured letter tiles Google generates for accounts that never set one: we fetch the image once, measure it, and discard it if it is a generated tile rather than store a picture you never chose. Where there is no photograph, your city animal fills the avatar, and if you haven’t taken the quiz we draw a simple letter from your name. You can add a phone number as an optional contact, and (if you host on wemeo) a short bio and your Instagram, Telegram or LinkedIn handles, which appear on your public host page. We also keep the hosts you follow and the events you have hidden from your list, so both stay as you left them.
- Activity. The communities, places and festivals you add to your list, and the events you save reminders for.
- Invites. Every account gets its own invite code, and the links you share carry it. If you arrive through somebody’s link and then create an account, we record which account invited you, once, at your first sign-in. The code lives in your browser tab until you sign in, and nowhere else.
- Outings. If you join an outing (small, capped group experiences hosted through wemeo) we record your participation and generate a personal ticket code. Joining requires a face other participants can recognise (either an uploaded photo or your city animal) and an email address we can reach you at; your first name and that face appear on that outing’s card to the other participants. Tapping “I’m interested” on the outings page stores that preference so we can tell you when sign-ups open.
- Outing chat. Every outing has a private group chat for the people on it. If you write there, we store your messages and show them, with your first name and your face (your photo or your city animal), to the other participants of that outing, and to nobody else. Messages are checked automatically, on our own servers, against a short list of disallowed words; they are never sent to any AI service. Another participant can report a message, in which case we keep a copy of the reported message together with the report so we can act on it. The chat closes 24 hours after the outing ends, and its messages are deleted 14 days after the outing’s date.
- Blocking and reports. If you block someone, we store that you did, on your account and as a marker on theirs, so the block applies in both directions, together with their first name and avatar, so the list in the app is one you can read and undo. The person blocked is never told. If you report someone, or a message, we keep the report: who reported whom, the reason you chose, anything you wrote, and for a message a copy of the message itself, so a moderator can still read it once it is deleted.
- Paying for a seat. Some experiences are ticketed. If you buy a seat, we keep the record of that purchase against that experience: the amount, the currency, how many seats, the payment method as the payment provider described it (for example “Apple Pay · Visa ending 4242”), the provider’s own reference for the payment, and the times it was authorised, charged or refunded. We never receive or store your card number. The organiser of the experience is the seller and receives the money; we pass it through and keep the record so that both of you can account for the seat. Your payment is visible to you and to the organiser, never to the other participants.
- Listings you submit. If you submit a community, place or festival, we keep what you sent, including the contact details you gave us so we can reach you about it.
- Technical. A session token to keep you signed in: in your browser’s local storage on the web, and in the iOS Keychain in the app; a device push token if you enable notifications in our iOS app; in the iOS app only, a random per-install identifier so we can tell one app session from another before you sign in (it is not your name, your email, or any advertising or device ID from Apple, and it is regenerated when you delete your account); basic usage analytics; and, briefly, your IP address to throttle abusive sign-in attempts. The website stores no such identifier. On the web, events fired before you sign in carry no key at all.
- Account status. If an email to you bounces or you report our mail as spam, we record that so we stop sending; in practice, sign-in codes. If an account is reported and actioned, we keep a moderation flag on it.
Stays on your device. Some things the app asks permission for never reach us. If you allow it, your location is used on your phone and nowhere else: on the website to sort what’s closest under “Near me”, and in the iOS app to say how far away a venue is. It is never sent to us and never stored — the app reads your position once while it is open, keeps that one reading in memory to work out the distances it prints, and writes it down nowhere. “Add to calendar” writes the one event you chose to your own calendar. If you host and scan guests' tickets at the door, the camera reads the code on the phone in front of you and nothing else: no photo or video is recorded, and no image is sent to us, only the ticket code itself, which is the one thing in this paragraph that does reach us, and only so we can answer whether the ticket is valid. Saving your city animal picture writes it to your photo library. Nothing else here leaves your phone, and none of it is collected. (Your profile picture is different. You upload that to us on purpose, and it is covered above.)
How we use your information
- To sign you in and keep your session active.
- To send you sign-in codes, the only mail wemeo sends you, besides a security notice to your previous address if the email on your account is ever changed. There is no newsletter and nothing recurring. The reminders you set are notifications on your own device, and outing details (the location, your ticket, a change of plan) arrive as push notifications in the iOS app.
- To show your first name and a small avatar next to the communities and places you follow and the events you say you’re going to (the “people going / following” you see on pages). This is on by default; you can turn it off anytime with the “show my picture” setting. You’ll still be counted, just never shown, and your own screens stop showing your photo there too.
- To operate, secure, and improve the service (including throttling sign-in attempts to prevent abuse).
Legal basis (EU/EEA)
Where the GDPR applies, we rely on: contract, to create your account and run the service you asked for; consent, to send the reminders and notifications you ask for (switch them off anytime); legitimate interests / your settings, to show your first name and avatar next to what you follow or attend, which you can switch off at any time; and legitimate interests, to keep wemeo secure and working. You can withdraw consent at any time without affecting prior processing.
Sign in with Apple or Google
If you sign in with Apple or Google, authentication is handled by them and governed by Apple’s Privacy Policy or Google’s Privacy Policy. We never see your password. We only receive a signed proof of who you are, which we verify directly against Apple’s or Google’s public keys.
AI processing
We use AI models to keep the public event catalogue fresh: they help read publicly available web pages of event organizers, venues and ticketing sites (event titles, dates, venues, descriptions). Your account data (email, name, follows, activity) is never sent to AI providers. The AI providers we use for this public-content processing are Anthropic and locally hosted models under our control. The same models also translate that public catalogue text — an event’s title and description — into the languages the apps offer, so you can read a listing in your own language rather than in whichever one the organiser posted it in.
How we share information
We do not sell your personal data. We share it only with the providers (sub-processors) that run wemeo:
- Supabase: database and image storage.
- Vercel: hosting and anonymous analytics.
- Apple / Google: to authenticate you when you choose Sign in with Apple or Google.
- Google Maps: the embedded map on a community or event page. It loads in your browser, so your IP address reaches Google; the map is only requested on pages that show one.
- Open-Meteo: the forecast shown on an event page. It is asked about the venue’s coordinates and the event’s date — never about where you are — so what reaches Open-Meteo is your IP address, on pages that show a forecast.
- Resend: to deliver sign-in codes, the only mail wemeo sends.
- Anthropic: AI processing and translation of public event and organizer web content only; never your personal data.
Some of these providers are located outside the EU/EEA. Where personal data is transferred internationally, it is protected by appropriate safeguards such as the European Commission’s Standard Contractual Clauses.
Community and place pages may link to third-party groups, Instagram pages and websites run by the organisers; those are governed by their own terms and privacy policies.
Data retention
We keep your account information while your account is active. More specifically:
- Sign-in sessions expire automatically (currently after 90 days) and are then deleted.
- Abuse-prevention logs: we briefly keep an IP-derived record of sign-in attempts to throttle brute-force attacks; these are pruned automatically (within hours).
- Analytics events are deleted after 180 days.
- Outing chat messages are deleted 14 days after the outing’s date, and immediately when you delete your account. A message that was reported may be kept together with the report while we handle it.
- Blocks are kept until you undo one or delete your account. Reports are kept while we handle them, and for as long as we need them to act on repeated behaviour.
- When you delete your account, we remove your profile, sessions, your entries in any outings, your messages in outing chats, your identifying details from any communities you submitted, and the analytics events recorded under your account; we complete deletion within 30 days.
You can switch off reminders, or request deletion of your account and data, at any time.
Deleting your data
Delete your account directly in the app (Profile → Delete account) or send a request through the in-app Support form or by email at hello@wemeo.com. We delete your personal data within 30 days.
Your rights
You can access, correct or delete your data, ask for a copy of it in a portable form, object to processing based on legitimate interests, and switch off reminders at any time (in the app, or by writing to hello@wemeo.com). If you are in the EU/EEA you have these rights under the GDPR, including the right to lodge a complaint with your local data protection authority. In Romania, the ANSPDCP.
Analytics
To understand how wemeo is used and improve it, we record basic product-usage events (for example a page opened, a community added to a list, a reminder set) and crash reports when the app fails. We do not record what you type. A search records how long the query was, never the words. These feed:
- Our own first-party log: event names and minimal properties, linked to your account while you’re signed in, and to nothing at all when you are not. No IP address is stored. Deleting your account deletes the analytics events recorded under it, not just your profile.
- Crash and freeze reports: if the app crashes or hangs, Apple’s MetricKit hands us a technical report the next day: our build number, the OS version and device model, the error codes, how long a freeze lasted, and the call stack of our own code. It describes what the app was doing, not what you were doing: no content, no messages and no location are in it. These reports ride the same first-party log above and are deleted with it.
Campaign parameters (utm_source/medium/campaign) are read from the link you arrived on and held in memory for that visit, so we can see which channel brought you in. They are not written to your device and do not survive closing the tab. An invite code from a friend’s link is the one exception: it is kept in your browser tab until you sign in, because signing in leaves the page and comes back.
Cookies, local storage & the app
On the web, we use your browser’s local storage for a session token. That is what keeps you signed in, and it is the only thing we store there. We use no advertising cookies, and no analytics identifier: nothing kept on your device follows you between visits.
In the iOS app there are no cookies. The session token is held in the iOS Keychain rather than ordinary app storage, so it is encrypted at rest and kept out of unencrypted device backups; the per-install analytics identifier and your display preferences (language, theme) are held in ordinary app storage. Deleting the app removes all of it from your phone.
Children
wemeo is not intended for anyone under 16. We do not knowingly collect data from children.
Changes
We may update this policy. We’ll change the “last updated” date above and, for material changes, let you know in the app.
Contact
Questions or requests: hello@wemeo.com, or use the in-app Support form.