Who is responsible

This blog is run by Lans IT (KvK 42077043, btw NL005477083B77), in the Netherlands. Lans IT is responsible for the personal data described here. Questions and requests go to info@lans.cloud.

When you read the blog

Pages, fonts and images come from our own servers. Nothing on a post loads from Google, a social network or an ad network.

Visitor statistics. We count visits with Umami, an analytics tool we run ourselves at analytics.lans.cloud, on the same server as the blog. It sets no cookies. Your browser sends it the address of the page you open, the page that linked you here, your browser, operating system, type of device, screen size and language. Umami uses your IP address to work out your country, region and sometimes city, and to make a scrambled visitor code that changes every month, so it can count how many different people visited. It does not store the IP address itself. No other company receives these statistics, except IDrive, which stores our encrypted backups and cannot read them (see Backups under How long we keep what). We also use them to show the most read posts on the home page. Legal basis: our legitimate interest in knowing what gets read and whether the site works.

Server log. The blog writes a running log of errors and events. A few lines contain an email address (for example when a sign-in link is sent) or an IP address (when someone hits a rate limit). The comment system keeps a similar log, see Comments. The web server in front of the blog keeps no access log of the pages people open. Legal basis: our legitimate interest in keeping the site running and secure.

What your browser keeps. Your light or dark theme choice and, for multi-part series, which parts you have read. Both stay in your browser's storage; the only use beyond this page is that the comment section is told your theme, so it matches. Clearing this site's data removes them. The comment section keeps its own items in your browser for comments.lans.cloud, such as a comment you started but did not send and how you sort and fold comments.

The newsletter

If you sign up for new-post emails, we store your email address, when you signed up, when you confirmed and, if you leave, when you unsubscribed. Nothing is sent until you click the link in the confirmation email. Every email has an unsubscribe link that works at once. To limit abuse we count signups per email address and per IP address (see the rate-limit counters under How long we keep what). Legal basis: your consent, which you can withdraw at any time by unsubscribing.

Premium subscriptions and signing in

Paying. Payments go through Stripe. We pass Stripe your email address and the plan you chose, and you enter your payment details and billing address on Stripe's own checkout page. We never see your card number. Stripe is responsible for its own use of that data, as described in theStripe Privacy Policy.

What we keep. Your email address, your Stripe customer and subscription numbers, your plan, the subscription's status and renewal date, and when you subscribed and last signed in. Legal basis: our agreement with you (we need this to give you the subscription you paid for).

Stripe notifications. For each notification Stripe sends us we keep a short record (its number, type and time) so that none is handled twice. Since 21 November 2026 that record holds only Stripe's reference numbers, no name, email address, phone number or address. Before that date we stored each notification in full. One Stripe account serves several of our sites, so those older copies also cover purchases in our webshop, and can include a name, email address, phone number, billing and shipping address, business name and tax number, but never a card number. Nothing reads those older copies; they are still stored until we remove them. Legal basis for the short records: our legitimate interest in processing payments reliably.

Signing in. Subscribers sign in with a link we email them. With each link we store your email address, the IP address and browser it was requested from, and when it was used, to spot misuse. Opening the link sets one cookie,premium_token, that keeps you signed in for 30 days and does nothing else. Legal basis: our agreement with you, and for the IP address and browser, our legitimate interest in keeping accounts safe.

You can cancel or change your subscription at any time through Manage Subscription in the menu, which opens Stripe's customer portal.

Comments

Comments run on Remark42, a comment system we host ourselves at comments.lans.cloud. To comment you sign in with your email address and a name of your choice. We send a confirmation link to that address. The comment database does not store the address itself: your user id is a code calculated from it. That code is public, and anyone who already knows your email address can calculate it too, so they can tell whether you commented.

It stores your name, your comments and votes with their times, your picture, and a scrambled form of your IP address (used against spam and double votes). Signing in sets a cookie on comments.lans.cloud that keeps you signed in for 30 days, plus a security cookie that protects the comment form. Your name, picture and comments are public. We get an email at our own address for each new comment, so we can moderate.

The comment system keeps a log of the requests it handles, and the sign-in request contains your email address and name. That log is capped at 30 MB and the oldest lines are overwritten as new ones arrive.

Your picture. When you sign in, our server asks Gravatar (run by Automattic Inc., in the United States) whether your email address has a picture, sending it a scrambled form of the address that Gravatar can match to its own users. If it has one, we copy it to our server and show that copy; otherwise we make a simple pattern picture ourselves. Your browser never contacts Gravatar.

The comment section only loads when you scroll near it. Legal basis: our legitimate interest in running a comment section that is open to real people and closed to spam, including the cookies, the log, the Gravatar lookup and the emails to us.

Emails we send

Newsletter emails and sign-in links go out through our own mail service, which sends through a mailbox at Hostinger. The mail service keeps a copy of every mail it handles so we can check what went out: it deletes the text after 90 days, and keeps the address it went to, the subject and the time (see How long we keep what). Legal basis: our legitimate interest in knowing what we sent and whether it went out.

If our mail service fails while sending a sign-in link, the blog may send that link through Resend (Resend, Inc., United States) instead, which then receives your email address and the link.

The comment system sends its confirmation links straight through the same Hostinger mailbox, without our mail service.

How long we keep what

Newsletter address
Until you ask us to delete it. Unsubscribing stops the emails at once, but the address stays on the list, marked as unsubscribed. A signup you never confirm also stays until you ask.
Premium subscriber record
Until you ask us to delete it. It stays after a subscription ends, so a returning subscriber is recognised.
Sign-in link records (email, IP address, browser)
Until you ask us to delete them. The link itself stops working after 15 minutes.
Records of Stripe notifications
Until you ask us to delete them. Since 21 November 2026 they hold only Stripe's reference numbers, no name or contact details. Full copies received before that date are still stored; see Premium subscriptions.
Rate-limit counters (email or IP address)
Removed the next time someone uses the same kind of form after the hour is up. On a quiet site that can take a few days.
Comments and your comment account
Until you or we delete them.
Visitor statistics
For as long as this blog runs, unless we set a shorter period. They hold nothing that names you.
Server logs (the blog and the comment system)
Each is capped at 30 MB and the oldest lines are overwritten as new ones arrive. The blog's log is also discarded each time we update the site.
Copies of emails we sent
The text for 90 days. The address, subject and time for as long as this blog runs, unless we set a shorter period.

Backups. Every night we make encrypted copies (AES-256) of the blog's database, of the comments and of our mail service's copies of the emails we sent, along with the other databases on our server. We keep the copies of the last 7 nights on that same server. Every night we also send them to IDrive e2, a storage service of IDrive Inc., which keeps them in a data centre in Frankfurt, Germany. A copy normally stays there for about 37 days and is then deleted automatically. The newest copies stay until a newer night replaces them, so if our backups stop, for example because our server fails, they stay there until we restore from them or delete them. Now and then we also copy them to storage we run ourselves, and keep them there with no time limit for now. The copies are encrypted on our server before they leave it, and only we have the key, so IDrive cannot read them. The comment system also keeps its own daily copy of the comments, the last 10 of them, on the same server. So data we delete can still be in a copy for a while, and in an encrypted copy we keep longer. We use those copies only to restore the site after a failure, and to check now and then that restoring still works. Legal basis: our legitimate interest in not losing the site and your subscription when something breaks.

Who else handles data

  • Hosting and email: Hostinger International Ltd (Larnaca, Cyprus, EU), part of the Hostinger group based in Vilnius, Lithuania. The blog, its database, the comment system, the visitor statistics and our mail service all run on a server we rent there.
  • Payments: Stripe (for customers in Europe, Stripe Payments Europe, Limited, in Ireland), only if you take a premium subscription.
  • Gravatar (Automattic Inc., United States), only for the scrambled email address described under Comments.
  • Resend (Resend, Inc., United States), only as the fallback for sign-in links described under Emails we send.
  • IDrive Inc. (United States), for storing our encrypted backups (IDrive e2, in a data centre in Frankfurt, Germany). IDrive cannot read them. It works under a data processing agreement, and for any transfer to the United States it relies on the EU-U.S. Data Privacy Framework and, where that does not apply, the EU's standard contractual clauses.

Outside the EU. IDrive keeps our backups in Germany; for any transfer to the United States it relies on the safeguards in its entry above. Resend is certified under the EU-U.S. Data Privacy Framework, which the European Commission has found to protect data adequately, and its terms with us also include the EU standard contractual clauses. We have no agreement with Gravatar: our server asks it about a picture the way anyone can, and Automattic handles that request under its ownprivacy policy.

We do not sell personal data, and there are no advertisers on this site.

Your rights

You can ask us what we hold about you, and ask us to correct it, delete it, limit how we use it, or give you a copy. You can object to uses based on our legitimate interest, and withdraw consent at any time. Write toinfo@lans.cloud from the address in question, so we can tell the request is yours. Some things you can do yourself: unsubscribe with the link in any newsletter, and cancel a subscription in Stripe's customer portal.

You never have to give us anything to read the blog. An email address is needed only for what you ask for with it: the newsletter, a premium subscription, or commenting. We make no decisions about you by computer alone.

You can also complain to theAutoriteit Persoonsgegevens, the Dutch data protection authority.

Changes

When what we collect changes, this page changes with it. Last updated: 22 November 2026.