Skip to content

Privacy Policy

This policy explains how Wedding Overview handles personal information about account holders, partners, helpers, wedding guests, and website visitors. Health information has additional protection under our separate Consumer Health Data Privacy Policy.

1. Who is responsible

Wedding Overview is operated by Miron Digital, Deken Darraslaan 5 bus 101, 8700 Tielt, Belgium. Company number: 0793239175. VAT registration number: BE0793239175.

Email: hallo@weddingoverview.com. Phone: +32 (0)51 58 40 52. Website: weddingoverview.com.

We operate from the European Union. The General Data Protection Regulation, or GDPR, applies to our processing in the context of that business, including when the person concerned lives in the United States. Applicable U.S. federal and state privacy protections also remain in place.

For account administration, payments, our security, and customer support, Miron Digital determines how and why information is processed. When we process wedding content on a customer's instructions, our Data Processing Agreement explains the corresponding responsibilities. We carry the responsibilities stated in our Consumer Health Data Privacy Policy ourselves, including when a couple manages other guest details.

2. Information we collect and its sources

Account and access information. Names, email addresses, sign-in details, and the roles and permissions of people who work on a wedding. This comes from account holders, invited helpers, and their use of the app.

Wedding information. The wedding date, venues, tasks, schedule, budget, vendor information, seating chart, wedding website content, photographs, and uploaded documents. This comes from the couple and people they authorize.

Guest and RSVP information. Names, contact details, households or groups, plus-ones, attendance, and RSVP answers. A guest may provide this directly, a group member may respond with the guest's permission, or the couple or an authorized helper may enter it.

Sensitive guest information. Dietary needs, allergies, accessibility needs, pregnancy information, health or care notes, and answers to sensitive custom RSVP questions, when provided. A dietary preference may also reveal religious beliefs. The Consumer Health Data Privacy Policy explains the sources, purposes, recipients, and rights for health information.

Payment and communication information. Purchase details, payment status, payment references, and the information needed for receipts, refunds, questions, and complaints. These come from you, our payment service, and communications with us. We do not receive or store complete payment card details.

Technical and usage information. IP addresses, browser and device information, sign-in and security events, error reports, and limited information about pages or steps used in the website or app. This is generated when the service is used. Our first-party usage measurements do not include the contents of wedding, budget, guest, or RSVP fields. A technical account identifier may be used for authenticated app measurements and the reliability or security of reporting.

Required account and payment fields are needed to provide the requested service. Without them, we may be unable to create access or complete a purchase. Providing optional health information is not a condition of using the general RSVP function.

3. Why we use information

Providing the service. We create accounts, manage access, store wedding plans, display progress, and operate wedding websites and RSVP links. For our own processing needed to provide a user's account and paid service, the legal basis is performance of the agreement and steps requested before purchase.

Carrying out wedding instructions. We store and organize guest information, enable collaboration, produce requested exports, and send wedding invitations or reminders when the customer asks us to. Where we act as a processor, we follow the customer's documented instructions. Where we have our own legal obligations for guest information, including health information, we meet those obligations directly.

Payments and records. We process purchases and refunds and keep required accounting records. The legal bases are performance of the agreement and legal obligations.

Support and security. We respond to requests, diagnose problems, prevent fraud and automated abuse, and protect the service. The legal bases are performance of the agreement or our legitimate interests in a secure, properly functioning service.

Limited first-party measurement. We use limited technical information to understand whether the website and app work and where people encounter problems. The legal basis is our legitimate interest in maintaining and improving the service. You may object to processing based on legitimate interests.

Sensitive information and optional uses. We obtain specific consent where required, including explicit consent for health information or other special categories of personal data. Consent for an optional use can be withdrawn. Agreeing to general terms is not a substitute for that consent.

We do not sell your personal information and we do not share it for targeted advertising or cross-context behavioral advertising. We do not use guest information for advertising or to train AI models. We do not use personal information to make solely automated decisions that produce legal or similarly significant effects on you.

4. Guest information and wedding websites

Guests do not need a project account. They may view the wedding website or respond through a personal RSVP link. The couple decides what to add, what to publish, and who may help with planning. Access within the app follows the permissions assigned to each person.

Health and other sensitive RSVP information is kept out of the public wedding website. Guests can give or withdraw the relevant consent. A person answering for someone else must have permission to do so.

When the couple exports information for a caterer or venue, the couple decides who receives the export and is responsible for its further handling. The limits on health information in those exports are described in the Consumer Health Data Privacy Policy. An export does not allow us to reuse the information for a different purpose.

5. Who receives information

We disclose information only as needed for the purposes in this policy:

Health information is subject to the more specific recipient restrictions in the Consumer Health Data Privacy Policy.

Providers processing information for us must follow appropriate contractual limits on use, confidentiality, security, and deletion. The current provider list, including the relevant functions and processing locations, is available on request at hallo@weddingoverview.com. Guests may request the information relevant to their data without creating an account.

6. Where information is processed

Our primary wedding and guest data storage is in a data center in Frankfurt, Germany, within the European Union. Our email service and hosting provider process delivery or technical information in the United States. International processing or access by providers can also occur for support, security, or backups.

Where personal information is transferred outside the European Economic Area, we use an applicable adequacy decision or appropriate safeguards, such as the European Commission's Standard Contractual Clauses, with additional protection where required. We do not rely on your use of the website as consent to an otherwise unlawful international transfer.

You can ask us which safeguards apply and request a copy of the relevant protection, subject to lawful redactions of unrelated confidential information.

7. Cookies and browser storage

We do not use advertising or cross-site tracking cookies. We do not track you across other websites.

The app stores sign-in information and basic preferences, such as the selected wedding and the list or card view, in your browser. A private wedding website uses a functional session cookie to remember permitted access. These features support the service you request; they are not used for targeted advertising.

Offline access for the wedding day is off by default. If you enable it in Data and privacy, the app stores an encrypted local copy of the plan, with the key kept for the browser session. Dietary needs, allergies, and accessibility information are excluded. The offline copy expires after twenty-four hours and is removed when you sign out.

Our website counts page views and selected button clicks through first-party measurement without measurement cookies or additional storage on your device. These measurements are separate from necessary sign-in and preference storage.

You can remove cookies and local storage in your browser settings. Doing so may sign you out or reset preferences. Browser Do Not Track signals do not change these necessary functions. We do not undertake the sale, sharing for targeted advertising, or cross-site tracking to which an opt-out preference signal would apply.

8. How long we keep information

Wedding and guest information. The scheduled end date is twelve months after the wedding date in the app. Automatic deletion occurs only after that date and at least fourteen full days after a warning has been delivered to the owner's verified email address. The same protection applies to old or backdated wedding dates. A full export remains available until deletion.

No wedding date. The scheduled end date is twelve months after the last sign-in by any member of the wedding, or after creation if nobody has signed in. The delivered warning and fourteen full days of additional time also apply.

Account information. We retain information while it is needed to provide access and support. When the account is deleted, we remove information that is no longer needed, except records we must retain to meet a legal obligation or resolve an existing claim.

Payment and accounting records. Records subject to Belgium's ten-year accounting retention requirement are kept for that period. For invoices, the period runs from January 1 of the year following issue. Other payment information is kept only as needed to complete the transaction, deal with a refund, and establish or defend relevant legal rights.

Technical measurements and error reports. First-party usage measurement records and technical error reports are kept for no more than ninety days. Security records needed for a specific incident may be retained until the investigation and related legal obligations are complete.

Support and privacy requests. We keep the information needed to answer the request and document its handling. Further retention is limited to any applicable legal recordkeeping requirement or an unresolved complaint or legal claim.

Health information. Earlier withdrawal and deletion requests follow the shorter handling deadlines and backup removal commitments in the Consumer Health Data Privacy Policy. A guest does not have to wait until the wedding's scheduled end date.

You may request earlier deletion. An account closure, purchase refund, and privacy deletion request are different actions, and we will explain any information that must remain for a separate lawful purpose.

9. Security and children

We use encrypted connections, restricted access, separation between weddings, account protection, and backups. We limit access by our personnel to their work needs. No system can guarantee absolute security.

The planning service is intended for adults and is not directed to children under thirteen. An adult may include limited information about a child guest when needed to organize the wedding and when authorized to do so. We do not invite children to create accounts. Contact us if you believe a child has submitted information inappropriately so that we can investigate and take appropriate action.

10. Your rights and how to exercise them

You may ask to access, correct, or delete your personal information and receive a portable copy. You may also ask us to restrict processing, object to processing based on legitimate interests, or withdraw consent. These rights apply subject to their legal conditions. Withdrawing consent does not make earlier lawful processing unlawful.

Residents of U.S. states with their own privacy laws can use these same contact methods. Any additional right provided by applicable state law remains available, including applicable rights concerning sensitive information, authorized agents, appeals, or disclosures about recipients. We do not discriminate against you for exercising a privacy right.

Email hallo@weddingoverview.com or use Settings > Data and privacy in the app. A guest does not need an account to contact us. We may reasonably verify identity or an agent's authority before disclosing, changing, or deleting information. Do not send identity documents unless we explain why they are needed and how to send them securely.

We respond without undue delay and within one month after receiving a request. If a legally permitted extension is necessary, we explain the reason within that first month and comply with the applicable maximum extension. A shorter applicable deadline takes priority. The specific health-data deadlines are stated in the Consumer Health Data Privacy Policy.

Where we process a wedding's data on a customer's behalf, we coordinate with that customer to handle the request. We do not use that arrangement to avoid our own obligations for health information or other processing for which we are responsible.

11. Appeals and complaints

If we decline all or part of a privacy request, you can ask us to reconsider by replying to our answer or emailing hallo@weddingoverview.com. We provide a written decision and reasons within forty-five days, or sooner if applicable law requires. A denied appeal includes information on contacting the relevant state Attorney General or other competent authority.

You may also complain directly to the Belgian Data Protection Authority or the authority responsible for privacy complaints where you live. Contacting us first is optional. Information about the Belgian authority is available at gegevensbeschermingsautoriteit.be.

12. Changes and related documents

We update this policy when the service or our practices change. The current version and date are shown on this page. We give notice of material changes where required and obtain fresh consent before a new use that requires it.

Read this policy together with our Terms of Service, Data Processing Agreement, and Consumer Health Data Privacy Policy. If a more specific health-data protection applies, the Consumer Health Data Privacy Policy governs that information without limiting mandatory legal rights.