Legal · Draft for review
Privacy Policy
Version 2026-10-20.draft-1 · Prepared 20 October 2026 · Not yet effective
Not legally approved
A qualified legal professional must review this draft before live use. Operator details and legal settings remain incomplete. Visiting this page does not mean you accept it.
01
Draft scope and operator
Privacy Policy version 2026-10-20.draft-1 is a draft for qualified legal review and has no effective date. The legal data-controller identity, location, verified privacy contact, applicable law and lawful bases are not yet configured.
This notice describes the current preview and distinguishes planned live features from enabled services. It is not a claim of legal compliance or an invitation to enter sensitive real information.
02
Information used by Vows
Wedding tools use couple names, dates, venues, schedules, content, photos, planning records and guest details. RSVP forms use attendance, party size and optional dietary needs and notes. Public seat-request forms can collect names and optional email and phone. Physical gift reservations can collect a name, optional email, quantity and note.
The inactive registration screen includes name, email, phone and password fields. Sign-in is currently bypassed; the preview uses a sample identity rather than a verified account. No live registration or identity-bound consent storage is established by this preview.
Demo onboarding acknowledgements contain only the sample user ID, terms and privacy versions, acknowledgement time and workflow context. They do not contain passwords or payment credentials.
03
Why information is used
Information supports the wedding workspace, invitation rendering, attendance planning, schedules, physical wishlists and designs you choose to publish. Optional notes and dietary details should be limited to what the organizers need.
Contract, legitimate-interest and consent bases, including any special-category dietary data treatment, must be assessed for the operator’s jurisdiction before launch. Optional data submission is not blanket marketing consent. No marketing consent is inferred from an RSVP or from visiting these pages.
04
Current storage and security
While demo mode is enabled, app records, photos, design drafts, published snapshots and test acknowledgements are stored in this browser’s local storage. They are not synchronized to a shared production database; another device or browser will not have the same records.
Anyone able to use the same browser profile may access its demo data. Demo sign-in bypass and role checks are not production security. Local test acknowledgement records are editable by the browser owner and are not a tamper-proof legal audit.
Hosted authentication, storage permissions, collaborator access and retention must be verified before real personal data is collected. Existing hosted code paths in the project do not establish that those services are active.
06
Third-party requests
The application loads web fonts from Google and may display Google Maps, external image URLs or links configured in wedding content. These providers can receive network information, such as an IP address and browser metadata, when content loads or a link is opened. Their own policies apply.
The preview platform may process technical error reports and hosting diagnostics. Email, authentication and payment code exists in the project, but demo actions must not be described as active sending or payment processing. An accurate processor list, hosting regions, transfers and contractual safeguards require review before live launch.
07
Retention and your choices
Demo information persists in the browser until its storage is cleared or the preview is reset; clearing it can remove your test work. No automatic production retention schedule or account-deletion service is configured.
Do not share information you do not want visible to the couple or intended recipients. Contact the couple through a known channel to correct wedding or RSVP information. The operator must configure a verified privacy-request channel and procedures for access, correction, deletion, objection and any applicable consent withdrawal before launch.
Existing acknowledgement entries are not reset when a new draft is acknowledged. A lawful retention period and treatment of deletion requests for audit records must be set before hosted recording.
08
Children, sensitive data and payments
Do not enter children’s contact details or unnecessary sensitive information into the demo. Age rules and guardian requirements must be finalized for the actual launch jurisdiction. Dietary notes are optional and may reveal health or religious information.
Vows forms must never collect card numbers, bank passwords or payment credentials. Payments are disconnected in the current preview; a pledge or wishlist reservation is not a completed payment. Any enabled provider needs its own accurate privacy disclosure.
09
Policy changes and review
This draft has a stable version identifier. Material changes require a new version and appropriate notice. A Privacy Policy notice is separate from consent: reading it or submitting a necessary RSVP must not be treated as permission for unrelated uses.
Before live launch, a qualified reviewer and the operator must finalize controller details, lawful bases, processor and transfer disclosures, retention, data-subject procedures, age requirements and any cookie or tracking requirements based on the actual deployed system.