About EventUploader
EventUploader collects photos and videos from everyone at an event into one gallery the organizer owns. It is built and run by one person, and this page says who that is and how the service is operated.
Who builds it
EventUploader is designed, built, and operated by Paul Rosset, a software engineer. It is an independent product — no team, no investors, no outsourced support queue. When you write in through the support form, Paul is who reads it.
That has a practical consequence worth stating plainly: the person who wrote the upload pipeline is the same person who answers questions about it, and who is accountable for the photos you put into it.
How the service is run
Your files sit in private storage
Uploads go straight from the guest's phone into a private AWS S3 bucket in the EU using short-lived signed URLs. Nothing is public by default — a gallery or album is only reachable once you choose to publish it.
The database enforces who sees what
Event and upload records live in Supabase Postgres behind row-level security policies, so access is checked in the database itself rather than only in application code.
Guests hand over as little as possible
Attendees never create an account, and the name and email fields on an upload page are optional. If you don't ask for them, they're not collected.
Payments never touch our servers
Subscriptions and one-time payments run through Stripe. Card details go to Stripe directly; we store a customer reference and a plan, nothing more.
The privacy policy lists every processor involved and how long data is kept.
What it is not
It is not a social network, and it is not a place your guests are asked to sign up for anything. Guests open a link, pick their photos, and leave. The gallery belongs to whoever created the event, and it can be downloaded in full and taken elsewhere at any time.
Get in touch
Questions, bug reports, and feature requests all go to the same place, and they reach a person rather than a ticket queue.