Terms of Service

Terms of Service

Draft pending counsel review — not legal advice, not in force until approved by the owner

These terms are a working draft. The facts below are drawn from the operator’s trust documents (ops/docs/trust/ in the ops repository); the legal obligations are template language for counsel to complete. Reviewed by: (pending) · Reviewed on: (pending).

1. The services

These terms cover the tcpsystems services operated under the tcp.systems domain, including the acumen API and the consumer surface at ai.tcp.systems (source: ops/docs/trust/DPA-subprocessors.md, “What is processed”). The operator is [[REGISTERED-ENTITY]], [[ADDRESS]]: these placeholders stay until counsel confirms the registration details; none are invented here.

2. Accounts and API keys

Access to the API is authenticated with per-customer API keys that are revocable by the customer (source: ops/docs/trust/DPA-subprocessors.md §7). You are responsible for activity attributed to your keys: the key id is the unit of authentication and attribution in the request metadata the router records (source: ibid., §2).

3. Acceptable use

You must use the services in line with the acceptable use policy. Automated agents and other software acting on your behalf act under your API key, and their actions are attributed to you.

4. Your content

Prompts and completions are processed to deliver the requested inference and are not written to the router database: the optional exact-match cache that once stored response bodies was disabled on 2026-10-20 and its rows purged (source: ops/docs/trust/retention-schedule.md, “Row 5 in detail”). Requests are routed to upstream inference providers; see the sub-processors register for who those providers are and the open actions on cataloguing them. For business customers, the operator acts as a processor of customer content under the DPA.

5. End of service and deletion

When an agreement ends, content and metadata are deleted or returned, except records the law requires to be kept (accounting records: six years), and deletion is certified on request (source: ops/docs/trust/DPA-subprocessors.md §3.10). Retention periods per data category are published in the retention policy.

6. Changes and contact

These terms are a draft and will change before they take force. Questions about this document and any data-protection question: security@tcp.systems (source: ops/docs/trust/DPA-subprocessors.md §9).