Our own file

We ask you to hand an auditor everything. Here is what we hand ours. If something on this page is out of date, that’s a finding, so tell security@fieldproof.example.

Exception in our last SOC 2 Type II report, from Hadley & Crane. What it was, and what we changed, is T2.

T1

Our SOC 2 Type II report

Examined by Hadley & Crane LLP.

Observation period
1 Apr 2025 – 31 Mar 2026
Report issued
8 May 2026
Opinion
Unqualified
Exceptions
One, described in T2

Hadley & Crane audits us. Ardwell Pike audits our customers. We keep them apart on purpose: if the firm examining our controls also examined yours, its opinion of us would sit next to the business we send it. Hadley & Crane has no Fieldproof customers as clients, and we don’t refer any to them.

The full report is available under NDA, and you can request it without talking to sales. The request goes to a security engineer.

Request the report

T2

The exception

In Q3 2025, our quarterly access review for the production AWS account was completed 9 days after the quarter’s deadline. No access was found that should have been removed.

We now open the review on the first day of the quarter, and the Okta Tap blocks the quarter from closing until it’s done. We’d rather show you this than a report with nothing in it you can check.

T3

The dates we've held

We count every Opinion customer since our first, in March 2025, against the report date Countback gave them on the day they signed. That’s 71 reports. 68 were issued on or before that date.

Three weren’t:

  • Two customers used their free fieldwork move, and their reports issued 7 days late. We count those as misses anyway, because the date on the order form is the one their prospect heard.
  • One was ours. In February 2026, Ardwell Pike’s engagement lead was out the week of fieldwork, and the report issued 3 working days late. Every fieldwork week now has a second auditor booked.

Figures as of 12 October 2026. 9 customers are mid-window and aren’t counted until their date passes.

T4

We run on Fieldproof

Our own 47 controls sit in our own Ledger, pulled by the same six Taps, reviewed by a colleague who doesn’t report to the person being reviewed.

FieldproofLedgersnapshot 12 Oct 2026
Passed
47 / 47
Evidence
1,148
Type II window
Day 195 of 365
EvidenceControlStatus
Okta: MFA required for all 19 peopleFP-19Passed
Backup restore drill: ledger-db in 23 minFP-44Passed
PR #2291 merged with 2 approvalsFP-37Passed
Laptop encryption: 19 of 19, acceptedFP-29Passed
Q4 access review closed: 27 of 27, 1 removedFP-24Passed
Q4 access review opened on the first dayFP-24Passed

T5

We don't store your source code

The GitHub Tap reads metadata: pull requests, approvals, branch rules and alerts. It cannot read file contents, so there is nothing to store. Each evidence item records the commit hash, not the diff.

metadata:read · pull_requests:read · administration:read

T6

What we do store

Evidence records (setting values, user lists, timestamps), uploaded files, and your Binder. Stored in AWS us-east-1, encrypted at rest with AES-256 under keys that rotate yearly, and copied to us-west-2 for backup. Deleted 90 days after you leave, or sooner if you ask.

T7

Report a vulnerability

Write to security@fieldproof.example. We reply within one working day, won’t take legal action against good-faith research, and will credit you here if you’d like.

PGP key fingerprint4A1F 9C2E 77B0 13D8 5E6A  0C94 F2B1 8D37 1E05 6A2C

T8

Subprocessors

The companies that touch your data, and why. We give 30 days’ notice before adding one.

SubprocessorPurposeDataLocation
Amazon Web ServicesHosting, storage, backupsAll customer dataUS (us-east-1, us-west-2)
CloudflareDNS, TLS, request filteringRequest metadataGlobal edge
PostmarkTransactional emailNames, email addressesUS
StripeBillingBilling contact, payment methodUS
SentryError reporting, with request bodies scrubbedStack tracesUS
Ardwell Pike LLPYour SOC 2 examinationEvidence you share in the Fieldwork RoomUS