Privacy policy

Version 1 · applies from October 29, 2026

Short version.

  • Your plan (guest list, seating, budget, notes) stays in your browser until you delete it. We never see it.
  • Our servers hold only what a feature needs: an RSVP form you create, a wedding website you publish, a record of your Pass purchase, and emails you send us.
  • Guest RSVP data on our server is deleted automatically within 12 months after the wedding date; if the date is already past or very close, 30 days after you create or update the link, or at once when you delete the link.
  • A published wedding website can be seen by anyone with its address, unless you set a guest password. It is deleted automatically within 12 months after the wedding date; if the date is already past or very close, 30 days after you publish or update the site, or at once when you delete it.
  • No accounts, no ads, no tracking pixels, no cookies. Your guests’ data is never sold.

1. Who is responsible

The controller for the data on our servers is Appcellent Yazılım Hizmetleri Anonim Şirketi, Cumhuriyet Mah. Fatih Sultan Mehmet Blv. Cadde 224 A Blok No: 41 A/A, 16210 Nilüfer / Bursa, Türkiye. Email for privacy questions: support@preptowed.com.

2. What we collect and why

Your plan

Data: everything you enter in the planner: guests, households, tables, rules, notes, budget, checklist, timeline.

Where: only in your browser on your device. It is not sent to us, except what is described under “RSVP link” and “Wedding website”.

Visiting the site

Data: Cloudflare, our host, handles your IP address and browser details to deliver the site and protect it. Our page counter records only the page, the website you came from (domain only), campaign tags in the link, your country, phone or computer, and the response code. It stores no IP address, no cookie and no ID, so it cannot tell visitors apart. Guest RSVP pages are counted as “/r/”, without the link.

Why: run the site, keep it secure, see which pages are used. Legal basis: legitimate interest (GDPR Art. 6(1)(f)).

RSVP link (only if you create one)

From you: the wedding title and date, event names, meal options, your RSVP options, and for each household its label and its guests’ first and last names, plus-one flags and age group (adult, child or baby). Not your notes, tags, tables or diet notes. We store only a hash of the private key that lets your planner read the answers.

From guests: their answer per event, meal choice, a plus-one’s name, a note to you (up to 500 characters), a mailing address if you ask for one, and allergy or diet notes only if you ask and the guest ticks the consent box. Turning the allergy question off erases the stored notes at once.

Why: show the form to your guests and pass their answers to your plan. Legal basis: contract with you (Art. 6(1)(b)); for guests, legitimate interest in answering the couple (Art. 6(1)(f)); allergy and diet notes, explicit consent (Art. 9(2)(a)).

Wedding website (only if you publish one)

From you: what you write for the site (names, date, story, schedule, travel and hotel notes, questions and answers, registry links, theme), the photos you upload, the address you choose, the RSVP link and its deadline, and your own domain if you connect one. If you turn on “Find your table”, the first and last names of the guests seated for that event and the name of their table; not households, meals, notes or tablemates. If you set a guest password, we store only a salted hash of it. We store only a hash of the private key that lets your planner change the site, and the Paddle transaction id of your Pass, to check that the Pass is still valid.

Who can see it: anyone who has the address (or scans the QR code), unless you set a guest password. Search engines are asked not to list it. “Find your table” shows only the table of the name a guest types, never the guest list. Wedding websites have no page counter and no analytics.

From guests: the name they type to find their table is used for that search only and is not stored. Searches are rate limited (see “Abuse limits”).

Why: show your site to your guests. Legal basis: contract with you (Art. 6(1)(b)); for guests on the find-your-table list, legitimate interest in helping them find their seat (Art. 6(1)(f)).

Abuse limits

Data: your IP address (for IPv6, only the network part), or a hash of an email address, with a count of recent requests. On wedding websites we count only names that found no table and wrong passwords, so guests sharing the venue Wi-Fi are not blocked.

Why: stop people from creating forms in bulk, guessing guest names or passwords, or flooding the restore email. Removed when the counting window ends (10 minutes to a day). Legal basis: legitimate interest (Art. 6(1)(f)).

Wedding Pass purchase

Data: Paddle collects your payment details, name, email and country under its own privacy notice. We keep the Paddle transaction id and customer id, your market, the amount and currency, the date, whether the Pass is active or refunded, and a keyed hash of your email address, not the address itself.

Why: unlock your Pass, restore it on another device, lock it after a refund, keep purchase records. Legal basis: contract (Art. 6(1)(b)); tax records, legal duty (Art. 6(1)(c)).

Restoring your Pass by email

Data: the email you type. We use it once to look up your purchase at Paddle and, if there is one, send a single email with a link that works once and expires after 24 hours. We keep only a hash of that link’s code.

Why: unlock your Pass on another device. Legal basis: contract (Art. 6(1)(b)).

Emails to us

Data: what you write to support@preptowed.com. Why: answer you. Legal basis: legitimate interest or contract.

We do not use ads, advertising pixels, session recording or cookies. We never email or text your guests. We do not make decisions about you by automated means. We do not sell or share personal data, including for advertising.

3. Who processes data for us

These providers process data only on our instructions, under data processing agreements:

  • Cloudflare, Inc. (United States; global network): Hosting the site, the RSVP forms, wedding websites (and their custom domains) and the Pass records; the cookieless page counter; sending Pass restore emails; security. Transfers: EU-U.S. Data Privacy Framework (incl. UK extension) and Standard Contractual Clauses.
  • Google LLC (Google Workspace) (United States): Our email inbox (messages to support@preptowed.com). Transfers: EU-U.S. Data Privacy Framework (incl. UK extension) and Standard Contractual Clauses.

Paddle sells the Wedding Pass as merchant of record and is a separate controller for payment data; see Paddle’s privacy notice. Paddle’s checkout runs Paddle’s own code when you open it.

4. International transfers

We are a company in Türkiye. The GDPR and UK GDPR apply to us because we offer Prep to Wed to people in the EU and the UK, and we protect your data to that standard wherever it is processed. RSVP forms, wedding websites and Pass records are stored on Cloudflare’s network, usually in a data center near where they were first created. You can ask us for a copy of the transfer safeguards.

5. How long we keep data

  • Your plan: in your browser until you delete it, for example by clearing site data for preptowed.com. We don’t delete it for you, and we can’t.
  • RSVP forms and every answer in them: deleted automatically within 12 months after the wedding date; if the date is already past or very close, 30 days after you create or update the link (24 months after you created the link if your plan has no date; never more than 36 months), or at once when you delete the link. The RSVP section of the planner shows the date. From 30 days before, the planner also shows a banner so you can download a backup. We don’t send reminder emails. Answers already pulled into your plan stay in your browser.
  • Wedding websites, with their photos, find-your-table names and password hash: deleted automatically within 12 months after the wedding date; if the date is already past or very close, 30 days after you publish or update the site (24 months after you created the site if your plan has no date), or at once when you delete the website in the planner. Unpublishing takes the site offline at once; its data stays until you publish again, delete it or the date above. If your Pass is refunded or charged back, the site goes offline at once. From 30 days before a published site is deleted, the planner shows a banner so you can download a backup.
  • Abuse-limit counters: until the counting window ends (10 minutes to a day).
  • Restore links: they expire after 24 hours or after one use.
  • Pass purchase records: as long as tax and accounting law requires (usually up to 10 years).
  • Request logs at Cloudflare: kept for a short time, for security and debugging.
  • Emails to us: as long as we need them to help you.

6. If you are a guest

The couple added your name to their RSVP form. Only someone with the link can open it, and finding your household needs your name. Your answers go to the couple. To change them, open the link again and choose “Change my answer”. To have them removed, ask the couple, or write to us with the link and your name. You can withdraw consent for an allergy or diet note the same way.

If the couple turned on “Find your table” on their wedding website, your first and last name and your table are on it, so that you can look up your seat. The site shows your table only to someone who types your full name, never a list of guests. To be removed, ask the couple, or write to us with the site’s address and your name.

7. Your rights

You can ask for access to your data, a copy, correction, deletion or restriction, and you can object to processing based on legitimate interest. Where we rely on consent, you can withdraw it at any time; this does not affect what was done before.

Most of your data is in your browser, under your control. You can delete an RSVP link or a wedding website in the planner at any time. For anything else, write to support@preptowed.com. We answer within one month.

Please write to us first. You can also complain to a data protection authority:

  • EU: the authority of your country (list of EU authorities).
  • United Kingdom: the Information Commissioner’s Office (ico.org.uk).
  • Australia: the Office of the Australian Information Commissioner (oaic.gov.au).
  • Canada: the Office of the Privacy Commissioner (priv.gc.ca).

United States (California and others): we collect identifiers (email for a Pass, IP address for abuse limits), the guest details you or your guests enter for an RSVP form, and purchase records. We do not sell or share personal information as defined by California law, and we do not track you across other websites.

8. Cookies and browser storage

preptowed.com sets no cookies. The planner keeps your plan in your browser’s storage, which it needs to work. You can delete it any time in your browser’s settings (site data for preptowed.com).

  • ptw:planner Your plan: guests, diet notes, tables, seating, budget, checklist, timeline and your RSVP link key. Local storage, until you delete it.
  • ptw:planner:prev The previous saved copy of your plan, as a safety net. Local storage, until you start over or delete it.
  • ptw:planner:backup-v… A full copy of your plan, guest details included, saved before an update changed its format. Local storage, until you start over or delete it.
  • ptw:planner:studio Your print studio choices (paper, style, wording). Local storage, until you delete it.
  • ptw:planner:single-keys Whether single-key shortcuts are on in the planner. Local storage, until you delete it.
  • ptw:rsvp-link Your RSVP link with its private key, so an undo can’t lose it. Local storage, until you delete the link.
  • ptw:rsvp-seen:… Per RSVP link: the answers already copied into your plan, so they are not applied twice. Local storage, until you delete the link.
  • ptw:rsvp-hidden:… Per RSVP link: the unmatched answers you chose to hide. Local storage, until you delete the link.
  • ptw:rsvp-deleted The ids of the last 20 RSVP links you deleted here, so an undo can’t bring them back. Local storage, until you delete it.
  • ptw:rsvp-pulled When the planner last fetched new RSVP answers (at most every 10 minutes). Local storage, until you delete it.
  • ptw:rsvp-reminder The day you dismissed the deletion reminder (RSVP answers, wedding website), so it stays hidden for that day. Local storage, until you delete it.
  • ptw:site-link Your wedding website’s address and private key, so an undo can’t lose it. Local storage, until you delete the website.
  • ptw:site-deleted The ids of the last 20 wedding websites you deleted here, so an undo can’t bring them back. Local storage, until you delete it.
  • ptw:pass Your Wedding Pass: a signed code with the Paddle transaction id, no name or email. Local storage, until you delete it.
  • ptw:pass:checked When the planner last checked that your Pass is still valid (at most once a day). Local storage, until you delete it.
  • ptw:pass:checkout An open or paid checkout not unlocked yet: its Paddle transaction id and a one-time claim code. Local storage, until the Pass unlocks, at most 7 days.
  • ptw:pass:claim One checkout in progress, so a reload can still unlock the Pass. Session storage, until the tab closes.
  • ptw:pass:txn The Paddle transaction id of a checkout that is not unlocked yet, so you can try again. Session storage, until the tab closes.
  • ptw:rsvp:… On a guest’s RSVP page: the household they picked. Session storage, until the tab closes.
  • ptw:site:… On a password-protected wedding website: the key that shows the site after the guest typed the password. Session storage, until the tab closes.
  • ptw:accent, ptw:theme Preview builds only: the color choice for testing. Local storage, until you delete it.

9. Children

Prep to Wed is meant for adults planning a wedding. Couples may list children as guests (name and age group only). We do not knowingly collect data directly from children.

10. Security

Connections are encrypted (HTTPS). An RSVP link contains a long random code that can’t be guessed, guest search shows only household names and first names, and the key that reads the answers is stored only as a hash. A wedding website’s guest password and private key are stored only as hashes too.

Our host, Cloudflare, logs requests (for example the page address, time and response) for security and debugging, and keeps those logs for a short time. Pass restore codes are never in an address sent to us: they sit after the “#” in the link, which your browser keeps to itself.

11. Changes

If we change this policy in a way that matters, we post it here before it applies. The version and date are at the top.