Privacy policy
This policy explains what Vowly collects, why, and what you can do about it. Vowly is operated by Chris Richards (“we”, “us”). Questions go to hello@usevowly.com.
Two kinds of people
Users are the couple and anyone they invite to plan with them (collaborators). Users sign in to the iPhone app.
Guests are not users. The couple enters their guests’ details, and guests reply through a private link from their invitation, without an account.
What we collect and why
We collect only what the app needs to plan a wedding and run the guest pages. Most of it is entered by the couple.
| Category | What | Why |
|---|---|---|
| Account | Name and email from Sign in with Apple (often an Apple private relay address) and your Apple user identifier. | To sign you in and identify your account. |
| Sign-in sessions | Hashed session tokens, their expiry, and the user agent of the device that signed in. | To keep you signed in securely. |
| Wedding details | Partner names, date, time zone, location, currency, total budget, expected acceptance rate, guest page designs. | To plan the wedding and show the guest pages. |
| Events and menus | Event names, times, venue names and addresses, RSVP deadlines, meal options. | Shown to guests on their pages and used to count headcount. |
| Guest details (entered by the couple) | Household name, postal address, email, phone, notes, side, priority and tags. Guest names, whether they’re a child, dietary notes and notes. | To manage the guest list and RSVPs. Dietary notes can reveal health or religious information, so we treat them as sensitive. |
| RSVPs | Each guest’s reply per event, meal choice, and when and how they replied. | To show the couple who’s coming and update the budget. |
| Budget and planning | Budget categories, line items, vendors, amounts, payments and due dates, contributors, scenarios, tasks. | To run the budget and planning tools. Vowly never handles payments to vendors. |
| Collaborators | Each member’s role and access, and the email an invite was sent to. Invite links are stored only as hashes. | To share the wedding with the right level of access. |
| Photos, videos and files | Photos and videos uploaded for guest pages, and guest-list CSV files you import. | To show your guest pages and import your list. |
| Activity log | Who changed what in the wedding, including guest replies made through their link. | So everyone planning can see what changed. |
| Notifications | Your device’s push notification token and your notification settings. | To tell you when guests reply, if you allow notifications. |
| Wedding Pass purchases | Product, transaction ID, price, currency and who bought it. Never your card details. | To unlock the Wedding Pass for everyone on the wedding. |
| App analytics | Names of in-app events, such as “wedding created”, with no guest details. | To understand which features are used. |
| Server logs | Technical records of requests and errors, which can include the page address and IP address. | To keep the service running and secure. Rate limits use IP addresses without storing them. |
| Website analytics | Cookieless page view counts on usevowly.com marketing pages, via Cloudflare Web Analytics. Not on guest pages. | To see which pages are useful. No cookies and no personal profile. |
What we don’t do
- No ads, and we never sell or rent data.
- No tracking across other apps or websites: no advertising identifier (IDFA) and no App Tracking Transparency prompt, because there’s nothing to track.
- Guest pages set no cookies and load no analytics.
- Vowly doesn’t message guests on its own. The only email a guest gets from us is a save the date the couple chooses to send through the app.
Who processes data for us
These companies process data only to provide their service to us:
| Provider | What for |
|---|---|
| Cloudflare | Hosting the app’s server and guest pages, the database (D1), file storage (R2), server logs, app analytics (Analytics Engine) and website analytics. |
| Apple | Sign in with Apple, and App Store payments for the Wedding Pass. |
| RevenueCat | Records of Wedding Pass purchases, so the Pass unlocks on every device. |
| Expo | Delivering push notifications to your iPhone. |
| Resend | Sending email, such as save the dates the couple sends from the app. |
Where data is stored
Our providers run global networks, so your data may be stored or processed outside Australia, including in the United States and wherever Cloudflare places the database. We take reasonable steps under Australian Privacy Principle 8 to make sure overseas providers protect it.
If you’re a guest
The couple added your details to plan their wedding and decides what to keep. To correct or delete your details, ask the couple, or email us and we’ll help.
Your link is private to your household. The couple can replace it or it can expire, and then it shows “This link is no longer active”.
How long we keep data
- Account and wedding data: while your account exists.
- Deleting a wedding in the app removes everything in it from our database straight away.
- Deleting your account removes you, your place on each wedding, and weddings where you’re the only owner. Weddings shared with another owner stay with them. Until deletion is in the app, email us to delete your account.
- Database backups: up to 30 days. Server logs: up to 7 days. Sign-in sessions expire after 30 days.
- Purchase records are kept by Apple and RevenueCat as tax and accounting law requires.
Security
- Sign in with Apple; no passwords to store.
- Short-lived access tokens (15 minutes) and rotating sign-in sessions (30 days).
- Collaborator invite links and sign-in tokens are stored only as hashes. Guest links use long random codes.
- Public RSVP pages are rate limited.
- Guest pages never pass their link to other websites (a strict referrer policy).
Children
Vowly is not directed at children under 16. Guests’ children may appear on a guest list, entered by the couple.
Your choices and rights
You can ask to see, correct or delete your data at any time by emailing hello@usevowly.com. Wherever you live, we’ll respond within 30 days.
Changes and complaints
If we change this policy, we’ll update it here with a new effective date, and tell you in the app if the change is significant.
If you have a concern, email hello@usevowly.com first. If you’re not satisfied with our answer, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au, or your local privacy regulator.