Privacy notice

NearlyWeds is a service operated by Digital Galleries Ltd, a company registered in England and Wales, company number 17403040, registered office 167-169 Great Portland Street, London, W1W 5PF. You can reach us at help@nearly-weds.com.

We handle two kinds of information, and the law treats them differently.

If you are a couple or a wedding planner, we are the data controller for your account: we decide what we collect to run the service and we answer to you for it directly.

If you are a wedding guest, the couple is the controller of your information. They decide who to invite, what to ask you and how long to keep your answer. We process it on their instructions, as their processor. So if you want your details changed or removed, the fastest route is to ask the couple — though you can always come to us and we will help.

• Your email address, which is how you sign in. We send a link rather than storing a password.
• The names you choose to show on your website, your wedding date, your venue and your web address.
• Everything you write into your website: your story, travel notes, dress code, questions and answers, and the order of the day.
• Photographs you upload for your website.

• Names, and the household or family they were invited as.
• An email address, if the couple has one and wants to send the invitation that way. It is optional.
• Whether each person is coming.
• Menu choices, where the couple is offering a choice.
• Dietary requirements and allergies, written by the guest.
• Where each person is sitting, and any note the couple has made about who should or should not sit together.

Allergies are health information, and some diets say something about a person’s religion or beliefs. Under UK data protection law that is special category data and it needs more care than a name does. We treat it that way in the software, not only on this page:

• It is stored separately from the rest of the guest list, with its own access rules.
• Only the couple, any planner they have invited, and the household it was written in can read it. One person usually replies for their whole family, so anyone holding that household’s invitation can see and change what was written for the people in it. No other household can, and no other wedding ever can.
• It is never used to work out a seating plan, and it is not sent to any automated suggestion tool.
• It is never used for anything except telling the couple, and through them their caterer, what somebody cannot eat.

A guest gives it by typing it into their own reply, and can leave it blank.

• For your account: because we need it to provide the service you asked for — a contract between us.
• For guest information: the couple decides this, as controller. Their usual basis is their own legitimate interest in organising their wedding.
• For dietary requirements: the guest gives them explicitly, for the express purpose of being fed safely.
• For keeping the service running and secure: our legitimate interest in it working and not being abused.
• For helping you finish setting up: our legitimate interest in you getting the thing you signed up for. If you have not chosen a design or added your date, we may say so.
• For our own news: only if you asked for it. You can stop it whenever you like, in Settings or from any such email, and it changes nothing about your wedding or the emails your guests get.

We do not sell anything to anybody, and we never use your guests’ information to advertise. We use these companies to run the service, and no others:

• Supabase — the database your wedding, your guest list and their replies sit in. It is in London (eu-west-2), in the UK.
• Vercel — the hosting that serves the website itself.
• Resend — sends the emails: your sign-in links, and invitations where you have chosen to send them by email.
• HubSpot — holds your account details so we can help you get set up, and send you our own news if you asked for it. It holds your email address, your web address, your wedding date and how far through setting up you are. Nothing about your guests is ever sent to it — not their names, not their replies, and not anything they have told you about what they can eat.

Your wedding, your guest list and every reply are held in the United Kingdom. Nothing about them has to leave it, and no adequacy decision or transfer mechanism is needed for them.

Photographs uploaded to your website are stored in the European Economic Area. The UK recognises the EEA as providing adequate protection, which is the basis on which they go there, and they keep the protection of UK data protection law either way.

Where one of these companies moves information outside the UK and the EEA — for example to its own support teams — it does so under its contract with us and its own safeguards: [ to confirm: confirm each supplier’s onward-transfer safeguards from their current DPA ].

Your website is not visible to anybody until you publish it. Before then, only you and anyone you have invited to help can see it — a stranger with your address sees nothing at all.

Once published, the pages you have written are readable by anyone with the address. Your guest list, replies, dietary requirements and seating plan are never part of that: they stay behind your account whether you publish or not.

Invitation links and QR codes contain a code unique to each household. Anyone holding that link can see that household’s own invitation and reply for the people in it, which is the point of it — so treat it the way you would a paper invitation.

We use two, and neither of them watches you:

• A sign-in cookie, so you stay signed in. Without it the service cannot work.
• A preview cookie, while the site is not open to the public, which remembers that you have been let in early.

We do not use advertising cookies, and we do not track you across other websites.

We count visits to our own marketing pages — this site at nearly-weds.com — so we can tell which pages are useful and how quickly they load. It is run by Vercel, who already host the site, rather than by handing a copy to anyone else.

It sets no cookies and stores nothing on your device, which is why you have not been asked to agree to it. It records the page address, roughly where in the world the request came from and what kind of device it was. It does not build a profile of you, does not follow you to other websites, and is never joined up with your account or your wedding.

A couple's own wedding site is never measured. If you are a guest who followed a link to somebody's wedding address, nothing about your visit reaches us. Those pages are left out deliberately, in the code rather than by policy, because the address itself names the couple and their guests never asked us for anything.

[ to confirm: retention periods — how long after a wedding an account and its guest data are kept, and what happens to an account nobody has signed into ]

When a wedding is deleted, everything attached to it goes with it: guests, replies, dietary requirements, the seating plan and the uploaded photographs.

You can ask for a copy of what we hold about you, ask us to correct it or delete it, object to how we are using it, or ask for it in a portable form. Write to help@nearly-weds.com and we will answer within one month.

If you are a guest, the couple who invited you decides most of this, so asking them is usually quicker. We will pass your request on if you would rather not.

If you think we have got it wrong, you can complain to the Information Commissioner’s Office at ico.org.uk. We would rather you told us first so we can put it right.

If we change how any of this works, we will change this page and move the date at the top. If the change is a significant one, we will tell you rather than leaving you to notice.