A private place for shared memories

Who controls a wedding

The person who creates a wedding is its host and decides who receives the private invitation, whether contributions need approval, when the shared story is revealed, and when the event is deleted. VowCapture processes information to provide the service for that host.

Information we handle

Guests may provide an optional first name and contribute supported photos. Video contribution is paused until privacy-safe transcoding is available. We also store the selected photo mission, capture and upload times, file type and size, limited device context such as platform and language, and processing status. Guests do not need a VowCapture account.

Hosts provide a name, email address, authentication information, wedding details, event settings, and moderation choices. Passwords are stored only as secure hashes. Optional social sign-in providers supply the account details needed to authenticate the host.

How information is used

We use this information to accept and resume uploads, organize memories into the wedding timeline, enforce event settings, prevent abuse and duplicate uploads, provide private media, support account security, and show hosts operational and aggregate journey information.

Who can see contributions

Original files are available only to authenticated members of that wedding. Guests can see shared derivatives only when the host’s reveal and moderation settings allow it. Infrastructure providers may process encrypted or access-controlled data only as needed to operate VowCapture. We do not sell wedding media or personal information.

Retention and deletion

Wedding contributions remain available until the guest requests deletion or the host deletes the asset or event. A guest deletion request immediately revokes access and queues contributed files for permanent storage purge; the interface reports that purge as pending until background deletion succeeds. Host-deleted assets normally have a seven-day recovery period; guest privacy deletions and owner-confirmed event deletions do not. Failed storage purges remain queued for retry and operator attention instead of being silently abandoned. Raw privacy-preserving analytics expire after 180 days. Expired guest sessions are removed automatically.

Infrastructure backup or snapshot copies, where enabled by the hosting provider, may persist for the provider’s limited backup-retention period and are not used to serve wedding media. Operators must reapply migrations and deletion maintenance after any restore.

Your choices

Guests can open “Privacy & my contributions” from their wedding invitation to download a contribution record or permanently delete their contributions. Hosts can moderate, export, restore eligible deleted assets, or permanently delete an event. For another privacy request, contact the host who shared the invitation so they can identify the correct private wedding.

Security and limitations

VowCapture uses private object storage, capability-scoped uploads, access checks, size and format validation, rate limits, audit records, and restricted media responses. No internet service can guarantee absolute security, so invitation links and any optional event PIN should be shared only with intended guests.

Photos of other people

Guests should contribute only media they are allowed to share. Hosts are responsible for communicating event expectations and handling requests involving children, sensitive moments, or people who no longer want a contribution included.

Policy changes

Material changes will be reflected by a new effective date. Continued use after an update means the revised policy applies to future use; previously submitted privacy requests remain governed by the commitments in effect when they were made.