Privacy
You can use the composer, see a full estimate and share a wedding page without giving us anything at all. An account is needed only when you want a human planner to work on your plan.
There is no cookie banner on this site. That is not an oversight: we set one cookie, it holds your login session, and there is nothing else to consent to.
Delilah is the data controller for everything on this page. Write to planner@delilah.wedding about any of it and you will get a written answer.
Our registered company name, address and VAT number are not yet published here. If you need them in writing before you give us anything, which is a reasonable thing to want, ask at the address above and we will send them.
Nothing about your wedding is stored. Your plan lives in the address bar, which is why a shared link reopens on the same figures. We set one cookie, and only after you sign in: it holds your session and nothing else. There is no advertising pixel and no cross-site tracker.
We run Vercel Web Analytics and Vercel Speed Insights. Both are cookieless. They record which pages are viewed, roughly where in the world from, which browser, and how fast the page loaded, and they aggregate it. They do not set an identifier, do not follow you to other sites, and never see your email, your account or anything you typed. We use them to find out which pages are worth writing and which are slow. Both are served from this domain, so nothing about your visit is sent to a third-party host at page load.
We store your email address, a hashed password, and the wedding plans you have asked a planner to work on. A plan includes the venue, guest count, month and flowers you chose, the computed estimate, and any brief you wrote in your own words. We store the messages between you and your planner, and a log of each status change so you can see who moved your plan and when.
The brief is free text about your wedding, so it is the most personal thing here. It is shown to your planner exactly as you wrote it and is not used for anything else. It is never sent to a language model and never shown to a venue without your agreement.
Each purpose, and the lawful basis for it under Art. 6 of the GDPR. Almost everything here is performance of a contract: you asked us to plan a wedding and this is what planning it requires. Nothing rests on consent, which means there is no consent for you to withdraw, and the one purpose that rests on our legitimate interests is the aggregate page counting, which you can object to.
| What we do | Basis | Where it happens |
|---|---|---|
| Composing an estimate before you have an account | No basis needed: nothing is stored. The plan is in the URL and in your own browser. | lib/plan-url.ts |
| Holding your plan so a planner can work on it | Performance of a contract, Art. 6(1)(b). You asked for a planner; this is that request. | prisma/schema.prisma, Wedding |
| Your account and login session | Performance of a contract, Art. 6(1)(b). There is no way to hold a plan for you without one. | lib/auth.ts |
| Answering you when you have written to us without an account | Steps taken at your own request before any contract, Art. 6(1)(b). You gave us an address or a number in order to be answered, and answering it is the only thing either is used for. It is not marketing, so there is no legitimate-interests balancing to do and nothing to object to under Art. 21: ask us to stop and the record goes the same day. | lib/leads.ts, lib/contact.ts, app/admin/(console)/inbox/actions.ts |
| Emailing you about your own wedding | Performance of a contract, Art. 6(1)(b). These are transactional: a quote is ready, a deadline is due. We send no marketing, so there is no consent to give or withdraw. | lib/mail/ |
| Telling a supplier what they need in order to quote | Performance of a contract, Art. 6(1)(b), limited to the date, the guest numbers and the service. | A planner, by hand. There is no automated disclosure to suppliers. |
| Counting page views and load times, in aggregate | Legitimate interests, Art. 6(1)(f): knowing which pages are worth writing. Cookieless and never linked to you, which is what keeps the balance in your favour. You may object. | app/layout.tsx |
| Keeping the record of a booked wedding after it has happened | Legal obligation and the defence of legal claims, Art. 6(1)(c) and 17(3)(e). This is the one case in which erasure is refused, and it says which record refused it. | lib/gdpr/, eraseUser |
Your planner sees your plan. Suppliers are told only what they need to quote: the date, the guest numbers and the relevant service. Today that limit is a planner following an instruction rather than a query that cannot return more, which is a weaker guarantee and we would rather say so than imply otherwise.
Our hosting and database are run by Vercel and Neon, both in the European Union. Transactional email is sent through Resend. We do not sell data and we do not share it for advertising.
One thing leaves the European Economic Area. Resend, which delivers our transactional email, is a United States company, so an email we send you is a transfer to a third country. What crosses is the address we are writing to and the contents of that one message: a quote is ready, a deadline is due. Your brief, your password and your plan do not.
We have not yet published which safeguard covers that transfer, and we are not going to name one on this page before it is checked. If it matters to you before you give us an address, ask at planner@delilah.wedding. Everything else, the database, the hosting, the files, stays in the European Union.
One feature uses a language model: reordering the venue list against a sentence you type. It receives that sentence and the names of venues already published on this site. It never receives your email, your account or your brief, and it can never produce a price. Every figure on this site comes from our own pricing engine.
A saved wedding page has a long random address so it can be forwarded to family without an account. That means anyone holding the link can read it. Treat it the way you would a shared document, and ask us to revoke it if you need to.
| What | How long | Why |
|---|---|---|
| An estimate you never sent | Never stored | The wizard keeps it in the URL and in your own browser. Nothing reaches our database until you ask for a planner. |
| A plan nobody has touched | 2 years from the last message or change | Long enough for a wedding planned eighteen months out, plus a season of changing your mind. |
| A wedding you booked | 7 years after the wedding date | The period in which a disagreement about what was agreed could still surface. We hold the plan, never the invoices: those are your suppliers' and they keep them for ten years under Italian law. |
| An account with no plan in it | 180 days | There is nothing left to do for you, so there is no reason to keep it. |
| A request to be reached: your number, WhatsApp or Telegram | 1 year | Held so a planner can answer you and for nothing else. It is never passed to a supplier, and if nobody has answered you within a year it goes on its own. |
| An enquiry you left without opening an account | 1 year | Your address, the sentence you wrote about your day, and the property you were looking at, held so a planner can answer you. If we have not, it goes. Ask us sooner and it goes the same day. |
| Your login session | 30 days | The cookie expires on its own. Logging out ends it immediately. |
A daily job deletes what is past these periods. The periods and the job are read from one place in the code, so this table and the job cannot disagree.
Under the GDPR you can ask for a copy of everything we hold about you, correct it, have it deleted, restrict how we use it, or object to the one purpose that rests on our legitimate interests. For most of that you do not have to ask us at all.
If you have an account, your data page does two of them immediately and without a form: export writes everything linked to you as a file, and lists what it left out and why; erase deletes the account outright. Erasure refuses in exactly one case and tells you which record refused it: a booked wedding, or one with an invoice against it, is a record the law requires us to keep.
For anything else write to planner@delilah.wedding and you will get a reply within thirty days. If you are not satisfied you can complain to the Garante per la protezione dei dati personali, which is the Italian supervisory authority, or to the authority in the country you live in.
The date at the top is the day this page last changed. If a change affects what we collect, who sees it, or how long we keep it, and you have an account, we will email you before it takes effect rather than change the page quietly. Fixing a sentence that described the software wrongly is not that kind of change and does not get an email.
This page describes what the software does. If you find a difference between the two, the software is the bug and we want to hear about it.