Cookie Policy

A cookie is a small piece of text a website asks your browser to hold on to and hand back on your next visit. Your browser also has something called local storage, which does the same job by a different mechanism — the browser keeps it, and only the site that wrote it can read it.

Both exist so a site can recognise your device from one page to the next. That is what makes staying signed in possible, and it is what lets a guest come back to an album and still see the photos they sent. This page covers both, because heading it "cookie policy" and then quietly leaving local storage out would be a dodge.

A small number of things get stored whatever you choose, because the service does not work without them. They are not used to track you, and they are not shared with anyone.

• Staying signed in. If you are a couple with an account, a cookie holds your session so the app knows the dashboard it is showing is yours. That cookie is what being signed in consists of — without it you would be signed out on every page.
• Recognising a guest’s own uploads. Guests never make an account, so a random token is kept in their browser instead. It is what lets an album know which photos are theirs, so they can see them and take one down if they change their mind. It is not built from anyone’s name, email or device, and it identifies nobody anywhere else.
• Finishing an interrupted upload. A note of where a photo got to, so patchy signal at the venue means it carries on rather than starting again. Each one is discarded the moment its upload finishes.
• Remembering your answer to the cookie banner, so we do not ask you every single visit.

Clearing this storage does not delete photos already uploaded — they belong to the album now. It only means the album stops recognising your device, so you can no longer remove them yourself. Ask the couple if you need one taken down.

This is the part worth reading even if you skip the rest.

The page your guests open when they scan the code — browsing the gallery, uploading their photos — carries no analytics of any kind. Nothing is loaded there, so there is nothing to consent to, and your guests are never shown a banner. This does not change when you accept on your own account: your choice covers your visit, not theirs.

Session recording tools work by capturing what is on the screen. On a wedding album that would mean capturing the photographs, the names guests type, and the album link itself — from people who scanned a code at a party and never agreed to anything. We do not run them there, and this page is the commitment not to. We do not run them on the signed-in pages either.

Everywhere else — this marketing site, and the pages a couple signs in to — we would like some measurement, because knowing which parts people actually use is how the thing gets better. That is not a good enough reason to set cookies without asking, so we ask, and take the answer seriously.

• Nothing analytics-related loads before you answer. Not held back, not loaded in a restricted mode — not fetched.
• Decline and none of it is ever downloaded on this browser. There is no configuration mistake that could quietly turn it back on, because the code is not there to run.
• Accept and the tools we use set a couple of cookies that recognise your browser on a return visit, so three visits from you count as one person rather than three. They hold a random identifier, not your name or email, and we never link them to an account.
• On the app, what gets counted is which pages you open, when you create an album and when you buy one. That is how we find out where people give up. There is no recording or replay of your screen anywhere on the app, and your photographs are never part of it.
• You can change your mind at any time — on this site with the button further down the page, and on the app from its own cookie settings.

The site and the app ask you separately, and that is deliberate rather than clumsy: they are different addresses, and a browser will not let one read the other’s answer. So declining on one never silently commits you on the other.

Before you answer, and forever if you decline, these pages make no third-party request at all — no tag manager, no advertising pixel, no embedded video, no map, no chat widget, no social buttons. Even the fonts come from our own domain rather than a font service.

Running the service means relying on a few other companies. In each case they only get what they need to do their job:

• Analytics providers — on this site and on the signed-in pages of the app, and only once you have accepted there. They see which page you looked at, roughly where you are from your IP address, and what device and browser you used. We have not switched on any advertising feature, so your visit is not added to an advertising profile by us.
• A session-recording tool, on this marketing site only. It records how these public pages get used — mouse movement, clicks, scrolling. This site has no sign-in and no forms, so there is nothing on it for a recording to capture about you personally, which is exactly why it is confined here and runs nowhere else.
• Our payment provider — paying takes you to their own checkout page, so nothing of theirs runs on ours. We never see your card details.
• Our hosting, storage and sign-in providers — they hold your photos and album data, and the sign-in cookie is theirs. Your photos are stored in Australia.

Our hosts also keep standard server request logs, the same as every website has since the 1990s. Those are not cookies, they are not tied to a profile of you, and we do not use them to follow anyone around.

• No advertising or marketing cookies, and no remarketing pixels.
• No analytics inside a wedding album. Nothing measures or records what happens there, and your guests are never asked to agree to anything, because there is nothing to agree to.
• No session recording on the app at all — not on the album, and not on the pages you sign in to. Recording is confined to this marketing site.
• No tracking you across other websites, and no device fingerprinting.
• We do not sell, rent or hand anything about your visit to data brokers or advertising networks.
• We do not set anything optional before you have said yes to it.

If any of that changes, this page is updated before the change ships, not after — and anything needing your consent gets asked for properly rather than switched on quietly.

Analytics on this site is yours to turn on or off whenever you like:

The app keeps its own separate answer, which you can change from its cookie settings the same way.

Everything else is controlled from your browser rather than from us. Every major browser lets you see what a site has stored, delete it, and stop it storing anything more — look for cookies or site data in its privacy settings.

If you block all of it: this marketing site keeps working exactly as it does now, because nothing here depends on a cookie. Couples cannot stay signed in, which makes the dashboard unusable. Guests can still upload, but the album stops recognising them between visits, so they will be asked for their name again and cannot remove a photo they sent earlier. Photos already uploaded are safe either way.

Some browsers also send a Do Not Track or Global Privacy Control signal on your behalf. Neither is a substitute for the banners we show, which ask you directly and default to no — so a browser sending either signal is already getting what it is asking for.

When what we store changes, this page changes with it and the date at the top moves. Anything material resets the banner so you are asked again, rather than being quietly added under an answer you gave about something else.

Wedding QR Code is operated by D-EFFCON. If you have a question about anything on this page, or you want to know what we hold about you, email [email protected] and a person will answer — usually within a business day or two.

Our privacy policy covers personal information more broadly, and our terms of service cover everything else about using Wedding QR Code.

If you are not satisfied with how we have handled a privacy question, you can take it to the Office of the Australian Information Commissioner.