Your guests, your memories.

Partake is a wedding guest experience. Couples buy a Partake package to run photo, video, game, and memory features at their wedding. Guests use Partake for a single night by scanning a QR code.

This policy covers both sides: what we collect from couples who sign up, and what we collect from guests who show up.

From couples: name, email address, wedding date, couple names, event PIN, an optional RSVP list if you upload one, your love story if you choose to write one for Mad Libs, your trivia answers, your custom challenges, your video prompts, and your Stripe customer ID and last-4 of your payment card (Stripe holds the full card, we never touch it). That is the whole set.

From guests:the name they type on the entry screen, the photos and videos they upload, the trivia answers they type, the mad lib words they type, the video prompt answers they record, and the names of guests they meet during challenges. We don’t collect email addresses, phone numbers, or account information from guests. There is no guest account.

Automatic, minimal:a random session token stored in the guest’s browser localStorage so we can recognize them when they come back mid-event. Standard request logs from Vercel (IP address, user agent, timing) are kept for 30 days for abuse prevention and then deleted.

We do not sell data. We do not share guest names, photos, videos, or anything else with advertisers, data brokers, or analytics companies. Partake is paid for directly by the couple, so we’re never under pressure to monetize your guests.

We do not train AI models on your love story, your photos, or anything your guests create. When The Partake Wizard generates a mad lib or trivia draft it calls the Anthropic API with your story once, receives the draft, and forgets the input.

We do not use facial recognition. We do not scan photos for faces, people, or identity. Uploaded images are stored as plain files.

Every piece of event data (photos, videos, mad libs, trivia, challenges, video prompt answers, guest names) is retained for 12 months from the wedding date. We email the couple at month 11 and again two weeks before the deadline with a one-click export link. At 12 months, everything is permanently deleted.

Couple account data (name, email, payment history) is retained for as long as the account is active. Delete your account any time from the dashboard and we remove it from our live systems within 30 days.

RSVP lists are a sensitive case: they get deleted from our systems as soon as the event expires, regardless of whether the couple has exported the rest of their memories.

Every guest page has a “Delete my data” button in the footer. Tapping it removes the guest’s session, every photo and video they uploaded, their trivia answers, their mad lib entries, their video prompt responses, and every challenge completion they logged. There is no confirmation email and no approval from the couple: the guest decides, the data is gone.

Guests can also flag any photo (theirs or someone else’s) with the flag button on the gallery. Flagged photos disappear from the gallery immediately and land in the couple’s moderation queue for final delete.

Guests who want a copy of their own uploads can email us at hello@partakeweddings.com from the address they’re willing to identify with and we’ll send a ZIP within 30 days.

Couples can export every artifact from their event any time via the memory portal’s “Export all” button. The export streams a single ZIP with photos, videos, video prompt answers, mad libs, trivia, challenges, and event metadata.

Couples can delete any individual photo, video, or prompt response from the memory portal. Deletes are permanent.

Couples can delete the whole event and everything in it from the dashboard. One confirmation, no undo.

Partake runs on Vercel (application hosting), Supabase (database, file storage, authentication), Stripe (payments), Resend (email), and the Anthropic API (The Partake Wizard). These are the only four processors that ever see your event data in the course of normal operation. Each of them is under a data processing agreement with us and cannot use your data for their own purposes.

Supabase stores files in AWS S3 in US regions. Every file URL we hand to a browser is short-lived and signed: they expire within an hour, so a URL leaking later doesn’t grant access.

We use a small number of strictly necessary cookies for couple authentication (session cookies set by Supabase Auth) and a single localStorage entry per guest per event to remember their session token so they can pick up where they left off.

We do not set analytics cookies, advertising cookies, or tracking pixels. There is nothing to accept or reject: the only cookies are the ones that make the product work.

Partake is intended for adults setting up and attending weddings. The service is not directed at children under 13, and we do not knowingly collect data from them. If you believe a child has submitted personal data through Partake, email us and we’ll delete it.

If you’re a couple in the EU, UK, or another jurisdiction with a formal data processing framework, we’re happy to sign a Data Processing Agreement with you before you run your event. Our standard DPA mirrors the obligations in this policy and covers the usual GDPR requirements: security, sub-processors, data deletion, and incident notification.

Email hello@partakeweddings.com with the subject “DPA request” and we’ll send you a countersigned copy within 48 hours. There is no fee and no minimum event size.

If this policy ever changes in a way that affects what we do with existing data, we’ll email every active couple before the change takes effect. Minor wording edits that don’t change the substance can ship without notice but will update the “last updated” date below.

Questions, concerns, or a data request? Email hello@partakeweddings.com. A human replies within 48 hours.