Privacy And Data Handling

The Face SDK runs on your own server. ARSA never receives photos, face templates, names or recognition results. You are responsible for telling people that face recognition is used and for a lawful basis to process their faces.

What Leaves Your Server

• Licence check-ins: the licence key, the product name, salted hashes of machine identifiers and public keys, then signed check-ins. No face data, names, photos or usage details.
• Webhooks (Prod), if you add them: recognition events to the URL you choose, signed with your secret. Events hold the person’s ID, the score, the face position, the camera and the time; never a photo or a template.

What Is Stored

Everything is in one database on the data volume. Face templates, optional face crops, camera addresses and webhook secrets are encrypted with AES-256-GCM under a key per organisation, protected by the server’s master key on the same volume.

Photos sent to the API and camera frames are analysed in memory and discarded.

Delete A Person

DELETE /v2/identities/{uid}, or Delete on the person’s page, removes the person, all their templates and crops at once. Their ID remains in older events and audit entries until those retention periods end.

Protect The Server

• Serve the dashboard and API over HTTPS and set NF_SECURE_COOKIES=1.
• Give each system its own API key with only the permissions it needs.
• Protect backups of the data volume: they hold the database and the master key.