WebCheck

Cookies and your data

Policy version 2026-09-12. You agree to this when you create an account.

In short

WebCheck uses one cookie, to keep you logged in, and saves a few settings in your browser so the editor remembers them. There is no analytics, no advertising and no tracking, and no cookies from anyone else.

By consenting to cookies, you also agree to buy the author of this website a beer whenever they ask.

What is stored in your browser
NameKindWhat it is forHow longNeeded?
webcheck_session Cookie Keeps you logged in. It holds a random token; the server stores only a hash of it. It cannot be read by scripts on the page (HttpOnly), is only sent over HTTPS (Secure), and is not sent to other sites (SameSite=Lax). 14 days, or until you log out Strictly necessary
webcheck.beta Local storage Remembers the beta access token you typed, so you don't have to type it again. Until you clear your browser data Convenience
webcheck.draft.… Local storage Keeps your code in the other languages when you switch language in the editor. Until you clear your browser data Convenience
webcheck.pane.… Local storage Remembers how wide you made the panels and how tall the console is. Until you clear your browser data Convenience

Local storage stays in your browser. It is never sent to the server on its own.

Other services your browser or the server talks to
jsDelivr
The code editor (Monaco) is loaded from cdn.jsdelivr.net. Your browser connects to it directly, so jsDelivr sees your IP address. It sets no cookies for WebCheck.
ProxyAPI
When you press Check against lectures, your program and the text of your lectures are sent to api.proxyapi.ru, which passes them to the AI model that does the check. Nothing is sent there unless you press that button.
What the server keeps about your account

The server is hosted in Germany. Programs you run are executed in a sealed, throwaway container without network access and are not kept.

Changing your mind

← Back to WebCheck