Security

Sign-in protection

• Passwords are stored only as strong one-way hashes (argon2) – never in readable form.
• Optional two-factor sign-in with an authenticator app and one-time backup codes.
• Repeated failed sign-ins are rate-limited, and a password reset signs the account out everywhere.

Who can do what

• Role-based access: owner, manager, engineer, technician, viewer, student and national-service roles each see and change different things.
• Technician, data-management and export PINs are checked on the server and are never stored in the browser.
• Every facility is verified and approved before it can sign in.

Protecting data

• All traffic uses HTTPS, with browser security headers that block framing and content sniffing.
• Each facility's records are kept separate; requests are checked against the signed-in facility on the server.
• Changes are stamped with the person who made them, and important events are written to an audit log.
• Signed-in requests that come from another website are refused, so a malicious page cannot act as you.

Backups and your own copy

Records live in a managed database. We also recommend that owners download a backup from Data management regularly and keep it somewhere safe.

What we ask of you

• Use a strong, unique password and turn on two-factor sign-in.
• Give each person the lowest role that lets them do their job, and suspend people who leave.
• Tell us straight away about anything suspicious, at the address below.