Security
- Home
- / Security
Security and data protection
How Movalytics handles data: where it lives, who can access it, and what happens when something goes wrong. This page answers the questions healthcare organisations and research partners ask us most often.
Data stays in the EU
All application data is processed and stored in a data centre in Paris (Scaleway); transactional email (verification, password reset) is delivered through Scaleway Transactional Email, also in Paris. Everything stays within the European Union; no data leaves the EU. Video is held only in file storage and nowhere else; the measurements computed from it are written to separate databases, which contain no video.
Encrypted, in transit and at rest
All traffic to and from the platform travels over an encrypted connection (HTTPS). Stored data and backups are encrypted at rest (AES-256); passwords are only ever stored hashed. Keys and other secrets live in the key vault of our infrastructure provider, never in source code and never on an unencrypted disk.
Pseudonyms, not names
Subjects and patients are registered under a pseudonym (for example P001); the application never asks for a name. The key list linking pseudonyms to people stays with the healthcare or research organisation and is never stored at Babon.
Access is limited and logged
Logging in always requires a second step beyond a password (two-factor authentication). A recording is visible only to the uploader and to anyone it is explicitly shared with. All access is logged: ours through the infrastructure provider and our own working processes, and everyone else only through an application account. Operational logs stay within our EU infrastructure and are kept for a few months.
Every analysis runs isolated
Video analysis runs in short-lived, sealed environments with no persistent storage. Each recording is processed in its own temporary directory that is destroyed immediately afterwards, and the environment itself is cleaned up automatically when it is done, together with the machine it ran on.
Retention and deletion
Raw and processed video are deleted in every configuration immediately after a successful analysis, education included; what remains are the measurements and the 3D skeleton. An upload whose processing failed is kept so we can check it by hand and retry the run, and is deleted automatically at most 30 days after upload. Derived results (angles, parameters, reports) remain available per the project or processor agreement; users can delete their own recordings. At project end we delete all project data on request.
Backups and recovery
Backups cover the databases: continuous, encrypted, within the same EU region, with restore to any point in the past seven days. Because they contain no video, no recording can ever come back through a backup. File storage deliberately has no second copy and no recycle bin: versioning is switched off, so there are no earlier versions, and a deleted file is gone at once and cannot be restored by anyone, us included. That is a privacy choice, not an omission. All configuration is under version control, so every change is traceable.
When something goes wrong
In case of a data breach we inform the data controller within 24 hours and, where required, the Dutch Data Protection Authority within 72 hours. Every incident is documented and evaluated.
Found a vulnerability?
Tell us right away and we will fix it. Our reporting point is listed in security.txt, or email us directly at support@babon.eu.
Live availability of our systems is at status.babon.eu.
Documentation for procurement
For procurement and privacy reviews we provide on request: our data-processing and security description, a data processing agreement, the full processor list, and the security certificates of our infrastructure provider.
Our privacy statement is at app.babon.eu/privacy.