Community data policy
Community is the free class. You pay with data instead of money, so this page says exactly what that data is. Paid classes (Advanced, Enterprise) are not covered here and are never used for training.
1. Who sees your request
- Cloudflare carries traffic to
api.tessovix.comand terminates TLS, as it does for any site behind it. - The Tessovix gateway reads the request to route it.
- One community node runs the model and therefore sees the prompt and the reply. Community requests are not end-to-end encrypted. Do not send other people's personal data through the Community class.
- The local
tessovixproxy replaces API keys, tokens and similar secrets with placeholders on your machine before anything is sent, and restores them in the reply. - The gateway regularly sends decoy requests carrying unique tokens. A node that leaks one is caught and banned.
2. What we keep
| Data | Contents | Kept |
|---|---|---|
| Usage ledger | Time, account name, model, how the request was served, serving node. No prompt or reply text. No IP address. | While the account exists (quotas and contribution points depend on it) |
| Conversations for training | Only with training consent. Prompt and reply of successful chat requests, after masking (section 3). | 12 months, then deleted automatically |
| Gateway logs | Errors and timings. No prompt or reply text, no API keys. | 14 days |
| Client telemetry | Error class, retry counts, time to first token, client version, operating system. Never prompt text, keys or full IP addresses. | Kept only as aggregated metrics |
| Offsite backup | Encrypted copy of the ledgers and the last 7 days of training conversations. | 30 days |
3. Masking before storage
Before a conversation is written to disk the gateway:
- replaces secrets (API keys, tokens and similar) with placeholders;
- replaces emails, Vietnamese phone numbers, CCCD/CMND numbers, payment card numbers and IPv4 addresses with fixed tags such as
‹EMAIL›; - encrypts each record (ChaCha20-Poly1305) and files it under a pseudonym instead of your account name.
Masking is pattern based. It does not catch names or street addresses, and unusual formats can slip through. Treat Community like a public forum.
4. Training consent and withdrawal
- Conversations are kept for training only when your key has training consent. Without it, nothing beyond the usage ledger is kept.
- Withdraw at any time with
tessovix data delete. The withdrawal is recorded, collection for your key stops, and every stored conversation of yours is deleted. Copies in offsite backups expire within 30 days. - Or email privacy@tessovix.com to withdraw or to ask what we hold about you.
5. Telemetry
- The proxy sends client telemetry by default for Community keys. Turn it off with
TESSOVIX_TELEMETRY=0. It is off by default for paid classes. - Nodes report operating system, architecture and job counts. Node owners turn this off with
--no-telemetry.
6. Advertising
Community may later show ads on Tessovix web pages and dashboards. Ads are never inserted into model output, and conversations are never sold or shared with advertisers.
7. Giving back
If Community conversations are used to train a model, the resulting model or a filtered dataset will be released openly.