Your people’s details matter.

Vow Motion is currently a launch preview. This page explains the application’s implemented data handling; it is not a claim of legal certification.

Who operates this deployment

The operator running this deployment has not yet published their legal identity, jurisdiction, or a privacy contact here. Nothing below should be read as satisfying that requirement. See docs/LEGAL-CHECKLIST.md for what the operator needs to confirm and configure before accepting real guest data.

Information in your wedding

The hosts manage guest names, contact details, invitation access, event replies, meal choices, dietary notes, seating, and uploaded photos. Personalized invitation links grant access to a household’s information. Keep them private.

Messages and consent

Guests can update contact details and withdraw messaging consent from their invitation. The local demo records messages in a development outbox and does not send email or SMS. Production sending requires a configured provider.

Contact enquiries

When you use our contact form, we store the details you submit and forward your enquiry to the Vow Motion team by email so we can reply. Contact enquiries do not sign you up for marketing, and are kept for up to two years. For questions about an enquiry or to request its removal, email aldo@vowmotionweddings.com.

Photos

Uploaded images are resized and re-encoded to remove embedded metadata. Guests can see their own uploads; other guests see only photos approved by the hosts. Photo files are served through authorized endpoints.

Storage and accounts

Studio usage measurements help us understand which steps take effort. These contain only predefined action and screen names, counts, elapsed time and navigation counts. They do not contain wedding names, guest details, answers, messages, invitation links or a persistent tracking identifier. Demo measurements are separated. The browser’s Do Not Track preference disables collection.

Passwords use salted scrypt hashes. Session cookies are HTTP-only and expire after seven days. Invitation tokens are stored as hashes. Demo workspaces contain fictional data and are separate for each visitor.

Access, correction, and deletion

Guests can correct their contact details and responses using their invitation. Ask your hosts to export or remove guest information. Hosts can remove guests and photos in the Studio. Account owners can export everything stored for their weddings, or schedule their own account for deletion, from Studio → Settings → Privacy centre. Deletion has a 14-day grace period you can cancel, then removes owned weddings, their guest information, and their photo files.

Before a public launch

The deployment operator must publish their legal identity, contact information, retention policy, and provider disclosures for the environment they operate. None of that has been configured yet.