Privacy policy
Revised 2 November 2026
We keep the data the farm needs to work with your Steam accounts and to handle your purchases, and we do not sell it to third parties.
1. What data we process
Email and password hash for signing in to the cabinet (or your Discord, Google or Telegram account identifier if you sign in with them); the second-factor secret if it is enabled. Data of the Steam accounts you added: login, password, Steam Guard secrets and the Steam token obtained at sign-in. The proxy assigned to an account. Results of the farm’s work: match history, received drops and drop offers, account level and inventory. Identifiers, amounts and statuses of purchases. Technical session data: browser and time of sign-in. Correspondence with support: messages, attachments and whatever you tell us about yourself in it; if you write from the cabinet, the account identifier, its display name, the linked Discord ID and the number of active slots are attached to the conversation. If you take part in the partner programme: the payout wallet address and its network, accruals and payout requests.
2. How Steam sign-in data is protected
The password, Steam Guard secrets and Steam token are stored encrypted and are never shown in the cabinet or in the admin interface. They are decrypted only to sign the account in to Steam — on the farm machines that run jobs for that account.
3. Payment data
Wallet and card details are entered on the payment provider’s side and never reach us. We keep only the payment identifier, amount, fee and status.
4. Why we need it
To sign your accounts in to Steam and run jobs, to grant and track slots, to show the results in the cabinet, to handle support requests and to protect the service from abuse. We do not sell data to third parties or use it for advertising mailings.
5. Who receives the data
Payment providers — the purchase number and amount, to issue an invoice. Steam — the account’s sign-in data, when it signs in to the game. Cloudflare — the IP address and browser details: the site is served through it, and in the support chat its Turnstile service checks that a person, not a program, is writing. Services that help us answer support requests — the content of the request and the details needed to answer it. Steam passwords and secrets are not shared. No one else.
6. Retention and deletion
A Steam account’s data is deleted together with the account when you remove it from the cabinet; only the login stays in the service log that records when farm machines received sign-in data. Purchase data is kept as long as needed for support and accounting. Correspondence with support is stored on our own server. You can ask to delete your cabinet account and the data linked to it, including the correspondence.
7. Public Steam data
Level, inventory, item prices and profile appearance come from public Steam and game data. The project is not affiliated with Valve Corporation.
8. Visit statistics
We count site visits with our own analytics system running on our server. The data stays with us and is not shared with third parties. To connect visits with sign-ups and payments, the site stores a split_acquisition cookie for 30 days with a random identifier, the first public page and the referring domain. It does not include URL query parameters or search terms. These details are saved to your account when you sign up. We also count clicks on links in blog articles. If you arrive through a link with a source tag (utm_* or ref parameters in the address), the site remembers the tag in the split_utm cookie for 30 days. When you sign up, the tag is saved to your account: this shows us which posts bring customers. A partner code from the link (the ref parameter) is additionally remembered in the split_ref cookie for 30 days: at sign-up, the account is linked to that partner. The partner sees how many users they referred, how many of them paid for slots and the amounts and dates of their own accruals (from which a referred user’s payment amount and date can be worked out), but sees neither the email nor any other account data of the referred users.