Halden
Log inGet started
All posts

Company

Our SOC 2 Type II report, in plain English

What our auditors tested over twelve months, the two findings they raised, and what we changed because of them.

THTomás HerreraSeptember 23, 2026 · 1 min read

We received our first SOC 2 Type II report this month. Rather than just add a badge to the footer, we wanted to explain what it covers — including the parts that weren't perfect.

What a Type II report actually means

A Type I report says controls were designed properly on a single day. A Type II report says they worked across a period — in our case twelve months. The auditor samples real evidence: access reviews, change approvals, incident tickets, backups that were actually restored.

What was in scope

  • Security — access control, encryption, vulnerability management and monitoring
  • Availability — uptime, incident response, backups and disaster recovery
  • Confidentiality — how customer data is classified, retained and deleted

The two findings

No report is clean on the first try, and we'd be suspicious of one that was. Our auditor raised two exceptions:

  1. Two quarterly access reviews were completed eleven days late.
  2. One production change in March was approved after it was deployed, during an incident.

Neither led to unauthorised access. We've since automated access reviews with reminders that escalate, and our deploy tooling now blocks production changes without a recorded approval — including during incidents, where a second on-call engineer approves.

How to get the report

Customers and prospects can request the full report under NDA by contacting us. It usually takes us less than a day to send.

Notes on trusting machines with money

One email a month: regulation, playbooks and what we shipped. No spam, unsubscribe any time.