Seguridad y protección de datos
Esta página existe en francés, ucraniano e inglés: aquí está la versión en inglés.
Audit of 26 October 2026
Summary
This report describes how Staff Flow protects its users' data, what the latest audit checked, what was fixed and what remains to be done. It covers the server, the API, the web and Android app, and the website.
The audit was carried out internally. It does not replace a certification; the planned steps are listed at the end.
Hosting
Server and backups at OVHcloud in Frankfurt (Germany), in the European Union.
Debian 13 system with automatic security updates. Only three ports are open to the Internet: HTTPS, HTTP (redirected to HTTPS) and remote administration. The database and internal services cannot be reached from outside.
Each service runs in its own container; the API runs without administrator rights. The development and demo environments have their own databases and never contain real data.
Encryption
All connections are encrypted (HTTPS, TLS 1.2 and 1.3 only, HSTS). Old and vulnerable TLS versions are refused.
Documents sent in the app: encrypted on the server (AES-256-GCM), downloaded through links valid for 10 minutes and checked every time.
Authenticator app secrets: encrypted (AES-GCM). API keys, backup codes and kiosk tokens: stored only as hashes.
Daily backups, encrypted (AES-256), kept for 30 days.
Accounts and access
Sign-in with Google, or without Google with an authenticator app (2FA): lockout after 3 wrong codes, limited attempts per address.
Sessions of 30 days, closed everywhere as soon as an account is linked to another Google account. Each person sees only what their role and privileges allow, in their own companies and on their own sites only.
Platform administration is restricted to a list set on the server, never changeable from the web.
App and API
All database queries are parameterised; every value received is checked (type, size, rights).
Rate limits per API key, per company and per address; signed webhooks (HMAC); call log available to the company.
Allowed web origins limited to Staff Flow; protective headers: no display inside another site, strict file types, referrer policy, camera and location for Staff Flow only.
Profile photo addresses are signed: they cannot be guessed, and they are only given to members allowed to see the person.
Personal data (GDPR)
Only data needed for the service is requested; no medical reason is asked for an absence. No advertising trackers or audience measurement.
When the app opens, nothing is loaded from Google apart from the “Sign in with Google” button. Photos (including the “Pop” style) and translations are processed on our own server.
Everyone can export their data and delete their account themselves, from “My profile”. Retention periods are set and applied automatically (see the privacy policy).
For the data a company enters about its team, Staff Flow acts as a processor (Article 28 GDPR); a data processing agreement is available on request.
Payment
Payment takes place on the LiqPay (PrivatBank) page. Staff Flow never receives, sees or stores card details. Each payment confirmation is checked by its signature before the subscription is activated, and can only be applied once.
Fixed during this audit
When opening, the app loaded files from Google (display engine, font, notification scripts), which passed on visitors' addresses: they are now served by Staff Flow.
Profile photos could be read by anyone who knew a person's identifier: their addresses are now signed.
The privacy policy stated the wrong hosting location and a copy of the backups that does not exist: it is corrected and completed (clock-in, messages, documents, photos, payroll).
Test payments can no longer be used in production except by administrators.
Next steps
A copy of the backups outside the main server, in a second location.
Stronger access for server administration (keys only, automatic blocking of repeated attempts).
A complete Content Security Policy (CSP) for the web app.
Penetration test by an independent provider, then certification (ISO/IEC 27001).
Report a vulnerability
Write to contact@staff-flow.cloud describing the problem. Please do not access other people's data, and give us time to fix it before any publication. See also /.well-known/security.txt.