Privacy
This is a static site of game guides: it has no accounts, no comments, no forms and no mailing list, so there is almost nothing about you for it to hold.
Accounts and stored personal data
There is nothing to sign up for. No accounts, no comment threads, no contact form, no subscriber list — the pages are pre-built files with no database behind them, so no name, email address or profile of yours is stored here. The only things written to your device are kept by your browser and never sent anywhere: your light or dark theme choice, your answer to the analytics question if you are asked one, and the measurement opt-out switch described below. Clearing site data in your browser removes all three.
Analytics
Cloudflare Web Analytics runs on this site. It counts page views and basic request details — the page requested, the referring page, rough country, browser and device type — and it is cookieless: it stores nothing on your device and never builds a profile that follows you between visits. Because it identifies no one, it needs no consent, and it is off entirely if you use the switch below.
Google Analytics 4 runs on this site, but only if you say yes. It sets _ga cookies and builds a per-visitor profile of the pages you view here, so it is not loaded at all until you accept the consent banner; decline and no Google script is ever fetched. Advertising features are switched off in the configuration — Google Signals and ad personalisation are disabled, and your IP address is truncated before it is stored. Your answer is kept only in this browser's local storage, not on a server.
Once measurement is on, more than page views is recorded: which internal links you follow and from where on the page (table of contents, breadcrumb, tag, related guide, search result), how far down an article you scroll, when you copy a code or config block, when you use a share button, and what you type into on-site search — including searches that returned nothing. Search terms are text you wrote, so treat that box as public: do not type anything personal, an account name or a key into it.
Your answer stands for a year and is then asked again, and the same year applies to a no as to a yes — a refusal that was re-asked on your next visit would not be a refusal. If your browser sends Global Privacy Control, that is read as a no on every load, no banner is shown, and any _ga cookies an earlier yes left behind are deleted. Changing the answer yourself is one button, in the next section.
Change your analytics-cookie answer
Withdrawing is one button, and it is no harder than saying yes was. Switching to no also deletes the _ga cookies the earlier yes created: an answer withdrawn while its cookies stayed on your device would not be a withdrawal. The page reloads either way, because a script the browser has already fetched cannot be unloaded — saying so and reloading is more honest than leaving a page that contradicts what you just chose.
This control covers the consent question only. The switch further down is separate and stronger: it stops every counter on this device, the cookieless one included, whatever you answer here.
Share links
The share buttons on an article append campaign parameters to the link they hand to the other app — a utm_source naming the channel you shared through (x, telegram, copy link, and so on), plus a fixed medium and campaign. They say which channel a visit arrived from, never who shared it or who clicked: nothing about you is encoded in them. Delete the ?utm_... part of a shared link and it opens exactly the same guide.
Turn measurement off on this device
The switch below turns off every counter this site loads — both the cookieless one and the consent-gated one — and it beats any answer you gave the banner. It is remembered per browser, so it applies to this browser on this device only, and clearing site data forgets it. Opening /?lsp-analytics=off does exactly the same thing, which is the easy way to apply it to a phone from a link; /?lsp-analytics=on undoes it.
One thing no switch on this page can reach: the server that sends you these pages sees the request itself. Your IP address, the URL you asked for, your browser's user agent and the time are handled by the host at the moment of the connection, before any script on the page runs. That is how the web works rather than a choice this site makes, and the hosting section below says who processes it.
Hosting
The site is a set of static files with no server behind them — no database, no accounts, nothing to query about you. Those files are served by Cloudflare, from lastsaveprotocol.com, and Cloudflare is therefore the one party besides you that necessarily sees each request: your IP address, the page you asked for, your browser's user agent and referrer. That is the ordinary request metadata any host on the internet receives, it is what Cloudflare uses to serve the file and to absorb attacks, and it is described in Cloudflare's privacy policy. Nothing on this side of it is stored, joined to anything, or passed on.
Requests
Ask what is held about you, or ask for it to be deleted, at one address. The address comes from site.config.ts: contact@lastsaveprotocol.com. It is a working address, forwarded to a monitored mailbox. In practice the honest answer to most requests is that nothing identifying you was collected in the first place — there are no accounts and no list to be removed from.