What the check collects, who holds it and how long it stays.
screenshare.ac is a tool that game server administrators use to check a player's computer for cheating software. It reads a lot about that computer, so this page states plainly what is collected, who holds it and how long it stays.
The data controller is Joris Dabkevičius, registered for individual activity in Lithuania (certificate no. 1489948). Questions, requests and complaints: info@screenshare.ac. You can also complain to the Lithuanian State Data Protection Inspectorate (vdai.lrv.lt).
This service deals with two groups, and they are not treated the same.
When a player runs the program, it examines their computer and produces a report. That report can include:
The contents of personal files are never read or sent - only names, sizes and checksums. No screenshots are taken and no keystrokes are recorded. Nothing is installed and the program does not stay on the computer after it closes.
For players, the basis is consent (GDPR Art. 6(1)(a)). Before anything runs, the program shows the full terms and the check only starts if the player presses Agree. Declining closes the program and nothing is collected. Consent can be withdrawn afterwards: ask the administrator who sent the link - they can delete the report from their panel in one click - or write to info@screenshare.ac. Either way the report goes, although that cannot undo a decision the administrator has already made.
For administrators, the basis is the contract (Art. 6(1)(b)): an account, an email address and a password are needed to provide the service.
A profile picture is optional. If you sign in with Discord or Google, a small 128 px copy of that account's picture is kept here so your browser never has to load it from them; you can also upload your own or remove it. Only members of your own account see it, and it is deleted with the account.
The report goes to the administrator who created the check code, and to nobody else. Accounts are separated: one customer cannot open another customer's checks.
The controller can technically access the database to run and fix the service, and does so only for that purpose.
Nothing is sold, and nothing is shared for advertising. There are no analytics scripts, no advertising trackers and no third-party fonts on this site - the fonts and images are served from our own server.
An administrator can switch on two integrations. Both are off by default:
If an administrator turns these on, they are responsible for telling their players.
On a server located in Lithuania, inside the European Union. The database is not replicated outside the EU. Sign-in through Google or Discord, if used, is handled by those providers under their own policies.
Payments are handled by Stripe. The card is entered on Stripe's page and kept by Stripe for the renewals of a plan; this server never sees or stores the card number. We keep the Stripe customer and subscription identifiers, the plan and the amounts paid.
| Data | Kept for |
|---|---|
| Full forensic report | 90 days from the check, then deleted automatically together with the computer and user name |
| Check record - code, label, date, verdict and the number of findings | 12 months, then deleted automatically |
| Account: email, name, password hash | until the account is closed - the owner can close it in the panel, and everything goes at once |
| How the account found us: the answer to that one question in the panel, if given, and the name of the site or campaign link it signed up from - such as google or discord, never a full address | as long as the account record exists; after closing, only this channel name stays with the anonymised record |
| Sign-in sessions | 30 days |
| Failed sign-in counters | minutes, in memory only |
| Accounting records, once paid plans exist | as long as Lithuanian accounting law requires |
Deletion is automatic, not a promise to do it by hand: the server removes expired reports every time it starts and once a day while running.
It does not have to be waited out. An administrator can delete a single check - report, computer name and player name together - from the panel at any time, and the account owner can close the whole account there too. Both happen immediately.
Under the GDPR you may ask for a copy of your data, ask for it to be corrected or deleted, object to processing, or withdraw consent. Write to info@screenshare.ac and you will get an answer within one month. If a player asks about a report, they should mention the check code they were given - without it the report cannot be located.
An administrator does not need to write at all for deletion: both the single check and the whole account are deleted from the panel, and neither waits for anyone.
One cookie, ss_session, keeps an administrator signed in for 30 days, plus a short-lived one during Google or Discord sign-in. There are no advertising or analytics cookies, so there is no cookie banner to click away. The name of the site that sent you here travels in the page address until you sign up, and is not stored in your browser. The video on the front page is loaded from YouTube (youtube-nocookie.com) only after you press play - until then nothing is requested from YouTube.
Passwords are stored as PBKDF2-SHA256 hashes, never as text. Results are accepted only with the key embedded in that one download, and only once per check code; results that could not have happened are marked for the administrator. Traffic runs over HTTPS.
If this policy changes, the date at the top changes with it and administrators are told by email before anything material takes effect.