Privacy Policy
Bridelume ("we", "us", "our") is a wedding photo-sharing platform. This page describes what we collect, why, and how to exercise your rights. It is written in plain English because legalese is the enemy of consent.
1. What we collect
From hosts (the couple paying for the event)
- Email address — for sign-in via magic link and event notifications.
- Event metadata — title, date, slug, plan tier you selected.
- Optional cloud-mirror tokens — encrypted OAuth tokens for Google Photos, iCloud, Dropbox, or OneDrive when you opt in to auto-mirror.
- Payment information — handled exclusively by Stripe; we never store card numbers.
From guests (anyone uploading via your event QR)
- Photos, videos, and voice messages uploaded to the event.
- Optional name entered on the upload page.
- Technical metadata — IP address, user agent, EXIF data, file size, content type, and upload timestamp. This is used to debug uploads and detect abuse.
From everyone
- A single session cookie (
auth_session) when you sign in. See our Cookie Policy.
2. Why we collect it
- To provide the service: store and serve photos, send sign-in emails, generate QR codes, run optional cloud-mirror jobs.
- To moderate uploaded content (AI moderation via Amazon Rekognition on photos and videos).
- To prevent abuse: rate-limit uploads, detect malicious files, comply with DMCA.
- To improve the service: aggregate, anonymized usage analytics.
3. Who we share it with
We use a small set of named processors, each contractually bound by GDPR-compliant data-processing agreements:
- Neon — Postgres database hosting (EU region).
- Cloudflare R2 — encrypted object storage for uploaded media.
- Resend — transactional email delivery.
- Stripe — payment processing.
- Amazon Web Services (Rekognition) — automated content moderation. Photos sent for moderation are not retained by AWS beyond the request.
- Twilio — when you enable the voice-message phone line.
We never sell your data, run advertising, build user profiles, or share it with third parties for purposes other than delivering the service you signed up for.
4. Where data is stored
Primary infrastructure runs in EU regions (Neon eu-central-1; Resend eu-west-1). Cloudflare R2 is jurisdiction-agnostic with EU residency available on request.
5. How long we keep it
- Free tier: 30 days after the event.
- Wedding tier ($39): 12 months of upload window plus 12 months of storage.
- Forever tier ($69): 5 years of archival storage, plus an automatic mirror to your own cloud — so your photos outlive our service if we ever shut down.
- Account data: retained as long as your account is active. Deleted within 30 days of account closure.
6. Your rights (GDPR, CCPA)
You have the right to:
- Access — request a copy of all data we hold about you.
- Rectification — correct anything wrong.
- Erasure — ask us to delete your account and all associated uploads.
- Portability — export your event in a structured, machine-readable format.
- Object — opt out of any non-essential processing.
Email privacy@bridelume.anten.site for any of the above. We respond within 30 days.
7. Children
Bridelume is intended for adult use. We do not knowingly collect data from anyone under 16. If a guest of an event is a minor and a parent or guardian requests removal of their image, we will action it within 7 days.
8. Security
TLS everywhere, hashed credentials, scoped API tokens, principle-of-least-privilege access, and incident response within 72 hours of detection.
9. Changes
If we make material changes, we'll email registered hosts 30 days before they take effect.
10. Contact
Bridelume — privacy@bridelume.anten.site. Data Protection Officer inquiries: same address, subject line "DPO".