Skip to content
BEROSSOS
Data handling

What we collect, and where it stays

The short version: this site collects nothing at all, and the systems we build are designed so that your data never has to leave your building.

Last reviewedAugust 2026

This website

Analytics
None. There is no analytics script, no tag manager, no tracking pixel and no advertising network on this site. We do not know who visits it.
Cookies
None set by us. Every page is served as a static file and holds no session.
The contact form
It has no backend. The form composes a message in your own mail client, and nothing leaves your machine until you press send yourself. Nothing you type into it is transmitted to or stored by us.
The simulations
They run entirely in your browser on synthetic data. No frames, inputs or results are uploaded anywhere.

Systems we build for you

On-premise first
Video and patient data stay inside your building. Cloud deployment is an option we support when you ask for it, never a requirement we impose.
Computer vision
People are tracked as anonymous objects. Identities are not stored, no face data is held, and tracks expire with the session. The vision work runs on your hardware, and video is not sent to us.
Access and audit
Every action leaves a record with a named owner. Roles and permissions are part of the schema rather than a layer added afterwards.
Handover
Source code, schema, deployment steps and operating notes are handed over in writing. You can audit exactly what the system stores, because you hold all of it.

If you contact us

What we hold
The email you send us and whatever you chose to put in it. We use it to answer you and to scope the work, and for nothing else. We do not sell it, share it or add it to any list.
Removal
Ask, and we delete the thread. There is no marketing list to unsubscribe from, because we do not run one.

This page describes how we work, not a legal filing. If a hospital, ministry or company procurement process needs a signed data-processing agreement, ask for one and we will provide it against the specific deployment.