Privacy Policy

Our Commitment to Privacy

At Fizz, we understand the deeply personal nature of your wedding day and the memories you create with the people you love. We are committed to protecting your privacy and handling your personal information with the utmost care and respect, recognizing that you are entrusting us with some of your most precious moments.

Information We Collect

How We Use Information

We use your information for: Wedding Page Services (Creating, maintaining, and securing your wedding page and content), Security & Safety (Protecting your account, preventing fraud, maintaining service integrity, and checking guest book text against a fixed list of terms so the couple can review anything that matches before it appears), Service Improvement (Enhancing our services and developing new features to better serve you).

Information Sharing

We share your information with third-party services to provide and improve our services. Additionally, guest information (name and email address) is shared with the wedding page owner who invited you, to enable them to manage access to their wedding page. Guest book posts and uploaded media are visible to all guests of the wedding page.

Writing Assistance and Artificial Intelligence

Some parts of the site offer to help you write, your story, a speech, a message to the couple. These features are optional and only ever run when you choose to use them. They are there to help you make a start, not to write anything for you. One thing that is often assumed to be artificial intelligence is not. We check the text of guest book posts and comments against a fixed list of terms, so that the couple can look at anything matching before it appears on their wedding page. That check is a straightforward comparison against a list, carried out on our own servers. Nothing is sent anywhere for it, no other company is involved, and it builds no profile of you. It has no legal or similarly significant effect, and the decision that follows is made by a person: the couple hosting the wedding, who choose whether to publish the post or delete it.

When you use one of these features, the text you have entered is sent to Vercel's AI Gateway, which passes it to an artificial intelligence provider (currently Anthropic) and returns a suggested draft. Vercel acts as our data processor and Anthropic as its sub-processor. Both operate in the United States, and the transfer is covered by the safeguards described under International Data Transfers. When you are posting a single photograph to the guest book, you can also choose to let the assistant look at it, so that the suggestions can refer to what is actually in the picture. This is switched off unless you tick the box, and it is only offered on a post with exactly one photo. If you do tick it, a reduced-size copy of that photograph is sent with your text, through the same gateway to the same provider, and everything described in this section applies to it. The copy is not kept once your request has finished and is not used to train AI models. Photographs are never sent for any other feature, and never without you choosing it each time. The seating planner works the same way when you ask it for help: the guest names and table arrangement you have entered are sent, and a suggestion comes back.

• •Nothing is sent unless you choose to use one of these features.
• •A photograph is only ever sent if you tick the box to include it, on a post with a single photo. Your photographs are never sent otherwise, and never by default.
• •What comes back is a draft. You decide whether to keep it, change it, or discard it — nothing is ever published or applied on your behalf.
• •Artificial intelligence is never used to make a decision about you, your account, your subscription, or your access to the service.
• •The gateway does not keep your text once your request has finished, and we do not permit your content to be used to train AI models.
• •You can use every part of the service without ever using a writing-assistance feature.

We also use artificial intelligence internally to help us answer support enquiries and find records more quickly. It can read and summarise information; it cannot change your account, your subscription, or your event pages. Anything that needs acting on is done by a person.

The Fizz Wedding App

Fizz Wedding has a companion app for phones and tablets, which couples and their guests can use to share photos, videos and voice toasts on the day. The app is optional. Everything it does can also be done from the website in a phone browser, so you never need to install anything to take part in someone's wedding. This section covers what the app does that the website does not. Everything else in this policy applies to the app in exactly the same way.

Each permission is requested at the moment you first use the feature that needs it, never at sign-in, and you can refuse any of them. Refusing stops that one feature working and leaves the rest of the app unaffected. You can change your mind at any time in your device's own settings under the Fizz Wedding app. We do not receive your photos, videos or recordings unless you choose to share them to a guest book.

Analytics in the app

The app can collect anonymous usage analytics through Google Analytics for Firebase, which tells us things like which screens people open and whether a feature is working. Doing that requires storing an identifier on your device. We ask you first. The first time you open the app you are asked whether you are happy for us to collect usage analytics, and the answer is no until you say otherwise. If you decline, no identifier is stored and no analytics are sent. If you accept, you can change your mind at any time in the app under Settings, and collection stops from that point. None of this is used for advertising. Advertising identifiers are switched off in the app, we do not build advertising profiles, and we do not share analytics data with advertisers. Our legal basis for this processing is your consent, which you can withdraw at any time.

Crash and error reporting

Separately from analytics, the app reports crashes and errors to Sentry so that we can find and fix faults. This runs whether or not you accept analytics, because without it we cannot tell that the app has broken for you. A crash report contains technical information about the fault and the device: the type of device, the operating system version, the app version, and what the app was doing at the time. Before anything leaves your device we remove personal information and strip the security tokens from media links. Two sets of rules apply here, and we rely on a different one for each. For the information stored on or read from your device, we rely on the exemption for preventing or detecting technical faults, which the Privacy and Electronic Communications Regulations allow without consent. For our use of the information once we have it, our lawful basis under UK GDPR is our legitimate interest in keeping the app working, weighed against the limited and technical nature of what is collected. We do not use crash reports to build a profile of you or to track you between apps.

Reporting, blocking and screening

The app lets you report a post or comment you think is inappropriate, and lets you block the person who wrote it. Both are available from the same menu on the item itself. When you report something, we record what you reported, the reason you chose, and that the report came from you. Reports go to the couple whose wedding it is and to our support team, so that either can act. When you block someone, their posts, comments and reactions stop appearing for you anywhere in that wedding. Blocking is private from other guests: the person you block is not told, sees no change, and can carry on taking part for everyone else. It only changes what you see. You can review who you have blocked, and unblock them, in the app under Settings. Our support team can see how many people have blocked someone at the same wedding, but not who did the blocking. This is so we can tell the difference between one falling-out and someone causing a problem for many guests. Neither the couple nor other guests see this. Posts and comments written in the app are also checked against a fixed list of terms, exactly as they are on the website. Anything that matches is held back from the wedding page and shown only to the couple, who choose whether to publish it or delete it. A held post is stored in the same way as any other and is deleted with the wedding page. Reports and blocks are kept for as long as the wedding page exists and are deleted with it.

App stores

The app is distributed through the Google Play Store and the Apple App Store. When you download it, the store collects its own information about that download under its own privacy policy, which we do not receive. We do not receive your payment details from the store either. If you need help with the app, please contact us rather than the store, since the store cannot see your Fizz Wedding account and we cannot see what the store holds about you.

Data Security

We take protecting your memories and personal information seriously. Here's how we keep your wedding page content safe:

Data Retention

We only keep your information as long as needed for the wedding page services we provide or as required by law. Wedding page content is preserved while your page remains active. If your subscription ends, your wedding page and its content are kept for at least 30 days so that resubscribing restores them, after which they are permanently deleted. If you cancel during a free trial, your account and content are kept for at least 5 days before permanent deletion. The specific periods we apply are set out below.

Your Rights

You have rights regarding your personal information.

Age Requirements

Our services are for adults. Subscribers must be 18 or older to enter into a payment agreement, and guests must confirm they are 18 or older before they can join a wedding page. We do not knowingly collect personal information from anyone under 18 in their own right, and will delete such data if we discover it. There is one situation where information about a child reaches us, and we want to be clear about it. When an adult guest replies to an invitation, they may name the people they are bringing with them, including their children, and may add dietary requirements for them. That information comes from the accompanying adult rather than from the child, it exists so that the couple can seat and feed everyone, and it is deleted along with the wedding page. Children do not have accounts, cannot sign in, and cannot post. If you believe a child has provided us with personal information directly, please contact us immediately.

International Data Transfers

Your personal information may be transferred to and processed in countries outside the UK and European Economic Area (EEA), including the United States. When we transfer your data internationally, we ensure appropriate safeguards are in place to protect your information. We use third-party services that may process data in different locations: • Stripe (payment processing) - EU/Ireland and US • Supabase (database hosting) - UK region • BunnyCDN (media storage and delivery) - UK (London) with US replication • Google Analytics (website analytics) - US • Google Analytics for Firebase (optional app analytics) - US • Vercel (website hosting and AI Gateway) - US • Anthropic (AI writing assistance, as a sub-processor of Vercel AI Gateway) - US All our service providers have Data Processing Agreements (DPAs) in place and are required to maintain appropriate security measures and comply with applicable data protection laws. For transfers to the United States, we rely on: • The UK Extension to the EU-US Data Privacy Framework (UK-US Data Bridge) for certified organisations • The UK International Data Transfer Agreement (IDTA) or UK Addendum to EU Standard Contractual Clauses where applicable • Adequacy decisions for countries with adequate data protection Where possible, we prioritise UK and EU-based data storage to minimise international transfers.

Governing Law & Supervisory Authority