zeekayandHanzo Dev
2eeb7d6a4d
lib/layers.ts is the product: six layers and the Record, each with the operations api.hanzo.ai serves for it (checked against hanzoai/cloud openapi.yaml), a request to paste, docs and the site's own pages. /products, /products/<layer>, the home band, the header's Product menu and the footer row all read it. - Header: Product, Developers, Research, Pricing, Enterprise. - Memory leads with /v1/graph: assert, read, resolve, diff, answer. - /sql, /kv, /docdb, /vector and the old /products/<category> addresses forward through one MOVED table in lib/publish. - /affiliate and /oss state apps/affiliate's and apps/author's own rates; the second pages for the same programmes forward to them. - No real-person faces on agents, no Lux or Zoo partner logos. - Orphans linked, dead links and private-repo links removed; sitemap gate and nav spec hold both. Co-authored-by: Hanzo Dev <[email protected]>
3.6 KiB
title, slug, kind, status, version, updated, summary, order
| title | slug | kind | status | version | updated | summary | order |
|---|---|---|---|---|---|---|---|
| Legal & Trust Center | index | index | draft | 2026-07-22 | 2026-07-22 | The canonical home for Hanzo's legal agreements, policies, and notices. Every Hanzo product links here. | 0 |
This is the canonical home for the agreements, policies, and notices that govern the Hanzo Services. Every Hanzo product — the Console, cloud, API documentation, and signup — links to these documents at hanzo.ai/legal/<name> rather than restating them, so there is one authoritative version of each.
Status: draft, pending counsel. The documents below are complete drafts written to be truthful about what the platform does today. They are not yet effective. Each carries a publication gate listing what must be verified — entity address, mailboxes, retention jobs, subprocessor rows, consent pipeline — before it is published as binding. See the internal implementation checklist for the engineering gates behind these commitments.
Agreements
- Terms of Service — the master agreement for all Services, including Enso routing, benchmarks, research, agents, and APIs.
- Data Processing Addendum — processor terms, SCCs, subprocessor governance, and security measures for business customers.
Policies
- Privacy Policy — what personal data we process, why, and the four data-use states that govern research and training.
- Acceptable Use Policy — the conduct rules for every user, application, and agent.
- AI Research and Data Contribution Terms — the opt-in terms for using your data in Hanzo research and training, and the Verified Commons.
- Consumer Health Data Privacy Policy — our posture under Washington's My Health My Data Act and similar laws.
- Cybersecurity Policy — how we protect your data: who can reach it, how it is encrypted, and what happens if something goes wrong.
Notices and registers
- Research API Supplemental Terms — terms for the
/v1/researchregistry, evidence integrity, and durability states. - Subprocessor Register — the providers that process data on your behalf, including the Enso routing chain.
- Cookie Notice — cookies and similar technologies, and how to control them.
- Biometric, Voice, and Likeness Notice — how features that process faces, voices, or likeness are governed.
- Text message opt-in — how to consent to, and stop, two-factor codes and account alerts by SMS.
How these fit together
The Terms of Service is the spine; it incorporates the Acceptable Use Policy, Privacy Policy, DPA, and — only on an affirmative election — the AI Research and Data Contribution Terms. The Privacy Policy defines four data-use states (service-only by default, then private improvement, research and training, and public commons); no data is used for training without an affirmative election, and none is published without a separate per-artifact contribution. The Subprocessor Register names every provider a request can reach, including model providers behind an inference gateway. The remaining notices cover cookies, biometric/voice/likeness, consumer health, and the research registry.
Contact
- Legal notices: [email protected]
- Privacy requests: [email protected]
- Security reports: [email protected]
- Abuse reports: [email protected]