Policies and Team Audit
Read the effective policy and its displayed version on the live pages:
- Terms of Service at
/terms - Acceptable Use Policy at
/acceptable-use-policy - Privacy Policy at
/privacy - Refund Policy at
/refund
Unpublished policy drafts are not offers and do not show a past refund promise. Effective versions, not a seeded draft ID, govern new starts. Guest browser/API/MCP access requires actual acceptance of the effective Terms and Acceptable Use Policy; creating a connection does not accept them for you.
English is the canonical version. An approved translation may be shown for your locale; when it is unavailable, Chab shows canonical English. Translation-only corrections do not change the canonical policy version. A change in legal meaning creates a new version and may require acceptance again when that version becomes effective.
Acceptance required
Every user accepts the current Terms for browser entry. A team owner or an admin with settings permission accepts the current team Terms and Acceptable Use Policy before any new API operation or marked team mutation. API tokens cannot accept policies. Missing team acceptance returns policy_acceptance_required with policy IDs and safe URLs before rate or credit effects. Its idempotency claim is released. Replaying an already accepted operation keeps the policy version captured at its original start.
The team audit timeline begins at its displayed coverage date; Chab does not invent earlier history. It includes customer-safe categories such as policy, access, security, support, privacy, operation controls, team membership, projects, and API-token changes. Visibility follows the viewer's current team role. Corrections are appended instead of rewriting prior events, and sensitive content, credentials, raw addresses, and private diagnostics are excluded.