DATA USE · CONSENT VERSION 2026-11-12.v4

How devseek uses your data

devseek is free. It is paid for by turning the prompts and responses of users who agree into datasets that we sell. This page says all of it.

This page is available in several languages. If a translation differs from the English version, the English version prevails.

1. What we collect

• Everything you send: the messages (prompts), the model's responses, the model name, the time, and the consent version and time. Agreeing to this is a condition of the free service.
• Everyone: contact email, level, and usage records such as request counts, token counts, response times and whether each request was about coding (no content).

2. Why

To build anonymised conversation datasets and license (sell) them to third parties. That revenue keeps access free. Usage records are also used to run the service: abuse prevention, levels and status measurements.

3. Who receives it (buyer categories)

• Companies and labs that train or evaluate AI models
• Dataset brokers and marketplaces
• Academic research institutions

We do not sell account data (email). Dataset records are grouped by a random hashed ID, not your account.

4. What we remove before export

• Email addresses, phone numbers, card numbers, IP addresses and national ID numbers are replaced with placeholders.
• Any record that shows a secret — API keys, tokens, passwords, private keys — is dropped entirely.
• This is automated and not perfect. Do not send secrets or other people's personal data.

5. Storage and retention

Prompt records live in a separate database from account data. Each record is compressed and then encrypted with AES-256-GCM. The key is only in the server's configuration and only the operator can access it. Records are deleted after 30 days. Records already exported into a dataset are moved off the server to the operator's storage and follow the buyer's contract.

6. Your controls

• From the dashboard you can download your data (JSONL), delete stored prompts or delete your account at any time.
• Deletion applies to the stored records and to every future export.
• Questions and deletion requests: [email protected]

7. Coding classification

To set your level we classify each request as coding or not. Most requests are decided by local rules on our server. Some unclear requests are sent as one short yes-or-no question, built from the request text, to jev, a decision model run by opencode. Only the verdict (coding or not, and where it came from) is kept.

8. How sign-up works

There is no developer or GitHub verification. Sign-up needs a Cloudflare Turnstile human check, verified on our server, and a contact email; disposable addresses are refused and sign-ups are rate-limited per IP and per email domain. Whether you use devseek for coding is judged afterwards, request by request: local rules decide clear cases and jev decides unclear ones. Coding raises your level; other use lowers it.