Last updated: August 14, 2026
This policy explains what personal data Event Snaps Collective (“the Service”) collects when you join an event as a guest or run an event as a host, why we collect it, where it's stored, and how you can exercise your rights over it. Event Snaps Collective is built for use at events in the Philippines — weddings, debuts, showers, birthdays, reunions, anniversaries, graduations, corporate gatherings, and similar — and is written with the Philippine Data Privacy Act of 2012 (Republic Act No. 10173, “DPA”) in mind.
Two different relationships sit inside one product, and the distinction decides who you should ask for what.
In practice: ask us about the Service, our storage, and our security; ask the host about who was invited to their event and what they do with the photos afterwards. Where a request reaches the wrong one of us, we will point you to the other.
As a guest, joining and using an event collects:
As a host, setting up and running an event additionally involves:
Weddings and similar events in the Philippines commonly include children as guests. Event Snaps Collective does not ask for or verify the age of anyone photographed, and photo prompts are not filtered by subject. If children are photographed through the Service, that is personal data (and potentially sensitive personal information) about a minor, and the DPA's heightened protections for children's data may apply. Hosts are responsible for ensuring guests understand that photos taken at the event — including of children — will be visible to the host in a shared gallery, and for obtaining any parent/guardian awareness or consent that applicable law requires before those photos are collected.
Event, guest, and photo metadata (names, device-token hashes, prompt text, EXIF data, timestamps, and similar fields) is stored in a Supabase-hosted Postgres database. The photo files themselves — both the original full-resolution upload and generated thumbnail versions — are stored in Cloudflare R2 object storage. Guest photos upload directly from your phone to Cloudflare R2 using a short-lived, single-use upload link; the application server itself never receives or handles the raw image bytes.
Event Snaps Collective does not embed third-party advertising trackers or analytics scripts (no Google Analytics, Meta Pixel, or similar) on guest- or host-facing pages. We do not sell or share your data with advertisers, and we do not use cookies for advertising or cross-site tracking anywhere on this service.
On our public marketing pages only — the home page, FAQ, pricing and sign-up pages, and these legal pages — we use Vercel Web Analytics and Vercel Speed Insights to count page views and measure page load performance. These are cookie-less: they set no advertising identifier, do not follow you across other websites, and are not loaded at all on event, guest, host, or account pages. Their purpose is limited to understanding which parts of our own marketing are used and whether our pages load acceptably.
The third-party infrastructure involved in running this service is Supabase (database hosting), Cloudflare (file storage and, where applicable, CDN), Vercel (application hosting and the marketing-page analytics described above), and Resend (transactional email). Each processes data on our behalf as a service provider under our instructions, not as an independent controller of it.
Two separate things are worth keeping apart here: how long an event stays open, and how long we hold the files.
Every paid package includes an access window — a set number of days after the event date, shown on the pricing page and on the host's own setup page. While it is open, guests can upload and the host can download. Once it closes, new uploads are refused and the bulk ZIP export is switched off. The gallery itself remains viewable, and nothing is deleted at that moment.
Separately, Event Snaps Collective does not automatically delete photos or guest data on a schedule — there is no purge job. Photos and guest records persist until someone actively deletes them:
Deleting a photo removes the original file and its generated thumbnails from Cloudflare R2 and the corresponding database row — this is a permanent action, not a soft hide. Because there is no automatic deletion, hosts should not assume event data disappears on its own after the event; if you want your event and its guests' photos removed, contact us using the details below. Equally, because the access window does close, hosts should export anything they want to keep before it does.
If you're a data subject under the DPA (which includes guests whose photos or name were collected through the Service), you have the right to:
To exercise any of these rights against data held directly by us, contact us using the details in section 11. For data an event host controls (such as asking a specific host to remove your photo from their gallery), you may also need to contact that host directly, since hosts independently control their own event's guest list and gallery.
If we become aware of a personal data breach that is likely to give rise to a real risk of serious harm to affected data subjects, we will notify the National Privacy Commission and the affected hosts and guests in line with the timeframes the DPA and its implementing rules require, describing what happened, what data was involved, and what we are doing about it. Where we are acting as a processor for a host's event, we will inform that host promptly so they can meet their own obligations as controller.
We may update this policy as the Service changes or as our legal obligations change. We'll update the “last updated” date above whenever we do. See also our Terms of Service.
Questions about this policy, or requests to exercise your data privacy rights, can be sent to hello@eventsnapscollective.com. Please tell us which event you are asking about and, if you are a guest, the name you joined under, so we can find the right records. We aim to acknowledge requests within five working days and to resolve them within the period the DPA allows.
If your request concerns data an event host controls — for example asking for your photo to be taken out of a particular gallery — contact that host as well, since they decide what stays in their own event. We will help you reach them where we reasonably can.