Controller
The controller is LLMcode, for the service at https://llmcode.org. Contact: [email protected]. No data-protection officer is appointed. No postal address, registration number, VAT number, or Union representative is published. This policy is the Article 13 notice under Regulation (EU) 2016/679 for data collected from you.
What this version processes
An email account stores the email, a password hash, the display name, the time and version 2026-10-21 of the registration tick, whether the email was confirmed, and the link to the UT account. A Telegram sign-in stores the numeric Telegram id and uses the first name as the display name. The phone number is not asked and is not stored. Identity documents are not asked and are not stored.
A session stores a hash of the refresh token and the user-agent string. Sign-in and call limits use the IP address in the memory of the process. The usage log does not store the IP address. If you save an IP allowlist on a key, those addresses are stored with the key.
An order stores the top-up amount in USD, the UT quota, the payment-provider reference and the invoice link. No card number is stored. The public price list does not show a price. Dollar price is not set.
The usage log stores a request id, the profile, token counts, the UT charged, an estimate flag and the time. It does not store the prompt. It does not store the response text. LLMcode does not run GA4, Yandex Metrika, Plausible or Umami in this version.
Calls to the API
The text of a call is transmitted to the model-access supplier so a reply can be generated. LLMcode does not keep that text. Do not send special-category data under Article 9 of Regulation (EU) 2016/679. The forms do not ask for it. LLMcode does not build a file of it.
Purposes and legal bases
The account, the quota, the key metadata, the order, the transmission of the call, and mail about the account are processed to perform the contract. The legal basis is Article 6(1)(b) of Regulation (EU) 2016/679. Without the email, or without the Telegram id when you choose Telegram, the account cannot be opened.
The record of the tick (time and version 2026-10-21) is kept to show that you ticked the box. Where that record is consent, the basis is Article 6(1)(a). There is no marketing list and no separate marketing consent.
Rate limits and abuse controls use Article 6(1)(f). The legitimate interest is to keep the service available and to stop stuffing of passwords and scanning of keys. You may object under Article 21. LLMcode does not score you for advertising. Metering UT is performance of the contract. It is not a decision under Article 22 that refuses a contract from a profile of you.
Recipients
The model-access supplier receives the call, including the prompt, only to produce the reply. The supplier key and the supplier address are not published here.
When you pay, the crypto invoice provider you use receives the payment reference. In this product those providers are Crypto Pay and CryptoCloud, when that provider is connected. LLMcode stores the provider reference and the invoice link. No card number and no identity document go to them from these forms.
When a message is sent, the mail host receives the account email and the text of that message. The published sender is [email protected]. A verification code is kept only as a hash, for 10 minutes.
When you use Telegram Login, Telegram provides the signed fields. LLMcode stores the numeric id. Username, surname and photo are checked for the signature and are not stored as account fields.
Support and an administrator can see the account email, the name, key masks, orders and usage metadata in order to run the service. They do not see the key secret.
Transfers
A recipient above may be outside the European Economic Area. Article 13(1)(f) of Regulation (EU) 2016/679 asks the controller to say whether an adequacy decision exists and, if not, which safeguards are used.
LLMcode has not published an adequacy decision for a named country. LLMcode has not published a signed copy of the standard contractual clauses adopted by Commission Implementing Decision (EU) 2021/914. Ask [email protected] which tool applies to a given recipient. This page does not claim that a transfer safeguard is already signed.
Cookies and storage on your device
Article 5(3) of Directive 2002/58/EC, as amended by Directive 2009/136/EC, requires consent before information is stored on your device, except where storage is strictly necessary for a service you explicitly asked for. This version sets no analytics cookie.
llmcode_locale remembers EN or RU for one year. It is HTTP-only. It is set when you choose a language. It is strictly necessary to show that language.
llmcode_access keeps the signed-in session for 15 minutes. llmcode_refresh keeps it for 30 days. Both are HTTP-only. They are strictly necessary for the session you asked to open. Third parties do not read them.
llmcode_tg_consent lasts 10 minutes. It carries the ticked box into the Telegram sign-in you just started. It is not an analytics cookie. It is not sent to an advertising network.
The key llmcode-theme in local storage remembers light or dark on your device until you clear it. It is not stored as an account field. It is strictly necessary to show the theme you chose.
How long data stays
Account fields stay while the account is open. After you confirm closure, sign-in stops, sessions end, keys are revoked and remaining UT is burned. The email and the name are not overwritten by that step.
Usage detail is deleted after 30 days. Daily aggregates of token counts and UT have no fixed end date and contain no prompt and no response text. A password-reset link and a deletion link last 30 minutes. The verification-code hash lasts 10 minutes. The consent record stays with the account so the tick can be shown.
Your rights
You may ask for access, rectification, erasure, restriction, and a copy you can take with you, under Articles 15 to 20 of Regulation (EU) 2016/679. You may object to processing based on legitimate interests, under Article 21. Where processing is based on consent, you may withdraw that consent. Withdrawal does not make earlier processing unlawful. Data the contract still needs can be kept under Article 6(1)(b) until the account is closed or the law requires erasure.
You may lodge a complaint with a supervisory authority, in particular in the Member State of your habitual residence, your place of work, or the place of the alleged infringement, under Article 77. LLMcode has not published its own lead authority, because no Member State of establishment is published.
The registration form does not ask your age. This service is not directed at children.
Contact
Send privacy requests to [email protected]. Say the account email and the right you want to use. LLMcode will reply to that mailbox address.