1. Introduction
EventSync ("we," "our," or "us") is dedicated to protecting your privacy. This Privacy Policy explains how we collect, use, and share your personal information when you use our website, EventSync Workspace and mobile applications ("Services"). EventSync is a wedding planning and day-of coordination tool that helps couples, planners, and wedding teams manage event timelines, guests, vendors, budgets, team communication, and live day-of recovery.
2. Information We Collect
We collect the following types of information:
- Account Information: Name, email address, and profile photo when you sign in via Apple, Google, or other providers.
- Event Data: Wedding timelines, vendor details, guest lists, budgets, checklists, seating charts, meal preferences, and related notes you create.
- Guest Information: Names, email addresses, phone numbers, RSVP status, dietary restrictions, and meal preferences for wedding guests. This may be entered manually, imported from device contacts (with your permission), or imported via CSV files from other planning platforms.
- Couple Photos: Photos uploaded for wedding cards and invitations, stored securely in Firebase Storage.
- Usage Data: Aggregate usage metrics (screen views, feature taps, session length) sent to Firebase Analytics. Crash logs and stack traces sent to Firebase Crashlytics.
- Device Information: Device model, operating system version, app version, and a Firebase Installation ID. We also store an FCM push notification token per device so we can deliver notifications.
3. How We Use Your Information
We use your information to:
- Provide, maintain, and improve the Service.
- Sync your event data across devices in real-time.
- Facilitate collaboration between you and your wedding team (vendors, bridal party, etc.).
- Send push notifications about schedule changes and team updates.
- Respond to customer support requests.
4. Data Sharing
We do not sell your personal data. We share data only in the following circumstances:
- With Your Team: Event details are shared with other users you explicitly invite to your event.
- Service Providers: We use trusted third-party services (e.g., Firebase by Google, RevenueCat) to host data, facilitate authentication, and manage subscriptions.
- Legal Compliance: We may disclose information if required by law or subpoena.
5. Third-Party Services
EventSync uses the following third-party services. Each is listed with the specific Firebase or vendor product where applicable.
- Firebase Authentication (Google): Sign-in, account linking, and user identity.
- Cloud Firestore (Google): Real-time database for events, timelines, guest lists, vendors, broadcasts, change requests, and team membership.
- Firebase Cloud Messaging — FCM (Google): Push notifications. We send a push notification for each FCM event we generate, including: 10-minute next-up alerts before each timeline block (block title, start time, and event name), team broadcasts (sender name and message body), vendor late alerts, and recovery plan updates. FCM token IDs are associated with your account so we can deliver notifications to your specific devices.
- Cloud Functions for Firebase (Google): Serverless backend for next-up alerts, broadcasts, vendor late alerts, and timeline recovery announcements. Cloud Functions read your event data (block titles, locations, schedule times) on a schedule to determine which notifications to send.
- Firebase Crashlytics (Google): Crash reporting. Crash logs include stack traces, device model, and OS version. We do not send personally identifying content (event names, guest names, vendor names) to Crashlytics.
- Firebase Analytics (Google): Aggregate usage metrics (screen views, feature taps). Used to improve the product. Usage events can be associated with device or installation identifiers and, when signed in, an account identifier. Workspace Assistant usage events record opening, sending and displaying a reply, and where the Assistant was opened. They exclude question text and wedding details.
- OpenAI: When you submit an Assistant question, the question, conversation context and relevant saved wedding details your account is allowed to access are sent to OpenAI to generate a reply or proposal. Do not submit information you do not have permission to share. Provider processing is also subject to its applicable terms and policies.
- Firebase Storage (Google): Image storage for couple photos and uploaded wedding-card assets.
- RevenueCat: Subscription management and in-app purchase processing. Receives your Apple/Google purchase tokens and a stable user identifier; does not receive event data.
- Sign in with Apple / Google Sign-In: Authentication providers. Apple supports private email relay, which we honor.
- Resend: Email delivery for guest invitations. Guest email addresses are shared with Resend only when you explicitly send an invite, and only for that delivery.
- Foursquare Places: Venue discovery and search. Location queries (city names you type into the venue search) are sent to Foursquare to return nearby venue results. No personal data is shared with Foursquare.
Each of these services has its own privacy policy governing the data they collect.
Wedding Assistant
Assistant conversations require an online request. Replies and proposals can be incomplete or mistaken. Closing the dialog clears its active conversation history in the app; saved proposals and outcomes are separate records and are not erased by closing the dialog. Nothing changes automatically: an eligible owner, planner or team lead must review and explicitly confirm a proposal before it is applied.
Contacts (Optional)
If you choose to use the "Import from Contacts" feature in the Guest List, EventSync will read names, email addresses, and phone numbers from contacts you select. Contact data is read on-device only when you tap a specific contact to import. We do not bulk-upload your contact list, and we do not share contact data with any third party other than the storage and email providers listed above.
Notifications and Background Schedules
When you enable Next-Up Alerts (Settings → Notifications), our Cloud Function checks your active wedding's timeline once every minute and pushes a notification for any block whose start time is within the next 10 minutes. The push payload includes the block title, the event name, and the start time. You can disable Next-Up Alerts at any time from Settings, and you can disable all push notifications via your device's system settings.
6. Data Security
We implement industry-standard security measures to protect your data, including encryption in transit and at rest. However, no method of transmission over the internet is 100% secure.
7. Data Retention
Guest planning data can remain in the current browser or device. Signed-in event data, shared records and saved Assistant proposals or outcomes are stored to support the service. Deleting an event can hide or mark it deleted without immediately erasing every related stored record. Delete Account removes the sign-in account and starts associated-data cleanup; some shared event records or related stored data may remain. Contact support@geteventsync.app for a deletion request or confirmation of what remains.
8. Your Rights
You have the right to:
- Access your personal data stored in the app.
- Request correction of inaccurate data.
- Request deletion of your account and associated data by using the "Delete Account" feature in app settings or by contacting us.
- Opt out of push notifications via your device settings.
9. Children's Privacy
EventSync is not intended for use by children under the age of 13. We do not knowingly collect personal information from children under 13.
10. Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last Updated" date.
11. Contact Us
If you have questions about this Privacy Policy, please contact us at:
Email: support@geteventsync.app