Privacy Notice for Guests
Each wedding invitation sent with Cire is a private website (“the site” in this notice). It asks for the small amount of information your hosts need to plan the day and cater for you. This notice explains what is collected, why, how long it is kept, who decides what, and the rights you have over it.
Who decides what
Two parties are involved, and it matters which one you need.
- Your hosts — the couple, and whoever is helping them organise. They chose to invite you, decide what to ask you, see your answers, and use them to run their wedding. Almost anything you might want changed — your name, your household, whether you are on the list at all — is theirs to change, and they are the fastest route to it.
- Us, English Street Ventures Pty Ltd, who build and run the site. We hold and process guest information on your hosts’ instructions. We also make some decisions on our own account and for every wedding alike — how long guest data survives the event, how the site is secured, and what technical telemetry it produces — and for those decisions the responsibility is ours, not your hosts’.
You can contact us about anything in this notice at [email protected], whether or not you have spoken to your hosts first.
What is collected
- Guest names — the names on your household invitation, and the name of anyone a guest is allowed to bring and chooses to.
- RSVP status — whether each named guest is attending each event.
- Dietary requirements and access needs — anything you choose to type into the free-text field (for example allergies, intolerances, or requirements that may reveal health information, or religious or belief-based dietary needs).
- When your household first opened the invitation — a single timestamp, shown to your hosts as a “Sent / Opened” marker so they know whether an invitation arrived. Not a record of every visit, and not what you looked at.
- When your household’s replies changed — each time a reply is sent or changed, which guest and event it was for and when, but not the answer itself. Your hosts see it as a “new” mark beside that reply, and the couple and anyone helping them plan get a daily count of changes by email, with no names in it. When one of your hosts sets a reply’s status for you, the record also notes which host did it, so the couple can tell who changed what; that change is not shown as new.
- Which of you sent each reply — each reply and change records the guest who sent it. When your invitation names more than one guest, it asks which of you is answering. Your household sees “Answered by” and that guest’s first name under each reply, and your hosts see it too. It rests on your word, not on a check of who you are.
- Where you sit, if your hosts plan seating — the table each guest is at for each event, set by your hosts. They see it, and may print it or send it to the venue; other guests never do.
- Your email address, if you or your hosts add one — so your hosts can send you news about the wedding through us. You can add, change or remove your own on your invitation. If your hosts add it, they confirm to us that you agreed, and your invitation shows it as added by them. With it we keep who added it, when, and the wording that was agreed to. We use it for nothing else.
- Gifts, if you give one through the registry — what your household reserves or marks as bought from your hosts’ list, and any money you send: the amount, the currency, the day, and the name and note you choose to add. Your hosts see these so they can thank you; other guests never do.
- Technical records — the session cookie that keeps you signed in to your invitation after you enter your code, and server logs kept to keep the site secure and working.
Nothing else is asked for or knowingly collected through the site. You only ever fill in details for the members of your own household, and for a guest your hosts have let you bring.
A note on dietary information
Some dietary or access details are treated as a protected category of information — under the Privacy Act 1988 (Cth) as “sensitive information”, and under the GDPR and UK GDPR as “special category” data — because they can reveal your health or your religious beliefs. Both regimes say such information should be collected only with your explicit consent (APP 3.3; GDPR Art. 9(2)(a)). The field is therefore optional, you tick a box to confirm before it is submitted, and a record of which version of this wording you agreed to is stored alongside it. If you give your answer to your hosts another way — over the phone, say — they can record it for you, and what is stored then is their confirmation that you agreed, not yours. If you are bringing a guest, you can give their dietary requirements only by ticking a separate box confirming that they agreed, and what is stored for them is your confirmation and the version of the wording you confirmed. Either way the person the information is about can withdraw it with us directly. Please don’t include any health or other sensitive detail you’d rather not share — a simple note such as “vegetarian” or “no nuts” is all that is needed.
Why it is used, and on what basis
- Guest names & RSVP status — to manage invitations, confirm numbers, and organise seating and logistics. Your hosts have a legitimate interest in running the event they invited you to, and providing the invitation is what our contract with them requires of us.
- Dietary requirements / access needs — to cater safely and accommodate your needs on the day. Because this can include protected information, the basis is your explicit consent, given when you tick the box and submit your RSVP, and withdrawable at any time. For a guest someone brings, it is that guest’s explicit consent, as confirmed by the person bringing them.
- Your email address — so your hosts can send you news about the wedding. The basis is your consent: given when you add it on your invitation, or given to your hosts when they add it. Remove the address on your invitation to withdraw it at any time, and we delete it. After that we will not email it to you about this wedding, even if it is added again, unless you add it back yourself; and if your hosts added it, we will not email it to anyone else at the wedding either.
- The first-opened timestamp — so your hosts can tell a delivered invitation from one that never arrived. Their legitimate interest in administering their own wedding; you can ask for it to be removed.
- Technical records — to keep your session working and the site secure. Our legitimate interest in a site that functions and is not abused.
Your information is never sold, and never used for marketing or advertising.
If a guest is bringing you
Your hosts may let a guest bring someone with them. If that is you, the guest who is bringing you gave us your name, and may give us your RSVP and — only if you agreed — your dietary requirements. One of your hosts may also record your RSVP and dietary requirements on your behalf; when they record your dietary requirements, what is stored is their confirmation that you agreed. You have no invitation code of your own and may never see the invitation itself, which is why we ask that guest to pass this notice on to you.
We hold your details for your hosts on the same terms as every other guest’s, set out in this notice, and delete them on the same schedule. Your name and RSVP rest on your hosts’ legitimate interest in running their wedding. Your dietary requirements rest on your explicit consent, and what is stored is the confirmation of the guest who is bringing you that you agreed, with the version of the wording they confirmed.
You have the same rights as any other guest, set out below, and do not need a code to use them: ask your hosts, or email us at [email protected], to correct your name, withdraw your agreement to your dietary requirements being kept, or have your details deleted. The guest who is bringing you can also change your name or remove you until RSVPs close.
Who can see it
Your hosts, and the people they have asked to help — a caterer or a venue, for instance — strictly so those people can do their job. Your hosts choose who that is; we don’t.
Your email address, if one is held, is seen by your hosts and everyone helping them with the guest list. Your invitation shows it to whoever opens it with your household’s code and says they are you, so that you can check and correct it, and never shows one member’s address to someone who says they are another.
On our side, the site and its data are hosted on Cloudflare, which provides hosting, the database and security. Beyond that, information is disclosed only where the law requires it.
If you send money through the registry, the payment is taken by Stripe on your hosts’ own Stripe account. Stripe collects your card details and the name and email you give it, under its own privacy policy; we never see your card, and we tell Stripe nothing about you beyond the amount.
Where your information is stored
Our primary region is Australia — the site is operated from there, and the infrastructure supporting its security is pinned to Sydney. Some technical records — server logs, error and performance telemetry containing no guest content — are processed by providers outside Australia in the course of running the service.
If you are in the EU or the UK, this means your information is transferred outside that area to Australia. You can ask us what protections are in place for that transfer, and we will tell you.
Cookies and content from other companies
There is no personal tracking on the site: no advertising or tracking cookies, and no analytics. The only storage the invite uses is strictly necessary, and it needs no choice from you:
- Your invite session — Keeps you signed in to your invite after you enter your family code, so you don't have to type it again on every page.
- Your privacy choices — Remembers the choices you make here, so we don't ask again on every visit. Storing this is what lets us honour a refusal.
- Cloudflare Turnstile — Checks that a real person is entering the family code, so the invite can't be opened by automated guessing. Data goes to Cloudflare, Inc. (US). Their privacy policy.
The other companies involved
Two parts of the invite are served by other companies, and each has its own switch. When one of them loads, that company receives your IP address and browser details, because that is inherent in your browser fetching something from their servers. So each stays off until you allow it, and you can allow one without the other.
- Google Maps — Shows an interactive map of each venue inside the event details. Data goes to Google LLC (US). Off until you allow it; stops loading again if you switch it off. Their privacy policy.
- Pinterest moodboards — Shows the couple's inspiration moodboard for an event's dress code. Data goes to Pinterest, Inc. (US). Off until you allow it; stops loading again if you switch it off. Their privacy policy.
Changing your mind
You can review or change these choices at any time — there is a Privacy Choices link in the footer of every page of the site.
Turning something off stops it loading from then on. Anything already sent while it was switched on has already left your browser and cannot be recalled. The venue map and the moodboard stay off until you allow them, and load only when you open an event’s details after that — so unless you have done both, nothing has gone to that company.
How long it is kept
Guest information — names, RSVPs, dietary needs, email addresses — is deleted 1 year after the final wedding event, after which it is permanently removed from our systems. Now and then it goes up to 30 days later, while we finish the record of your hosts’ gifts. That period is set by us and applies to every wedding; your hosts cannot extend it. You can ask for your own information to be deleted sooner.
When that happens your hosts keep a record of their gifts with no names in it: how many were reserved and bought from their list, and the amount, currency and day of each money gift. It stays with their wedding until they delete it.
The record of when your household’s replies changed is kept for 90 days, or less if the rest of your information goes first.
When you remove your email address, or replace one your hosts added, it comes off your guest record at once, though copies can remain in your hosts’ saved guest-list history until that is deleted on the schedule above. We keep a fingerprint of the removed address, not the address itself, so that we can recognise it and not email it again, and delete that with the rest of the wedding’s guest information. For an address you added yourself, the fingerprint applies to you alone: your hosts are told if they add it back for you, and it does not stop anyone else at the wedding adding it for themselves.
Your rights
You can ask to:
- Access the information held about you;
- Correct anything wrong or out of date;
- Delete your information;
- Withdraw your consent to the dietary and access information, or to your email address being used, at any time — this doesn’t undo anything done while it stood.
If you are in the EU or the UK, the GDPR and UK GDPR give you these rights plus the right to object to processing based on legitimate interests, the right to a copy of your information in a portable form, and the right to restrict processing while a dispute is resolved. We honour all of them wherever you are; they are set out separately only because the law that names them is.
Ask your hosts, who can act on most of it immediately, or email us at [email protected] and we will act on it ourselves and tell your hosts only what we must. We respond as soon as we reasonably can, and within a month at the outside.
Complaints
We would rather resolve a concern directly. If you are in Australia and are not satisfied, you can contact the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au. If you are in the EU or the UK, you can complain to your local data protection authority instead.
Changes to this notice
If how your information is handled changes, this page is updated and the “last updated” date above revised.