Wedding KittyBack home

Privacy policy

Your details are not a wedding favour.

This policy explains how Wedding Kitty handles personal information about couples, guests and visitors. We aim to collect only what we reasonably need to operate and protect the service.

1. Information we collect

Account information

When a couple signs up, we may collect their name, email address, authentication identifiers and account preferences. If Google sign-in is used, Google provides the basic account information authorised during sign-in; we do not receive the Google password.

Registry information

We collect registry URLs, couple names, wedding details, page copy, gift descriptions, goals, categories, images, image credits, product links, design choices, publication status and related settings. Published registry content is public.

Guest and contribution information

When a guest contributes, we may collect their name, email address, contribution amount, selected gift, personal message, anonymity choice, currency, payment status and Stripe transaction references. Couples may also record a manual gift and optionally add the guest's name and email.

Technical information

We and our providers may process IP address, browser and device information, approximate country, region and city, timestamps, referring pages, security events, error logs and cookie or session identifiers. Wedding Kitty's product analytics store a one-way salted hash derived from an IP address rather than the raw address. We do not use registry or contribution data to build advertising profiles.

Product analytics and attribution

If you allow analytics, we collect page visits, button and link interactions, visit duration, scroll depth and first-touch attribution. First touch can include the original landing page, referring page, UTM campaign parameters and advertising click identifiers included in the URL. We connect this history to an account after sign-in so we can understand the journey from first visit to registry creation and contributions. Founder and automated traffic are classified separately from ordinary visitor reporting.

2. How we collect information

We collect information directly from couples and guests, automatically when the service is used, from authentication and payment providers, and from a product page when a couple asks us to import its public metadata. We may receive payment, refund, dispute and connected-account updates from Stripe.

3. Why we use information

We use personal information to:

4. Public registry information

A published registry can be viewed by anyone with its link and may be copied, shared or indexed by search engines. Couple names, wedding details, photos, gift descriptions and messages included on the page should therefore be treated as public. Unpublishing stops the page from being intentionally served as public, but does not remove copies already made by other people or search services.

5. Payments

Stripe collects and processes card and bank information. Wedding Kitty does not receive or store full payment-card numbers or bank credentials. We receive limited transaction information needed to display contribution records and handle payment events, such as Stripe identifiers, amount, currency, payment status, refund amount and dispute status.

Stripe also verifies the recipient and payout account connected to a registry. Wedding Kitty receives payout readiness and limited account-status information, but not the recipient's complete bank or identity credentials. Manual gift entries are records supplied by the couple and do not confirm that Wedding Kitty observed or processed the underlying payment.

6. When we disclose information

We may disclose information:

Core providers currently include Supabase, Vercel, Stripe, Resend, Google for optional authentication, and Unsplash when its image library is used. We do not sell personal information.

7. Overseas processing

Some providers may process or store information outside Australia, including in the United States and other regions where they or their subprocessors operate. Our primary application functions and Supabase database are configured in Sydney, Australia, but provider support, security, email and network systems may still involve overseas access. We take reasonable steps to select reputable providers and configure access appropriately.

8. Cookies and local storage

Wedding Kitty uses cookies and browser storage for sign-in sessions, security and registry editing state. With your permission, we also set a first-party visitor identifier for up to 400 days, preserve first-touch attribution for up to 90 days and keep a per-tab session identifier that rotates after 30 minutes of inactivity. Choosing “Only necessary” prevents browsing analytics identifiers and interaction events from being created. Operational account, registry and payment records are still kept when you use those features. Wedding Kitty does not use third-party advertising cookies or cross-site advertising trackers.

9. Retention

We retain account and registry information while the account is active. After deletion, information may remain for a limited period in backups or where needed for payment reconciliation, fraud prevention, disputes, tax, legal claims or regulatory obligations. Payment and contribution records may need to be kept longer than ordinary page content. We delete or de-identify information when it is no longer reasonably required.

10. Security

We use measures including encrypted HTTPS connections, access controls, authenticated database policies, restricted server credentials, managed infrastructure and payment tokenisation through Stripe. No online service can guarantee absolute security. Please use a unique password, protect access to your email account and contact us promptly if you believe an account has been compromised.

11. Access, correction and deletion

You may request access to or correction of personal information we hold about you, or ask us to delete information that is no longer needed. Couples can update much of their registry content directly. Send requests to hello@weddingkitty.com. We may need to verify identity and may retain information where law or legitimate payment and security needs require it.

12. Email choices

We send operational messages required to run an account or complete a contribution. Couples may control optional contribution alerts and summaries in their settings. A transactional message such as an account-security notice, receipt or requested thank-you may not include an unsubscribe link because it relates directly to the service requested.

13. Children

Wedding Kitty accounts and contributions are intended for adults. We do not knowingly invite children under 16 to create accounts or provide personal information. Contact us if you believe a child has supplied information without appropriate authority.

14. Privacy complaints

Send a complaint to hello@weddingkitty.com with a clear description of the concern. We will acknowledge it and aim to respond within 30 days. If you are not satisfied, you may be able to contact the Office of the Australian Information Commissioner through oaic.gov.au.

15. Changes to this policy

We may update this policy as Wedding Kitty, our providers or applicable law changes. The effective date above will be updated, and we will give reasonable notice of material changes where practicable.