Security review

The controls your security review asks about, stated plainly

Position
No security certifications held yet. SOC 2 Type II and ISO 27001 are in preparation.
Method
Each control below is implemented and enforced in the product today, not planned.
Limits
Where a control a reviewer would expect is not in place yet, the security pack says so, under NDA.
  1. 01

    Tenant isolation

    The first question in every security review is whether another customer can reach your data. Your organisation is resolved from the verified credential, never from a URL, and every request is checked against your organisation before any data is returned. The database also refuses to link a record to another organisation’s data.

  2. 02

    Tamper-evident trail

    When a decision is challenged — a dismissal, a client dispute, an audit sample — you need a record nobody can quietly edit afterwards. Governance changes, data access and our own staff actions are each recorded on a SHA-256 hash-chained, tamper-evident audit trail, and you can re-verify it yourself through the API.

  3. 03

    Immutable anchoring

    Evidence is only evidence if it outlives the person who would rather it did not. Checkpoints of the audit trail are written to write-once storage that cannot be altered or deleted early.

  4. 04

    AES-256-GCM

    The encryption row on your questionnaire, answered precisely rather than with the word "encrypted". Secrets are encrypted with AES-256-GCM: integration credentials, single sign-on secrets, two-factor seeds and signing keys. Our full encryption posture is in the security pack.

  5. 05

    Subject requests, self-served

    A subject-access request lands on HR and legal as a fortnight of manual collation, and a works council asks the same questions again. Monitored employees get self-scoped access to what is captured about them, to who viewed it, to consent controls, to a private-time pause they run themselves, and to a dispute that freezes automated re-decision while it is open. The request is answered by the product, on the record.

  6. 06

    Certifications: none yet

    If a certificate is a hard gate in your procurement, we are not through it: WorkMonitor holds no certifications yet. SOC 2 and ISO 27001 are in preparation. What your reviewer gets in the meantime is a detailed control and limitations inventory, shared under NDA, rather than a badge we have not earned.

Commitments

Four commitments, enforced by the product

Most security pages quote figures about the vendor. These are properties of the product itself: what it does on every request, and what it will not do at all.

  1. 01

    Checked on every request

    Every request is checked against your organisation before any data is returned.

  2. 02

    Linked only within your organisation

    The database itself refuses to link a record to another organisation’s data.

  3. 03

    Tamper-evident audit trail

    Governance changes, data access and our own staff actions are hash-chained, so an edit anywhere is detectable.

  4. 04

    No keystroke content

    Keystroke content is never recorded. The desktop agents count key presses and never read what was typed.

Commitment 03, above

A record nobody can quietly rewrite, us included

Every entry carries the hash of the one before it, so an edit anywhere breaks each entry after it. The audit trail is hash-chained and tamper-evident, and checkpoints of it are written to storage that cannot be altered or deleted early.

You do not have to take our word for it. Verification is available to you through the API, so your own team can re-check the trail whenever a record is challenged.

Commitment 04, above

Some switches are locked because there is nothing behind them

Keystroke content is not a setting. The agents never record what anyone types, so there is nothing an administrator could switch on, and nothing to hand over if asked.

Anything that is captured has to be allowed by your plan, your policy, the working schedule and, where it is required, the person’s consent, all at once. A person’s own private time pauses capture entirely.

Why this page reads like a document

A control nobody outside this company can check is a promise, not a control.

So every control here is one the product enforces today, stated no more strongly than it holds, and the detail a reviewer needs is in the security pack.

Trust Center

Everything your reviewer asks for.Including the limitations.

A review stalls in the round trip: a question goes out, a week passes, half of it comes back. The pack removes the round trip. Pre-written answers to the standard questionnaire, a detailed control and limitations inventory, and our data processing agreement. We hold no certifications yet, and that is the first line your reviewer reads rather than something they find late in procurement.

In the pack

  • Security overviewEvery control, what it covers, and a plain statement wherever a control a reviewer expects is not in place yet.
  • Questionnaire answersWritten answers to the standard security questionnaire, so your reviewer starts from a stated position rather than a blank form.

A detailed control and limitations inventory is shared with customers and security reviewers under NDA.