Privacy Policy

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.

Who we are

The controller is the Wemeo operator identified below. Contact hello@wemeo.com about this policy or your rights, even if you do not have an account.

Wemeo is the trading name. Any registered company-name change will be reflected after registration is confirmed. / Wemeo este denumirea comercială. Numele societății va fi actualizat după confirmarea înregistrării schimbării.

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. We store your participation, ticket and relevant communications to operate the outing. A profile photo is required to join; the organizer and other participants may see your name and photo. Email is optional unless needed for a specific service. Public visibility beside follows and saved events is a separate choice.
• 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. We use session tokens, preferences, catalogue caches and optional notification tokens to provide the service. Optional usage analytics are disabled until you opt in. When enabled, the iOS app uses a random installation identifier; web events can be linked to your signed-in account. Abuse prevention uses short-lived IP-derived records.
• 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.
• We send sign-in codes and necessary service, security, legal and outing updates. These may use email or notifications depending on the service. Optional reminders can be switched off. Promotional email requires a separate lawful permission; a public contact address is not treated as marketing consent.
• Public names and avatars beside follows or saved events are off by default. You can explicitly opt in through Privacy settings and withdraw that choice there. These associations can reveal personal interests, including sensitive interests. Private participation in an outing has a separate audience: its organizer and participants.
• To operate, secure, and improve the service (including throttling sign-in attempts to prevent abuse).

Legal basis (EU/EEA)

We use contract for the requested service and participation eligibility; consent for optional analytics and optional public visibility; and assessed legitimate interests for security and operation. Interests can reveal sensitive information: public display beside follows and saved events requires explicit consent and is off by default. You can withdraw consent for future processing. Service notifications and promotional communications have separate purposes and legal bases.

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

AI-assisted imports process reviewed public source pages and organizer content only for permitted purposes. Incidental email addresses and phone numbers are removed from prompts where detected. Public names and text may still be personal data. External AI processing requires a reviewed provider agreement, model licence and data-processing configuration; local processing is an alternative. Account records and private chats are excluded from this catalogue pipeline. Contact us for the source and recipient details concerning your information.

How we share information

We do not sell personal data. We use the providers below to deliver the service. Their role depends on the activity: authentication or map providers may act as independent controllers for their own services; hosting and storage providers process data under the applicable agreements.

• 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.

Management and investor access use session records and, for investor sign-in, a verification email. Expired verification/session metadata is scheduled for removal after 24 hours unless held for an incident or legal obligation. Recipient access grants and case/audit records have separate reviewed retention rules. / Accesul conducerii și investitorilor folosește înregistrări de sesiune și coduri de verificare prin email. Metadatele expirate sunt programate pentru eliminare după 24 de ore, cu excepția păstrării necesare pentru incidente sau obligații legale. Drepturile de acces și cazurile/auditurile au reguli separate de păstrare.

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.

Public-source information and reports / Date din surse publice și raportări

We may obtain event, professional organizer and venue information from the source linked to a listing. We assess a lawful basis for each use; a public source is not consent. You can request source details, access, correction, deletion or object through the report form, without an account. Notices and decision records are used to investigate, respond and establish or defend rights; restricted retention depends on the case and legal obligations. Applicable individual notices are provided where required; this page does not replace them.

Putem obține informații despre evenimente, organizatori și localuri din sursa indicată în anunț. Evaluăm temeiul fiecărei utilizări; o sursă publică nu reprezintă consimțământ. Poți cere detalii despre sursă, acces, corectare, ștergere sau te poți opune prin formular, fără cont. Raportările și deciziile sunt folosite pentru investigare, răspuns și apărarea drepturilor, cu păstrare restricționată potrivit cazului și obligațiilor. Furnizăm informări individuale când sunt necesare; această pagină nu le înlocuiește.

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

Optional product analytics are off by default. You can enable or withdraw them in the controls below on the web, or Privacy preferences in the updated iOS app. Withdrawal stops new collection and clears pending events and identifiers on that device. Previously collected server events follow the retention and data-rights rules below. Crash reporting also passes through this optional analytics pipeline. Third-party analytics scripts are disabled.

• First-party log. With your choice enabled, we record event names and limited properties. Web events can be linked to your signed-in account. iOS uses a random installation identifier and links it to the account on sign-in. Search text and private messages are not included. Account deletion removes associated analytics under the deletion procedure.
• 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

The website stores essential sign-in information, choices such as language and privacy preferences, and cached catalogue data. An invite code may be kept temporarily to complete a sign-in you requested. We do not load advertising cookies or third-party analytics scripts. Optional first-party analytics require the separate choice below.

The iOS session token is stored in Keychain. Preferences and catalogue caches use app storage; optional analytics identifiers and queued events are stored only after opt-in in the updated app. Withdrawal clears that analytics storage. Uninstalling does not itself request deletion of server data, and Keychain entries may persist; use account deletion to request erasure.

Children

The discovery service is not intended for people under 16. Hosting and Wemeo-hosted participation require an adult declaration (18+). We store the declaration version and time for these eligibility rules, rather than your date of birth or an identity-document copy. Contact us if you believe an ineligible person is participating.

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.