Last updated · November 1, 2026
The short version.
We collect: your email, the trip details you enter, what you choose to record about paying your organizer (never card or bank details), and emails forwarded to your trip's inbox.
We use this to: run the product, deliver trip-related emails, and compute aggregate trends for our investors and our team.
We don't: sell your data, share it with advertisers, run ad-tech tracking pixels, or train AI models on your private content.
Your rights: access, correct, export, or delete your data. privacy@wegoingapp.com.
What we collect, and why.
Account data · email, display name, password hash (we never store the plaintext), optional phone, avatar, home country, hometown, work type, hourly rate (used by our date-ranking algorithm — Patent B — to weigh lost wages against PTO). Lawful basis: contract (we need this to provide the service).
Trip data · trip name, destination, dates, party size, currency, dropout policy, itinerary items, lodging options, invite codes. Visible only to other members of the same trip. Lawful basis: contract.
Response data · the availability windows, budget ranges, room preferences, and flight details each traveler submits to plan a trip. Aggregated for the organizer; individual numbers (like your exact budget) are never shown to other travelers without your explicit choice. Lawful basis: contract.
Payments · WeGoing! does not process payments and never sees your card or bank details. Travelers pay their organizer directly in an app they already use (for example Venmo, Cash App, Zelle, Monzo or Revolut). We only keep what you record in the Trip Budget: amounts, dates, status, currency, and the payment-app name or handle an organizer chooses to share with their group. Lawful basis: contract.
Inbound mail (per-trip inbox) · when you forward a confirmation email (flights, hotels, Airbnb, Viator etc.) to your trip's unique @inbound.wegoingapp.com address, we parse it to extract relevant details (cost, dates, vendor) and attach them to the trip. The original email body is retained for 30 days then deleted. Lawful basis: contract.
Feedback · when you tap the 👍/👎 widget, we record your sentiment + any comment you wrote, the route you were on, your viewport size, your theme (light/neon), your scroll position, your device pixel ratio, your browser's user-agent string, your page title, any recent JavaScript errors your browser logged, and a screenshot of the visible page taken at the moment you tapped a thumb. The screenshot helps us reproduce visual bugs. It captures only what was on your screen at that moment — never another tab, the keyboard you typed, or anything that scrolled off-screen. Screenshots are stored in a private storage bucket and only the WeGoing! team can view them. They're deleted when you delete your account, or sooner on request. Lawful basis: legitimate interest (improving the product).
Analytics · we capture pseudonymous events (e.g. "a trip was created in country X with party size bucket Y") to build the trends dashboard our team and investors use. The events table has no link back to your identity on its own — the link lives in a separate, service-role-only table that an attacker would have to compromise in addition to the events to identify anyone. Events are bucketed (e.g. budget rounded to a range like $1k-$2k, not the exact amount) before they're ever written. Lawful basis: legitimate interest. See The privacy architecture, in detail below.
The privacy architecture, in detail.
We designed our analytics to be GDPR-grade by default, not US-grade with a GDPR retrofit. Here's what that means in practice:
Pseudonymous IDs. Every user gets an opaque analytics_id UUID. Our events table only carries that UUID. The mapping profile_id → analytics_id lives in a separate, service-role-only table. Compromising one without the other reveals nothing useful.
Bucketed values. Before any value goes into the events table, it's normalized into a range. A $4,237 budget becomes "3.5–5k." A trip to "Sapporo, Japan" becomes country = "Japan" (we drop the city). Names, emails, phones, and free-text fields never reach the events table.
90-day retention. Raw events are hard-deleted after 90 days. Only the pre-aggregated daily rollups (which are already deidentified) persist longer.
k-anonymity floor. Any aggregate we publish externally (press, reports, pitch decks) is gated at k≥5 — no bucket with fewer than 5 unique users contributing is ever shown. Cells below the floor render as "—".
Right to erasure. Hard-deleting your account severs the mapping. Your past events become orphan rows pointing at an unmappable UUID — they still contribute to aggregates (so our trends don't lie about history), but they can never be re-tied to you.
Aggregate publication.
We may publish aggregate insights about how WeGoing! is used — total trips planned, popular destinations, budget distributions, group-size patterns — in marketing materials, press, pitch decks, or industry reports. Every aggregate we publish is bound by the k≥5 floor described above. No individual user, trip, or transaction can be identified from any aggregate we publish. We do not, and will not without your explicit opt-in consent, sell or license your individual data to third parties.
Third-party processors.
We use the following companies to run WeGoing!. Each is contractually bound to handle your data only as instructed by us:
Supabase (Postgres database, auth) · supabase.com/privacy
Vercel (web hosting) · vercel.com/legal/privacy-policy
Postmark (transactional and inbound email, and newsletters advisors send to clients who opted in) · postmarkapp.com/eu-privacy
Google (Places + Maps APIs for destination search, photos, and the map tab; OAuth sign-in) · policies.google.com/privacy
SerpAPI (flight price lookups via Google Flights) · serpapi.com/legal/privacy-policy
Viator (a Tripadvisor company) (excursion search + booking deeplinks) · viator.com/privacy
Twilio (text-message notifications when you turn them on, and texts from your travel advisor when you agree to them) · twilio.com/legal/privacy
Stripe (payments for WeGoing!'s own paid features) · stripe.com/privacy
Microlink (link previews — when you paste a link in chat, we fetch its public preview) · microlink.io/privacy
Anthropic (AI — reads booking confirmations you forward, to pull out flight/hotel details; see "AI features" below) · anthropic.com/legal/privacy
Group chat & message security.
Each trip has a private group chat. Messages you post are personal data, and we protect them a few ways:
Members-only. Only people on that trip (the organizer + joined travelers) can read a trip's messages. This is enforced at the database level, not just in the app.
Encrypted at rest. Message text is encrypted (AES-256) before it's stored, using a key kept separately from the database — so a database breach would expose only unreadable ciphertext. This is not end-to-end encryption: our servers decrypt messages to display and search them for you, so we can technically read them (and will only do so where necessary, e.g. lawful requests or abuse investigations).
Private photos. Photos you share in chat are stored in a private bucket and served through temporary signed links — not public URLs.
Deletion. You can delete your own messages, and deleting your account removes your messages and the photos you uploaded.
When a travel advisor plans your trip.
Some trips are planned by a travel advisor who uses WeGoing! Pro. Your advisor decides what to send you, and we deliver it for them. They can only send you the two kinds of messages below if you said yes yourself. We never tick a box for you.
Newsletters from your advisor. If you tick the newsletter box on your advisor's intake form, a proposal, or a signing page, your advisor can email you their newsletter. If you signed up on an intake form, we first email you a link to confirm. We send each newsletter for your advisor through Postmark, under your advisor's name, with their agency's postal address at the bottom. We record whether each email was delivered, opened or clicked, or whether it bounced or was marked as spam, and your advisor can see this. Every newsletter has an unsubscribe link. Once you unsubscribe, or if an email bounces or is marked as spam, that advisor can't send you another newsletter. This does not stop the emails your advisor sends about a trip you're on. To prove you agreed, we keep the words you agreed to, when and where you agreed, a scrambled (hashed) version of your IP address, and your browser type. We don't use this list for WeGoing!'s own marketing, we don't share it with other advisors, and we never sell it.
Texts about your trips. If you turn on texts in You · Notifications, we text the number you give about your trips: payments, date changes and the day before you go. We first show you what we'll send, that message and data rates may apply, and how to stop. We keep the words you agreed to, when, and the number they cover. Changing your number or turning texts off stops them; reply STOP at any time. Sign-in codes are sent separately and aren't marketing.
Text messages from your advisor. Your advisor can text you trip reminders only if you tick the box and give your mobile number. We send one text right away to confirm. Texts go through Twilio, from our toll-free number in the US and Canada and from the sender name "WeGoing" in other countries. We only send texts between 8am and 9pm your time. A text due at night waits until morning. Reply STOP at any time to stop all texts from WeGoing! advisors to that number, and START to turn them back on. Where reply STOP isn't available, each text has an opt-out link. How many texts you get depends on your trip, usually a few around key dates. Message and data rates may apply. We keep your number, the words you agreed to and when, each text we sent, and whether it was delivered. Your advisor sees the texts they sent you. We don't use your number for marketing, and only Twilio receives it, to deliver the texts.
Paying for WeGoing! features.
Some optional features cost money, such as Agency Branding for travel advisors. When you buy one, Stripe (through its Link service) is the seller of record. Stripe collects your card details, works out sales tax, and sends your receipt. We never see or store your full card number. Stripe tells us your name, email, the amount, and whether the payment went through. WeGoing! does not take, hold or send any money for trips.
AI features.
We use AI to save you typing — never to profile you or make decisions about you. Specifically:
Reading forwarded confirmations. When you forward a flight or hotel confirmation to your trip's inbox, we send that email's contents to Anthropic (Claude) to extract the details (route, dates, confirmation number) and add them to your trip. We send only the forwarded email you chose to send. Per Anthropic's commercial terms, that content is processed to return the result and is not used to train their models.
No AI reads your chats. We do not run AI over your group-chat messages.
You stay in control. Everything the AI extracts is shown to you as a draft to review before anything is added to your trip.
Cookies & third-party embeds.
Our own cookies are strictly necessary. We set a small set of first-party cookies to run the product — your session, theme preference, per-trip view choice, our admin session, and a region flag used only to decide whether embeds need your consent (below). We do not use ad-tech cookies, tracking pixels, or cross-site identifiers, and we don't run behavioral advertising.
Embedded social posts are third-party. Some articles embed posts from Instagram and Facebook (Meta), TikTok, and X (Twitter). When one loads, that platform serves its own content and may set cookies and process your data under its privacy policy — not ours. WeGoing! never receives that data.
Instagram / Facebook (Meta) · privacycenter.instagram.com/policy
TikTok · tiktok.com/legal/privacy-policy
X (Twitter) · x.com/en/privacy
Your choice. If you're in the EU, UK, EEA, or Switzerland, these embeds stay off until you choose to load them — tap an embed to load just that one, or pick "Allow all embeds" to load them automatically from then on. Everywhere else they load automatically. You can change this any time, including withdrawing consent:
Your rights.
Under GDPR (and similar regimes elsewhere) you have the right to:
Access · request a copy of the data we hold about you, or download it yourself any time from You · Privacy & security · Download my data (your profile, your answers, payments you logged and messages you sent; never other people's).
Correct · ask us to fix anything that's wrong.
Erase · delete your account and the data tied to it. Self-service via Settings → Delete my account, or email us.
Port · receive your data in a machine-readable format.
Object · opt out of our legitimate-interest analytics. Email us and we'll honor it within 30 days.
All requests: privacy@wegoingapp.com. We'll respond within 30 days as required by GDPR.
Retention.
Active accounts · we keep your data as long as your account exists.
Inactive accounts · accounts with no activity for 24 months are flagged for review and may be deleted; we'll email you first.
After account deletion · we remove your personal data within 30 days. We retain payment records as long as required by law (typically 7 years for tax purposes), but those records contain only what the law requires, not your full profile.
Analytics events · 90 days raw, then aggregated into rollups that retain no personally identifiable information.
Inbound mail · raw forwarded emails retained 30 days; parsed structured data attached to your trip stays with the trip.
International transfers.
We're based in the United States, and our processors — hosting (Vercel), database (Supabase), email (Postmark), text messages (Twilio), payments for our own features (Stripe), and AI (Anthropic) — operate primarily in the US. If you're in the EU/UK and use WeGoing!, your personal data will be transferred to and processed in the US under the standard contractual clauses our processors have in place. If you have concerns, email us.
Children.
WeGoing! is not directed at children under 16. We don't knowingly collect data from anyone under 16. If you believe we have, email us and we'll delete it.
Changes to this policy.
We'll update this page when we change how we handle data. Material changes get an in-app notice. The "last updated" date at the top of the page is the source of truth.
Contact.
Privacy questions, GDPR requests, or anything else data-related: privacy@wegoingapp.com. General support: hello@wegoingapp.com.
