This is a draft. It has not been checked by a solicitor and it is not in force.
We are publishing the wording while it is still being reviewed, because a page that hides its own status is worse than one that admits it. Where something is genuinely undecided, this page says so rather than guessing.
Privacy notice for couples
It covers you, the couple: the person who paid, the person who signs in, and the content you write for your site.
Last updated 28 August 2026
1. Who we are
Sandbanks Digital Ltd is the controller for the personal data described in this notice.
| Legal name | Sandbanks Digital Ltd |
|---|---|
| Company number | 17268570, registered in England and Wales |
| Registered office | 457 Ashley Road, Poole, Dorset, BH14 0AX, United Kingdom |
| ICO registration | ZC206995 |
| contact@sandbanksdigital.com | |
| Telephone | 01202 028175 |
We have not appointed a Data Protection Officer. We do not believe Article 37 requires one at this size and shape of processing, but that is a judgement the solicitor should confirm rather than one this draft should assert. Data protection questions go to the address above.
2. What this notice covers, and what it does not
It covers you, the couple: the person who paid, the person who signs in, and the content you write for your site.
It does not cover your guests. Guests are described in a separate notice because their data reaches us from you rather than from them, which is a different legal duty with a different content list. You have your own obligations to your guests, and those are set out in the couple data terms that sit alongside this notice.
3. What we hold, and where it comes from
Everything here comes from you, except where the table says otherwise.
| What | Where it comes from | Where it is stored |
|---|---|---|
| Your email address | You, at checkout, at sign-in, and on your account record | The product's own Postgres database, twice: on the wedding record and on the account record |
| Both partners' first names | You, in setup | Postgres. Your site address is minted from them plus the year, so the names are also in the URL |
| Wedding date, RSVP close date | You, in setup | Postgres. Every retention date in this notice is calculated from the wedding date |
| Venue name and area | You, in setup | Postgres |
| Your page content: schedule, travel, accommodation, dress code, FAQs, gifts | You, in setup | Postgres, as a single content record |
| Your chosen template and colourway | You, in setup | Postgres |
| Your guest list: household names, household email addresses, guests' first names | You, typed in by you | Postgres. This is your guests' data, held on your behalf, and the guest notice and the couple data terms deal with it |
| Guests' replies, including dietary requirements where your tier includes them | Your guests, through their invitation link | Postgres. You can see these on your dashboard and in your guest CSV |
| Photographs uploaded by you and by your guests | You and your guests | Object storage, with a database row per photo. See section 9 |
| Payment records: tier, amount, currency, Stripe session and payment intent references | You, through the checkout | Postgres. Card details never reach us: they go to Stripe |
| Sign-in links and sessions | Generated by us when you ask to sign in | Postgres, hashed. We store a SHA-256 hash of the link and of the session, never the value itself |
| A message log of invitations and reminders sent | Generated by us | Postgres, with the recipient address stored only as a hash |
| Your email address and your guests' IP addresses as rate-limit keys | Generated by us when a request is made | A Redis cache, in the clear, for one hour |
| Server logs | Generated by us | Our hosting platform's log store. Email addresses, anything token-shaped, and named sensitive fields are removed from every log record before it is written |
| A record of staff actions on your wedding | Generated by us when a member of staff acts on your record | Postgres |
| A record of each retention deletion run | Generated by us, nightly | Postgres. See section 8 |
We do not collect a date of birth, a postal address, a phone number or a password from you. There is no password: sign-in is by emailed link. We do not collect an age, an age band or a date of birth for any guest, adult or child.
4. Why we hold it, and our lawful basis
| What we do | Why | Lawful basis |
|---|---|---|
| Create and run your account, your setup and your site | It is the thing you bought | Article 6(1)(b), performance of our contract with you |
| Send you sign-in links | You cannot reach your own account otherwise | Article 6(1)(b) |
| Hold and display your guest list and their replies | It is the thing you bought | Article 6(1)(b) for our relationship with you; the guest notice sets out the basis for the guests themselves |
| Send invitations and reminders to your guests, on your instruction and in your name | You asked us to | Article 6(1)(b) as against you |
| Take and reconcile payment, and keep the record of it | It is the thing you bought, and we have to account for it | Article 6(1)(b), and Article 6(1)(c) for the tax record |
| Keep accounting and tax records | Company and tax law | Article 6(1)(c), legal obligation |
| Rate limiting, abuse prevention, and keeping the service up | Nobody's guest list should be reachable by someone guessing at it | Article 6(1)(f), legitimate interests |
| Keep a record of each deletion run and the staff action log | So that we have our own record of what the nightly job did, and so that staff power over your record is reviewable | Article 6(1)(f), legitimate interests |
| Answer support questions and defend legal claims | Ordinary running of a business | Article 6(1)(f), legitimate interests |
Where we rely on legitimate interests, we have to have balanced our interest against yours and written that down. That assessment is being completed, and we will make it available once it is.
Dietary requirements typed in by a guest are special category data under Article 9. The guest gives explicit consent for them by ticking a box on their own RSVP page, which starts unticked for a guest who has given us nothing and reflects their own earlier choice on a return visit. That tick is the Article 9(2)(a) condition. The Article 6 basis that sits underneath it is Article 6(1)(a) or 6(1)(f), paired with Article 9(2)(a); unresolved, see DPIA OI-4. That consent belongs to the guest, not to you, and it is described properly in the guest notice. It appears here only because you can see it: it shows on your dashboard and in your guest CSV, and your tier decides whether it is collected at all. It is not offered on Classic.
5. Who else sees it
We use a small number of suppliers to run the service. They act on our instructions. This is what each one actually does today, which is not the same as what each one is configured to do.
| Supplier | What it does | Where | Status today |
|---|---|---|---|
| Railway | Hosts the whole product: the web app, the API and the nightly purge job. It therefore has access to everything in this notice, including the log store | Project region EU West (Amsterdam) | Live. Everything runs here |
| The database plugin behind Railway | Holds everything in section 3 that is stored in Postgres | As Railway, if it is Railway's own plugin | Live. Whether the provider is Railway's plugin or Supabase is not yet settled |
| The Redis plugin behind Railway | Rate limiting. It holds your email address in plain text and your guests' raw IP addresses as counter keys, for one hour each | As Railway | Live. |
| Cloudflare R2 | Object storage for photographs | EU jurisdiction, public access off | Not enabled. No API credentials exist. See section 9 |
| Resend | Sends email: sign-in links, invitations, reminders | United States | Not enabled. The mail backend is set to console, which writes to the log instead of sending. No email leaves the machine today |
| Stripe | Takes payment and holds the card details we never see | Not reachable. The checkout endpoint refuses to run until the VAT setting is chosen, and the web app does not call it at all | |
| Google Fonts | Supplies two font files to our build machine when we build the app | Build time only. The fonts are downloaded once at build and served from our own domain. Your browser sends nothing to Google |
Your browser contacts our servers and nothing else. That is true today and was verified from the built application, not from a policy: there are no analytics, no tracking pixels, no third-party scripts and no remotely loaded fonts.
6. Sending data outside the UK
Everything we process today is processed inside the EEA, in Railway's EU West (Amsterdam) region. UK adequacy regulations cover that leg, so no additional transfer mechanism is needed for it. There is no transfer to a third country today, and none may start before a mechanism is in place. The full position, processor by processor, is held internally, and this section states its conclusion rather than restating it.
Resend is a United States company. When it is switched on it will receive recipient email addresses and the full text of every message, which for a guest invitation includes the household name, both partners' names, the wedding date, the venue, and the working invitation link itself. A transfer to the US needs a transfer mechanism, an International Data Transfer Agreement or the UK Addendum to the EU standard contractual clauses, plus a transfer risk assessment.
We have not put one in place. Resend is switched off, so no transfer is happening, and none may happen until it is.
Cloudflare's bucket is set to EU jurisdiction. Whether that guarantee covers object metadata and access logs as well as the objects themselves is not something we have confirmed in writing.
7. Cookies
One cookie, mb_session. It is set when you sign in and it is what keeps you signed in. It is first-party, it is httpOnly so no script on the page can read it, it is sameSite=lax, it is marked secure in production, and it lasts 14 days, which matches the life of the session behind it.
It is strictly necessary for a service you asked for, so under regulation 6(4) of PECR it does not need your consent and there is no cookie banner. There are no other cookies anywhere in the product. Your guests are given no cookie at all.
8. How long we keep it
Everything below is calculated from your wedding date. If your wedding moves, the date moves and everything in this table moves with it.
| When | What happens |
|---|---|
| RSVP close date, 14 days before the wedding by default | Replies lock |
| Wedding date + 7 days | Guests' dietary text and its consent timestamp are erased. The guest rows themselves stay |
| Wedding date + 30 days | Your site comes down. Every guest and household record for your wedding is deleted, the message log is stripped of recipient hashes, and your open sign-in sessions are revoked |
| Wedding date + your tier's photo period | Every photograph is deleted from storage, along with its database row. Classic: 30 days. Signature: 90 days. Bespoke: 365 days |
| Wedding date + 90 days | Your wedding record is marked as purged |
The job that does this runs every night at 03:15 UTC. We keep a record of each deletion run.
Your own record now has a deletion too, and this is when. Thirty days after the last thing we still held for you has gone: your photographs on your plan, or the ended page, whichever runs longer. On Classic that is 120 days after the wedding, on Signature 120, and on Bespoke 395, because your photographs are kept for a year. At that point we delete your email address, both your names, your venue, your page content, your account and every sign-in session. Your web address is retired at the same time, kept only as a fingerprint that cannot be turned back into your names, so that it can never be handed to another couple. A setup that never got a wedding date is deleted a year after you last used it, and only after we have emailed you twice, a month and a week before, to say so; signing in at any point starts the year again.
What is left afterwards is the record of what you paid, which we have to keep for company and tax purposes, and which describes a transaction rather than a person. The thirty days is our own choice rather than something the law sets, and if you want your record gone sooner, email us and we will do it.
Payment records are different. We have to keep the record of what you paid for company and tax purposes, and that obligation outlasts everything else here. We keep the order record, the amount, the currency and the Stripe references for as long as company and tax law requires. That record contains no guest data.
9. Photographs
Every photograph is re-encoded the moment it arrives. That is how location data and device identifiers are removed: nothing is written back out except the pixels, so there is no separate stripping step that could be skipped or fail quietly. Orientation is baked into the image first. We keep three sizes and we never keep the file you or your guest sent us. Because we do not keep it, we describe the export as high resolution and never as original quality.
Only you can see the photographs. There is no guest-visible gallery at any tier. A guest with an invitation link can add a photograph and can never list, view or download anything, and the photo records carry no uploader identity at all. That is a deliberate boundary and it is verified in the code.
Deleting a photograph from your gallery removes the stored object before it removes the database row, so a failure part way through leaves a record pointing at nothing rather than a file nobody can reach.
10. Your rights
You have the right to:
- be told what we hold and why, which is what this notice is for;
- ask for a copy of your personal data;
- have it corrected if it is wrong;
- have it deleted, where we do not have to keep it;
- restrict what we do with it while a dispute about it is open;
- object to processing we do on the basis of legitimate interests;
- portability, meaning a copy in a machine-readable form for data you gave us and that we process on the basis of our contract with you; and
- complain to the Information Commissioner's Office.
Ask us by email at contact@sandbanksdigital.com, or write to the registered office above. We answer within one month. We do not charge, unless a request is manifestly unfounded or excessive.
Two things you can already do without asking us. Your guest list downloads as a CSV from your dashboard at any time. Your photographs download as a ZIP from your gallery, and the export names what it could not include rather than quietly omitting it.
If you are not happy with how we have handled your data, tell us first so we have the chance to fix it. You can then complain to the Information Commissioner's Office: Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF, telephone 0303 123 1113, ico.org.uk. Complaining to us first does not take away your right to go to them.
11. Automated decisions and AI
We do not make any decision about you by automated means, and there is no profiling.
No part of this product sends anything to an AI or machine learning service. There is no such code path: not for your content, not for your guest list, and above all not for dietary data. That was verified by searching the whole codebase, not asserted from policy.
12. How we keep it safe
Sign-in links are single use and expire in 30 minutes. Sessions last 14 days and can be revoked. Every token in the system is stored as a hash, never as the value, so a copy of our database does not let anyone sign in as you. The session value never reaches the browser's JavaScript: it lives in an httpOnly cookie on our own web server, which forwards it to the API over private networking. The browser never talks to the API directly. Both application containers run as a non-root user. Logs are scrubbed of email addresses, token-shaped strings and named sensitive fields before they are written, and every request carries a correlation id so a support question can be answered from logs holding no personal data at all.
13. Changes to this notice
If we change it we will date the change here. If the change matters, we will email you rather than rely on you noticing.