Back home

Privacy policy

Privacy policy

Last updated: 10 November 2026

This is a small personal site run by Lazzeking. It has no accounts, no ads, no third-party analytics and no tracking cookies. This page explains what still happens with your data when you visit, and why.

If you have a question or want to use any of your rights below, write to [email protected].

When you visit

Cloudflare. The site is delivered through Cloudflare, which protects it and makes it load faster. Cloudflare handles your IP address and the details of each request in order to do that.

Server logs. The web server keeps a log of requests (time, page, browser, the page you came from) for security and troubleshooting. Because traffic arrives through Cloudflare, these logs contain Cloudflare's network address rather than your own IP address. Logs are deleted after 14 days.

Rate limiting. To keep the site and ModDB from being overloaded, the site counts how many requests each visitor makes in a short time. Visitors are counted by a one-way code made from their IP address, a secret key and the current date. Your IP address itself is never stored, the code changes every day and can't be turned back into your address, and the counters are deleted within 24 hours.

Post views and reactions. When you open a post in Updates, the site counts the view, and you can react to it (a star, a heart and so on). So you're counted only once per post, you're remembered by a one-way code made from your IP address, the post and a secret key. Your IP address itself is never stored and can't be read back from the code, and because the code is different for every post, it can't be used to see which posts one person read. The site only shows totals (how many views and reactions a post has). The codes are kept for as long as the post exists and are deleted with it. Search engines, link previews and other crawlers aren't counted.

Login cookie. The mod stats can be limited to people who have a password. If you log in, one cookie (vstools_access) remembers that for 30 days. It only holds an expiry date and a signature, nothing about you. Logging out deletes it.

Theme choice. If you use the light/dark switch, your choice is saved in your own browser (local storage) so it's remembered next time. It never leaves your browser.

Signing up to test a mod

Some posts in Updates have a form to sign up as a tester for a mod that isn't out yet. If you use it, the site saves what you type: a name, your Discord username and/or email address, the optional "about you" text, the time you signed up, and the text you agreed to. Only Lazzeking can see it, on a page that needs the writer password. It's used for one thing: contacting you about testing that mod. It's never shown on the site, shared, sold or used for newsletters.

So you can see that you're on the list and take yourself off it, your browser gets a cookie (updates_signup_ and the post number) holding a random code, for a year. Taking yourself off the list deletes your details and the cookie. Otherwise your details are deleted once testing for that mod is done, or whenever you ask at [email protected].

A list can cover more than one post and more than one mod (for example a mod and an add-on for it), so signing up once puts you on that list for all of them, and the box tells you which list you're joining. Your details stay on the list even if the post you signed up on is taken down.

To keep bots from flooding the lists, the form uses Cloudflare Turnstile, a check that you're a person. It runs in your browser when the form is shown and sends Cloudflare your IP address and some browser details, without cookies for tracking you across sites.

Content loaded from other services

Some parts of the pages are loaded by your browser directly from other services. When that happens, those services receive your IP address and basic browser information:

The banner tool

When you make a requires banner, the mod id you enter is used to look the mod up on ModDB. The "latest banners made" list only keeps the mod, the options picked and the time, nothing about you.

Data about mod authors

The mod stats show public information from the Vintage Story ModDB: author names, mod names and summaries, download and follow counts over time, and what descriptions and public comments say about AI use, with short quotes. This is collected from ModDB's public API and pages and saved daily, so the tools can show history and trends. The How the data is collected page explains exactly what is collected, when, and for how long.

Opting out

If you're a mod author, you can ask for:

Use the opt-out page or write to [email protected]. Requests are checked by hand, so nobody can hide someone else's work, and pages say when something was changed at the author's request.

Running and protecting the site, rate limiting, counting post views, and showing public mod statistics are based on legitimate interest (Article 6(1)(f) GDPR): keeping a free site working and safe, and giving the Vintage Story community useful tools. Saving your theme choice and your reactions on a post are things you ask for by using the switch or the reaction buttons. Signing up to test a mod is based on your consent (Article 6(1)(a) GDPR), given with the tick box on the form, and you can take it back any time by taking yourself off the list.

Your rights

You can ask for access to, correction of, or deletion of data about you, ask for its processing to be restricted, or object to it. You can also complain to the data protection authority in your country.

Changes

If this policy changes, the date at the top changes with it.