Privacy Policy

Last updated: 13 October 2026 Effective date: 6 October 2026

1. Introduction

WedBuild ("we," "us," "our") is operated by WedBuild Pty Ltd, an Australian company. We provide a wedding planning platform accessible at https://app.wedbuild.com and related services (collectively, the "Service").

This Privacy Policy explains how we collect, use, disclose, store and protect your personal information when you use our Service. It applies to all users of WedBuild, including account holders, their partners, guests, and visitors to published wedding websites.

We are committed to complying with the Australian Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs), the EU General Data Protection Regulation (GDPR), the UK GDPR, the California Consumer Privacy Act as amended by the California Privacy Rights Act (CCPA/CPRA), and other applicable privacy laws.

By using WedBuild, you acknowledge that you have read and understood this Privacy Policy. If you do not agree with our practices, please do not use the Service.

2. Information We Collect

2.1 Account Information

When you create a WedBuild account, we collect:

• Email address
• Password (stored as a cryptographic hash; we never store plaintext passwords)
• Authentication data if you sign in via Google (name and email provided by Google)

2.2 Wedding & Profile Information

When you set up your wedding, we collect:

• Your name and your partner's name
• Wedding date and location (including venue name, address, and geographic coordinates)
• Estimated guest count
• Primary use cases and preferences
• Currency and timezone settings
• Referral source (how you heard about WedBuild)

2.3 Guest Information

When you manage your guest list, you and your guests may provide:

• Guest names, email addresses, phone numbers, and postal addresses
• RSVP status and responses
• Meal preferences and dietary requirements
• Song requests
• Table and seating assignments
• Custom responses to questions you create
• Plus-one details
• Category and group assignments
• Notes you add about individual guests

2.4 Financial & Vendor Information

When you use the budget planner and vendor features, you may provide:

• Budget amounts and expense details
• Vendor names, contact details (email, phone, website), quotes, ratings, and notes
• Invoice details, payment records, and confirmation numbers
• Attachment files (e.g., invoices, contracts)

2.5 Wedding Website Content

When you build a wedding website, we store:

• Text, images, and design choices you create
• Published website content (accessible to anyone with the link)
• Custom domain settings, and, if you buy a domain through WedBuild, the details described in Section 2.12

2.6 Announcements & Email Communications

When you send announcements or email campaigns, we collect:

• Email content, subject lines, and design
• Recipient email addresses, names, and phone numbers
• Delivery, open, and click tracking data
• Whether a guest has unsubscribed from your wedding's emails (every email you send your guests includes an unsubscribe link)

2.7 Checklist & Planning Data

When you use planning tools, we store:

• Task details, due dates, priorities, assignees, and notes
• Comments and activity logs
• File attachments you upload

2.8 Payment Information

When you buy a paid plan, an AI credit pack or a domain, payment is processed by Stripe. We do not directly store your credit card number or full payment details. We store:

• Stripe customer ID and subscription ID
• Subscription tier and expiry date
• For a domain bought through WedBuild, the amounts paid and the renewal schedule (Stripe keeps your card on file so the domain can renew automatically)

Stripe's handling of your payment information is governed by the Stripe Privacy Policy.

2.9 Information Collected Automatically

When you use the Service, we automatically collect:

• Device and browser information: browser type, operating system, device type, screen resolution
• Usage data: pages visited, features used, actions taken within the app, timestamps
• IP address
• Referrer URL (the page that linked you to our Service)
• Sign-up attribution: the page you first landed on, the site that referred you, and any campaign tags or ad click identifiers in the link, which we store with your account when you sign up
• Cookies and local storage data (see Section 7)

2.10 Information from RSVP and Public Pages

When guests interact with your published wedding website, RSVP forms, "Find My Seat" pages, contact details forms, or guest self-entry forms, we collect:

• Names, email addresses, phone numbers, and addresses submitted
• RSVP responses and custom question answers
• Session data including IP address, user agent, referrer, and form progress
• For website visit statistics: device type, browser, referring page, and a visitor identifier made from a keyed hash of the visitor's IP address and browser (the IP address itself is not stored with the visit)
• Photos guests choose to upload to the couple's website photo wall (if the couple has turned it on), with the first name a guest chooses to add. Photos are re-encoded on upload, which removes location and camera details

When a guest submits an RSVP, we also set a cookie on their device (wb_rsvp_guest) that remembers their name and a reference to their guest record for that wedding. This lets them use the "Find My Seat" feature without re-entering their name. The cookie expires after 180 days and can be cleared at any time through their browser settings.

2.11 AI Assistant Interactions

When you use our AI assistant features, we collect:

• Messages and questions you send to the assistant
• Wedding context data sent to generate responses (e.g., guest counts, event details, budget data)
• Invoice files you ask us to read, and the website addresses of vendors you ask us to import

2.12 Domain Registration Information

If you buy a domain through WedBuild, we collect the domain owner's name, email address, phone number and postal address and send them to our domain registrar, Openprovider, so the domain can be registered in the owner's name. Domain registries and ICANN rules require these details. Openprovider emails the owner to confirm their email address. Once the registrar holds the owner's details, we delete our own copy of the address and phone number and keep the owner's name and email address with the registration record (see Section 6).

We do not turn on the registrar's WHOIS privacy service. Depending on the rules of the registry for the domain ending you choose, some of the owner's details may appear in public domain registration (WHOIS/RDAP) records.

3. How We Use Your Information

We use the information we collect for the following purposes:

3.1 Providing and Operating the Service

• Creating and managing your account
• Delivering wedding planning features (guest management, seating charts, budget planning, checklists, website builder, announcements, email campaigns, RSVP, vendor comparison)
• Connecting custom domains to wedding websites, and registering and renewing domains you buy through WedBuild
• Processing payments and managing subscriptions
• Sending transactional emails (account confirmations, password resets, RSVP notifications)
• Enabling AI-powered assistance and recommendations

3.2 Improving the Service

• Understanding how users interact with features to improve functionality
• Analysing usage patterns and trends
• Conducting product analytics and research
• Testing new features

3.3 Communication

• Responding to support requests and enquiries
• Sending service updates and important notices
• Sending optional product tips and feature announcements (you can unsubscribe at any time)
• Inviting couples, once and about a month after their wedding, to share their story for our Wedding Diaries (you can unsubscribe at any time). If you choose to take part, we use what you send us, including any photos you choose to share, to write a story for publication on our website

3.4 Security and Integrity

• Detecting and preventing fraud, abuse, and security incidents
• Monitoring for errors and performance issues
• Enforcing our Terms of Service

3.5 Legal Compliance

• Complying with applicable laws, regulations, and legal processes
• Responding to lawful requests from authorities

4. How We Share Your Information

We do not sell, rent, or trade your personal information for money. The Meta Pixel on our marketing site (wedbuild.com), and the sign-up and purchase events our servers send to Meta when your app cookie choice allows Marketing, share limited browsing, event and identifier data with Meta to measure and improve our advertising. Under the CCPA/CPRA and similar laws this may count as "sharing" for cross-context behavioural advertising. Where prior consent is required (the EU/EEA and UK) the Pixel loads only after you opt in; elsewhere it runs by default and you can opt out (see Sections 7.4, 7.7 and 9.4). The WedBuild app, including the pages your guests use, does not load the Meta Pixel. We otherwise share your information only in the following circumstances:

4.1 Service Providers

We use trusted third-party service providers who process data on our behalf to operate the Service:

We use a small number of third-party service providers to operate the Service. Each provider processes your data under their own data processing terms, which require them to safeguard it and limit how it can be used.

4.2 Public Features

When you publish a wedding website or enable public features (RSVP forms, "Find My Seat," guest self-entry), the content you publish becomes accessible to anyone who has the link. This may include:

• Wedding details, event information, and images on your website
• Guest names and seating assignments (via "Find My Seat")
• Photos guests share on your website's photo wall, once you approve them (or straight away, if you turn on automatic approval)
• Website visit statistics

You control what is published and can unpublish at any time. We do not submit your wedding website to search engines, but we cannot guarantee it will not be indexed by third parties.

4.3 Legal Requirements

We may disclose your information if required by law, regulation, legal process, or enforceable government request, or to protect the rights, property, or safety of WedBuild, our users, or the public.

4.4 Business Transfers

If WedBuild is involved in a merger, acquisition, reorganisation, or sale of assets, your information may be transferred as part of that transaction. We will notify you via email or prominent notice on the Service before your information becomes subject to a different privacy policy.

4.5 With Your Consent

We may share your information in other circumstances where you have given us explicit consent.

5. International Data Transfers

WedBuild is based in Australia. Our main database, file storage and application servers are located in Singapore. Many of our other service providers are located in the United States, and our domain registrar is located in the Netherlands (see Section 4.1). By using WedBuild, your personal information may be transferred to, stored, and processed in countries outside your country of residence, including Singapore, Australia, the United States and the Netherlands.

We take steps to ensure that international transfers of personal information are subject to appropriate safeguards, including:

• Standard contractual clauses (for transfers from the EU/UK)
• Data processing agreements with all service providers
• Ensuring providers maintain appropriate security certifications and practices

For Australian users, we take reasonable steps to ensure that overseas recipients handle your personal information in accordance with the Australian Privacy Principles.

6. Data Retention

We retain your personal information for as long as your account is active or as needed to provide the Service. Specifically:

• Account data (active subscription): Retained while your account has an active subscription (one-time or monthly).
• Account data (Essentials plan): The free Essentials plan does not expire. Your data is retained while your account exists.
• Account data (expired subscription): When your subscription expires and you do not have an active monthly plan, your account enters a read-only state. Your data is retained for up to 12 months after your subscription expires. During this period, you can log in and view your data, and you can restore full access at any time by subscribing to a monthly plan. If you do not resubscribe within 12 months, your account and all associated data will be permanently deleted.
• Wedding and guest data: Retained while your account exists (including the 12-month retention period after subscription expiry). Deleted upon account deletion, subject to backup retention periods.
• Payment records: Retained for 7 years after the transaction to comply with Australian tax law and financial record-keeping requirements.
• Analytics and usage data: When you delete your account, we ask PostHog to delete your analytics profile and the events and session recordings linked to it. What remains is aggregated or anonymised and not linked back to you.
• Server logs: Retained for up to 90 days for security and debugging purposes.
• Email delivery records: Retained for up to 12 months after sending for delivery tracking and troubleshooting.
• RSVP session and website visit details: The IP address, browser and referrer details recorded with RSVP sessions, and the visitor identifier, browser and referrer recorded with website visits, are anonymised after 24 months.
• Domain registration records: If you buy a domain through WedBuild, we keep the registration record (the domain, the owner's name and email address, and its payment history) after your account is deleted, because our registrar's terms require us to keep the registration agreement for two years after the registration ends.

6.1 What Happens When Your Subscription Expires

When your paid subscription expires and no monthly plan is active:

1. Your account enters read-only mode: you can log in and view all your data but cannot make changes.
2. Your wedding website is unpublished (taken offline).
3. Your RSVP forms are closed (guests can no longer submit responses).
4. A 12-month countdown begins. If you do not resubscribe within this period, your account and all data will be permanently deleted.
5. You will receive email notifications at key intervals (30 days before expiry, 7 days before expiry, at expiry, and periodic reminders during the retention period) informing you of your account status and how to resubscribe.

6.2 Resubscription

You may restore full access at any time during the 12-month retention period by subscribing to a monthly plan. Upon resubscription:

• Your account is immediately restored to full access.
• The 12-month deletion countdown is cancelled and reset.
• Your wedding website and RSVP forms can be manually republished and reopened.

You may request deletion of your data at any time (see Section 9).

7. Cookies and Tracking Technologies

7.1 What We Use

7.2 Essential Technologies

Some cookies and local storage are strictly necessary for the Service to function (e.g., the cookies that keep you signed in). These cannot be disabled without breaking core functionality.

7.3 Analytics and Performance

We use PostHog (and, on the marketing site, Google Analytics and Vercel Analytics) for product analytics, including page views, feature usage events, and session recordings (in production only). PostHog data helps us understand how users interact with the Service so we can improve it. Session recordings mask what you type into fields, so they do not capture passwords or payment details, but they can show other text on the screen, such as names. On the marketing site these analytics are region-aware: in the EU/EEA and UK they load only after you opt in; elsewhere (such as Australia and the US) they run by default and you can opt out at any time via the cookie banner. In the app, visitors in the EU/EEA, the UK and Switzerland are asked first; elsewhere these analytics run by default (see Section 7.7 for how to opt out).

Our marketing site's servers also count page views and QR code scans without using cookies or storing anything on your device. Each count is sent to PostHog with an identifier made from a salted hash of your IP address and browser, which changes every day.

When you use the WedBuild app while signed in to your account, we record how you use it (the pages you visit, the features you use, what you click and any errors you meet) and link it to your account (your account ID and email address). We do this to provide, secure, support and improve the Service, and it is part of the Service under section 12 of our Terms of Service. Outside the EU/EEA, the UK and Switzerland it continues even if you have declined analytics cookies: in that case PostHog stores no cookies or local storage on your device and never records your screen. In the EU/EEA, the UK and Switzerland it happens only if you opt in. People who are not signed in, including wedding guests using the app's RSVP and Find My Seat pages, are recorded only if their cookie choice allows it; outside the EU/EEA, the UK and Switzerland, that is the default. Our Cookie Policy explains exactly what your cookie choice controls.

Separately, our servers record key account events (such as signing up, completing onboarding, confirming your email, starting, renewing or cancelling a plan, and buying an AI credit pack or a domain) in PostHog against your account ID and email address, together with the wedding details you give during onboarding (such as your first names, wedding date, expected guest numbers and city), so we can operate and measure the Service. When you use an AI feature, we also send PostHog a record of the request (such as the model used, its cost and timing) with a copy of your message in which email addresses, phone numbers, amounts, links and guest names are replaced with placeholders, shortened to 500 characters. The AI's reply is not sent.

We use Sentry for error monitoring and performance tracking. Sentry captures error data, browser information, and page context when errors occur. For signed-in users, error reports also include your account ID and email address so we can identify and assist affected accounts. Sentry also keeps a replay of a sample of app sessions (about one in ten, plus sessions in which an error occurs) with all text masked and all images and media blocked. Replays are not recorded on guest-facing pages.

7.4 Advertising (Meta)

We use the Meta (Facebook) Pixel on our marketing site (wedbuild.com) only, to measure the performance of our advertising, build audiences, and show relevant ads on Meta platforms. The WedBuild app (app.wedbuild.com) does not load it, and neither do the pages your guests use (RSVP forms, Find My Seat, published wedding websites). It is region-aware and a separate choice from analytics: in the EU/EEA and UK the Pixel loads only after you opt in to Marketing; elsewhere (such as Australia and the US) it runs by default. You can opt out at any time by choosing Reject or turning off Marketing in our cookie banner, after which it stops sending data to Meta. It records page views and standard events (such as PageView, Lead and InitiateCheckout) along with device/browser data and Meta cookie identifiers.

When you sign up or make a purchase in the app, our servers may send that event directly to Meta (through Meta's Conversions API) with a hashed copy of your email address, your account ID, and your IP address and browser details. We do this only when your saved cookie choice in the app allows Marketing, and never for your guests.

See our Cookie Policy for details.

7.5 Email Tracking

When you send announcements or email campaigns through WedBuild, we embed tracking pixels and link wrappers to provide open and click analytics, and our email provider, Resend, also reports delivery, open and click events to us. This tracking applies to emails you send to your guests, not to emails we send to you.

7.6 Functional Cookies

Some cookies are not strictly essential but improve convenience. The RSVP guest cookie (wb_rsvp_guest) is set when a guest submits an RSVP and lets them use the "Find My Seat" feature without re-entering their name. It expires automatically after 180 days. Guests can clear it at any time through their browser's cookie settings without affecting their RSVP itself.

7.7 Managing Cookies

On our marketing site you can change or withdraw your analytics and marketing choices at any time via the Your Privacy Choices link in the footer, which re-opens the consent banner with your current settings; we also honour the Global Privacy Control (GPC) signal there as an opt-out of advertising. In the WedBuild app, visitors in the EU/EEA, the UK and Switzerland make these choices in the app's cookie banner. Elsewhere the app does not show a banner and applies the default for your region; a Reject choice you made on our marketing site is carried into the app when you follow a link from wedbuild.com, and you can also contact privacy@wedbuild.com to opt out. You can additionally control cookies through your browser settings. Disabling cookies may affect the functionality of the Service. For more information on managing cookies, visit www.allaboutcookies.org.

8. Data Security

We take the security of your personal information seriously and implement reasonable technical and organisational measures to protect it, including:

• Encryption in transit: All data transmitted between your browser and our servers is encrypted using TLS/HTTPS.
• Encryption at rest: Data stored in our database and file storage is encrypted at rest.
• Authentication security: Passwords are cryptographically hashed. We support Google OAuth for secure sign-in. Sessions are held in secure, httpOnly cookies and are automatically refreshed and expired. Sign-in, sign-up and password reset are rate-limited, and an email address must be confirmed before its account can be used.
• Access controls: Server-side authentication and authorisation on all API endpoints. Row-level security policies on database tables.
• Infrastructure security: Hosted on managed platforms (Railway, Supabase) with automatic security updates, backups, and access controls.
• Payment security: Payment processing is handled entirely by Stripe, a PCI DSS Level 1 certified provider. We never store full payment card details.
• Rate limiting: API rate limits protect against abuse and brute-force attacks.
• Error monitoring: Real-time error and security monitoring via Sentry.

No method of transmission or storage is 100% secure. While we strive to protect your information, we cannot guarantee absolute security. If you become aware of a security vulnerability, please contact us immediately at privacy@wedbuild.com.

9. Your Privacy Rights

Depending on your location, you have certain rights regarding your personal information. We honour these rights for all users regardless of location, to the maximum extent practicable.

9.1 All Users

• Access: Request a copy of the personal information we hold about you.
• Correction: Request correction of inaccurate or incomplete personal information.
• Deletion: Delete your account yourself at any time from your account settings, which deletes it straight away (including the files you uploaded and any guest photos, and cancels any monthly plan), or ask us to delete your personal information and account, in which case we will delete your data within 30 days. Both are subject to the exceptions described in Section 6 and to retention required by law.
• Data export: Download your data at any time from your account settings, as a ZIP file of structured, machine-readable JSON files (uploaded files such as images and attachments are listed with download links rather than included).
• Withdraw consent: Where processing is based on consent, withdraw your consent at any time.
• Complaint: Lodge a complaint with us or with the relevant supervisory authority.

9.2 Australian Users (Privacy Act 1988)

Under the Australian Privacy Principles, you have the right to:

• Access your personal information held by us (APP 12)
• Request correction of your personal information (APP 13)
• Complain about a breach of the APPs

If you are unsatisfied with our response to a complaint, you may lodge a complaint with the Office of the Australian Information Commissioner (OAIC).

9.3 European Users (GDPR / UK GDPR)

If you are in the European Economic Area (EEA) or United Kingdom, you have additional rights under the GDPR:

• Legal basis for processing: We process your data on the following legal bases:
  • Contract: Processing necessary to provide the Service you requested (Article 6(1)(b))
  • Legitimate interests: Analytics, security, and service improvement (Article 6(1)(f))
  • Consent: Marketing communications and optional analytics (Article 6(1)(a))
  • Legal obligation: Tax and financial record-keeping (Article 6(1)(c))
• Right to restriction: Request restriction of processing in certain circumstances.
• Right to portability: Receive your data in a portable format and transmit it to another provider.
• Right to object: Object to processing based on legitimate interests, including profiling.
• Right to erasure: Request deletion of your data ("right to be forgotten").
• Automated decision-making: Our AI assistant features use automated processing to generate wedding planning suggestions (see Section 11.1). These outputs are advisory only and do not produce legal effects or similarly significant effects concerning you. You have the right to request human review of any AI-generated advice by contacting privacy@wedbuild.com.

To exercise these rights, contact us at privacy@wedbuild.com. We will respond within 30 days (or within the time required by applicable law). You may also lodge a complaint with your local data protection authority.

9.4 California Users (CCPA / CPRA)

If you are a California resident, you have the following rights:

• Right to know: Request disclosure of the categories and specific pieces of personal information we have collected, the sources, the purposes, and the third parties with whom we share it.
• Right to delete: Request deletion of your personal information.
• Right to correct: Request correction of inaccurate personal information.
• Right to opt-out of sale or sharing: We do not sell your personal information for money. However, the Meta Pixel on our marketing site, and the sign-up and purchase events our servers send to Meta when your app cookie choice allows Marketing, "share" limited personal information (online identifiers, a hashed email address, and browsing/activity data) with Meta for cross-context behavioural advertising (see Section 7.4). The Pixel runs on the marketing site by default. On our marketing site you can opt out at any time via the Your Privacy Choices link in our footer (which re-opens the cookie banner) or by choosing Reject/turning off Marketing, and we honour the Global Privacy Control (GPC) browser signal there as an opt-out. For the app, see Section 7.7, or contact privacy@wedbuild.com. We honour these choices.
• Right to non-discrimination: We will not discriminate against you for exercising your privacy rights.

To exercise these rights, contact us at privacy@wedbuild.com.

10. Guest Data & Your Responsibilities

When you collect information about your wedding guests through WedBuild (via guest lists, RSVP forms, contact detail forms, guest self-entry, or your website's photo wall), please be aware:

• You are the data controller (or equivalent under applicable law) for guest information you collect. WedBuild acts as a data processor on your behalf.
• You are responsible for ensuring you have an appropriate legal basis to collect and process your guests' personal information.
• You should inform your guests that their information is being collected and processed through WedBuild.
• You should use guest data only for wedding-related purposes and not for spam, unsolicited marketing, or other inappropriate uses.
• If a guest contacts us to request access to, correction of, or deletion of their information, we will direct them to you as the account holder. We may also action the request directly where required by law.

11. AI Features and Automated Decision-Making

WedBuild offers AI-powered features: AI Help (a help assistant available on every plan), the AI Wedding Assistant (Pro plan), and two Pro tools that read a document for you: reading an invoice you upload to fill in its details, and importing a vendor's details from their website. These features are powered by Anthropic's Claude models. When you use them:

• Your messages and relevant wedding context (such as guest counts, event details, and budget information) are sent to Anthropic for processing.
• If you ask WedBuild to read an invoice, the file you uploaded (a photo or PDF) is sent to Anthropic so its details (such as the vendor, amounts and dates) can be filled in for you to review. Nothing is saved until you choose to save it. If you import a vendor from their website, the text of that website's pages is sent to Anthropic.
• Anthropic processes this data to generate responses. Anthropic's handling of data is governed by the Anthropic Privacy Policy and its commercial terms. Under those terms, data sent through Anthropic's API is not used to train its models.
• We implement rate limits (50 requests per hour, 200 per day) to prevent misuse.
• AI features are optional. You are not required to use them.

11.1 Automated Decision-Making Disclosure

In accordance with the Privacy Act 2024 amendments, the GDPR (Article 22), and other applicable laws, we disclose the following about our use of automated decision-making:

Kinds of decisions made by automated means:

• The AI wedding planning assistant generates personalised suggestions and advice about your wedding, including seating arrangement recommendations, budget guidance, guest list insights, vendor comparisons, timeline suggestions, and general wedding planning advice.
• The AI help assistant answers questions about how to use WedBuild's features.
• Intent classification determines which subset of your wedding data is relevant to your question, so only pertinent context is sent to the AI model.
• Invoice reading suggests an invoice's details (and which of your budget categories it belongs to) for you to check, and vendor import suggests a vendor's details from their website. You review and edit these before anything is saved.

Kinds of personal information used:

• Your messages: The questions and instructions you type into the AI chat.
• Wedding context (full assistant only): Depending on your question, the system may send a relevant subset of your wedding data to Anthropic, such as event details (dates, venue names, addresses), guest names, RSVP statuses, dietary requirements, seating assignments, budget figures, vendor names, quotes, and ratings.
• Privacy protections applied before processing: Guest contact details (email addresses, phone numbers, and postal addresses) are automatically stripped from the wedding data we send to Anthropic. The AI is also instructed never to reveal, request, or reference guest contact details. In help mode, no guest-level or other detailed wedding data is sent: only your plan and, where relevant to your question, a one-line summary of totals (such as your guest and RSVP counts, or your overall budget and spending).

Nature of the decisions:

• All AI-generated outputs are advisory only. The AI provides suggestions and information; it does not take any action on your behalf, modify your data, make purchases, send communications, or produce any legally binding decisions.
• All decisions about whether to act on the AI's suggestions remain entirely with you.
• There is no profiling: the AI does not build profiles about you, score you, or make eligibility determinations.

12. Children's Privacy

WedBuild is not directed at children under 16 years of age. We do not knowingly collect personal information from children under 16. If your guest list includes minors, you as the account holder are responsible for their data.

If we become aware that we have collected personal information from a child under 16 without parental consent, we will take steps to delete that information promptly. If you believe a child has provided us with personal information, please contact us at privacy@wedbuild.com.

13. Third-Party Links and Integrations

The Service may contain links to third-party websites or integrate with third-party services (e.g., Google Maps, Stripe, Spotify or Apple Music embeds on wedding websites). These third parties have their own privacy policies, and we are not responsible for their practices. We encourage you to review their privacy policies before providing them with your information.

14. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices, technology, or legal requirements. When we make material changes, we will:

• Update the "Last updated" date at the top of this page
• Notify you by email or by prominent notice within the Service

Your continued use of the Service after the effective date of any changes constitutes your acceptance of the updated Privacy Policy.

15. Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us:

Email: privacy@wedbuild.com Website: https://wedbuild.com

WedBuild Pty Ltd Australia

For privacy complaints, we will acknowledge receipt within 5 business days and aim to resolve your complaint within 30 days. If you are not satisfied with our response, you may escalate your complaint to the relevant authority:

• Australia: Office of the Australian Information Commissioner (OAIC) (phone 1300 363 992)
• European Union: Your local Data Protection Authority
• United Kingdom: Information Commissioner's Office (ICO)
• California: California Attorney General