Open menu

Security and data handling

What follows describes how the product is built, not what we intend to build. Where something is not implemented yet, it says so.

Guest selfies

A selfie is received in memory, converted to a numeric face descriptor, compared against that one event, and discarded when the request ends. It is never written to disk, to a database or to a log, and it is never sent to a third-party face API.

Face data from event photos

Photos you upload are indexed into numeric descriptors stored against that event. They are not readable by any browser client, and they are removed with the event.

Tenant isolation

Every record carries its owning workspace, and access is enforced by row-level security in the database rather than by application code alone. Face search is scoped to a single event in the query itself.

Photo storage

Originals stay in private storage. Only the derivatives intended for your event page are public, and those are re-encoded without camera metadata.

Credentials

Uploads use short-lived permissions scoped to one object. The browser never receives a storage credential it could reuse.

What is not in place yet

We do not hold a SOC 2 or ISO 27001 certification, and we do not claim one. Independent penetration testing and a published incident-response commitment are planned before general availability.