Legal · Draft for review
Terms and Conditions
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
About this draft
These proposed Terms and Conditions describe Vows, a wedding planning, invitation, RSVP and design service. Version 2026-10-20.draft-1 is a draft for qualified legal review, not an approved legal agreement. It has no effective date yet. Opening this page is not acceptance.
The operator’s legal identity, applicable jurisdiction, legal address and verified support channel must be supplied before these terms are approved or live account acceptance is enabled.
02
The service and current testing mode
Vows offers wedding workspaces, guest lists, schedules, planning tools, invitations, editable website designs and physical gift wishlists. Availability depends on which services have actually been connected.
The current preview bypasses sign-in and uses sample identities and browser-local demo records. Demo publishing saves a snapshot in this browser; it is not live hosting. Email actions are disconnected in demo mode. Do not enter confidential or real guest information while testing.
03
Your responsibilities
Provide accurate information, use only content you have permission to use, and share invitations only with intended recipients. Do not upload sensitive information that is unnecessary for the wedding.
For a future live account, protect access credentials and notify the operator through a verified support channel about suspected misuse. Demo access is not secure authentication.
04
Accounts and wedding content
You retain the rights you hold in your photos, text, wedding details and designs. Vows does not claim ownership of your wedding content. Platform software, built-in templates and third-party materials retain their respective owners’ rights.
The proposed service permission is limited to processing, storing, rendering and sharing your content as instructed by you to provide the enabled service. The precise licence wording and retention obligations require legal review.
05
Invitations and RSVP processing
Invitation links and QR passes may identify an invited guest and allow a response to be viewed or updated. Treat personal invitation links as private; forwarding a link can disclose information or permit someone else to respond.
The couple and wedding managers use guest names, contact details, attendance, party sizes and optional notes to organize the celebration. Dietary information is optional and may be sensitive; share only what the couple needs. An RSVP request is not a guarantee of confirmed seating.
06
Collaborator access
In a live service, access must be limited to the relevant wedding and explicitly authorized roles. Owners should review access, disclose sharing to guests where required, and revoke access when no longer necessary.
Secure hosted role enforcement, collaborator invitations and revocation are not yet verified or enabled in this preview. Demo role displays are for interface testing, not production access control.
07
Publishing and sharing
Review names, venue details, photos and other information before confirming publication or distributing a link. Only publish material you are entitled to share. A shared or public page may be copied by recipients, and removing it cannot retrieve copies already made.
Atelier draft edits remain separate from confirmed published snapshots. Current demo snapshots exist only in local browser storage. Hosted publication requires a connected and verified service.
08
Acceptable use
Do not use Vows for unlawful activity, harassment, impersonation, fraud, malicious uploads, unauthorized access or infringement of privacy and intellectual property rights. Do not collect payment credentials in wedding content or guest forms.
09
Gift wishlists and disconnected payments
A physical wishlist reservation records an intention to bring an item; it is not a processed payment, purchase receipt or delivery guarantee. External item links are operated by their respective providers.
Online billing and gift payment processing are not enabled for this demo. No payment, refund or settlement conditions are activated by this draft. Any future standalone opt-in contribution service needs reviewed conditions matching its actual provider and must clearly distinguish a pledge from a completed payment.
10
Availability and ending use
You may stop using the preview. Browser-local demo data may be lost when browser storage is cleared, the device changes or the preview is reset; it is not a production backup.
Before a live launch, the operator must finalize lawful suspension and termination grounds, notice, access to exports, deletion and retention rules, service limitations and any mandatory consumer protections. This draft does not promise those unconfigured capabilities.
11
Versions, acceptance and support
Any required acceptance must be an affirmative action, not a page visit or a preselected checkbox. Demo onboarding records this draft version, the privacy version, a timestamp and the sample user identity locally, without replacing older entries. This is a test acknowledgement, not evidence of legally approved consent.
Material changes must receive a new version. Existing acceptance history must be retained according to a reviewed lawful retention policy, not silently overwritten. Live identity-bound acceptance remains pending hosted storage and legal approval.
No verified operator support or privacy contact has been configured. For invitation corrections, contact the couple through a channel you already know. The operator must supply a real support and privacy-request channel before collecting live personal data.