Privacy policy

SnapPool is run by [business name — registration pending] ([UEN pending]) in Singapore and follows the Personal Data Protection Act (PDPA). Photos of people are personal data, and this policy covers both hosts, who have an account, and guests, who don't. Where a guest is in the EU, the GDPR also applies and we treat it the same way.

What we collect

From hosts

• Your email address, the event details you enter, and your plan and payment status. You pay on a page run by HitPay, our payment provider, so card details never touch our servers.
• Usage of the dashboard — enough to run the service and fix problems.

From guests

• The photos, videos and messages you add, with the name you choose to give (optional — you can skip it).
• The date and time of the upload and a device identifier stored in your browser, so your own uploads show up as yours and so a host can block a device that is misusing the event. We do not ask for your email, phone number or account.
• Basic technical information — browser type, rough device class — so the page works on your phone.

From anyone who writes to us

• What you send through the contact or partner form: your name, email address and message, and your company, phone number and event details if you give them. It reaches our inbox by email and is kept only to reply to you. We don't add you to a mailing list.

From visitors to this website

• We count page views on this website and on the page where you start a pool, ourselves and without any outside service. For each view we add one to a daily total for the page, the site that linked to it, any campaign named in the link, the country the request came from, and whether it was a phone, a tablet or a computer. The count uses no cookie, keeps no IP address and holds nothing that identifies you, so it cannot tell one visitor from another. Event and gallery pages are not counted.

What we do with it

• Show the photos to the host and to other guests of the same event, in the gallery and on the venue screen if the host uses one.
• Unless the host has switched AI Gate off, screen uploads for inappropriate content before they appear. Screening looks at content only and does not identify anyone. It is performed by Cloudflare Workers AI, a third-party classification service; the image is sent to it for the check and is not stored there.
• Email hosts about their events: expiry warnings, receipts, and important changes. Never marketing to guests — we have no way to contact you and we like it that way.
• Keep the service running, secure and debuggable.

We never sell personal data, and we never use photos to train models. We do share a little with two advertising platforms, and only about our own ads. When someone reaches SnapPool from one of our ads on Google or Meta and then starts a pool, we share the ad-click identifiers that ad's own link carried and a one-way scrambled (hashed) version of the email address used to sign up. Google and Meta use it only to measure our ads, and it tells them which ad worked — not who you are. Guests are never part of this: nothing a guest uploads, writes or is identified by ever reaches an advertiser, and no photo ever does.

Who can see photos

The host and anyone with the event's link or QR code. Events are never public or listed. Hosts can hide any photo, add a password, or close the gallery. If a host uses the venue slideshow, photos appear on a screen in the room where they were taken.

How long we keep it

Photos stay for the retention period the host chose (14 days on the free pool; 1 to 9 months on paid one-off plans; while the subscription is active on subscriptions). After that they move to cold storage for 90 days, then are permanently deleted. Host account details are kept while the account exists; ask us to close it and they are deleted within 30 days. Payment records are kept as long as Singapore tax law requires.

Your rights

• Guests: if you are in a photo and want it removed, open it in the gallery and tap “I’m in this photo” — the request goes to the host, who can take it down straight away. You can also ask the host directly, or write to us with the event name. We will act within 3 business days, and we will not ask you to prove who you are beyond what is needed to find the photo.
• Hosts: you can download, correct or delete your data from the dashboard at any time, or ask us to.
• Anyone can ask what we hold about them, or complain to the Personal Data Protection Commission of Singapore.

Where the data lives

Photos are stored with Cloudflare R2 and application data with Neon, both under contracts that bind them to protect it. Data may be stored outside Singapore; where it is, we make sure it is protected to a standard comparable to the PDPA. Our hosting provider is Vercel.

Four more services handle part of it for us: Resend sends sign-in and expiry emails to hosts and delivers contact-form messages to our inbox, Sentry receives error reports so we can fix what broke, and Cloudflare Workers AI runs AI Gate's screening. HitPay takes payments: we send it the amount and an order reference, you give it your payment details on its own page, and it tells us whether the payment went through. Two more receive only the ad-measurement data described above: Google and Meta, and only where a host reached us from one of our ads.

What we don't do

No face recognition, no face grouping, no "find every photo you're in". If we ever consider adding a feature like that, it would need separate, explicit consent from each person before any of their photos were analysed, and it would never be applied to an existing event's photos. We are saying this now so it is on the record.

Cookies

Hosts get a sign-in cookie. Guests get one small identifier in their browser so their own uploads can be shown to them, and one more if the event has a password, so they are not asked for it again. If you arrive from one of our ads, our own pages set one more cookie holding that ad's identifiers, so a pool you start afterwards can be credited to the right ad. It is set only on that arrival, is kept for 90 days, and is never set on an event or gallery page. The page also keeps two things on the device itself, never sent to us: the last few events it opened, so the home-screen icon can find them again, and whether you dismissed the install prompt. There are no third-party cookies and no cross-site tracking cookies, and no advertising scripts or outside analytics services anywhere on the site — guest pages included. The count of page views described above is our own and sets no cookie.

Contact

Data protection officer: [name — to be appointed], at hello@snappool.photos. If this policy changes in a way that matters, hosts will hear by email and the date at the top will change.