Account

Security and your data

Rignos holds your customer list and your trucks’ history. Here is exactly how that is protected, in the terms that matter to a shop.

Shop data is walled off

Every database query in Rignos runs through a shop-scoped handle. There is no screen, search, export or report that crosses from one shop into another’s data. This is enforced in code and covered by an automated test suite that fails the build if a query escapes the boundary.

Sign-in

• Two-factor available on any account, from Security in the workspace. Once on, it applies to the website and to activating a machine from the app.
• Rate limiting on password attempts, shared across the website and the app so an attacker cannot use one to work around the other.
• Password reset by email, with single-use links.

Machines

Each activated laptop carries its own token and can be revoked individually from the office. Revoking is immediate on the next request. A revoked machine cannot upload, and its past sessions remain in your workspace.

At the truck

Rignos is read-only on the vehicle bus. It listens to J1939 and does not write calibration data. The single exception is clearing stored fault codes, which happens only when a tech presses the button.

Audit log

Account changes, machine tokens, orders and other consequential actions are written to a log the owner can read. It answers “who did this, and when” without a support ticket.

Backups

The production database is backed up on a daily schedule, and again automatically before any schema change is applied. Backups are kept on the server’s own storage volume, separate from the application image.

Reporting a problem

Found something that looks wrong? Write to rignos@vietdiesel.com with enough detail to reproduce it. We would rather hear it from you than read about it later.