Privacy policy

Who we are

wedplanner.io is a trading name of Chirpee LTD, a company registered in England and Wales (company number 17320087), whose registered office is at 66 Paul Street, London EC2A 4NA. For privacy questions and requests, email privacy@wedplanner.io.

Our role

We are the controller of the data about our members and their accounts, about payments, about supplier directory listings, and about visitors to wedplanner.io.

The couple or professional wedding planner who runs a wedding decides what goes in its plan, including its guests. We look after that data for them and use it only to run the wedding: its plan, its website and its emails. For planners and agencies, the data processing agreement sets out how.

If you are a guest

The couple or planner running the wedding added you to its plan. They decide what is recorded about you and who sees it. We host it, send you the wedding's emails and keep it secure.

Dietary needs and allergies can reveal health or religious beliefs. Only the people running the wedding see them, and they use them so your meal is right. You can give them yourself on the reply form, after a note saying who sees them.

To see, correct or remove what is held about you, ask the couple or planner, or email privacy@wedplanner.io.

What we hold and why

Your account: the name, email address and profile photo your sign-in provider gives us, your preferences, and what you do in the app. We use it to provide the service you signed up for (contract).

A wedding's plan: whatever the couple or planner adds, often including guests' names, email addresses, phone numbers, travel, rooms, meal choices, dietary needs and replies, and the emails we send for the wedding. We process it to run the wedding for the couple or planner (contract with them).

Payments: Paddle collects your payment details. We receive your name, email address, country, what you bought and the transaction references, to give you the plan you paid for and to keep the records the law requires (contract, legal obligation).

Assistant questions and writing help: stored in the wedding so you can see them again, and sent to our AI provider to answer them (contract). Never used for analytics.

Supplier listings and enquiries: the business details a supplier publishes, shown to anyone, and the enquiries couples send them (contract).

Technical records: logs, error reports, IP address and device details, to keep the service secure and to fix problems (legitimate interests).

Analytics: the pages viewed and the buttons pressed, in the app, on our site, and on wedding websites and guest pages, with the private part of guest links removed, to improve the product (legitimate interests).

Where a visit to our site came from: the ad or link that brought you (campaign tags, an ad click reference, the referring site) and, when you sign up or pay, that fact and its value. We keep it with your account for 90 days to learn which of our ads lead to sign-ups and payments and to show our ads to people who visited our site (consent where the law asks for it, otherwise legitimate interests).

Support: what you tell us when you write to us, to answer you (legitimate interests).

No decision about you is made by automated means alone.

Who receives it

The people invited to a wedding, at the level the owner set. A supplier sees what the day needs: the schedule, guests' names and the parts of the plan about its work. It never sees guests' contact details, their replies, the budget or other suppliers' quotes. Guests see their own page and what the couple publishes, and a published website is seen by its visitors.

Our service providers, only to run the service: Vercel (hosting), Supabase (database and files), Clerk (sign-in, which uses Cloudflare to tell people from bots), Resend (email), Inngest (background tasks), PostHog (product analytics), Sentry (error reports), Anthropic (the assistant, translation, writing help and reading the documents you ask it to read) and OpenAI (only the pictures you commission, from your words or a photo).

Google (Google Analytics and Google Ads) receives what our site records about your visit and, when you sign up or pay, that fact, its value and a scrambled (hashed) copy of your email address, so it can tell us which ads worked and show our ads to past visitors. In the UK, the European Economic Area and Switzerland this happens only after you agree. Google uses it as described in its own privacy policy, and is responsible for what it does with it for its own purposes.

Some of our emails load their typefaces from Google Fonts, and the emoji picker loads its data from jsDelivr, so those services can see the IP address of the device that shows them.

Paddle, our merchant of record, handles payments and is responsible for the payment data it collects under its own privacy policy. A supplier you contact through the directory receives your enquiry and handles it under its own privacy policy. Our professional advisers, and authorities where the law requires it. We do not sell personal data.

Where it is

The database and files are in the European Union (Ireland). The application runs in European regions, email is sent from the EU, and product analytics and error reports are stored in the EU.

Some providers are in the United States, among them our sign-in, background-task, AI and advertising-measurement providers, so some data is transferred there. Each transfer is covered by the EU Standard Contractual Clauses with the UK Addendum, or by the EU-US Data Privacy Framework and its UK Extension where the provider is certified. Ask us for a copy of the safeguards.

How long

A wedding's data, including its assistant conversations, is kept while the wedding exists. A deleted wedding is kept for thirty days so we can restore it if you ask. Then its plan is purged. Files uploaded to it are not yet removed automatically: email us and we delete them.

When you delete your account, we remove your name, email address and photo from it. We keep the fact that a change was made, without your name on it, so a shared history does not develop holes. Weddings you belong to stay with their other members, and so does any guest-list entry about you. We keep the record of account changes our sign-in provider sent us, which includes your name and email address, for as long as we need it to answer security questions and disputes about the account.

The answers in a wedding you started but did not pay for are deleted ninety days after you last touched it. Payment records are kept as long as tax and company law require, normally six years.

Technical records, error reports and analytics are kept only as long as we need them to keep the service secure, fix problems and see how it is used. Our AI providers keep what they receive only for the short periods their terms allow, to keep their services safe, and do not train models on it.

When you commission a picture from a photo, the photo is never shown to guests and is deleted thirty days after you choose the picture or set it aside.

Cookies

We use cookies to keep you signed in, to open a password-protected wedding website, and to remember settings you choose, such as your language and whether a panel is open. These are needed for those things to work. Paddle sets its own cookies inside the payment form while you pay.

Product analytics (PostHog, hosted in the EU) set a cookie and keep a note in your browser's storage that recognise a returning browser for up to a year. We do not use them for advertising or share them with anyone else.

On our site (not in the app, on wedding websites or on guest pages), Google Analytics and Google Ads set cookies that recognise a returning browser and the ad that brought it, for up to two years for analytics and 90 days for ads, and let us show our ads to people who visited our site on other websites (remarketing). Google Analytics uses Google signals for this. In the UK, the European Economic Area and Switzerland they are set only after you agree; elsewhere they are on, except advertising when your browser sends Global Privacy Control. We remember your choice for six months, and where a visit came from for 90 days.

You can change your choice at any time with "Cookie settings" at the foot of our site. You can also choose how Google personalises ads at adssettings.google.com, and stop Google Analytics in your browser with the add-on at tools.google.com/dlpage/gaoptout.

Your browser also keeps a few of your own choices in its storage, such as recent searches and answers you have not saved yet.

Your rights

You can ask for a copy of what we hold about you, ask us to correct it, delete it or limit what we do with it, ask for it in a portable form, and object to what we do on the basis of legitimate interests. Where we rely on your consent, you can withdraw it at any time.

Members can correct their details and delete their account from their profile. For a copy of your data, or anything else, email privacy@wedplanner.io. Guests can ask the couple or planner managing the wedding, or email us and we will help.

We answer within one month. If a request is complex, we may take up to two more months, and we tell you within the first month.

If you are unhappy with how we handle your data, tell us first at privacy@wedplanner.io. We confirm we have received your complaint within 30 days. You can also complain to the UK Information Commissioner's Office (ico.org.uk) or to the data protection authority where you live in the EU.

Security

Data is encrypted in transit and at rest. Every request is checked against the wedding and the role of the person making it, access is limited to what a role needs, and changes to a plan are recorded in its history.

Children

Accounts are for people aged 18 or over. A guest list can include children; the couple or planner adds them and is responsible for doing so.

Changes

When this policy changes we update the date at the top, and we email account holders about significant changes.