1. Information We Collect
We collect minimal information necessary to deliver the digital film experience:
Host Account Information
When you sign in as an event host using Google OAuth, we receive your name, email address, profile avatar, and unique authentication identifier. We do not receive or store your Google account password.
Guest Participation Information
Guests join events via QR code or direct link. We collect only the guest's chosen display name and generate an anonymous device session token stored locally in their browser. No email, phone number, or password is requested from guests.
Photographic Media & Event Data
Photos captured through the Kept Shot in-browser viewfinder (including selected analog film filters such as Original, Vintage Film, and Black & White), capture timestamps, allocated exposure counts, and event configuration settings.
Technical & Device Data
Standard technical metadata including device type, operating system, browser version, and approximate viewport dimensions necessary to operate the camera interface and render responsive images.
2. How We Use Your Information
Your data is used exclusively to provide and enhance the Kept Shot experience:
- To allocate and manage digital film rolls and track exposure limits per guest.
- To process, apply analog film simulations, and securely store captured photographs.
- To enforce host privacy rules: Instant Reveal versus After-Event Darkroom Reveal, and Public Guest Gallery versus Host-Only Private Vault.
- To provide hosts with real-time guest rosters, shot counts, and high-resolution archive ZIP downloads.
- To maintain platform security, prevent abuse, and resolve technical issues.
3. Storage Architecture & Media Security
We implement enterprise-grade security and modern storage infrastructure:
- All original photographic files are stored in private Cloudflare R2 object storage buckets with zero public directory browsing.
- All image viewing and download URLs are dynamically generated with cryptographic signatures and expire automatically.
- Database records, authentication sessions, and access permissions are managed through Supabase PostgreSQL with strict Row Level Security (RLS) policies.
- All data transmission between your device, our servers, and storage providers is encrypted using TLS 1.3 / HTTPS.
4. Photo Sharing & Event Visibility
Photo visibility is governed strictly by the host's event configuration:
- Everyone Mode: If the host configures the event for shared visibility, guests who join the event can view photos taken by other participants once revealed.
- Host Only Mode: If configured as private, captured photos are delivered exclusively to the host's private management vault and are never visible to other guests.
- Darkroom Reveal Timing: In 'After Event' mode, photos remain locked and undeveloped in the darkroom until the host concludes the photo-taking period.
5. Third-Party Service Providers
We engage reputable infrastructure providers who adhere to rigorous data protection standards:
- Google OAuth: For secure host authentication.
- Supabase: For PostgreSQL database hosting, authentication sessions, and row-level security.
- Cloudflare: For global edge network delivery, image transformation, and private object storage (R2).
6. Data Retention & Deletion
We respect your right to control your memories:
- Hosts can delete individual events or request full account deletion at any time.
- Upon event deletion, associated photo metadata and stored media files are permanently purged from our storage infrastructure.
- Guests can clear their local session and camera access at any time by clearing their browser cache and site permissions.
7. Your Privacy Rights
Depending on your location, you have the right to access, rectify, download, or delete your personal data. To exercise any of these rights, please contact our team.
8. Contact Information
For questions, privacy requests, or feedback regarding this policy, please reach out to us via our official page at https://www.facebook.com/keptshot.