How we protect your payroll data.

Hosting and encryption

Location	Google Cloud, Montréal region (northamerica-northeast1). The database and the application servers reside there.
In transit	HTTPS everywhere, with HSTS. Connections between the application and the database are encrypted too, on a private network: the database has no public address.
At rest	Data and backups are encrypted by the infrastructure. Access keys to third-party systems saved per company (DMS, Acomba) are encrypted a second time by the application (AES-256-GCM).
Backups	Automated daily database backups, with a documented restore procedure.

Isolation between customers

Each customer (a dealership group) is isolated from the others at two levels: by the application, and by the database itself, which enforces a security policy on every row of every table. A request can only read or change the data of the customer of the current session. Automated tests check this boundary on every change to the software.

Accounts and access

Passwords	Never stored in clear text: hashed with argon2id. Temporary lockout after several failed attempts.
Sessions	Server-side, revocable sessions in an HttpOnly, Secure cookie. On mobile, short-lived tokens renewed by rotation and kept in the phone's secure storage.
Permissions	Roles per company, checked by the server on every request. Viewing rates and salaries requires a separate permission.
Biometrics	Face ID and fingerprint are checked by the phone. Veloce only receives the result, never the biometric data.

Traceability

• Audit log: every change is recorded in the same transaction as the change itself, with its author and date, and its reason for a correction or a reopening. The application can neither edit nor delete a log entry.
• Immutable source data: punches imported from the DMS are never rewritten. Corrections are layered on top and keep their history.
• Locked payroll: a locked period is frozen with a digital fingerprint. It is only reopened through a logged action that states why.

Development

• Every change goes through an automated test suite, including customer isolation tests, before it is deployed.
• No secrets in code: keys are held in a secret manager, and deployment uses no long-lived keys.
• Inputs are validated at the server boundary. Passwords, tokens and keys are never written to logs.

Privacy

No advertising, no tracking, no sale or rental of data. Location is read only at the moment of a punch, never in the background, and the employee can turn it off in the phone's settings. What is collected, how it is used and your rights are detailed in the privacy policy.

This website

veloce-erp.com is a static site: no cookies, no trackers, no third-party scripts, no fonts loaded from another domain. A strict content security policy (CSP) forbids any script or style that does not come from the site itself.

Reporting a vulnerability