Telemetry Disclosure
1. Why we collect telemetry
TitanOcta is local-first AI infrastructure. Telemetry submission is a condition of TitanOcta use across all tiers, free and paid. The data feeds community dashboards and the benchmark layer so every user benefits from aggregate performance insight across real hardware. This disclosure applies to TitanOcta; other SynOct products state their own collection, if any, on their product pages.
2. What we collect
This is the complete list. If it is not on this table, we do not collect it.
| Data point | Description | Collected |
|---|---|---|
| Hardware specs | CPU model, GPU model/VRAM, total RAM, disk type | Yes |
| Model identifier | Which model was routed to | Yes |
| Performance metrics | Tokens/sec, latency, throughput, VRAM usage during inference | Yes |
| Benchmark data | Standardised benchmark scores when running evals | Yes |
| Deployment stats | Agent start/stop events, uptime, restart counts | Yes |
| Crash reports | Stack traces, error codes, OS version at time of crash | Yes |
| Prompts | Your messages to agents | Never |
| Session content | Agent responses, conversation history, outputs | Never |
| API keys | Your third-party provider credentials | Never |
| Agent memory | Persistent memory stored by your agents | Never |
| File contents | Documents, code or data processed by agents | Never |
3. How telemetry is transmitted
- Sent over TLS to our ingestion endpoint.
- Tagged with an anonymous installation ID — not your account email or name.
- Payloads contain only the fields above. No ambient data collection.
- You can inspect the exact payload in your agent logs before it leaves your machine.
4. How we use it
- Community benchmarks: aggregated, anonymised stats on public dashboards.
- Routing optimisation: Flow uses aggregate performance data to improve routing recommendations.
- Stability: crash reports help us identify and fix bugs.
We do not use telemetry for advertising, user profiling or model training.
5. What we do not do
- We do not sell telemetry to third parties.
- We do not correlate telemetry with your identity for ad targeting.
- We do not train AI models on any user data — telemetry or otherwise.
- We do not share individual hardware profiles externally. Only aggregates.
6. Retention
Raw telemetry is retained for up to 90 days, then aggregated and anonymised. Aggregated benchmark data is retained indefinitely as part of the community dataset.
7. Your controls
- Inspect: all telemetry payloads are logged locally.
- Non-essential telemetry: crash reports and deployment stats can be disabled in account settings.
- Core telemetry: hardware specs and model performance data are required as a condition of use under the Terms of Service.
8. Changes
If we ever expand what we collect, we will update this page and notify all users at least 14 days before the change takes effect. The boundary — no prompts, no session content, no keys, no memory — does not change.