Privacy
Short version: we store the least we can get away with, a guest list is never readable from a public page, dietary notes and messages are erased automatically thirty days after the wedding, and guests' postal addresses six months after it. The rest of this page is the long version.
What we store, and for how long
| What | How long |
|---|---|
| The couple's names, wedding date and page content | Until the couple deletes the page |
| A page nobody kept: no email given, and nothing chosen, written, downloaded or shared | Deleted after 14 days |
| The email address of each person keeping a page, and the devices and passkeys they use to get in | Until that person is removed, or the page is deleted |
| Photographs a couple adds | Until the couple removes them, or deletes the page |
| A guest's name and whether they are coming | Until the couple deletes the page |
| A guest's postal address, if the couple asked for it | Deleted six months after the wedding |
| Gifts, and which thank-you notes are written | Until the couple deletes the page |
| What a guest cannot eat | Erased 30 days after the wedding |
| A message a guest wrote | Erased 30 days after the wedding |
| Counts of visits, and the steps couples take recorded against their page, each with a one-word source (never a name, an address or anything typed) | 13 months |
| How a couple found us, as one word, on their page | Until the page is deleted |
| If you buy a web address: the order (your email, the address, the amounts, what you agreed to and when) | Kept after the page is deleted, as the record of a payment |
The erasures are not a policy we intend to honour. Each is a scheduled job that runs against the database every night at 03:00 and deletes the values, not just hides them. Dietary requirements and anything a guest writes to a couple are treated as special-category data: kept only as long as a caterer needs them, then gone.
Who can read what
A guest list is never readable from a public web address. Submitting an RSVP is a one-way door: the public form can only add a reply, it cannot read one back. The only way to see a wedding's guest list is through the private editing link the couple holds, which is not guessable and is not indexed by search engines.
A guest's postal address goes one way too: a guest can write it on their own page, but nothing on that page shows it back. Only the couple sees it.
A page password keeps strangers off the page, but it does not lock each photograph. A photograph has its own web address that nobody can guess, and anyone who is given that address can open it. The page's own address is made from the couple's names.
While deckle is small, the person who makes it may look at a page once it is kept, to offer help if something looks wrong. Only the public page your guests see: never your guest list, your replies, or anything behind your private link.
When something happens that a person should look at (a page kept, or an address bought, refused, connected or failing to connect), our server sends that person's phone a message through Telegram, a messaging company. It carries the page's web address and, for an address, its name and price. Nothing else: no names typed into a form, no email address, nothing a guest gave.
We do not sell or rent any of this. There is no advertising on any page here, ever. See why it's free.
The companies that run it for us
Nobody else gets any of this, except the few companies the site runs on, each for its own job and nothing more:
| Company | What it does here |
|---|---|
| Cloudflare | Runs the site, stores photographs, forwards mail sent to hello@deckle.page, and registers a web address you buy |
| Supabase | Holds the database |
| Resend | Sends our emails, so it sees each email and who it goes to, including the private link in it |
| PayPal | Takes payment for a web address. We never see your card |
| Telegram | Carries the one alert described above |
None of them is ever asked to load anything on a guest's page.
Pages made through an AI assistant
If you ask an assistant such as Claude to make your page (how), it sends us the two names, the wedding date, and the look and colour if you chose them. Our server also sees the network address the request comes from (for an assistant, the assistant company's), uses it for one minute to limit how many pages can be made, and reads which assistant is asking, to record that one word. Nothing else reaches us: not your conversation, not who you are. The page is stored exactly like one made on our front page, with one word saying which assistant made it, and the same 14-day rule applies. Your conversation is the business of the company that runs your assistant, under its own privacy policy.
Trackers and third parties
A page a guest visits makes no request to any other company: no ad tech, no analytics service, no font CDN, no embeds, no gravatar. Every font and every byte a guest's browser loads is served from here. A map link opens OpenStreetMap in a new tab if a couple adds one; it is a link the guest chooses to click, never an embedded request.
What we count
How often pages are visited is counted on our own server, and so is how far couples get in setting up their page: each step is recorded against their page, so we can see how far each page got and what to improve. No script runs in your browser for it. No analytics company or ad network sees it; it is kept in the same database as everything else here. We note which site or campaign sent a visitor (“google”, “chatgpt”, a partner's code, or the bare name of a site that linked to us), never the page they came from, never your IP address or your browser, and nothing you type. The counts are deleted after 13 months. The one word recording how a couple found us stays with their page until it is deleted.
Cookies
There is no tracking cookie here, and no banner, because every cookie we set does a job you asked for. There are four. If you start a page, we keep your way back to it in this browser for 30 days, so closing the tab does not lose it (two cookies, one for a draft and one for a page you started; neither holds anything you did not type). Once you open your editor, we remember this device for 400 days, so it can get you back in without your link; every device is listed under Yours, where you can remove it. And if a couple puts a password on their page, we remember for a year that you got it right, on that page only. Clearing your cookies removes them all; nothing is lost but the convenience.
Deleting everything
A couple can delete their page and everything attached to it (the content, the guest list, the photographs, all of it) from their editing link, with no email to us required. Guests stop seeing the page at once. The deletion itself happens 24 hours later, so that anyone else keeping the page can stop it if it was a mistake. Write tohello@deckle.page if anything here needs deleting sooner than that, or if a guest wants their own reply removed, and we will do it by hand.
What stays when a page is deleted, and why:
- The record of the steps taken. It is no longer linked to the page or to anyone, and it is deleted at 13 months.
- If you bought a web address: the order, as the record of a payment, and the address itself, which stays registered to you until it expires. PayPal keeps its own record of the payment.
- Copies of the emails we sent, which Resend keeps for as long as it keeps its sending logs, and our server's logs, which name the email address each email went to and are kept for a few days.
If we ever close
A couple's page stays up through their wedding day and a year after it. If deckle.page ever shuts down, we commit to six months' notice and to handing every couple their data before it happens. Seewhy it's free for the rest of that promise.
deckle.page is run by Hieu Truong, one person, based in Hanoi, Vietnam. Questions: hello@deckle.page. Last updated 17 October 2026.