Privacy Policy

Effective October 12, 2026

You are about to hand us your wedding contracts, before you have paid us anything and before you know whether you ever will. Those are private documents with your name, your money, and your vendors in them. Here is exactly what happens to them — including if you never become a customer, which is the outcome for anyone whose documents do not add up to enough to be worth buying a plan for.

What changed

This policy used to say that we did not sell data and that uploads were deleted on a schedule. From September 27, 2026, we keep data with no scheduled deletion and may sell or share it, as described here. At that date the only orders on file were our own test orders; nothing a couple sent was collected under the earlier policy.

From October 1, 2026, this page also describes our own log of how the site is used and the two cookies behind it, how fast pages load, and what we hold about guests, helpers and family who use a page a couple shares. It no longer describes an opt-in benchmark contribution: the box it described is not in the product.

What we collect

Your answers to the optional questions

Roughly when the wedding is, the state it is in, your target budget and what you project spending, what you have already paid or committed, guest count, which categories you have signed or are still deciding, and whether you have documents to hand. While you are answering, these sit in your own browser’s local storage; they reach us only when you ask for the estimate. They contain no name and no free text.

Your email address

How we send your estimate, your sign-in link, what we found in your documents, and — if you buy — your receipt and your plan. Nothing works without it.

The documents you upload, and what we extract from them

Contracts, quotes, invoices, and vendor emails — whatever you choose to give us — plus the figures, dates, vendor names, and clauses our pipeline pulls out of them, and the findings and scripts built from those figures.

Email you forward to your plan

If you use your private forwarding address, the messages that arrive at it: who sent them, the subject, the text and the attachments. Mail from an address that is not yours or your partner’s is held, unread, until you approve or discard it. Approved mail is treated like a document you uploaded.

Details you add about other people, and what they send through your pages

Guests and their replies; the people in each household, with an age group (adult, teen, child or baby) and whether they are a plus-one; children’s names, which we keep as initials only; dietary and allergy needs and menu choices; guests’ postal addresses, email addresses and phone numbers, and the name for the envelope; groups, seat allotments and where a household is staying; your events, with their places, times and your notes; the dates you mail invitations and thank-yous; your own return address; the column headings of a spreadsheet you import; notes and photos; the people you list as paying for parts of the wedding, with an address if you give one; the names you write against your costs as having paid them, and how much; where you say the money comes from; helpers you give steps to; the people with a part on your wedding day, with their roles, phone numbers, email addresses, what they wear and bring, and any note you keep about them; children on the day, whose names we keep as initials only, and the adult who looks after each; who is needed for each moment; bring lists and rain plans; your family photo list, with the names in it; and vendors’ contact details, including the vendors you are considering, the people you deal with there, their websites, the quotes they give you, your notes and answers from a tour or call, and the scores you and your partner give them.

You add these, or the people themselves send them through a page or link you share: your wedding page (a reply, a question, a note, a photo), a household’s own invitation link (who is coming to each event, meals and dietary needs, a song request, a note) and a link you send a relative to collect addresses or a list of households. What a relative sends waits for you and joins your list only when you accept it. We use them to run your workspace, your prints and downloads, and the pages and links you share. We do not mail, email, call or text your guests from these details. We do not contact a vendor from these details: a message opens in your own mail app, and you send it.

When you send someone their schedule link, the page it opens shows them their own times, places and what they bring, any child they look after by initials, and the name and number of the person you chose for them to call. It does not show amounts, your guest list, your notes or anyone else’s details.

Your kind of wedding, and your own planning notes

If you tell your checklist what kind of wedding it is, we keep your answer: one of seven shapes (a venue, a courthouse or registry office, an elopement, at home, a destination, several events, a vow renewal or commitment ceremony) and any of nine optional parts you tick. One of those parts is “a religious or cultural ceremony”; we record only that you ticked it, never which faith or tradition. We also keep the country where you are marrying, and the steps, notes and dates you add to your checklist. We use them to build your checklist and This week, and to word a few steps for where you marry.

Your license and admin desks

What you write down about the legal side of your marriage: the office you dealt with and its website, who you spoke to and when, the date of the legal ceremony, the documents each of you is bringing, the fee and how to pay as you note it, the waiting period and how long the license lasts as the office told you, witnesses, papers about a previous marriage if you add them, who brings, signs and returns the license, and how many copies you will order. After the wedding: what each of you decides about your names, and the places you are updating (for example a bank, an employer, a passport office), with dates and notes. We use it to work out dates from your own numbers, to put those dates in This week, your calendar and, on the $79/month plan, a reminder email, and to give you a spreadsheet of it.

Your wedding page

The words, links and photos you put on your page, in each language you write it in. Anyone with the page’s link can read it while it is published. Anyone with the link can also report the page to us, with a reason and, if they choose, an email address so we can reply; we read reports and may take a page down, and tell you when we do.

Gifts and thank-yous

What you were given, by whom and at which occasion, who opened it, and the notes you draft. A gift of money can carry an amount if you type one.

Schedule links

You can make a link for each adult with a part on your day. It works for whoever has it, without an account, until the end of the day after your last event, or until you turn it off or make a new one. We keep a scrambled form of each link, when it was made and whether it has been opened, so you can see that it reached the person.

Free tools

The free tools (the calculators, the payment calendar, the checklist, the speech timer, the day timeline, the sunset times and the invitation wording) keep what you type in your own browser’s storage, so it is there when you come back. It is not sent to Wedding Remedy while you use a tool. Clearing the tool’s entries, or your browser’s site data, removes it from that browser.

If you press “Add this to my free planner”, the tool’s result is sent to Wedding Remedy and becomes part of your planner, like anything else you enter there. Depending on the tool that can be: payment amounts, due dates and vendor names; quoted totals; your wedding date, guest count and reply-by date; your venue’s town or map coordinates and time zone; the times of your day; and the words of a speech, vows or invitation, including any names you typed, such as family members’ names or the name of someone you are remembering. If you are not signed in, we ask for your email address to send a sign-in link, and the result is sent with it. What we keep, for how long, and with whom it may be shared is set out in the retention and sharing sections.

Searching or filtering the guides happens in your browser; what you type in the guide search is not sent to Wedding Remedy.

Guests who ask for updates

A guest who ticks the box on your wedding page gives us their email address, the time they agreed and the wording they agreed to. We record which updates were sent to them. Each update carries a link that stops further updates with one click.

Phone notifications, if you turn them on

The address and keys your phone’s browser gives us for notifications. We use them to send the title of a reminder that is also emailed to you. Turning notifications off, or signing out on that phone, removes them.

Your order record, and a payment record only if you bought

An order record exists from the moment you upload: it is what your documents and your analysis hang off. A payment record — amount, status, refunds — exists only if you accepted a quote. If you never did, there is nothing here at all, because nothing was charged. Card details are handled entirely by our payment processor and never reach our servers; where there is a payment, we store the processor’s identifiers for it so we can issue a refund if one is owed. If you buy the plan from your planner: a record of the purchase (when, the amount, whether you or your partner bought it, when you agreed that access starts at once, and the payment references from our payment processor), kept as a payment record. The plan renews monthly, so each renewal, a failed payment and a cancellation are kept as payment records in the same way.

How you found us

Campaign parameters (UTM tags), the ad click id that rides along in the link you clicked, the ad platform’s browser id from its own cookie, which landing page you arrived on, and which creative brought you. Our attribution record is deliberately fenced: it may hold marketing metadata and may not hold budgets, vendor names, contract text, findings, your answers to the optional questions, guest count, or location. That fence is enforced in code, not by good intentions.

Messages you send us

Support email, and whatever you tell us in it — including anything you quote from your own contracts.

Technical data

Ordinary server request data: IP address, user agent, and the page requested, plus error reports when something breaks. Used to keep the site up, to rate-limit public endpoints against abuse and double-submits, and to debug. We do not build an advertising profile from it. We also measure how fast pages load and respond in your browser (web vitals): timings about the page, recorded with the kind of page they came from.

An internal event log

An append-only record of what happened to an order — documents received, analysis run, figure shown or threshold missed, and then paid, delivered, or refunded if it got that far — with timestamps. It holds identifiers and statuses, not document contents. It is how we can answer “so what actually happened to my order” honestly, including for an order where nothing was ever charged.

Our own log of how the site is used

Recorded on our own server, not by an advertising platform: which kind of page was viewed (the homepage, a guide, a tool — never its address), the step of a form reached, the buttons pressed and which of the four options on the start sheet was chosen, the site and campaign tags a visit arrived with, which version of a page was shown, and when a page failed or was not found. It is keyed to a random visitor id kept in a cookie (below), and joined to your order once there is one. It holds no document contents and no figures from your paperwork. Pages a couple shares with guests, helpers and family send none of this and set no cookie.

Dietary and allergy information. If you record a guest’s dietary needs or allergies, that can be information about their health. You add it so you and your caterer can plan the meal; the planner shows it to you and puts it on the prints and downloads you choose to make. We do not record anyone’s religion: menu options are your own words.

Why we process it

• To analyse your documents and work out whether there is enough in them to be worth a plan — the part we do before any money is discussed.
• To produce your plan and the scripts that go with it.
• To deliver it to you and to support you afterwards.
• To answer your questions in the 24/7 Concierge and in Quick answers, from what is in your planner and, on the $79/month plan, your contracts.
• To take payment if you accept a quote, and to issue refunds, including automatic ones.
• To keep the accounting and tax records a business is required to keep.
• To keep the service working and safe: rate limiting, abuse prevention, error monitoring, and debugging.
• To measure whether our advertising pays for itself, in the narrow way described below.

• To sell, license or share data with other businesses, as described under “Selling and sharing data” below.

The AI providers that read your documents for us are contractually barred from training their models on your content. A business we sell, license or share data to uses it for its own purposes, which can include building or training models.

The Monday email from your planner. If you use the free planner and your wedding date is ahead, we email you on Mondays when something in your planner is due in the next two weeks or past its date. It is about your own planner and carries no offer. Every one has a link to turn it off, and you can turn it off or back on at the foot of This week. Turning it off does not stop sign-in links or other emails about your account.

Planning tips for the free planner (only if we turn them on). Up to three emails in your first week. They are marketing, so each one includes our postal address and a one-click way to stop them.

Reminders before your own dates (the $79/month plan). A week before a date you set in your planner (a step of your own, a date from your license desk, a follow-up), we email you, and your partner unless you turned copies off. A helper is emailed only about steps you gave them. Ticking an item stops its reminders.

Each planner email carries a link that turns the planner’s emails off for that wedding. The link opens a page with one button, because email scanners open links on their own. Your email program can also do it in one click from the message header. This is separate from a guest’s link to stop a couple’s wedding updates.

What happens to your documents

An uploaded file goes into private storage that is not publicly listable and is not linked from anywhere. An automated pipeline reads it and pulls out the figures, dates, and clauses that matter. Those extracted numbers are what become your analysis, and your plan if you buy one.

People on our side can open a document when there is a reason to: you have written to support about your order, or a run has failed and we are working out why. Access is limited to the people who need it for one of those reasons. It is not something anyone browses.

We do not contact your vendors. Every message in your plan is one you send yourself, from your own address.

If you are never charged

We read first and ask for money only after you’ve seen your summary. Some people never buy, and their documents are handled the same way.

• Nothing about the handling changes. Same private storage, same limited access, same providers, and the same retention and sharing described on this page.
• No card details are collected to reach that point, so there is no payment method held for you and nothing to cancel.
• The requests described further down are handled on the same terms as a paying customer’s. We do not have a slower queue for people who did not buy.

We will email you about your own analysis, because that is what you gave us an address for. Marketing email is a separate thing and every one of those carries an unsubscribe link that works.

Who else processes your data

Separately from the selling and sharing described below, these service providers process data on our behalf to operate Wedding Remedy, under contractual restrictions. Each is a role, and each role sees only what that role needs:

• Payment processor — runs checkout and refunds, and holds the card details we never see. Involved only if you accept a quote, and then gets your email and the amount. Never sees your documents.
• Cloud database and file storage — where your order record, your uploaded files, and your plan live. Technically holds everything; contractually processes it only on our instructions.
• Email delivery — sends your estimate, receipt, sign-in link, plan, and support replies, the updates you send to guests who asked for them, and receives the mail sent to your forwarding address. Gets the addresses and the contents of those messages.
• Push notification services — run by the maker of your phone’s browser, they deliver the notifications you turn on. They get the reminder’s title and one fixed line asking you to open your plan, and nothing else from it.
• AI document processing — reads your documents to extract terms and to draft your plan. Gets the document contents. Contractually barred from using them to train models.
• Concierge assistant — on the $79/month plan, answers questions about your wedding. For a question our own software cannot answer, it gets: what you type into it; your saved priorities; a summary of your planner made of counts, dates, times, categories and the amounts you entered (for example how many guests have replied, your checklist steps and their dates, your budget lines by category, the times on your run sheet and the sizes of your tables); the dates on your license and admin desks (not your notes, the office’s name or the fee); counts and times from your wedding day: how many people have a part and in which roles we offer, the range of their call times for each event, how many things are on the bring lists and how many photo groupings you have; your budget targets, the payment schedules you entered and your currency, and the vendors on your shortlist as counts by category and status, with tour dates — without the names you typed; and, once your contracts are read, your plan and the text of your documents as we read them. The summary leaves out your guests’ names and the words you typed yourself, such as moment titles, notes and labels, and it does not include meal choices, dietary or religious details, guest notes or anything about children. It also leaves out people’s names, the things on your bring lists and the names of your photo groupings, and it never includes children’s names, your private notes about people, and phone numbers. Questions about your own lists, such as who hasn’t replied or what’s due in a month, are answered by our own software. Neither those questions nor their answers are sent to it. It gets this for as long as it takes to answer, and is contractually barred from using it to train models. Your conversation is not stored: it lives in your browser tab and is gone when you close it. When you ask the 24/7 Concierge a question, the summary of your planner sent to our model provider includes your guest list’s numbers, your events’ dates and counts, and your menus’ totals. It does not include your guests’ or children’s names, their addresses or contact details, or anyone’s dietary or allergy needs. Quick answers on the free planner are worked out by our own software from your planner and our guides. They do not use an AI provider.
• Error monitoring — records technical errors so we can find and fix them. Gets stack traces and request metadata, not your documents.
• Hosting and content delivery — serves this site and runs our server code. Sees ordinary request data, including your IP address.
• Advertising platform — receives only the conversion signal described in the next section. Never receives documents, extracted figures, findings, vendor names, wedding dates, or budget amounts.

None of these service providers is permitted to sell your data or to use it for their own purposes. If we change who does one of these jobs, the role list above stays true; if we add a new kind of processing, this page changes first.

Advertising, attribution, and your hashed email

If you arrive from an ad, we store the campaign parameters alongside your record so we can tell which advertising is worth paying for. When you ask for an estimate, and again if you buy, we tell the advertising platform that the event happened. What goes with it is limited to:

• Your email address, scrambled first with a one-way hash, so the platform can match its own record without receiving the address itself.
• The click id and browser id that platform issued in the first place, and the value of the purchase if there was one.
• Your IP address and browser user agent, in the clear. The platform requires them to match the event to the same device. We are naming this plainly rather than leaving it under “analytics”.
• Which page or offer the event was about, and our own advertising metadata: the landing-page variant under test and the id of the ad creative you clicked. That is our information about our own marketing, not information about you.
• How far through the scan you got — the step number, how many steps there were, and which step it was. Not your answers.
• Identifiers for the estimate, the order and the plan, and for a delivered plan whether it went by email or the portal, and for a refund which of our stated reasons it was. The identifiers are random and mean nothing outside our own database.

That list is the whole list, and it is the same list our code enforces: a single array names every field that may leave, a type error stops a new one being added by accident, and a test fails the build if this page and that array ever disagree.

What this conversion signal never carries: your documents or anything extracted from them, your vendors’ names, your wedding date, your budget figures, your guest count, the financial qualification bucket produced by your answers, whether we recommended buying a plan, your findings, and any conclusion in your plan. An allowlist in our code rejects those fields before a payload can leave, and a browser is never trusted to report a purchase — only our payment processor’s verified webhook is.

Some state laws treat a conversion signal like the one above as “sharing” or as targeted advertising.

Selling and sharing data

We may sell, license or share the data we hold — including your documents, what we extract from them and what you add to your workspace — with other businesses, for their own purposes. That can include your contact details, what you told us in the scan, the documents you upload and everything we extract from them, your plan, what you add to your workspace (checklists, budgets and payment schedules, the vendors you consider and your scores of them, guest lists, including guests’ addresses and contact details, the people in each household and their dietary and allergy needs, notes and photos), how you found us, and how you use the site. A business that receives data from us may use it for its own purposes, including marketing, research, analytics, product development and training models, and may combine it with other data it holds.

If you add other people’s details — guests, their children, vendors, family — please only add what you are entitled to share with us, and tell them if the law where they live requires it. Children’s names are kept as initials. Guests who reply through a wedding page or add photos are shown a notice linking to this policy.

We do not hold card details, so none can be sold: they go only to our payment processor. If Wedding Remedy or its assets are sold or merged, the data we hold would be part of that transaction.

If you are a guest, a helper or family

A couple can share pages from their plan: a wedding page where guests reply and add notes and photos, a day-of link for the people helping on the day, and a page for someone paying for part of the wedding. We run those pages for the couple. What you send through them — your reply and meal choice, notes, photos, your email address if you ask for updates, and a contributor’s name and address — is handled as this policy describes, in the words it uses for everyone:

• We keep what you send us, what we build from it and what you add to your workspace, with no scheduled deletion, whether or not you become a customer.
• We may sell, license or share the data we hold — including your documents, what we extract from them and what you add to your workspace — with other businesses, for their own purposes.

If a couple shared a page or link with you — their wedding page, your household’s invitation link, or a link to send addresses or names for their guest list — Wedding Remedy runs it for them. What you send there (your reply, the people in your household and their meals and dietary needs, a question, a note, a photo, a postal address, an email or a phone number) goes to the couple’s planner and is kept by Wedding Remedy, with no scheduled deletion, and may be sold or shared with other businesses as this policy explains. Children’s names sent through a family list are kept as initials.

The couple whose page it is can see what you send. You can ask for a copy of what we hold or ask us to correct it. A request made under a privacy law that applies to you is handled as that law requires.

Cookies and what is stored in your browser

• Your answers to the optional questions, in local storage, so a refresh does not lose your progress. Clearing site data removes them.
• Our own attribution record, in local storage: the campaign parameters and click ids described above, and nothing about your wedding.
• Your free wedding starter, saved in local storage when you choose “Save on this browser.” It stays on that browser until you clear it or clear site data. It does not sync between devices. Bringing it into the paid shared plan and saving there stores it with your order, visible to people with access to that plan.
• What you type into the free tools, in local storage, so the calculators, the planning checklist and the quote comparison still have your entries when you come back. It stays on that browser until you choose Clear entries on the tool or clear site data, and it is not sent to us.
• A session cookie for the portal, to keep you signed in after you follow your sign-in link — which is how you upload, before there is any question of paying.
• A visitor id, a cookie named wr_vid set by our server so our own log of how the site is used can tell one visit’s pages and steps from another’s. It is a random value, holds nothing about your wedding, and lasts up to 400 days.
• Which version of a page you were shown, a cookie named wr_cta, so a page we are testing shows you the same version when you come back.
• Calendar files. The free planner can download a calendar file of your remaining steps, the dates you set and the wedding day, with no amounts and no guest names. Once it is in your calendar app, it is held there under that app’s terms. On the $79/month plan, the calendar link your phone subscribes to also includes the dates you set, with alerts a week and a day before.

The site does not load the advertising platform’s browser script. The limited server conversion signals described above remain separate from your planning notes.

How long we keep things

We keep what you send us, what we build from it and what you add to your workspace, with no scheduled deletion, whether or not you become a customer. Nothing is deleted on a schedule: not uploads after a plan is delivered, not an analysis that never became a purchase, and not a free account nobody uses.

Your documents, your plan and your workspace

Kept. A photo removed from a wedding album disappears from the album, and its file is kept. Other things you delete in your workspace, such as a guest or a note, are removed from your workspace.

Your sign-in link

Stops working 60 days after your wedding date. The data behind it is kept. If you bought a plan, download the PDF and keep your own copy.

Your order record and messages

Kept.

The internal event log

Append-only by design, so nobody can quietly rewrite the record of what happened to an order. It holds identifiers, statuses, and timestamps rather than document contents.

Encrypted recovery backups: seven days

We keep encrypted database and file snapshots for recovery work for seven days. They are restricted to recovery and are not used for anything else.

Unsubscribe records

If you unsubscribe, we keep the fact that you did. It is the only way to be sure we do not email you again.

Security, and what we are not claiming

In place today:

• The site is served over HTTPS with strict transport security, so a browser refuses to load it over plain HTTP, and with headers that block framing and content-type sniffing.
• Nothing in your browser talks to our database. Row-level security is enabled and forced on every table with no permissive policy for public or signed-in roles, so order data is reachable only through our own server code.
• Card details never reach our servers. Checkout runs on the payment processor’s own hosted page.
• Portal and plan routes are served with no-store caching and are excluded from search engines, so nothing behind your sign-in link is cached by an intermediary or indexed.
• Public endpoints are rate-limited.

Built in, but not yet tested by real traffic:

• Sign-in tokens are held as a hash. The database has no column for the value we email you, so a copy of it is not a set of keys.
• Uploads are constrained by file type, size, and count, and the same file uploaded twice is one document rather than two.
• Uploaded files go to storage that is not publicly listable and not linked from anywhere.

What we are not claiming: we have not commissioned an independent security audit, and this page does not claim encryption at rest, formal access logging of who opened which document, or any certification. Some of those are on the build list; none of them are true today just because a privacy policy would look better saying so. When one becomes true, this page will say it and the effective date will move.

Requests about your data

Write to help@weddingremedy.com from the address you gave us and say what you are asking for. We reply within 30 days. There is no form and no phone call, and it makes no difference whether you ever paid us.

• Access — a copy of what we hold about you.
• Portability — that copy in a structured, machine-readable file rather than a screenshot.
• Correction — fix anything we have wrong, including a figure misread out of one of your documents.
• Unsubscribe — stop marketing email. We keep a suppression list so that it sticks, rather than relying on someone remembering.

A request made under a privacy law that applies to you is handled as that law requires. We do not charge for any of this and we do not make the service worse for people who make a request. If we refuse a request, we will tell you why and you can ask us to reconsider.

State privacy rights

Several U.S. states give their residents privacy rights about their personal data. If one of those laws applies to you, write to us and say which right you are using; we handle it as that law requires.

If something goes wrong

If we discover unauthorised access to your documents or your personal data, we will investigate and contain it first, then email the people affected without undue delay: what happened, what data was involved, what we have done, and what — if anything — you should do. Where the law requires us to notify a regulator, we will. We will not wait for a journalist to ask.

Automated processing

An automated pipeline reads your documents and drafts your findings, and an automated check decides what the finished plan may claim — which is to say, whether you are shown a figure and asked to pay at all, or told honestly that there is not enough there. That check is arithmetic on figures traced to your own paperwork, described in full on the How we count page — not a judgement about you as a person, and never a credit, insurance, or eligibility decision. If you think it got something wrong, a human will look.

Where your data is processed

Our providers run infrastructure in more than one region, and processing may happen outside the state or country you are in. We are not naming specific locations on this page until we have verified them in each provider’s contract, because a location claim that turns out to be wrong is worse than no claim at all.

Age

Wedding Remedy is for adults. Do not use it if you are under 18. We do not knowingly collect data from anyone under 18, and if we learn we have, we delete it.

Changes to this policy

If we change this policy, the effective date under the heading at the top of this page changes with it. If the change actually affects you, we will email you rather than quietly editing the page.

Questions

Write to help@weddingremedy.com. Support is answered by an assistant first, with a person stepping in when it needs one. Anything about your data, access, or a mistake in your plan reaches a human.

See also our Terms of Service, our Disclaimer, and our accessibility statement.