Privacy Policy

Vow Atlas Privacy Policy
Launch-review draft • October 11, 2026 • Not yet effective
Operator: The Vow Atlas, Florida, USA.
Privacy contact: help@thevowatlas.com.

1. Scope
This policy covers Vow Atlas’s app, website, and guest-information forms. It applies to couples, guests, planners, vendors, and wedding staff. It describes enabled services; features under development do not imply that information is already being collected through those features. Vendors and external services may have their own privacy policies.

2. Information we collect
Account information includes names, email addresses, authentication identifiers, account roles, and profile photos. Wedding information may include dates, locations, preferences, budgets, tasks, vendor choices, seating, timelines, and invitations. Guest information may include names, required phone numbers, email or mailing addresses where requested, age at the wedding, individual photos, companion relationships, RSVP responses, meal selections, and optional dietary or allergy details. Professional information may include business identity, services, prices, packages, contact and social links, portfolios, and booking connections. Collaboration information includes messages, assigned duties, permissions, and activity records. When RSVKeys is enabled, guest-token associations, check-in status, method, time, and staff actions may be recorded. Purchase records may include purchaser account ID, wedding ID, product, payment-provider transaction identifiers, and entitlement/refund status. Payment processors and app stores collect payment details under their own policies; the app integration should not store full card numbers.

3. How information reaches us
You provide information through forms, uploads, imports, and messages. Couples or authorized professionals may provide information about guests and collaborators. Apple, Google, and Firebase authentication provide identifiers needed for sign-in. Hosting and application services may process technical information such as IP address, device/browser information, request timestamps, errors, and security logs. Device storage helps retain settings and navigation. Optional analytics or advertising tracking must be disclosed and assessed before activation; this draft does not authorize undisclosed tracking.

4. Why we use information
We use information to maintain accounts and wedding records, collect and review guest submissions, organize RSVP and seating information, show authorized collaborators their assignments, support vendor discovery and communication, coordinate schedules and check-in, verify purchases, prevent abuse, provide support, and meet legal obligations. Guest photos help authorized wedding participants recognize the correct person; they are not intended for automated facial recognition or biometric identity verification. Optional allergy and dietary information is used for wedding meal planning, not advertising. Do not provide unnecessary medical information.

5. Who can see information
Couples can see guest submissions and approved records for their wedding. Guests using an appropriately secured personal link should access only their own authorized information and invited companions. Planners, vendors, and staff receive information permitted for their role; a caterer may need meal and allergy information, while a beauty vendor may need relevant inspiration and authorized bridal-party details. Public vendor profiles, galleries, prices, and social links are visible to their intended audience. Private guest lists and photos are not public vendor-directory content. Sharing links does not grant permission to view another wedding’s records. Permission enforcement and verified personal editing must be completed before those features are enabled publicly.

6. Service providers and other disclosures
Firebase/Google services support authentication, storage, databases, hosting, and backend processing. Apple and Google support sign-in and applicable store purchases; Stripe supports web payments where enabled. Twilio will process phone numbers, message content, delivery information, and verification events when SMS or Verify is enabled. These providers may operate in other countries. External social links and vendor sites are governed by their operators. We may disclose information when reasonably necessary to comply with law, protect safety and security, resolve disputes, or complete a business transfer with appropriate privacy safeguards. No sale of guest information or use of private guest photos for advertising is authorized by this policy. Any materially different practice requires an updated notice and any legally required consent.

7. Messaging, links, and choices
Automated texts require the applicable permission; importing contacts is not itself SMS consent. Where supported, reply STOP to unsubscribe and HELP for assistance. Opting out of optional texts does not cancel a wedding invitation. SMS providers and phone carriers process message delivery. Private links should not be forwarded. General collection links create submissions for approval; they must not expose existing guest records. Personal editing links require separate identity verification before updates. Camera and photo access should be requested when needed for an upload; device permissions can be withdrawn in device settings. Required guest photos and phone numbers are necessary for the guest-form flow; contact the couple if you prefer an alternative way to provide details.

8. Retention and security
We retain information for the purposes described here, taking account of the wedding lifecycle, account activity, deletion requests, financial recordkeeping, fraud prevention, disputes, and legal obligations. Some archived records, backups, audit logs, and purchase records may remain after removal from an active guest list. Exact retention and backup-deletion schedules must be confirmed before this draft becomes effective. We use access controls and other safeguards appropriate to the service; no system can guarantee absolute security. Report a lost private link or suspected unauthorized access promptly. We do not publish secret payment or messaging credentials in the app.

9. Access, correction, and deletion
You may correct information through available account or guest tools and contact us to request access, correction, or deletion. We may verify your identity before responding. Guests can also contact the couple about wedding information the couple controls. Account-deletion tools and a public deletion-request route must be available before store launch. We may retain limited information necessary to comply with law or preserve security and payment records, and explain applicable limits when responding. Additional privacy rights may apply based on your location; contact us to exercise them. We will not penalize you for exercising applicable privacy rights.

10. Children
Vow Atlas accounts and guest-form submission are intended for adults, not for children acting independently. A parent or legal guardian must provide and authorize information about a minor guest. A couple’s child-free age cutoff is separate from legal rules about children’s privacy. Collection of a minor’s photo or contact details requires an appropriate guardian process; do not enable a direct child-submission flow without assessing applicable requirements. Contact us if a child submitted information without appropriate authorization.

11. International use and updates
Vow Atlas operates from Florida, USA, and information may be processed in the United States and other locations used by service providers. If offered in additional jurisdictions, applicable transfer safeguards, legal bases, and required regional disclosures must be assessed before rollout. We will update this policy as practices change and communicate material changes through an appropriate channel. The published version will include its effective date. Questions and requests can be directed to the privacy contact above.