kn0w makes the Automation Report from company data. Data that identifies a company is held in the region where it was collected. The peer data holds anonymised data only. One anonymisation step crosses between the two.
The controls on this page are live. SOC 2 Type II and ISO 27001 are being pursued and are not yet held.
When a certification is granted, this page carries it.
The same controls run in every region and for every company.
Identifiable data is held inside AWS regional boundaries: Sydney (ap-southeast-2) for Australian companies, London (eu-west-2) for United Kingdom companies. It does not cross those boundaries.
kn0w's AI processing takes place within the company's home region. Readings, narrative and the report draft are produced within that region. No identifiable data is sent to a model endpoint outside it.
The peer data is a separate store in the United States (AWS us-east-1). It holds anonymised data only. Identifiable data is never part of it.
Anonymisation completes inside the home region before anything crosses. A company's anonymised contribution joins the peer data after its report is issued. No placement is read from fewer than five companies.
Each voice session is recorded to produce the readings.
KN0W PTE. LTD. (Singapore, UEN 202615303G) is the data controller and the contracting party on every commission. kn0w LLC (Wyoming) is the technical sub-processor and operates the infrastructure under instruction from Singapore. Both are named in the Data Contribution Agreement, which is executed before any session opens.
This page states what the architecture does. The legal basis is at /privacy. The contractual terms are at /terms. For legal, risk and procurement review, the underlying documents are available on request.
Report 000142, a sample report for a fictional company. kn0w Score 51, Systematic.