Fleet telemetry (payload fingerprints, spread counts, R estimates, control-registry state) is per-operator / per-fleet isolated, and used only to defend the operator's own fleet; no sale of operator data, no cross-operator use, no telemetry beyond what the product surface documents. Fingerprint queries return spread state for a fingerprint, not another operator's message content. Per-operator isolation is enforced server-side: identity comes from your Bearer token, never from request bodies.
Outbreak alerts and quarantine records are the operator's own operational records, retained under the production retention policy: operational state persists while the account is active; daily backups are kept 30 days and then pruned. API tokens are stored only as SHA-256 hashes; breaker keys are held in a separate key store file with owner-only permissions.
Support correspondence (support@textforagents.com) is handled under the company's ordinary support privacy practice.
Legal state (stated plainly): patentability memo LEGAL-167 on file (FILE-NARROWED); FTO screen LEGAL-168 on file (AMBER — no plausible read on the product as designed, no RED; keep-clear conditions apply: no per-segment length-threshold injection scoring, no address-placeholder substitution).