Sarluma
  • Features
  • Security
  • API
  • Terms
  • Privacy
Sign in

Security

Performance reviews are sensitive. This page describes, in plain terms, how the service protects them and what we have and have not had checked.

Each company is separate

  • Every record carries its company, and the database itself refuses links between records of different companies.
  • The application can only query through a layer that is locked to the signed-in company. A request cannot name another company.
  • Automated tests sign in as one company and attack another on every release. A record of another company looks exactly like one that does not exist.

Signing in

  • Passwords and PINs are stored only as salted, slow hashes combined with a secret that is kept outside the database. Nobody, including us, can read them.
  • A temporary password or PIN must be replaced at first sign-in. Easy PINs such as 123456 are refused.
  • Five wrong attempts lock the account for 15 minutes.
  • Management accounts can turn on two-step verification with an authenticator app.
  • Sessions expire automatically, and end at once on sign-out or when a password is reset.

Who can see what

  • Evaluators see only the evaluations assigned to them. Department managers see averages of their own department. Only HR and the company administrator see who scored what.
  • A submitted evaluation is locked. Only HR can reopen it, and that is recorded.
  • Questions are frozen when a cycle opens, so editing a form later cannot change past results.

Audit log

Sign-ins, PIN and password resets, form and cycle changes, API key changes and support access are recorded in a log the company administrator can read. Entries cannot be edited or deleted.

Support access

Our staff cannot open a company account silently. A support session needs a written reason, ends automatically after 60 minutes, and everything done in it appears in that company's audit log.

Hosting

The service runs on Cloudflare. All traffic is encrypted with HTTPS, and data is encrypted at rest by the hosting provider. The pages load no third-party scripts, fonts or trackers.

What has been checked

The code has been through an internal security review and has automated tests for company separation, sign-in protection and permissions. It has not yet had an independent penetration test and holds no certification such as ISO 27001 or SOC 2. We will say so here when that changes.

Report a problem

If you believe you have found a security problem, write to [security contact email]. We will reply within [3] working days.