Your love story, your data.
A wedding brings together a lot of personal details – about you, your family and your friends. Here’s exactly what we keep, why, who sees it and how you stay in control.
- We never sell your dataNot to advertisers, not to vendors, not to anyone – and we don’t “share” it for ads.
- Guests only see their ownEach guest’s link shows their household’s RSVP – never anyone else’s answers.
- No ad trackingNo ad cookies, no tracking pixels, no data brokers. Statistics run cookie-free on our own server.
- Stored in GermanyOur servers, database and photo storage run in Germany under EU data protection law.
- Allergies only with consentGuests decide themselves. We delete allergy and access notes the day after the wedding.
- Ask us anythingDownload a copy of your data or delete your whole account yourself on your account page – or write to privacy@justmarried.one.
1. Who is responsible & how to reach us
JustMarried.one is operated by Tobias Kurig, Isarweg 1, 85774 Unterföhring, Germany (see Imprint). We are the “controller” under the EU General Data Protection Regulation (GDPR) for the data we process to run JustMarried. Because we are based in the EU, the GDPR applies to all of it – wherever you live. US state privacy laws may give you additional rights (section 12).
Privacy questions and requests: privacy@justmarried.one. Everything else: hello@justmarried.one.
2. The personal data we store
We only store what a wedding needs. Most of it is entered by you; some by your guests, your team and your photographer.
| Whose data | What we store | Who enters it |
|---|---|---|
| Your account | Name, email, password (hashed) or your Google/Apple sign-in ID, language, time zone, when you accepted the Terms; for each login session the IP address and browser | You |
| Your wedding | Your names (also after the wedding) and emails, date, venues and addresses, story, FAQ, photos of you two, memorial photos and names, hashtag, timeline, checklist, your venue’s AV contact (name, phone) | You and your team |
| Team | Name, email and role of co-planners and helpers you invite – and of a partner whose email you enter in “You two”, who is invited as “Couple” | You (the person accepts) |
| Guests | Name, email, phone, postal address, side, list, relationship, wedding-party role, age group (adult, teen, child, baby), language, plus-one, notes | You – or the guest in their RSVP |
| RSVP answers | Yes/no per event, meal choice, “alcohol?” answer, a note, a history of earlier answers (without health data) | The guest |
| Allergies, dietary & access needs | Free-text notes and the time of consent – treated as health data (section 5) | The guest, with consent |
| Photos & videos | Files, uploader name, upload time, reports and your approvals – location and camera data are removed from photos | Guests, your photographer, you |
| Toasts | Speakers’ drafts and your comments | Speakers, guests |
| Registry | Gift links, product name, price and photo from the shop page; who reserved a gift (name, note); cash-fund pledges (name, amount, message) | You, guests |
| Budget & vendors | Your budget limits; for each vendor: name, service, cost and amount paid, contact person, phone, email, address, website, a note; order emails you send them (recipient, time) | You and your co-planners – helpers don’t see the budget |
| Payments | Which guest tier, amount, currency, date and Stripe’s session number – never card or bank details | Stripe, after you pay |
| Emails | Recipient, type and time of each email we send for you, opt-outs | Our system |
| Technical data | IP address and browser in server logs and, for a short time, in memory to slow down login and code guessing | Your browser |
We don’t ask for Social Security numbers, ID or marriage-certificate data, and we don’t use face recognition.
3. Why we use it (purposes & legal bases)
| Purpose | Data | Legal basis (GDPR) |
|---|---|---|
| Your account and planner, team access | Account, wedding, team, guest list | Contract – Art. 6(1)(b) |
| Invitations, RSVPs, reminders, thank-yous, toasts, website, photo sharing for your wedding | Guest data, RSVP answers, media | Our and your legitimate interest in running your wedding – Art. 6(1)(f) |
| Allergies, dietary and access needs | Health data | The guest’s explicit consent – Art. 9(2)(a) |
| Paid add-ons | Payment records | Contract and tax law – Art. 6(1)(b) and (c) |
| Security: login wait times, rate limits, logs, backups | IP address, browser, technical data | Legitimate interest in a safe service – Art. 6(1)(f) |
| Anonymous visit statistics | Shortened IP address, browser type, pages without codes | Legitimate interest in improving the site – Art. 6(1)(f) |
We never use your data for advertising, profiling or to train AI, and we make no automated decisions about you. You don’t have to give us any data, but without an email address we can’t create an account, and without guest details we can’t send invitations.
4. Your guests’ data
You decide who is on your list and what goes in; please only add people you actually invite. Each guest page links to this policy.
- Guests don’t need an account – their personal link or 6-digit code only opens their own household’s invitation and RSVP.
- Guests can change their answers until your RSVP deadline and withdraw their allergy consent at any time.
- Guests can unsubscribe from your emails with one click. We never email your guests for our own marketing – only messages you send: invitations, reminders, toast requests, RSVP confirmations and thank-yous.
- Guests can ask you or us (privacy@justmarried.one) to see or delete their data.
- Please don’t write health details into notes – the allergy field with consent is there for that.
5. Sensitive details: allergies, access needs, drinks and kids
- Allergies, dietary and access needs are only stored if the guest ticks a separate consent box on their RSVP. Unticking it deletes them.
- Only you, your co-planners and helpers see them. Your caterer gets them only if the guest also ticked the separate box to share them with the caterer, and you send the caterer list. They are never part of the RSVP history.
- We delete them automatically the day after your wedding. Our backups keep a copy for up to 14 more days.
- The optional “alcohol?” answer is only seen by your team and, if you send it, your caterer.
- Children are added by you or their parents, with name and age group only. Kids never get their own account.
- Residents of Washington, Nevada and other states with consumer health data laws: see our Consumer Health Data Notice.
6. Photos & videos
- Guests sign in to the upload page once with their code or name. Photos are re-encoded (AVIF) and stripped of location and camera data; videos are stored as uploaded.
- Your professional photographer can upload through a private link you create and can revoke. We keep a full-size print copy for your team; guests and screens only see a smaller copy, and only after you approve it.
- You decide what is shared: you can let guest uploads wait for your approval, turn the shared gallery on or off, and hide or delete any photo. Your photographer’s uploads always wait for your approval.
- Guests can report a photo or video – it is hidden right away until you decide.
- To have an intimate image of yourself removed, write to privacy@justmarried.one – we take it down within 48 hours, whether or not you are a guest.
- We don’t use face recognition and never use photos for advertising or AI training.
7. Private links and public pages
Some pages work without a login, so guests, speakers, vendors and TVs don’t need an account: RSVP pages, the RSVP entry by code, toast pages, the vendor run of show, “find your seat”, the photo upload page, the photographer’s upload page and the photo wall, table-of-honor and seating screens. Each is found only with a long random code or key, is hidden from search engines and shows only what that person needs – the vendor page never shows drafts or contact details.
Your wedding website’s address ends in a random key so nobody can guess it, and you can add a password. Anyone who has a link can open that page, so please share links only with the people they are meant for.
8. Who receives data
| Recipient | What for | Where |
|---|---|---|
| netcup GmbH | Hosting of our server, database and photo storage (data processing agreement) | Germany |
| Stripe | Card or wallet payment when you pay for your wedding’s guest tier, and refunds after a withdrawal. Stripe gets the amount, your email and payment details and acts as its own controller for payment and fraud checks | Ireland and USA |
| Google or Apple | Only if you choose “Continue with Google/Apple”: they confirm your name, email and profile picture to us and learn that you signed in to JustMarried | USA |
| Brevo (Sendinblue SAS) | Delivery of every email we send – invitations, reminders, account and confirmation mails (data processing agreement). When you open one of our emails, your mail app loads its header picture from our own server; that request is logged like any page view and is the same for everyone, so it tracks no one. A blind copy of each email goes to our own operator mailbox so we can spot delivery problems and misuse – never emails with a log-in link (account confirmation, password reset, planner invitation) and never the caterer’s list with allergy notes | France (EU) |
| US Census Bureau | Checking and standardizing the venue and vendor addresses you enter (only the address, no guest data) | USA |
| Photon by komoot (OpenStreetMap geocoder) | For a wedding in Germany: placing the venue and vendor addresses you enter on the map (only the address, no guest data; our server asks, not your browser) | Germany (EU) |
| OpenPLZ API | For a wedding in Germany: checking the postcode, town and street of those addresses against the official directory (only postcode and street name) | Germany (EU) |
| OpenFreeMap (OpenStreetMap map tiles) | The map around a venue in the planner (only tile numbers for that area, no names, no guest data; our server asks, not your browser) | EU / worldwide |
| US National Weather Service | The weather forecast for the wedding day (only the venue’s coordinates, no names) | USA |
| Bright Sky (open data of the Deutscher Wetterdienst) | For a wedding in Germany: the weather forecast for the wedding day (only the venue’s coordinates and the date, no names) | Germany (EU) |
| Your caterer, your photographer, your guests | Only what you send or publish: meal lists, the upload link, your website | Chosen by you |
| Authorities | Only if the law requires us to | – |
- Registry links: when you add a shop link, our server reads the public product page to fill in name, price and photo. The shop sees our server, not you. We store the photo ourselves, so guests’ browsers don’t contact the shop until they click the link. We don’t earn commissions on the product links you add.
- Shop buttons (“Find gifts at”): some of them may be affiliate links – if you buy through one, the shop may pay us a commission; your price stays the same. The note sits right next to the buttons. The shop may set its own cookies once you’re on its site; we don’t share your data with it.
- Notifications (push): if you turn notifications on for a device, we store that device’s push address and keys with your account and the wedding. Notes – for example “The Smiths replied: 2 coming”, “Anna shared a photo” with a small preview, or “RSVP deadline is tomorrow” – go through your browser’s push service (Apple, Google or Mozilla) and never contain allergies or contact details. The preview picture loads from our server through a link that stops working after a day. Turn them off in the planner or your browser settings; we delete addresses the push service reports as gone.
- AI apps (MCP): if you create your wedding’s AI code, you can connect an AI app you choose (for example Claude or ChatGPT). That app can then read and change your plan – guests with their contact details, RSVP answers, timeline, seating, checklist and registry – and its provider handles what it receives under its own terms. Allergies and access needs are never shared this way. We store the code and the app’s keys only as hashes; a new code or “Turn off” ends every connection at once.
- Emails to vendors: from the budget page you can email a vendor an order or request. It goes out through our mail service in your name (“Emma & Liam via JustMarried”); their reply goes straight to your own email address. We keep who it went to and when, not the text.
- Weather forecast: from a week before the wedding, the planner and your guests’ pages show the forecast for the venue. Our server asks the US National Weather Service – for a venue in Germany Bright Sky, which serves the Deutscher Wetterdienst’s open data – with the venue’s coordinates (and the date) only. Unless you switch it off, guests who said yes and your planners get the forecast once by email (guests can unsubscribe) and planners also as a notification.
- Address check: when you enter the address of a venue or a vendor, our server asks the US Census Bureau’s public geocoder whether it exists and how it is spelled officially. Only that address goes there – never your guests’ addresses or any names – and the Census Bureau sees our server, not you. JustMarried uses the Census Bureau’s geocoding services but is not endorsed or certified by the Census Bureau. For a wedding in Germany the address goes instead to Photon by komoot (an OpenStreetMap geocoder) and its postcode and street name to the OpenPLZ API; they too see only our server.
- Maps: the planner shows a small map around a venue. Our server loads the OpenStreetMap map tiles for that area from OpenFreeMap and draws the map itself – only tile numbers go there, no names or guest data, and OpenFreeMap sees our server, not you. Map data © OpenStreetMap contributors (ODbL).
- Maps: we show links to Apple Maps or Google Maps; they only open when you click them.
- Fonts and statistics are served from our own server – no Google Fonts or third-party analytics calls.
9. International transfers
If you use JustMarried from the US, your data is transferred to and stored in Germany. Stripe, Google and Apple may process data in the USA; there we rely on the EU–US Data Privacy Framework and the EU’s standard contractual clauses. Ask us for a copy of the safeguards.
10. Cookies & statistics
We only use cookies that JustMarried needs to work – for your login, a website password you entered, a guest’s photo sign-in, a paired TV and your language. No advertising cookies and no cross-site tracking. For anonymous statistics we run our own Matomo on our server in Germany: no cookies, IP addresses shortened before storage, your browser’s “Do Not Track” is respected, and codes and keys in links (like an RSVP link or your website address) are replaced before anything is recorded. Nothing is shared with third parties. Details: Cookie settings.
11. How long we keep it
- Allergy, dietary and access notes: until the day after your wedding, or until the guest withdraws consent.
- Your account, wedding, guest list, RSVPs, photos and videos: as long as your account exists. You can delete guests yourself at any time. Deleting a photo or video hides it from everyone; it stays stored so you can restore it, until your account is deleted; you can delete your whole account yourself on your account page: it goes at once, with every wedding you own alone.
- Photos and videos can be viewed, downloaded and added for 3 months after your wedding day. After that they stay stored, but nobody – not you, your guests, screens or your photographer – can open them any more.
- Login sessions: 30 days, or until you close the browser if you didn’t choose “Keep me logged in”.
- Backups: 14 days. Server logs: until they are overwritten (size-limited, usually a few days). Login and code-guessing counters: at most one hour, in memory.
- Payment records: as long as tax law requires (up to 10 years).
- Withdrawals (name, email, the contract and what you wrote): 3 years after the end of the year you sent them, as proof.
- Reports from /report (what and where, your description, and – if you give them – name, email and signature): 3 years after our decision, as proof; a reported intimate image is hidden at once and deleted when we remove it.
- Messages from the contact form: in our mailbox as long as we need them to help you, at most 3 years.
- Our blind copy of the emails we send (see Brevo above): at most 90 days in our operator mailbox.
- For every photo and video: the uploader’s name (shown as “© name”) and when they agreed to the upload license – as long as the photo or video is stored.
12. Your rights
Wherever you live, you can ask us to:
- see the data we hold about you and get a copy in a common format (access, portability);
- correct it – most of it you can edit in your planner yourself;
- delete it or restrict how we use it;
- object to uses based on legitimate interest, and withdraw consent at any time (this doesn’t affect what happened before).
Write to privacy@justmarried.one. We may ask you to confirm it’s you, and we answer within 30 days (at the latest within the time your law allows). If we say no, you can ask us to reconsider by replying to our answer. You may also use an authorized agent. Using your rights never changes your price or features.
US residents: California and other states give you rights to know, delete, correct and to opt out of the “sale” or “sharing” of personal data and of targeted advertising. We don’t sell or share personal data and don’t do targeted advertising, so there is nothing to opt out of – we also treat a Global Privacy Control signal as an opt-out. We don’t use sensitive data to infer anything about you.
Complaints: you can complain to a data protection authority, for example ours, the Bavarian Data Protection Authority (Bayerisches Landesamt für Datenschutzaufsicht, Ansbach, Germany), or your state’s attorney general.
13. Children
Accounts are for adults 18 and over. JustMarried isn’t directed at children and we don’t knowingly collect personal data from children under 13. Children appear only as guests added by the couple or their parents, with name and age group. If you believe a child gave us data, write to us and we will delete it.
14. Security
- All connections are encrypted (TLS). Database and photo storage sit on an internal network without public access.
- Passwords are hashed; after several wrong passwords the next try has to wait. Co-planners have their own logins and roles.
- Every page and file checks that you belong to the wedding; guest links only open their own household.
- Payments are made on Stripe’s own checkout page – we never see card numbers.
15. Changes to this policy
When we change how we use data, we update this page and the date above. For important changes we tell account holders by email before they take effect.
16. B2B catalog for wedding vendors
- The catalog is paused at the moment: nothing is shown and no new entries can be added; the removal link in your email still works. While it was open, vendors could add their business to the public catalog B2B JustMarried: business name, category, business address, email, and optionally phone, website and a short description. Everything except the email link you receive is shown publicly to everyone.
- Legal basis: your consent, given with the checkbox on the form. The address goes through the US Census Bureau’s address check (like venue addresses) and is stored as returned.
- We email you one link: your entry shows only after you confirm it there, and the same link removes it at any time – then it is deleted right away. We store only a fingerprint of that link, not the link itself.
- Entries you never confirm are not shown. To remove an entry without the link, write to us.
17. News & special offers
- On our home page you can subscribe to news and special offers by email. We store your email address, your language and when you subscribed.
- Legal basis: your consent, given with the “Subscribe” button and confirmed with the link we email you right away (double opt-in). Until you click it, we send nothing else; only confirmed addresses get news – at most once a month.
- Every news email has a one-click unsubscribe link, and the confirmation page lets you leave at any time. Unconfirmed sign-ups get at most one reminder link per hour and are never used for news.