Privacy Policy
Last updated September 28, 2026
1. What we collect
Your account
Your email address and a password, handled by Firebase Authentication (we never see your password). If you sign in with Google, we also receive the name and profile photo on that Google account.
Your events
Everything you enter to plan an event: the event name, date, venue and agenda; guest names and, only if you add them, guests’ emails, phone numbers, notes, meal choices and RSVP status; tables, floor plan layout, seating, keep-together/keep-apart rules, day-of check-ins, and any venue photo or logo you upload.
Collaboration
When you invite a co-planner we store their email address, the invite, and their role (editor or viewer). We also remember which events have been shared with your account and which event you last opened, so it opens where you left off on any device.
Things you send us
- Feedback you submit in the app: your message, its category, the page you were on, your browser’s user-agent string, and your email if you’re signed in or choose to give it.
- Waitlist sign-ups: your email, where on the site you signed up, and your browser’s user-agent string.
- Error reports: when something breaks, the app sends the error message, a technical stack trace and the page address so we can fix it. They’re used only to fix problems, never for marketing.
Google Docs you paste
If you paste a link to a Google Doc to import a guest list, our server downloads the plain-text export of that document (it must be shared as “anyone with the link”), turns it into guests, and does not keep a copy of the document.
2. Who can see what
| Who | What they can see |
|---|---|
| You (the event owner) | Everything in your events. |
| Co-planners you invite | The event they were invited to. Editors can change it; viewers can only look. You can remove them at any time. |
| Day-of helpers (optional link) | Tables, check-ins and walk-ins for that event, while you keep the helper link switched on. |
| Anyone with your guest QR link | Nothing until you publish. After you publish: the event name, date, venue, agenda, theme and logo, and each guest’s name and table, nothing else. Unpublishing removes it. |
| Us | We access event data only to operate the service, fix a problem you report, or when the law requires it. |
3. Where it’s stored and who processes it
- Google Cloud / Firebase (Authentication, Cloud Firestore, Cloud Storage, App Hosting) stores your account and event data and runs the app. Data is encrypted in transit and at rest by Google.
- Stripe will process payments when paid plans launch. We’ll only ever receive a customer ID and subscription status, never your card number. During the public beta, nothing is charged and no payment data is collected.
- Google AI (Gemini) powers an optional planning assistant that is currently switched off. If we switch it on, this page will say so first and the assistant will only receive the event details you ask it about.
We don’t sell or rent personal data, and we don’t share it with advertisers or data brokers.
4. What’s stored in your browser
- Your Firebase sign-in session (IndexedDB), so you stay signed in.
- Your theme choice (light, dark or system) and the event you last opened (local storage).
- On a device used as a guest kiosk: a copy of the published guest lookup for that event, so the kiosk keeps working if the venue Wi-Fi drops.
We don’t use advertising or analytics cookies.
5. Your choices and rights
- Export: Settings → Your data → Download everything gives you all of your events as a JSON file; the Guests page exports a CSV.
- Delete: delete any event from Overview or Settings, or delete your whole account from Settings → Your data. Deletion removes your events, their guests, uploads and invites right away.
- Correct: everything you’ve entered can be edited in the app.
- Guests listed in an event who want their details changed or removed should contact the couple or planner who created it; we’ll help if they can’t.
6. Children
FlowlyPlanner is for adults planning events. Guest lists may include children’s names entered by the event’s planner; we don’t knowingly create accounts for anyone under 16.
7. Changes
If we change how we handle data in a way that matters, we’ll update this page and tell signed-in users in the app before the change takes effect.
8. Contact
Questions or requests: from the foot of any page, or from Settings when you’re signed in. A person reads every request.