Privacy Policy

Version 0.1 (draft) Effective date: 11 October 2026

This page says what personal data tradectl collects, why, who else gets it, how long we keep it, and what your rights are. It covers the website tradectl.com (with app.tradectl.com and docs.tradectl.com), the Lab, the bot and the shared Telegram bot.

1. Who is responsible

The controller of your data is tradectl. Full details of the seller are given on request by email. Contact for privacy questions: support@tradectl.com.

We have not appointed a data protection officer.

2. The short version

  • The bot runs on your machine. It keeps your exchange keys, trade database and configs there. Our server never queues, stores or forwards your exchange keys or your Telegram bot token. Our server does not send settings to your bot. Some other data passes through it, in the cases below (Telegram, trade reports on paid plans).
  • We keep what we need for your account, your plan and your payments.
  • Bots on a paid plan send us their closed trades and technical metrics. Bots on the Free plan do not send trades.
  • We do not use advertising cookies. We count page views without cookies and without storing your IP address. Only if you click "Accept", Microsoft Clarity records how you use our sites, so we can fix the confusing places.
  • We do not sell your data.

3. What we collect, why, and on what legal basis

Your account

  • What: when you sign in with GitHub: your GitHub id, user name, profile picture link and email. With Google: your Google id, name (we make a user name from it), email and profile picture link. If GitHub gives no email, we ask you to type one. Also: your plan, when you signed up, and a session id.
  • Why: to create your account, sign you in and give you your plan.
  • Legal basis: the contract with you (GDPR Art. 6(1)(b)).

API keys and servers

  • What: the API keys you make (we store only a hash), setup codes (only a hash), and for a server: its host name and a machine id (the host name plus random letters).
  • Why: so the Lab, your bots and your servers can sign in to your account.
  • Legal basis: contract (Art. 6(1)(b)).

Your bots

  • Bot registration (any plan, when you are signed in): machine id, bot name, the address and port where the Lab can reach the bot (often your public IP address), the fingerprint of the bot's certificate, and the bot's connection details locked with your pair key. Why: so the Lab can list your bots and connect to them. Only your Labs and your servers have the pair key. Our server cannot read your bot's access key, so it cannot use it to connect to your bot. Bots older than 0.2.6 send the access key unlocked; our server does not keep it. When a bot first starts as version 0.2.6, and whenever it gets a new pair key, it makes a new access key, so every key our server ever saw stops working. One exception, until we sign strategy files: a strategy file you install with tradectl install comes from our server and runs on your machine. If our server were broken into, a changed strategy file could read your pair key, and with it reach all your bots. The server setup command from the Lab checks the shot file against a hash published on GitHub; strategy files you install or update later are not checked yet.
  • Live check-in (paid live bots, every 10 minutes): machine id, bot name, start time, last seen. Why: to count your paid bots.
  • Closed trades (only bots on Starter or Pro): strategy name, bot name, config name, exchange, market, coin, side, entry and exit price, size, leverage, profit, close reason, order ids, open and close times, live or demo. Why: to show you your own statistics, and, only if you agree (see "Public statistics"), to build public statistics.
  • Technical metrics (only Starter or Pro): uptime, memory, number of exchange requests, delays, number of positions, strategy names. Why: to see that bots work and to find problems.
  • Watchdog heartbeat: host id, version, number of accounts watched.
  • Legal basis: contract (Art. 6(1)(b)) and our legitimate interest in running and fixing the service (Art. 6(1)(f)).

Strategies you upload

  • What: when you upload a strategy (tradectl upload): its name, description, source code, built files and versions.
  • Why: to build it and let you install it on your machines.
  • Legal basis: contract (Art. 6(1)(b)). Kept until you delete it or close your account.

Portfolio page

  • What: what you type on the Portfolio page: coins, balances, leverage and pairs, and daily snapshots of the total.
  • Why: to show your portfolio and its history.
  • Legal basis: contract (Art. 6(1)(b)). Kept until you change it or close your account.

Public statistics (only with your consent)

  • Public numbers on our website use live trades only from users who ticked the statistics checkbox. It is off by default. You can turn it off at any time.
  • Public numbers show the strategy, coin, prices, size, profit in percent and time. They never show your name, email, account id, exchange or order ids.
  • Legal basis: your consent (Art. 6(1)(a)).

Payments

  • What: your invoices (plan, period, price, the exact amount to pay, status, dates). For each incoming Binance Pay transfer: its id, time, amount, currency, and the details Binance gives about the sender (the sender's Binance nickname, and maybe a Binance id).
  • Why: to match your payment to your invoice, to give you your plan, and to keep accounting records.
  • Legal basis: contract (Art. 6(1)(b)) and our legal duty to keep accounting records (Art. 6(1)(c)).
  • We never see your card or bank details.

Email

  • We send a welcome email, plan reminders (7 days and 1 day before your plan ends, and when it ends) and payment messages. We do not send marketing email.
  • Legal basis: contract (Art. 6(1)(b)).

Telegram (only if you link it)

  • What: your Telegram chat id and user name, and which bot you talk to. Your bots' alert messages and your commands pass through our server to Telegram and back. Commands you send to the shared Telegram bot (for example /stop, /pause, /panic) go through our server to your bot.
  • You can avoid our server: give your bot its own Telegram bot token instead.
  • Legal basis: contract (Art. 6(1)(b)).

Bot settings

  • Our server does not send settings to your bot. Bots from version 0.2.6 refuse settings from our server; update older bots. You change settings in the Lab over a direct connection to the bot, or on the machine the bot runs on.

Security and logs

  • Our servers keep technical logs. They can contain your account id and user name. Our web servers log each request: the page, the page you came from, and your browser's user agent (not your IP address). We use your IP address for a short time to stop abuse: for page-view counting, for 1 minute in memory; for setup codes, a hashed IP for 15 minutes.
  • Legal basis: our legitimate interest in keeping the service safe (Art. 6(1)(f)).

Page-view counting

  • We count page views and download clicks per day: the page, and the domain of the website you came from. The page-view counters store no cookie, no IP address, no browser details and no visitor id. The counters cannot be linked to you. If your browser sends "Do Not Track" or "Global Privacy Control", nothing is counted.

Session recording (Microsoft Clarity)

  • What: only if you click "Accept" on the banner: the pages you open, clicks, mouse movement and scrolling, screen size, browser and device type, and your approximate country. Microsoft sees your IP address. Text you type is never recorded. In the dashboard, your personal data (email, balances, profit, trades, bot and server details, strategy code) is hidden in the recording. When you are signed in, your account id is attached, so we can see the visits of one account.
  • Why: to find the places on our website, docs and dashboard that confuse people, and fix them.
  • Legal basis: your consent (Art. 6(1)(a)). If you do nothing or click "Decline", nothing is recorded. If your browser sends "Do Not Track" or "Global Privacy Control", nothing is recorded and we do not ask. You can withdraw at any time: , or "Cookie settings" in the dashboard menu and at the bottom of the docs.

4. Cookies and browser storage

  • auth_session: keeps you signed in, 30 days. Needed for the website to work.
  • github_oauth_state, google_oauth_state, google_oauth_verifier: protect the sign-in, 10 minutes.
  • In your browser's local storage (not cookies): theme (light or dark), lang (language), lab-download-clicked (ticks a step on the Home checklist).
  • tc_consent: remembers your answer to the recording question, 180 days.
  • Only if you accept recording: Microsoft Clarity's cookies _clck (1 year) and _clsk (1 day).
  • We use no advertising cookies.

5. Who else gets data

  • GitHub and Google: when you sign in with them. Lab and bot downloads and updates are files on GitHub, so GitHub sees your IP address when you download.
  • Resend: sends our emails. It gets your email address, your user name and the message.
  • Telegram: if you link it. It gets the messages for your chat.
  • Binance: you pay through Binance Pay. We read the incoming transfers of the receiving account with a read-only key.
  • jsDelivr: blog posts load one script from it, so it sees your IP address.
  • Binance on the Portfolio page: your browser loads prices and coin logos straight from Binance.
  • Microsoft (Clarity): records how you use our sites, only if you accept. Microsoft may also use this data to improve its own products.
  • Our hosting provider: Hetzner, in Germany (EU).
  • Authorities, when the law requires it.

6. Data outside your country

Some of the companies above are in the USA or other countries outside the EU. Our servers are in Germany. GitHub, Google, Resend and Microsoft are in the USA. For them we rely on the safeguards these companies offer, such as the EU-US Data Privacy Framework or Standard Contractual Clauses.

7. How long we keep data

  • Account, API keys, bot registrations, trades, Telegram link: while your account is open. Revoked keys and unlinked Telegram chats are removed when you revoke or unlink them.
  • Session: 30 days.
  • Live check-ins: 1 day after the bot was last seen.
  • Detailed bot metrics: 30 days. The latest snapshot per bot: while your account is open.
  • Watchdog heartbeats: 7 days.
  • Page-view counters: 400 days (they hold no personal data).
  • Session recordings: 30 days in Microsoft Clarity. A few that we mark to keep: up to 13 months.
  • Invoices and payment records: 5 years.
  • Server logs: 90 days.
  • Backups: 30 days.

When you delete your account, we delete your data, except what we must keep by law. We do it within 30 days of your email.

8. Data we do not hold

  • Your exchange API keys and your Telegram bot token. Our server never queues, stores or forwards them, and the website does not store them. They stay in your bot's config on your machine.
  • Your pair key, and your bots' access keys in a form we can read. The pair key stays in your Labs and on your servers. Our server cannot read a bot's access key (see "Your bots" for the one exception, strategy files).
  • Your money or crypto. Your bot trades straight on your exchange account.
  • Your bot's trade database, configs and logs, which stay on your machine.

9. Your rights

You have the right to:

  • get a copy of your data;
  • correct wrong data;
  • have your data deleted;
  • limit how we use it;
  • get your data in a common format and move it;
  • object to use based on our legitimate interest;
  • take back your consent at any time (for public statistics: untick the checkbox). This does not affect what was done before.

To use these rights, write to us at the address in section 1. There is no self-service delete button yet. We answer within one month.

You can also complain to the Ukrainian Parliament Commissioner for Human Rights, who supervises data protection in Ukraine. If you live in the EU, you can complain to the data protection authority in your country.

10. Do you have to give us data?

  • To have an account, you must sign in with GitHub or Google. Without it, you can still use the Lab and demo bots without an account.
  • To buy a plan, we need your payment details as described above.
  • Bots on paid plans always send their trades and metrics. This is part of the paid plan.
  • Telegram and public statistics are optional.

11. Automated decisions

We do not make decisions about you by automated means that have legal or similarly important effects. Software applies the limits of your plan, and matches payments to invoices by amount. A person checks every payment that does not match.

12. Security

We use HTTPS. API keys and setup codes are stored as hashes. Your bots' connection details are locked with your pair key, which our server never gets.

13. Children

tradectl is not for anyone under 18.

14. Changes

When we change this policy, the date and version at the top change. For important changes, we email you first.

This policy is in English and Ukrainian. If the two texts differ, the Ukrainian text applies.