Privacy Policy
What data Voider stores, why, for how long, and the rights you have.
Current version: Nov 21, 2026. We may update this page; the latest version always appears here.
Controller
The controller for the processing is the operator of Voider. For privacy requests you can reach us by email at contact@v0ider.org.
What we store
For your account and to run the panel we store:
- Account data: username, email address and your password as a salted bcrypt hash, never in clear text.
- Session: a random session token in an httpOnly cookie; the server holds only its check value, together with the IP address and browser (user agent) of the sign-in, until the session ends (at most 30 days).
- Game accounts: the Steam username and the sign-in token Steam issues when you add the account, encrypted with AES-256-GCM. The Steam password is used only for that one sign-in and is not stored. For the farm we also keep, encrypted, the game's player ID, its session token and a random device identifier. None of this is ever sent back to the browser.
- Farm data: progress, Gems and Orbs per account, and for PvP runs level, rank and Duel Pass.
- Access: tier and term, and for each redeemed license key its tier, term, the time it was redeemed and when you agreed that it starts at once; this is the history of your bookings.
On top of that the servers keep logs (such as IP address, time, the address requested and technical events of farm runs) for the security and operation of the service; they are deleted after 30 days at the latest. A message you send us by email is kept to handle your request.
Purposes and legal bases
We process account, game-account and access data to perform the contract, that is, to provide the service. We process security and log data out of a legitimate interest in secure operation. Where the law requires it, we process data to meet legal obligations.
Cookies and tracking
Voider sets a single cookie: the session cookie, which is technically needed to sign in. There is no tracking, no analytics services and no third-party content embedded; fonts and scripts come from our own server. Your browser also keeps a few settings locally (the chosen language and how you set up the farm view); they are not sent to the server.
Recipients
To farm, Voider signs in to Steam (Valve Corporation) with the stored sign-in token and to Yu-Gi-Oh! Master Duel (Konami) with the game's player ID; that data goes to those operators. The farm itself runs on our own server.
Payments: you pay in a ticket on our Discord server (Discord Inc., USA). There our team sees your Discord name, the chosen tier and term, and the payment details you share in the ticket. For PayPal or crypto, PayPal or the crypto network processes the payment; we do not store payment details on the website. To run the service we also use providers for hosting and an upstream network service. They process data only on our behalf; where data is processed outside the EU, this happens only on a basis permitted under the GDPR.
Storage and deletion
You can delete a game account from the panel at any time; its credentials are removed in the process.
We store account data for as long as your account exists. You can delete your account yourself in the panel (account dialog); your sessions, game accounts and their encrypted sign-ins are removed at once. Bookings are kept without your name for as long as tax law requires (up to 10 years).
Backups of the database are kept for 14 days and then deleted; deleted data disappears from them within that time.
Your rights
- Access to the data stored about you
- Correction of incorrect data
- Deletion and restriction of processing
- Data portability
- Objection to the processing
- A complaint to a data-protection authority
You can delete your account yourself in the panel. For a copy of your data or anything else, a message to contact@v0ider.org is enough. You also have the right to complain to a data-protection supervisory authority.
Security
Connections run over HTTPS. Passwords exist only as a hash, sign-in data for game accounts only encrypted. The key for it is kept in a separate, access-restricted file, not in the database and not in its backups.
Changes to this policy
This policy may be adjusted; the version that applies is available on this page.