Privacy Policy

Optional website analytics and advertising measurement

We use Google Analytics (Google) and the Meta Pixel (Meta) on public website and trial-success pages to measure visits, signup progress and confirmed celebrant trials, and understand advertising performance. Tracking is enabled by default unless you have opted out on this browser. These providers may receive cookie identifiers, IP address, browser information, page URLs and advertising campaign identifiers, and process information outside Australia.

We do not include names, email addresses, passwords, booking information or marriage-document details in our tracking event parameters. We do not initialise these trackers on private couple, mate, booking or account-management pages. You can turn off tracking below and still use the service. This stops future optional tracking on this browser; it does not remove information already received by a provider. Previous opt-out choices are respected.

See Google’s privacy policy and Meta’s privacy policy for their handling of this information.

What we collect

Celebrant account details: name, business name, email address, phone number, and login credentials.

Booking and couple details: both partners' names, email addresses, phone numbers, wedding date and venue, package and fee information, and any additional contacts a celebrant or couple adds (e.g. a wedding planner or reading participant).

Notice of Intended Marriage (NOIM) details: where a couple chooses to use the NOIM Vault, this can include date and place of birth, passport or birth certificate number, occupation, residential address, conjugal status, and parents' names and countries of birth. Providing this through Ceremony Hub is always optional — a couple can leave any field blank and provide the same information to their celebrant in person instead.

Questionnaire responses and vows: answers a couple provides to their celebrant's ceremony questionnaires, and any personal vows they write. Vows and individually-answered questionnaire questions are private to the partner who wrote them.

Email correspondence: if a celebrant connects their own email inbox, messages relevant to a booking are fetched to display alongside that booking. This connection uses the celebrant's own mail credentials and is never shared with or visible to couples.

Google Calendar data: if a celebrant connects Google Calendar, see "Google Calendar Integration" below for what we access and how it's used.

Google Calendar Integration

A celebrant can optionally connect their own Google Calendar from Settings. Doing so grants Ceremony Hub two Google OAuth scopes: calendar.events (to create, read, update, and delete calendar events) and userinfo.email (to confirm which Google account is connected).

We use this access for exactly one purpose: keeping a calendar event in sync with each of that celebrant's own bookings in Ceremony Hub — creating an event when a booking is added, updating it if the date, time, or venue changes, and removing it if the booking is deleted. Ceremony Hub also reads back the celebrant's existing calendar events so they can see their full schedule (personal and Ceremony Hub-created events together) on the in-app Calendar page. We never read, modify, or delete events on behalf of anyone other than the celebrant who connected their own account, and calendar data is never shown to couples or to any other celebrant.

Access tokens for a connected Google account are encrypted (AES-256) before storage, used only server-side to make the calendar API calls described above, and never sold, shared with third parties, or used for advertising. A celebrant can disconnect Google Calendar at any time from Settings, or revoke access directly from their Google Account permissions page; either immediately stops all further access.

Ceremony Hub's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements.

How we protect it

Sensitive identity fields — NOIM details (date of birth, place of birth, passport/certificate numbers, and related fields) and connected-calendar access tokens — are individually encrypted (AES-256) before they're stored, and only decrypted on demand when the authorised celebrant or couple actually views that specific data. All data is transmitted over HTTPS.

Access is scoped so that a celebrant can only see their own bookings, and a couple can only see their own wedding — enforced both in the application and at the database level.

Who can see it

Booking and ceremony information is visible to the celebrant who owns the booking and the couple linked to that wedding. NOIM identity details are visible to that couple (each partner can see and edit their own entries) and to their celebrant, for the purpose of preparing the legal Notice of Intended Marriage. Vows and individually-answered questionnaire responses are visible only to the partner who wrote them and their celebrant — never to the other partner.

Third parties we rely on

Ceremony Hub is built on Supabase (database and authentication, hosted in Australia) and Vercel (application hosting). If a celebrant connects Google Calendar, Google processes calendar data under its own terms. If a celebrant connects their email inbox, their email provider (e.g. their own hosting provider, Gmail, Outlook, or iCloud Mail) is used to fetch and send messages using their own credentials. We don't sell or share personal information with third parties for marketing purposes.

How long we keep it

Booking and NOIM information is retained for as long as a celebrant's account is active, to support their recordkeeping obligations under the Marriage Act 1961 (Cth). A celebrant or couple can ask us to delete specific information at any time — see Contact below.

Your rights

You can ask to access, correct, or delete the personal information Ceremony Hub holds about you. Couples can edit most of their own information directly in their portal at any time. For anything else, contact us using the details below.

Changes to this policy

We may update this policy as Ceremony Hub changes. We'll update the date at the top of this page when we do.

Contact

Questions about this policy or your data can be sent to info@ceremonyhub.com.au.