Member identity never leaves
its home region.

Audit data is held under boundaries built into the architecture, not promised on top of it. The benchmark holds anonymised aggregates only.

ap-southeast-2 · eu-west-2
Sydney and London regional boundaries
k=5
Anonymisation floor from the first audit
One pipeline
The only permitted crossing point
01 — Posture

Built in, not promised on top.

kn0w holds audit data under boundaries built into the architecture, not promised on top of it. Member-identifiable data stays in the region it was collected in. The benchmark holds only anonymised aggregates. One pipeline crosses between the two, and nothing else does.

This page states what the architecture does. The legal basis is at /privacy; the contractual terms are at /terms.

02 — Security controls

Controls built into every component.

The same controls run on every regional instance. They are part of the architecture, not configured per engagement.

Encryption
At rest and in transit
Member data is encrypted in storage and on every connection.
Access
Least privilege
IAM access is scoped to least privilege across all infrastructure.
Audit trail
Append-only ledger
Lifecycle events are written once. No record is updated or deleted.
Monitoring
Continuous
Infrastructure is provisioned as code and monitored continuously.
03 — Regional boundaries

Held where it was collected.

Audit data is held in AWS regional boundaries — Sydney (ap-southeast-2) for Australian members, London (eu-west-2) for United Kingdom members. Member-identifiable data does not cross those boundaries.

ap-southeast-2
Sydney
Australian members. Member-identifiable data does not cross the boundary.
eu-west-2
London
United Kingdom members. Member-identifiable data does not cross the boundary.

The reasoning layer runs in-region. Scoring, narrative generation, and document drafting are performed within the member’s home region; no member-identifiable data is sent to a model endpoint outside that region. The issued Opinion is rendered deterministically.

04 — Anonymisation and the benchmark

The benchmark holds aggregates, not identity.

The benchmark holds anonymised aggregates only, in a dedicated US store (AWS us-east-1). Member-identifiable data is never part of it and never leaves its home region.

In-region anonymisation before crossingEach region — Sydney and London — anonymises within its own boundary. Member-identifiable data never leaves its home region. Only the anonymised aggregate crosses, via a single uniform pipeline, into the US benchmark store, which holds anonymised aggregates only at a k=5 floor.ap-southeast-2 · Sydney · home regionMember dataAustralian membersAnonymisestrips identity · k=5eu-west-2 · London · home regionMember dataUK membersAnonymisestrips identity · k=5us-east-1Benchmarkanonymised aggregatesk=5 floorAnonymisation completes inside each home region. Member-identifiable data never crosses the boundary.Where a cohort has fewer than five peers, the artefact says so rather than reporting a partial reading.

Every aggregate is stripped of member identity and assigned a fresh identifier at the moment it is written, so an anonymised record cannot be traced back to the member it came from. The benchmark operates at a k-anonymity floor of k=5 from the first audit: every cohort query resolves against at least five peer companies in the matching cohort, or it does not resolve. Where a cohort has not yet reached five, the artefact says so rather than reporting a partial reading.

05 — Retention

Retention is fixed, not discretionary.

Member-identifiable
Standing + 12 months
Held for the duration of standing plus twelve months, then auto-deleted.
Session audio
30 days
Deleted within thirty days of the session.
Benchmark aggregates
Perpetual
Retained perpetually — they carry no member identity to delete.
06 — Entities and access

Named entities, instructed access.

KN0W PTE. LTD. (Singapore, UEN 202615303G) is the data controller and the sole contracting party on every engagement. kn0w LLC (Wyoming) is the technical sub-processor, operating the infrastructure under instruction from Singapore. Both parties are named in the Data Contribution Agreement, signed once per engagement.

US CLOUD ActAs a US-incorporated entity, kn0w LLC may be subject to the US CLOUD Act. That exposure cannot be eliminated as a matter of law; it is managed. Under the Sub-Processor Agreement, kn0w LLC must notify KN0W PTE. LTD. of any legal demand, challenge or narrow it where the law allows, and withhold disclosure absent instruction except where legally compelled. Because member-identifiable data never leaves its home region, any demand to the US entity reaches the anonymised benchmark only — data that carries no member identity.
07 — Security documentation

The evidence behind the page.

For legal, risk, and procurement review, the underlying documents are available on request.

Data handling
Data Contribution Agreement
The agreement governing every engagement, in AU and UK variants. Available on request.
Subprocessors
Sub-Processor Agreement
KN0W PTE. LTD. to kn0w LLC, naming the infrastructure operator. Available on request.
Contact
Security review
Direct a security or data-handling question to audit@kn0w.co.
08 — Certification

Stated, not claimed.

kn0w states what it holds and does not claim what it has not yet earned. The architecture is compliant by design; the controls below are live today. The certifications are being pursued with Vanta and are marked as such until they are earned.

✓Regional data boundariesIn-region storage and reasoning, Sydney and London.Live
✓Anonymisation pipelinek=5 floor from the first audit. The only permitted crossing point.Live
✓Security controlsEncryption, least-privilege access, append-only audit trail, monitoring.Live
◯SOC 2 Type IIObservation period with Vanta begins at launch. Not yet certified.Pursuing
◯ISO 27001On the same Vanta platform, on a longer horizon. Not yet certified.Pursuing

When a certification is earned, this page carries it.

The audit is built to be submitted.

How its data is held is part of why.

Commission an opinion →Read the methodology