Privacy Notice — Perun The Trader web app

Last updated: 19 November 2026 · Terms version 2026-11-19

This notice covers the hosted Perun The Trader service at peruninthemachine.com/app: the account you sign in with, the trading worker that runs on our servers, and the browser dashboard. The Android app is a separate product that keeps your data on your phone — it has its own privacy policy.

Who is responsible

The service is operated by Łukasz Szczepankowski Perun in The Machine, a sole proprietor registered in Poland (CEIDG), ul. Mała 7, Kosewko, 05-180 Pomiechówek, NIP 5213271406, REGON 141477000. For anything in this notice — including any right you want to exercise — write to contact@peruninthemachine.com.

What we process, and why

We collect what the service needs to run your bot and keep your account safe, and nothing else. We do not use advertising, cross-site tracking or analytics that profile you.

Your account

  • E-mail address — the account identifier, and where verification, password-reset and security messages go. It is also used for the alerts you switch on.
  • Password — stored only as an argon2id hash. We never see or store the password itself.
  • Timestamps and the terms version you accepted — so we can show what you agreed to and when, and re-ask when the text changes.
  • Second factor — a TOTP secret stored encrypted, and single-use recovery codes stored as argon2 hashes. Two-factor sign-in is mandatory on this service.

Basis: performance of our contract with you (Art. 6(1)(b) GDPR); account security also rests on our legitimate interest in protecting the service (Art. 6(1)(f)).

Sessions and security records

  • Sessions — a random token, stored only as a SHA-256 hash, with creation, expiry and last-seen times, plus the IP address and browser user-agent that signed in.
  • Audit entries — sensitive actions are recorded (revealing a key, the kill switch, deleting an account, refused credential operations) with the time, IP address and user-agent. Failed sign-ins are counted on the account and lock it for a period; they are not written to the audit log.
  • Short-lived rate-limit counters — kept for minutes to stop password guessing and mailbox flooding.

Basis: legitimate interest in keeping the service and your keys secure, and in investigating incidents (Art. 6(1)(f)); where a record is required by law, legal obligation (Art. 6(1)(c)).

Exchange API keys and trading data

  • API credentials — the key, secret and (where the exchange uses one) passphrase, encrypted with AES-GCM under a key unique to your account. The per-account key is itself stored wrapped by a host key that lives outside the database. Where remote signing is enabled, the secret is held by a separate signing process and never reaches the trading worker.
  • What the exchange says about the key — the permissions it reports (spot, futures, withdrawal), so we can refuse a key that could move funds.
  • Trading data — your settings, orders, trades, positions, scans, backtests and alerts, in a database belonging to your account on our servers. This is the bot's working state and your history; without it the service cannot trade or report.

Basis: performance of the contract (Art. 6(1)(b)). A key is stored only because you bound it, and you can stop the bot and delete the key at any time.

Messages and notifications

  • E-mail — verification, password reset, deletion links and the alerts you enable, sent through Google Workspace from contact@peruninthemachine.com. We count how many messages were sent or failed each day; the counter holds no address.
  • Browser push (optional) — if you subscribe, we store your browser's push endpoint and keys and send new-trade notifications. Unsubscribing removes it; the subscription is never used for anything else.

Basis: contract for account e-mail; your consent for push notifications (Art. 6(1)(a)), which you can withdraw at any time in the browser or the account screen.

Cookies and browser storage

One session cookie keeps you signed in — HttpOnly, Secure, SameSite, and it expires. The browser also keeps your viewing preferences and a read-only cache of data you already loaded, so a dropped connection shows the last known state instead of nothing; writes are never cached, and signing out clears it. There are no advertising or cross-site tracking cookies.

Who else is involved

  • Hosting — the service and its databases run on a server operated for us in the European Union (netcup GmbH, Germany).
  • E-mail — Google Workspace delivers account and alert messages. Google may process them outside the EEA under the European Commission's standard contractual clauses.
  • Exchanges you connect — your keys are used to call that exchange's API on your instructions. The exchange processes your trading data under its own privacy policy; we do not control it.
  • Push services — only if you enable notifications, your browser vendor (Google, Mozilla or Apple) delivers them.
  • Offsite backups — copies on hardware controlled by us, not by a third party, encrypted at rest with AES-256-GCM; the key that decrypts them is kept in a separate file and never travels with a backup.
  • Authorities — when the law requires it, and nothing more than it requires.

We do not sell personal data, and we do not share it for advertising.

How long we keep it

  • Account and trading data — for as long as the account exists. Delete the account and it goes (see below).
  • Sessions — until they expire or are signed out.
  • Verification and reset links — until used or expired (verification 24 hours, password reset 1 hour, account-deletion link 30 minutes).
  • Audit entries — kept after an account is deleted, in pseudonymous form: the account row is gone, so the entry no longer identifies a person.
  • Backups — daily generations kept for 14 days on the server and up to the same window in a second copy. A deleted account is purged from the generations that still hold it, by a tombstone written at deletion, so backups do not quietly outlive the request.
  • Rate-limit counters — minutes.

Security

Traffic is TLS with HSTS. Passwords use argon2id; session and reset tokens are stored hashed; API keys are encrypted per account with AES-GCM and a key that never appears in the database; two-factor sign-in is required, and revealing a key, the kill switch and account deletion each need a fresh one-time code. Each account's bot runs as its own process with its own directory, and keys reach it through a file readable only by the service account. Where the exchange reports key permissions, a key that can withdraw is refused.

No system is perfect. If you believe an account or key has been compromised, stop the bot, revoke the key at the exchange, and tell us at contact@peruninthemachine.com.

Your rights

  • Access and a copy — the account screen exports your settings, trades and alerts as JSON. Credentials are never included: an export is what you did, not what can sign.
  • Deletion — the account screen deletes the account, its sessions, keys, second factor and trading database, after stopping the worker first. An account without a second factor can leave through a single-use link mailed to its address.
  • Rectification, restriction, objection, portability — write to us; we answer within one month.
  • Withdrawing consent — turn push notifications off. It does not affect anything done before that.
  • Complaint — you can complain to the Polish supervisory authority, the President of the Personal Data Protection Office (UODO), ul. Stawki 2, 00-193 Warsaw, uodo.gov.pl.

What deletion does, and does not, do

Deleting the account stops the worker and removes the account row together with its credentials, sessions, second factor and trading database. It does not close an open position. Stopping a bot may also cancel that position's exchange-side stop, so close your positions at the exchange first — the confirmation in the app says so before you press it.

Children

The service is for adults. It is not directed at anyone under 18, and we do not knowingly hold data of anyone under 18.

Changes to this notice

The notice and the terms carry a version, and your account records the one you accepted. A material change is shown and accepted again rather than applied retroactively — a page left open across a change is refused at signup.

Contact

Email: contact@peruninthemachine.com

See also the Terms of Service for the hosted service.