Privacy

The controller of personal data processed in WeddUniverse is:

These are the main categories of data. The exact scope depends on the features you use. We neither buy data about you nor enrich it from other sources.

• Data

  Email, name and sign-in method. Firebase Authentication handles the password; WeddUniverse does not store it.

  Why

  So you can sign in to your wedding.

  How long

  Until you delete the account.

• Data

  The couple’s names, date, venue, style and wedding settings

  Why

  To create and display your wedding space.

  How long

  Until you delete the wedding.

• Data

  Tasks, budget, suppliers, documents, schedule, menu, music, transport, accommodation and gifts

  Why

  So you can plan the wedding and share the work with people you invite.

  How long

  Until you delete the relevant record or the wedding.

• Data

  Guest names, emails, phone numbers, notes, seating

  Why

  So you can invite people and organise the day.

  How long

  Until you delete the guest or the wedding.

• Data

  A guest’s answer, dietary preferences, allergies, accommodation, transport, answers to your own questions

  Why

  So the couple know who is coming and what to serve them.

  How long

  Until you delete the guest or the wedding. Diet and allergies are deleted automatically 60 days after the wedding date.

• Data

  Uploaded photographs and who uploaded them

  Why

  The wedding gallery, and letting a guest remove their own.

  How long

  Until you delete the photograph, the album or the wedding — and no longer than the tier's retention window (7 days to 6 months after the wedding).

• Data

  Voice and video wishes, the author’s name and technical recording details

  Why

  So guests can leave a wish and the couple can play it back.

  How long

  Until you delete the message or the wedding.

• Data

  Content for the wedding website, stationery, newspaper and children’s materials

  Why

  So it can be edited, published or exported.

  How long

  Until you delete the content or wedding; a published website disappears when you unpublish it.

• Data

  A player’s name, answers and score in a live quiz

  Why

  To run the quiz, recover after a disconnect and show results.

  How long

  A live game accepts no more input after 12 hours. Its record leaves with the wedding; a saved result also leaves when the quiz is deleted.

• Data

  Your questions, the assistant’s replies, proposed changes and request-operation data

  Why

  So the assistant can continue a conversation and prepare changes that you confirm yourself.

  How long

  You can delete a conversation; conversations and proposals also leave with the account, membership or wedding. An unconfirmed proposal can no longer be used after 24 hours.

• Data

  Plan, subscription status and a copy of invoice details, including the payer’s name and email

  Why

  To unlock paid features and show the document history.

  How long

  Copies of invoices for 10 years from issue, even if you delete the wedding — Czech accounting and VAT law require it. An unfinished App Store order is valid for 4 hours and is then usually deleted by the database within 24 hours.

• Data

  The invited address and hashes of the invitation tokens

  Why

  So an invitation works, and works exactly once.

  How long

  The link works for 90 days. The invitation record remains until the wedding is deleted.

• Data

  A record of changes to the wedding: who, what and when

  Why

  So the couple can see what happened.

  How long

  Until you delete the wedding.

• Data

  A one-way fingerprint of an IP address or sign-in value, the attempt count and the start of its time window

  Why

  To prevent automated guessing of codes and passwords and flooding of public forms.

  How long

  The record expires no later than one security window after the last attempt; Firestore then usually deletes it within 24 hours.

• Data

  With consent: the feature used, time, language, opaque account or wedding ID, and limited technical event properties

  Why

  To learn which parts of the product work and which need improvement.

  How long

  The record expires after 400 days; Firestore then usually deletes it within 24 hours. No record is created without consent.

• Data

  Device token, platform, device name and language

  Why

  So the device can receive notifications you have enabled.

  How long

  Until you disconnect notifications on the device, the token becomes invalid or you delete the account.

• Data

  Name, email and the text of a contact-form message

  Why

  So we can reply.

  How long

  The record expires 12 months after it is sent; Firestore then usually deletes it within 24 hours.

• Data

  A technical description of a server error: the page address as a pattern without identifiers, and the kind of error. Emails, tokens and numbers are removed before it is sent.

  Why

  So we can find and fix faults.

  How long

  At most 90 days with Sentry.

We process the account and features you request to perform our contract with you or take steps before entering it. We also process accounting documents to meet legal obligations. Necessary security and operational records are kept under our legitimate interest in protecting the service and resolving faults. Product analytics is stored only with consent, which you may withdraw at any time. For guest data, the couple is the controller and WeddUniverse is its processor. Allergies and health-related dietary needs are processed only on the guest’s explicit consent (Art. 9(2)(a) GDPR).

An email address is required to create and secure an account. You provide other data according to the features you choose to use; without it, the relevant feature simply has nothing to display or process. We make no automated decisions with legal or similarly significant effects.

Allergies, a gluten-free diet and other health-related dietary needs are a special category of personal data (Art. 9 GDPR). A guest stores them only with their explicit consent, given by ticking the box in their answer; without it we do not store them. You can withdraw consent at any time by changing your answer or asking the couple — the data is then deleted. When the couple enter them for a guest, they are responsible for that as controller.

60 days after the wedding date we delete this data for every guest automatically. The answer about attending stays.

Only a person over 15 may create an account. The names of invited children are entered by the couple or by a parent in their answer, and giving them is optional.

Both the database and the photographs are stored in the European Union. The database runs on Firestore in the europe-west10 region; photographs are in European Cloudflare R2 storage.

The processors we use are Google (Firebase Authentication and Firestore; Google Places when you type a venue address), Cloudflare (file and photograph storage in the EU), Vercel (running the application), Stripe (payments and invoices), Apple (App Store purchases), an email provider for sending messages (Forpsi in the Czech Republic, or Resend in the EU), Sentry (server error reports, with no names or addresses) and — only when you use the assistant — OpenAI Ireland Ltd. They receive only the data needed to provide their service, not for our advertising.

Google, Vercel, Stripe, Apple, OpenAI and Sentry may process some operational data outside the European Economic Area, in particular in the USA. The transfer relies on the European Commission’s adequacy decision (EU–US Data Privacy Framework) for certified providers and otherwise on standard contractual clauses, always together with a processing agreement. The database, photographs, documents and voice wishes are stored in the EU.

Under the GDPR you have the right to:

• know what data we process about you,
• have inaccurate data corrected,
• have your data erased,
• restrict processing,
• receive your data in a machine-readable form,
• object to processing,
• complain to a supervisory authority — in the Czech Republic the Office for Personal Data Protection (Úřad pro ochranu osobních údajů, Pplk. Sochora 27, 170 00 Prague 7, uoou.gov.cz), or the authority in the country where you live.

To exercise any of these, write to info@wedduniverse.cz. We answer within one month at the latest.

If the assistant is switched on for your wedding and you write to it, your question goes to OpenAI Ireland Ltd., who run the model, together with a summary of the wedding — how many tasks, guests and budget lines, the date, the state of the website. We do not send your guest list or your budget rows; the assistant asks for detail only when you ask for it, and only within what you are allowed to see.

What you type is kept out of our operational records: each request there stores only the model, the token counts, the cost and how long it took. Your conversations are stored so you can come back to them, are visible to you alone, a button deletes one, and they leave with you when you leave the wedding.

The assistant is optional. The whole product works without it, and without it nothing reaches OpenAI at all.

Guest data is entered and controlled by the couple. We process it on their behalf under the processing terms that form part of the terms of use, and use it for nothing else. If you are a guest and want your data changed or removed, ask the couple first — or write to us and we will pass your request on without undue delay and let you know.

Only the people a couple invite can reach their wedding. Every access decision is made by the server, never by the browser. The database is closed to clients entirely, and a photograph in a private album can be opened only through a temporary signed link. We do not store passwords — Firebase Authentication handles signing in.