Cookies

Reading these pages sets no cookies. A cookie is set only when you sign in, open a guest link, choose a language, type the password of a wedding site or connect a screen to a photo wall.

The cookies we use

All of them are our own, sent only to BigDaySite over a secure connection and unreadable by scripts on the page.

• Organizer sign-in (__Host-bds_actor). Set when you open the sign-in link we email you. It keeps you signed in for at most 7 days and is removed when you sign out.
• Guest access (__Host-bds_guest_ followed by a code for the wedding). Set when a guest opens their private link, one for each wedding. It lasts at most 7 days, and never longer than the link itself.
• Guest language (__Host-bds_guest_locale). Set when a guest picks a language for their page. It holds only the language code and lasts 180 days.
• Wedding site password (__Host-bds_site_ followed by a code for the wedding). Set when a visitor types the password of a password-protected wedding site, one for each wedding. It lasts 8 hours and stops working at once if the couple changes the password or who can see the site.
• Photo wall screen (__Host-bds_screen). Set on the TV or computer that shows a couple's photo wall, when it asks for a pairing code. It holds only a random code for that screen, lasts at most 25 hours, and stops working at once when the couple disconnects the screen.

Browser storage

These stay in your browser. Only the phone's code for sending photos and videos, the last item below, is sent to us, and only with the files you send.

• Return to checkout (bds_sign_in_return). If you have to sign in again while choosing a plan, your browser remembers which checkout page to bring you back to. It is deleted as soon as it is used, and ignored after one hour.
• Chosen plan (bds_plan_choice). If you choose a paid plan on our pricing page before you have an account, your browser remembers which plan, so that after you create your wedding we can take you to it. It holds only the plan's name, is deleted when you continue, and is ignored after one day.
• Unsaved website edits (bds-website-draft: followed by codes for the wedding and your sign-in). While you edit your wedding site, your changes are kept in the tab until they are saved, so a reload does not lose them. Closing the tab removes them.
• Dismissed change notices (bds-change-hidden: followed by a code for the page). When a guest closes a notice that an event has changed, the tab remembers it so the notice does not come back. Closing the tab removes it.
• Photos and videos sent from this phone (bds-collect: followed by a code for the QR code). When a guest sends photos or videos with a couple's table QR code, the browser keeps a random code for this phone and the wedding's reference, so the guest can come back, see what they sent and remove it. The page sends that code to us with each file and each look at what was sent; it is never used for anything else. It holds no name or contact detail and stays until you clear your browser's site data.

If we add a feature that needs another cookie or storage item, we will list it here before it is switched on.

Why there is no cookie banner

Each of these is strictly necessary for something you asked for: signing in, opening your invitation, reading it in your language, visiting a password-protected site, keeping your edits, sending photos and videos or showing a photo wall. We use no analytics cookies, no advertising cookies and nothing from other companies, so there is nothing to ask your permission for. If we ever want to add a cookie that is not strictly necessary, we will ask you first.

You can delete these cookies in your browser at any time. You will then need to sign in, open your guest link or type the site password again.

More about how we handle your data is in our privacy notice. Questions: support@bigdaysite.com.