Privacy Policy
Last updated: 14 Nov 2026
This policy explains what personal data CS2FarmBot stores, why, and for how long. We keep as little as we need to run the service and keep it secure.
1. What we store
- Account details: your email address, your username, your password as a one-way hash (we never store or see the password itself), and your device's time zone (for the dates in our emails and the days in your Activity).
- Consent choices: when you accepted the Terms of Service and this policy, and whether you asked for emails about news, updates and offers.
- Security data: the IP address and browser description of your sign-ins and sessions, and a log of security events such as sign-ins and password changes. We use these to protect your account and to stop abuse.
- Steam account sign-in details: for each Steam account you add, its login name, its password and its Steam Guard shared secret, and its identity secret (it can approve trades and Market listings) when you enter it (when adding the account, later in its settings, or in a list matched by login name) or when an uploaded maFile contains one. The identity secret is used only if you turn auto-trade or the Steam Market on for that account with its switch (adding the secret never turns either on); with both off it is not used. Adding a line or maFile for an account that is already on your list replaces the saved password or secrets it contains. Turning auto-trade or the Steam Market off for an account keeps its identity secret; removing the account deletes it. From an uploaded maFile we read only the account name, these secrets and the SteamID; the rest of the file is not kept, and the SteamID counts only after our servers have signed in to the account. Passwords and secrets are stored encrypted: they are sealed so that only our farm servers can open them (this website itself cannot), are never shown again, and are used only to sign in to that account and run the service. Each account also keeps the proxy country you chose for it (Germany unless you change it): the country of the home internet line it signs in to Steam through.
- Steam profile data: the SteamID, profile name, avatar picture address, level and this week's progress of each account you add, as our servers see them while they farm.
- Farming records: when our servers signed in to each Steam account and played on it, which of our farm servers did it, whether the account has CS2 Prime, and problems such as disconnects, cooldowns or the account being in use by you. Our staff use them to run and protect the service; you see only each account's status.
- Bans and cooldowns: the restrictions on each account: what CS2 shows our servers while they play (a VAC ban, a matchmaking cooldown or ban and its reason, Steam refusing the sign-in) and what Steam's public ban list says. For that list, our servers send the SteamID of each account they have signed in to Steam's public Web API every few hours and soon after they notice a problem; it answers whether the account has VAC, game, Steam Community or trade bans. We keep each restriction with when it started and ended, when it ends if known, and where it was seen; you see them on the account's page.
- On our farm servers: our farm servers sign in to your Steam accounts automatically from their own network addresses. They receive your sealed sign-in details only for an account they are about to farm and open them only in memory. To stay signed in, a farm server keeps the sign-in token Steam gives it for each account, encrypted, on that server only; this website never receives it. Each account also gets one fixed set of PC details (its "machine identity") so Steam always sees the same PC; a sealed backup of it is kept on this website, which cannot read it.
- Drops and activity: the items claimed for each account, their market price when they dropped and the latest known price, and a log of what happened on your accounts (for example "reached this week's drop" or "needs your Steam Guard code"). We also keep when you last opened Activity, so its tab can show how many new problems you haven't seen yet.
- Match history: for every match our servers play on an account: when it started and ended, the map and game mode, the account's own kills, deaths, headshots and score, the XP it earned and how the match ended (for example "XP cap reached" or "server shut down"), and while a match is being played, its map and start time. Nothing about the other players or the game servers is kept with it.
- Inventory: the items in each account's CS2 inventory as our servers last saw them: name, Steam's item id, whether it can be traded (and until when it is trade protected) and its market price, with the total value. Each new look replaces the previous one.
- Auto-trade: your Steam trade link (one per site account), a change you asked for and when it takes effect, what you chose to send (farmed drops only, or all tradable items), which accounts have auto-trade on, and a log of every trade our servers made: which account, the items (name, Steam's item id, price), the Steam trade offer id, when, what was sent and how it ended (sent, waiting for you, accepted, declined, expired, failed or skipped, with the reason). The 6-digit codes we email to confirm trade link changes are stored only as a keyed hash and work for 10 minutes. Our farm servers use the trade link only to send trade offers to it, and the identity secret only to confirm those offers and, for an account with the Steam Market on, its Market listings and buy orders.
- Steam Market: what you chose for the Market (what to sell, how, and whether to buy TF2 keys), which accounts have it on, and a log of what our servers did on the Steam Community Market for each account: the item, Steam's listing or buy order id, the price and currency, how many, when, and how it ended (listed, sold, bought, taken down, cancelled or failed, with the reason and Steam's own message). Also each account's Steam Wallet balance and currency, its Market status as Steam last answered, and how many TF2 keys it holds. The 6-digit codes we email to confirm "Everything" are stored only as a keyed hash and work for 10 minutes.
- Service records: your invite code use, your plan, your balance history, your purchases and the drops claimed for your accounts.
- Medal Boost: your Medal Boost (how many slots, the period you paid for, when it renews, pauses or ends, whether auto-renew is on, and a change of slots you scheduled for the next renewal), which of your accounts are in its slots, since when, and which leave at the next renewal. For each account in a slot: its CS2 level and XP, the tier and year of its Service Medal, and the year it reached red at level 40, as our servers report them while they play.
- Your dashboard settings: the account groups you create and which accounts are in them, the columns you chose for the accounts list, and your bulk Start / Stop / Remove actions (when, which accounts).
- API: if you make an API key, we keep only a one-way hash of it and its first 8 characters (so you can tell which key it is), the IP address it works from, when it was made, when and from which IP address it was last used and last refused, and, once it stops working, when and why (refreshed, deleted, or revoked by our staff). Every call made with your key is logged with the IP address it came from, the time, the method, the path (never the values sent), the result and how long it took.
- Discord (optional): if you link your Discord account, its user ID, username, display name and avatar. If you add a Discord webhook for notifications, its address is stored encrypted, together with your notification choices.
- Our Discord server: if you open a support ticket there, we keep a copy of the ticket's messages and your Discord name and user ID on our own servers for 90 days after the ticket is closed, and staff keep a copy in a private log channel. If staff block someone from opening tickets, our bot keeps their Discord user ID and the reason until the block is lifted. When your linked Discord account gets or loses the Customer role, our bot posts a short note in a private staff channel with your Discord name and your CS2FarmBot username. When you join or leave the Discord server, our bot tells our website, only to give or remove the Customer role.
2. Payments
When you pay, we store the order email, the amounts in euros and in crypto, the receive address we showed you and the transaction hashes of the payments we received. Blockchain transactions are public and permanent: anyone can see them, and neither we nor you can delete them. We do not handle or store card or bank details. Exchange rates come from a third-party price feed. Our servers look up payments on public block explorers and blockchain services; your browser does not contact them.
If you pay with skins (CS2, Dota 2 or Rust), you trade them on SkinsBack (skinsback.com), an independent service with its own privacy policy. Its payment window opens inside our order page (loaded straight from skinsback.com, so SkinsBack sees your IP address and browser like any site you visit) or in a new tab; there you give it your Steam trade link and accept its trade offer in Steam. We do not see what you enter there. We send SkinsBack only the order number, the minimum amount and the addresses to send you back to; not your email. SkinsBack tells us the deposit's status, its id, the value it credited and when a trade hold ends, and we store those with the order. SkinsBack also reports the Steam account that traded and a risk summary; we do not store them.
3. Live view
When you open the Live tab of one of your Steam accounts, the farm server playing it sends us, only while you watch, what the live view shows: the positions, facing, team, health and weapon of the players on the bot's match server (about 16 times a second), their kill and death counts, the time left in the match, your bot's own armour, ammo, score, crosshair and view angles, the hits it lands, and the kills as they happen. Only you can watch your own accounts; there are no share links. Other players are shown with the in-game names and Steam profile pictures they use; for the pictures, their Steam IDs are sent to your browser with them, and your browser loads the pictures from Steam. The game server's address is not sent to the website, and nothing shows which other players are bots. The live view is passed straight to your browser and is not stored.
4. Why we use it
- To create and run your account and the service you bought.
- To farm: our farm servers sign in to each account automatically, play deathmatch or Arms Race on it and claim its weekly drop. Accounts without CS2 Prime are not farmed.
- To keep accounts secure, limit repeated sign-in attempts and investigate abuse.
- To protect Steam accounts from misuse: we record whether each sign-in to a Steam account worked. After a failed sign-in we don't try that account again until you replace its details, and if many sign-ins of one customer fail, the accounts that never signed in are paused and our staff review it.
- To send account and security emails, such as password reset links, sign-in codes and the code that confirms your email address when you create an account.
- To show your dashboard. An open dashboard page asks our server every few seconds whether anything changed, so it stays up to date without reloading. With "Live pop-ups" on (Account settings), new activity and finished matches also show as pop-ups; nothing about this is sent to anyone else.
- To send news, updates and offers, only if you opted in. You can opt out at any time by contacting us.
5. Who processes it for us
- Amazon Web Services (Amazon SES) sends our emails, so it receives your email address and the content of the messages we send you.
- Cloudflare sits in front of the site to protect it and may check that a visitor is human. It sees your IP address and basic browser data when you visit.
- YouTube (Google) plays our demo video on the home page in its privacy-enhanced mode. Nothing is loaded from YouTube until you press play; then YouTube receives your IP address and basic browser data and may set cookies.
- Discord receives the notifications you turn on (through your webhook) and, if you link your account, confirms who you are on Discord.
- Our servers are rented from a hosting provider in the European Union.
We do not sell your data and do not share it for advertising.
6. How long we keep it
- Account details: for as long as your account exists.
- Sessions: until you sign out or they expire (30 days without use).
- When you last used the site and the IP address you used it from: for as long as your site account exists; each visit replaces them.
- Password reset links: they expire after a short time and are deleted soon after.
- Sign-in and sign-up rate-limit records: about one day.
- Trusted devices and networks (so a known browser skips the emailed sign-in code): 90 days after you last confirmed a code there, or until you remove them in your account settings.
- Steam account passwords and Steam Guard secrets: until you replace them or remove the account, also while you have no active plan. "Remove account" (one account, or several at once with Remove on the accounts list) deletes them right away; they may remain only in our encrypted backups, which are kept for 30 days.
- Steam profile data, drop history, match history, the latest inventory, prices and the activity log: for as long as your site account exists, so your totals stay correct. After you remove a Steam account nothing new is recorded for it, and its past drops, matches, activity and trade log stay in your history. If you add the same Steam account again, its earlier history shows under it again. You can ask us to delete them.
- Sent emails: the record of a sent email is kept for 30 days; messages that carry a secret (such as a reset link) are blanked as soon as they are sent.
- Records of sign-ins to your Steam accounts (worked or failed, and when): for as long as your site account exists.
- Steam sign-in tokens on our farm servers: until you remove the account (they are deleted then) or Steam ends them. Machine identity backups: kept after removal so the account gets the same PC if you add it again; ask us to delete them.
- Farming records (assignments to farm servers, disconnects and other incidents): for as long as your site account exists.
- Your trade link and your auto-trade and Steam Market choices: until you change them or your site account is deleted. The trade log and the Market log: for as long as your site account exists.
- API: the details of your API keys (refreshed, deleted and revoked ones too, which no longer work) for as long as your site account exists; the API call log for 90 days, then it is moved to an archive on our own server. The archives are kept, not deleted.
- Support tickets: the copy on our own servers is deleted 90 days after the ticket is closed, and a ticket block is kept until staff lift it. The ticket logs and Customer role notes in our private staff channels on Discord stay there; you can ask us to delete them.
- Backups: encrypted, kept on our own servers for 30 days, then deleted.
- Security logs: kept longer so we can investigate abuse.
7. Cookies
We use a cookie to keep you signed in. It is needed for the site to work and is not used for tracking. When you place an order, a second cookie remembers that this browser created it, so only this browser can return to that order instead of starting a duplicate, or choose another coin for it; it lasts 90 days. While you link Discord, a short-lived cookie (10 minutes) checks that the answer from Discord belongs to your request. When you sign in from a new device or network, a short-lived cookie (30 minutes) holds the sign-in while you enter the code we email you, and after a correct code a cookie remembers this browser as trusted for 90 days. When you create an account with an invite code that is not tied to your email address, a short-lived cookie (30 minutes) holds the sign-up while you enter the code we email you; it keeps your password only as a one-way hash, and after a correct code this browser is trusted for 90 days as well. A cookie remembers the language you chose for the site; it lasts 1 year. We also save your language with your account, and each order saves the language of the page it was placed on; we use them to write our emails and Discord messages to you in your language. Another cookie holds your device's time zone name, so the site shows dates and times in your time zone; it lasts 1 year. Your account and your orders also keep that time zone, so the dates in our emails, and the days of the daily match lines in your Activity, are in your time zone. For each open tab, your browser's session storage also notes that time zone, so a page refreshes to show your time zone at most once; that stays in your browser. The live view remembers the camera you last chose, and whether its sound is on, in your browser's local storage; that stays in your browser. It also keeps a random id there that the browser sends when it opens a live view, so a refresh replaces your earlier view instead of counting as a second one (you can watch up to 2 bots at a time); the server holds it in memory only while that view is open. Cloudflare may set its own security cookies to tell people from bots. We do not use advertising or analytics cookies.
8. Your choices
You can ask us for a copy of your data, to correct it, or to delete your account and the data linked to it. Some records may have to be kept where the law requires it or to prevent abuse.
9. Changes to this policy
We may update this policy. When we do, we change the date at the top of this page, and for important changes we tell you by email or on the site.
10. Contact
Questions or requests about your data: [email protected]. See also our Terms of Service.