Privacy Policy

Guest Collab (“we”, “us”) is an event service at guestcollab.com: hosts create events, invite guests, collect RSVPs, and gather the photos and videos everyone takes. This policy explains what information the service handles, why, and the choices you have. It applies to hosts with accounts and to guests who use an event through an invitation link, with or without an account.

• Account information. You sign in with Google, Facebook, or Microsoft — we receive your name, email address, and profile photo from the provider — or, where offered, with a sign-in link emailed to an address that already matches your account or an event invitation, in which case the email address you enter is the account information we hold. You can optionally set a password, which is stored only in hashed form by our authentication provider. You can add profile details — phone, mailing address, dietary and accessibility preferences, and saved household members — to prefill future RSVPs.
• Event and guest-list information entered by hosts. Hosts enter event details (schedules, menus, links, notes for guests) and guest lists — names and, when the host has them, email addresses, phone numbers, mailing addresses, relationships, and internal notes. Hosts are responsible for having the right to share their guests’ details with us (see the Terms).
• RSVP responses. When you RSVP: your attendance, the people in your party, meal choices, and any allergy, dietary, or accessibility needs you choose to share. We use these only to run the event — they are shown to the event’s hosts (and its caterer, for meal planning) and never used for anything else.
• Content. Photos and videos you upload, guestbook and wall messages, comments, music requests, scavenger-hunt entries, and self-reported donations.
• Technical information. Session cookies for sign-in, a per-event cookie that remembers a guest’s check-in, a short-lived cookie used only to finish linking an invitation during sign-up, a fifteen-minute cookie that tells your browser a sign-in just created your account (so the sign-up is counted once), server logs, email delivery records (what we sent, bounces, and opt-outs), and a one-way code made from your network address (never the address itself), normally deleted within two days, used to limit repeated guest-list look-ups. The two measurement tools described under Analytics and advertising measurement below set their own cookies: PostHog’s (a year) and Meta’s (ninety days).

• Product analytics (PostHog). We use PostHog to see how the service is used — pages viewed, features used, and errors — so we can improve it. For signed-in hosts this is tied to the account (email, name, and plan). Guests using an event link are measured without a profile. Its click tracking does not record the text of what you click. We also use PostHog’s session replay, which records how a page looks and is used — including what appears on screen and what you type, but never passwords — so we can find and fix problems. Recordings are seen only by our team and kept for 30 days. Pages reached through a personal link (your RSVP, schedule, or unsubscribe link, or a sign-in link) are not recorded or reported at all.
• Advertising measurement (Meta Pixel). We use the Meta (Facebook) Pixel to measure whether our own advertising works: it tells Meta when someone reaches our site, views our pricing, creates an account, creates an event (that one was created — never what kind or its details), starts a checkout, or buys a plan (with the amount), and it may be used to show Guest Collab ads to people who have visited guestcollab.com. It never receives your guest lists, RSVP answers, photos, or messages, it does not run on pages reached through a personal link, and we turn off its automatic collection of button text and page metadata. If you arrived through a Meta ad, we keep the click identifier Meta attached to that visit on your account so that, if a conversion has to be reported to Meta from our servers instead of your browser (for example a purchase arranged by phone), it can be matched to the same ad; such a report carries your email address only as a one-way hash. You can limit all of this through your browser’s tracking protection or your Meta ad preferences.

• Running the service: events, RSVPs, galleries, schedules, menus, seating.
• Sending transactional email — invitations, RSVP confirmations and reminders, storage alerts, and security notices — through our email provider. Every non-critical email carries an unsubscribe link with per-category opt-outs, and we enforce sending caps and cooldowns so the same address is never flooded.
• Sending setup tips after you sign up or create an event: at most three emails, only while a step such as creating your event or getting your first guests in is still open. Turn them off any time under Account → Emails or from the unsubscribe link in any of them. To avoid emailing you at night, we keep an approximate time zone, taken from your connection when you sign in and from your browser when you create an event.
• AI drafting features (for example, drafting an event plan or a recipe from a dish name) send the text the host submits to our AI provider to generate a draft the host then edits. These features are host-initiated; we don’t feed guest lists to them.
• Security, abuse prevention, and debugging.
• We do not sell or rent personal information. The advertising measurement above is about our own ads for Guest Collab; your event content, guest lists, and RSVP details are never shared with advertisers.

Guest Collab is a sharing product, so visibility is part of the design — and worth stating plainly:

• An event’s hosts and the collaborators they add can see the guest list and RSVP details, including dietary and accessibility needs. A caterer the host connects sees meal-planning information (headcounts, meal choices, dietary roll-ups) — not guests’ private contact details.
• Guests see event content according to the access level the host chooses. At the most open levels, anyone with the event link can view shared photos and pages — treat event links accordingly.
• Your personal RSVP link is the key to your RSVP: anyone holding it can view and edit that response. Keep it private, and if an invitation is ever linked to the wrong account, the invitation page and the host can both undo it — and we notify the invited address whenever a linking happens.
• If you link an invitation to your account, the event’s host can see the account email your event mail goes to. Your saved private details (dietary preferences, address book, household) are never shown to hosts.

We share information only with the providers that run the service, under their own privacy commitments, and only what each needs: Supabase (database, authentication, and file storage), Vercel (hosting), Postmark (email delivery), Cloudflare (media storage and delivery), Google, Meta, and Microsoft (sign-in, when you choose them; Google also powers optional address autocomplete as you type a venue), Anthropic (AI drafting), Stripe (payments for paid plans — card details go directly to Stripe and never touch our servers), PostHog (product analytics), and Meta (advertising measurement, as described above). Information is processed and stored in the United States.

We keep information while your account or the event it belongs to is active. Deleting an event removes its guest list and uploaded content. If a paid subscription ends while your account holds more than the free storage allowance, uploaded photos and videos stay available to view and download for one month — we email warnings during that window — and are then permanently deleted. After account deletion (below) we remove your data within 30 days, keeping only what we must: billing records, and the email suppression list that ensures an address that opted out stays opted out.

• Account holders: email support@guestcollab.com from your account’s email address and ask us to delete your account. We will delete your account, your events, and their content within 30 days and confirm when done.
• Guests without an account: ask the event’s host to remove you from their guest list, or email us at the address above naming the event — we will remove your RSVP details and anything you uploaded.
• If you signed in with Facebook: you can also remove Guest Collab from your Facebook account’s Apps and Websites settings at any time; then email us as above to delete the data we hold. This section serves as our data-deletion instructions for Facebook Login.
• Email preferences don’t require deletion: every non-critical email has an unsubscribe link that works without an account.

Guest Collab is not directed at children under 13, and we don’t knowingly collect information from them. Hosts and guests may record a child’s first name, age group, or meal needs as part of a family’s RSVP — that information is provided by an adult and used only for the event. To have it removed, use the deletion contacts above.

Traffic is encrypted in transit, database access is controlled row-by-row so each account and event only reaches its own data, secret links (RSVP and unsubscribe tokens) are unguessable, and we log security-relevant account changes and email them to you. No online service can promise perfect security, but access to personal information is limited to what the feature in front of you needs.

If we change this policy in a way that matters, we’ll update the date at the top and, for significant changes, tell account holders by email. Questions or requests: support@guestcollab.com.