Spaces:
Running
Running
| # Data Processing Notice (Beta) — Draft for site / ToS | |
| **Not legal advice.** Have counsel review before production. This aligns product behavior with [`strategy-memo.md`](./strategy-memo.md) and [`beta-launch-checklist.md`](./beta-launch-checklist.md). | |
| --- | |
| ## What we process | |
| When you call `POST /api/v1/optimize` (and related APIs), you may send: | |
| - Agent execution logs: `input`, `output`, token counts, model names, agent identifiers | |
| - Optional trace IDs and feedback metadata | |
| We use this to: analyze cost patterns, suggest compression/routing, enforce quotas, improve policies (HERMES), and billing. | |
| --- | |
| ## What we do not do (public beta) | |
| - We do **not** transparently intercept your live LLM API calls unless you separately agree to a future gateway product. | |
| - We do **not** sell your data to third parties. | |
| --- | |
| ## Subprocessors | |
| - **Hosting:** Google Cloud (Cloud Run, optional Cloud SQL) | |
| - **Compression (if enabled):** DeepSeek API when `DEEPSEEK_API_KEY` is used server-side — clarify in your plan whether TCG or customer supplies the key | |
| --- | |
| ## Retention | |
| - Define: e.g. audit logs 90 days, billing records 7 years, shared memory until tenant delete | |
| - [ ] Fill before public launch | |
| --- | |
| ## Your obligations | |
| - Obtain any end-user consent required if logs contain personal data | |
| - Do not send secrets, API keys, or regulated health/financial data in logs | |
| - Rotate API keys if leaked | |
| --- | |
| ## Rights | |
| - Contact: [support email] | |
| - Deletion: [process TBD] | |
| --- | |
| ## Beta disclaimer | |
| Features and retention may change. See [Public Beta vs Roadmap](../README.md#-public-beta-vs-roadmap). | |