Privacy policy

The short version

• Apptractive Pty Ltd runs yourwedding.app. We do not sell personal information.
• We use guest information to provide the couple's wedding service, not to build our own marketing lists. Wedding sites and guest emails have no advertising from us.
• We may promote our services to customers and offer clearly identified affiliate links, subject to the choices and safeguards below.
• Wedding data is stored in Sydney. Some providers process information overseas, including in the United States.
• You can ask to access, correct or delete your information. Some payment, security and other records remain after a wedding is deleted.
• Contact hello@yourwedding.app.

Who we are and what this covers

yourwedding.app is operated by Apptractive Pty Ltd (ABN 37 627 379 800), Australia. This policy covers couples and account members, wedding guests, website visitors and people who contact us.

Couples decide which guests to add, what to ask and whom to share exports with. They must have authority to provide guest information and obtain consent where required. Guests can contact us directly about their information.

Information we collect and use

We collect information directly from you, from the couple and other authorised members, and from your use of the service:

• Accounts and weddings: sign-in and contact details, wedding details and pages, domain names, plan, payment records, preferences, last sign-in and actions in the account. Stripe handles card payments; we do not receive full card numbers.
• Guests and replies: names, households, contact details supplied by the couple, attendance, dietary needs, answers, notes, song requests, transport and accommodation choices. The reply form does not ask guests for a mobile number.
• Photos and videos: Photos and videos they share, who shared them, file information and any metadata present in the uploaded original.
• Communications: messages, delivery and bounce results, consent and unsubscribe records, sending-authorisation records, support enquiries and any marketing choices you give us.
• Support requests from the studio: your message, its subject and topic, and the email you sign in with, so we can reply. Unless you untick it, the form also sends the technical details it lists before you send: the app version, the page you came from, your browser and device settings, your account and wedding identifiers, the wedding's plan and status, counts of guests and replies (not who they are), and the type, place and time of recent errors. It sends no guest names, contact details or answers. Screenshots reach us only if you email them.
• Service and security activity: when a guest opens their personal link, account activity, device and network information needed to deliver or protect the service, and consented website analytics.

We use this information to operate accounts and wedding sites, manage invitations and replies, provide media sharing and messaging, take payments, support customers, protect the service, resolve complaints and meet legal obligations. Customer marketing is described separately below. We do not use wedding guest lists or sensitive guest information for our own marketing.

Dietary needs and children

Dietary information may reveal health conditions or religious beliefs. We collect it with consent so the couple and people helping with their wedding can arrange meals. The reply form requires consent to share dietary needs with the couple, their helpers, caterer and any AI assistant they connect. A couple recording dietary information for someone else must confirm that person agreed.

Members receive reply emails by default, including dietary notes, and can turn them off. A connected AI assistant can read dietary notes and may process them overseas. Please avoid unnecessary sensitive information in notes or custom questions.

Account holders must be adults. A parent or guardian replies for children through the household's link. Couples must not add email addresses or mobile numbers for guests under 16. Parents or guardians can ask us to correct or delete a child's information.

Customer marketing and affiliate links

We may use a customer's contact details, plan and activity in their own account to offer our services, onboarding tips, discounts or upgrades, including messages triggered by account activity. We send promotional email or text only with valid consent or another lawful basis permitted by the applicable messaging laws. Creating an account or accepting this policy does not, by itself, give marketing consent.

Every marketing message will identify us and provide a simple unsubscribe option. You can also email us to stop marketing. We honour unsubscribe requests within five working days. Necessary account, security, payment and wedding-service messages may continue; we do not use those messages to bypass your marketing choice.

We may include affiliate or sponsored recommendations on our marketing website, in customer-facing areas or in permitted customer marketing. We identify the commercial relationship near the recommendation or link. If you follow an affiliate link and buy or sign up, we may earn a commission. The provider or affiliate network may receive your referral, device and transaction information and use cookies under its own privacy policy. We do not supply your wedding guest list to affiliate partners. We will explain any additional tracking or sharing before introducing it and obtain consent where required.

Being listed as a wedding guest does not subscribe someone to our marketing. A guest who separately signs up for our services or marketing has the same choices as other customers.

Cookies and website analytics

We use browser storage for sign-in, guest access, preferences and pending uploads. The studio also uses a cookie to recognise the couple when they visit their own wedding site.

Our marketing website loads Google Analytics only after you accept analytics cookies. Use Cookie settings in its footer to change your choice. Guest sites and the studio do not currently use advertising trackers or third-party analytics. External maps, calendars and other linked services handle information under their own policies when you use them. We do not put tracking pixels in guest emails.

Who can access information

• The couple and their account members can see wedding details, guests, replies and dietary information. A nominated coordinator can access the messaging inbox.
• People the couple shares information with, such as a caterer, photographer or connected AI assistant, receive it at the couple's direction. Copies in recipients' inboxes or exported files are outside our control.
• Authorised personnel and service providers access information as needed for hosting, payments, communications, support, security and other disclosed purposes.
• We may disclose information where required or authorised by law, to handle a legal claim, or in a business transfer with appropriate safeguards. We will notify customers of a transfer affecting their information.

Public wedding pages can be viewed by anyone with their address. Personal replies and contact details require the relevant guest link or account access. Wedding sites tell search engines not to index them; this is not a guarantee that an address cannot be found or shared.

Photos and videos

• Guests of the wedding can see shared guest photos and videos, with the sharer's first name and last initial. The couple can hide them.
• Videos are shared as uploaded and can contain location metadata.
• A guest's browser removes its location from the copy other guests see when supported. Older browsers may not remove it.
• The couple receives every original as it was uploaded, including any location.
• The couple can share their own photos and allow a smaller or full-size copy to be saved. Full-size originals can contain location metadata.
• The couple can share some photos only with the guests they choose.
• Sharing to social media, where enabled by the couple, creates copies outside our control.

Providers and overseas processing

We store wedding and guest records with Amazon Web Services in Sydney and send service emails through Amazon in Sydney. Delivery networks and the following providers may process information outside Australia:

Provider or service	Information and location
AWS, including CloudFront and certificate services	Hosting, page delivery, domain/certificate and network information. Sydney storage, worldwide delivery locations and some US processing.
Mobile Message	Recipient and sender numbers, messages and delivery information, including any invitation link. Its Trust Centre describes Sydney storage and Australian delivery; its privacy policy also permits overseas processing, including OpenAI in the US for safety and support. Not all processing is confined to Australia.
Sentry	Error monitoring in the US: technical errors, software versions and internal identifiers. Reports are configured to remove names, contact and payment details, invitation codes, message contents and form answers. Session recording is disabled. Your internet address passes through Sentry when your browser sends a report.
Stripe	Customer payment, billing and transaction information; US and other processing locations. We do not send wedding guest lists to Stripe.
Google	Consented marketing-site analytics, studio map/address searches and our support mailbox; including US processing. We do not supply guest lists to Maps or Analytics.
Cloudflare	Domain-name services and routing support emails to our mailbox; US and worldwide processing.
Apple, Google or Mozilla push services	Device subscriptions and generic inbox alerts if you enable browser notifications; may involve overseas processing. We exclude guest message content and mobile numbers from push alerts.
AI providers, including Anthropic and OpenAI	Information made available to an assistant you connect, as described below; including US processing. Anthropic may also help create requested illustrations from place descriptions, without guest details.

These services have their own privacy and processing terms. Overseas privacy laws may differ from Australian law. We select providers and limit the information we send for the relevant purpose. Affiliate destinations, if you choose to visit them, handle information as explained beside the link and under their own policies.

AI assistants

On Pro, a couple can connect their own assistant with read-only or read-and-write permission. It can read wedding pages, guest names, replies and dietary notes. It cannot read stored guest email addresses or mobile numbers, but information you type into your assistant passes through its provider. Write access also allows supported guest, reply and page changes; it cannot send invitations, make payments or delete the wedding. Dietary changes require confirmation of the guest's consent.

The studio identifies the provider and access before connection. Information may be stored in the US, and the customer's agreement and settings with that provider govern its use. The couple can disconnect the assistant; we retain its activity log for 90 days.

We do not directly send guest information to AI for our own processing or training. Mobile Message's separate safety/support processing described above may occur without a connected assistant.

Emails, texts and automated actions

We send wedding invitations and updates at the couple's request, reply confirmations, and reply notifications according to members' preferences. Photo emails invite attending guests to share photos or view the couple's photos; the couple can turn them off or choose recipients. Guest emails identify the couple and our service and include relevant stop-email links. We also send necessary sign-in, payment and deletion messages to customers.

Wedding texts use a shared Australian number. Replies appear in the private wedding inbox. A STOP request prevents all weddings using that number from texting the recipient. Deletion cannot remove messages already on someone's phone.

Some actions happen automatically using account, wedding, delivery or report information: retention reminders and deletion, message suppression, hiding reported photos, and changes to access after a plan refund. They do not decide a customer's statutory refund claim. Contact us if you believe an action is wrong or need a review.

Retention and deletion

• Wedding and guest data, including guests' photos and videos: the couple chooses 3–24 months after the wedding, with 24 months as the default. The wedding is hidden first and deletion follows seven days later. Missed reminders extend the schedule and processing retries may delay completion. Unused free weddings follow a six-month inactivity schedule. Nothing is deleted sooner than 60 days after creation. Hidden weddings can be restored before hard deletion starts.
• Accounts and acceptance records: kept until account deletion, subject to the separate payment and safety records below. We retain the version and time of each terms acceptance.
• SMS contact and safety records: minimal authoriser contact details remain for 30 days after their latest send, including after account/wedding deletion. Routing markers remain for 90 days after wedding deletion; STOP suppression records remain while we send texts. Unmatched replies are held for up to seven days and failed text events for up to 14 days, including message content and recipient numbers where needed to investigate delivery, even after wedding deletion. Expired sender contacts are excluded from support lookups while physical cleanup completes.
• Operational records: AI activity logs for 90 days, system logs for 30 days and reply-change fingerprints for seven days. Backups can retain wedding data for up to 35 days after deletion.
• Payment and refund records: retained for accounting, fraud prevention and disputes, including applicable seven-year recordkeeping requirements. They have no automatic deletion date and survive wedding/account deletion. They include purchase identifiers, unused paid value where recorded, approved refunds and payment/dispute evidence, not guest messages or media.
• Support and marketing records: support correspondence, including requests from the studio's contact form, is kept in our support mailbox while resolving the request and longer where needed for legal obligations or a dispute. Where you give marketing choices, we retain the consent and suppression evidence needed to honour them. We do not use a suppression record to restart marketing. A count of each member's support requests that day is kept for two days to limit sending.

Providers retain their own records under their policies. Deletion does not erase recipient downloads, emails, texts or social media copies. Backups support service recovery, not a promise to restore an individually deleted wedding.

Security and incidents

We use encryption, access controls and other measures to protect information. No system is perfectly secure. We investigate incidents and notify affected people and authorities where required by law.

Access, correction, deletion and complaints

Couples can edit and export guest data and download available media in the studio, including through Export your data without accepting changed terms. Guests can update their replies through their personal link. Anyone can request access, correction or deletion by emailing hello@yourwedding.app. We may verify your identity and explain any lawful reason information must be retained. We aim to respond within 30 days.

For a privacy complaint, use the same email address. We will investigate and respond within a reasonable time, aiming for 30 days. If you are dissatisfied, contact the Office of the Australian Information Commissioner or call 1300 363 992 for guidance about its jurisdiction and complaint process.

Changes and contact

We update this policy when our practices change and notify customers of material changes. A policy update does not override an existing marketing opt-out or create consent for a new use. Earlier versions remain in our records.

Apptractive Pty Ltd 79 O'Donnell Street, North Bondi NSW 2026, Australia hello@yourwedding.app