Privacy Policy
This policy explains what we collect, why, who processes it for us, and how you can ask us to delete it.
1. What we collect
- Account information: your email, your password (stored hashed), sign-up and last sign-in times, and any invite, referral, or promo code used at sign-up. If you link a third-party sign-in, that account's identifier.
- Call records: for each call, the time, key, model, token counts, cost, duration, and the IP address and client information (User-Agent) it came from.
- Payment information: order amount, status, and the IP address used to place the order. Card numbers are handled by Stripe; we do not store them. For USDC payments, the paying wallet address and the transaction hash.
- Security and error logs: the IP address, client information, and error details of failed requests.
2. Request content
Requests you send through the API have to be passed to an upstream model provider to get a response.
By default we only record the usage information above and do not keep the body of requests or responses. To troubleshoot problems or deal with abuse, we may turn on full content logging for specific keys, specific models, or all requests.
If content moderation is turned on, request content is sent to a moderation service for checking, and we keep a short excerpt of anything it flags.
If usage analysis is turned on, we automatically classify the text in requests and responses, for example by task type, subject area, and language, to understand what people mainly use TokLens for. The analyzed text includes conversation content, tool calls, and tool output, but not system prompts:
- Before classification, common formats such as keys, tokens, email addresses, mainland China mobile numbers, Chinese ID numbers, and card numbers are masked automatically. Masking works by matching formats and cannot guarantee that all personal information is masked.
- The masked text is processed by our own classification model. It may also be sent to an upstream model provider to produce reference results that we use to check and improve the classification.
- Classification results are shown only to you. Outside your account, we only use aggregate statistics that cannot identify individual users.
If you do not want your requests included in usage analysis, or want existing analysis results deleted, email [email protected].
Please do not put sensitive information in requests that you do not want processed.
3. How we use it
- To run the Service: authenticate you, handle calls, and bill by usage.
- To show your usage, costs, and orders in the dashboard.
- To send verification codes and notices about your account and orders.
- To prevent fraud and abuse, troubleshoot problems, and keep the Service secure.
- To measure overall usage, such as common clients, models, and task types, and decide what to improve.
We do not sell your personal information.
4. Service providers
We only share what is needed to provide the Service, with these providers:
- Stripe, to process card payments.
- Cloudflare, for bot checks, sending email, and some data storage. The bot check sends your IP address to Cloudflare.
- Blockchain networks. USDC payments are recorded on a public blockchain that anyone can look up.
- Upstream model providers, to process your API requests. When usage analysis is on, they may also receive masked text to produce reference classification results.
- Cloud hosting providers, which host our servers and data.
- Third-party sign-in services, only if you link one.
These providers handle data under their own privacy policies. We may also disclose information to authorities when the law requires it.
5. Browser storage
The website uses your browser's local storage (localStorage and sessionStorage) for your sign-in state, theme, table settings, remembered email addresses, and keys you look up on the home page. Those keys stay in your browser.
The website has no analytics or ad tracking and sets no cookies for them. Linking a third-party sign-in uses a temporary cookie to verify the sign-in flow. The Stripe and Cloudflare scripts loaded for payment and bot checks may set their own cookies.
6. How long we keep it
- Account information and call records: for as long as your account exists.
- Error logs: deleted automatically after about 30 days.
- Payment orders: as long as accounting and legal requirements call for.
- Full request content logs: there is currently no fixed deletion period. You can ask us to delete them.
- Usage analysis: unprocessed text is deleted after about 1 hour, and masked text is deleted once it is classified. Classification results are kept for about 1 hour. Reference results from upstream model providers, and text waiting to be sent to them, are kept for up to 1 day. Samples used to improve the classification, which contain masked text and classification results, are kept encrypted for about 7 days. Each analysis leaves a record with no text, only hashes, character counts, and masking counts, which is kept with your call records. Aggregate statistics that cannot identify individual users are kept indefinitely.
Deleted data may remain in backups for a while, until the backups are overwritten.
7. Your rights
You can see your usage, costs, and orders in the dashboard. You can also email us to access, correct, or delete your personal information, or to close your account.
After your account is closed, records we are legally required to keep, such as payment orders, are kept until that period ends.
8. Security
Passwords are stored hashed, and you can also sign in with an email code alone. No online service can rule out every attack; if you notice anything unusual with your account or keys, contact us promptly.
9. International processing
Our servers and those of our providers may be outside your country or region, and your information may be processed and stored there.
10. Children
The Service is not intended for minors. If you believe a minor has given us personal information, contact us and we will delete it.
11. Changes to this policy
We may update this policy. When we do, we will update the effective date on this page.
12. Contact
Privacy questions or deletion requests: [email protected].
