Privacy

Privacy

Draft — to be reviewed

Plain language, not a substitute for legal advice. This describes what the app actually does.

What we collect, and why

To plan a night out, we ask an organiser for a date, area, group size and comfortable budget, and each friend who joins for the same five private answers: their budget, area, hard no's, vibes and travel limit. We use those answers only to work out three costed plans that fit the whole group — never for anything else.

If you sign in, we also collect an email address, used only to send a one-time sign-in code. We never ask for a password.

Who sees what

A participant's budget is never shown to anyone else in the group, or to the organiser — not the number, and not anything derived from it (a minimum, an average, a "comfort ceiling"). The plan page only ever shows qualitative states like "Fits everyone's budget" or "Stretch option". This applies to admins too: there is no admin view anywhere in laweyn that shows a participant's budget.

A venue owner sees numbers for their own venue only: how often it appeared in plans, how often a group chose it, the typical group size, and the booking requests sent to it (with the name and number the person booking chose to give). They never see who was in a plan or what anyone answered. laweyn admins see the same numbers for every venue, and a list of locked plans (date, area, the place chosen, group size, and the organiser's email if they were signed in) — never budgets, hard no's or anything anyone typed.

Your plan history

If you're signed in when you make or join a plan, or you sign in later on the same phone, the plan is saved to your account so you can find it again under Your plans. It stays there after the 30-day erasure below, as the date, the meeting area, how many people came and the place the group chose. Your budget, starting area and hard no's are still erased on schedule. Nobody else can see your list.

Erased after 30 days

Every participant and organiser's budget and hard no's, each participant's own starting area, and any free-text description of the plan are erased automatically 30 days after the plan's date. What's erased is gone — we don't keep a copy. What stays afterward is described below, and it's never anyone's individual answer.

What's kept

Some things aren't erased, because they're not private answers to begin with:

  • Names — shown to the group, so everyone knows who's coming.
  • The plan's meeting area — public by design; it's the whole point of the plan.
  • A booking's contact name and phone number — kept so a venue can honour a booking request made through laweyn.
  • Your plan history, if you're signed in (see above).
  • A phone number on your profile, only if you add one yourself — it prefills booking requests and is shown to a venue only inside a request you send. Remove it any time from your account page.
  • Your saved places, and which places you opened, picked or asked to book — kept under your account, or under an anonymous id in a cookie on your device if you never sign in. They order Explore for you and give your own plans a small, labelled nudge ("You saved this"); they never affect anyone else's plan and are never shown to your group. Which pages you opened is forgotten after 90 days.
  • Counts of how often each place is shown and chosen.
  • Anonymous aggregate statistics — a coarse budget range and how often an area/time combination comes up short, never linked to a plan, a person, or an exact figure.

Who else sees it

laweyn runs on Supabase (database) and Vercel (hosting), and sends sign-in codes through Resend. If AI-assisted free-text parsing is turned on, the text you type when describing a night is sent to Anthropic to extract the same five answers — never stored by laweyn alongside your other answers, and this only ever happens for the free-text box, never a friend's private answers. If error monitoring is turned on, it uses Sentry, configured to strip cookies, request bodies and anything that looks like a budget, area, hard no or free-text description before an error report is ever sent.

Questions

Reach us at [contact email — to be filled in].