Trust, verified — or absent from this page.
This page carries a standing rule: certifications appear here only once obtained, audits only once passed, partnerships only once signed. When something appears here, it is real. Nothing is padded, and today that means the lists below are short.
StrategyWhy verified trust is the work
Machine capability is becoming a commodity; no certification can be copied from a model release. Our stated goal is to accumulate the Japanese certifications and regulatory credentials worth holding — security, payments, and licensing practice — so that what walks through those gates is Sathi, operated by a company with a clean, verifiable record. Which certifications, in what order, is deliberately unstated until scoped with people who know the terrain.
Honest tensesWhat we hold today
- Certifications: none obtained yet. No SOC2, no ISO, no external penetration test — a compliance program is a deliberate later-phase cost, and the product's security page says the same: sathi.ai/security.
- Partnerships: none signed. Candidates are being explored; a candidate is not a partner and is not named here.
- What is real today: the engineering posture — encryption at rest, consent-gated operator access with tamper-evident audit, total signed export, provable deletion — published and checkable at sathi.ai/privacy.
The ruleHold us to it
If this page ever lists something that cannot be verified — a certification without a certificate, a partner without a signed, named public statement — that is a defect of the highest severity. Tell us.