Privacy

The short version: this blog collects as little as it can. The analytics don’t use cookies or store your IP address, and nothing is sold or used for advertising.

Who runs this blog

CoopNET Blog is run by one person: me. I’m responsible for the information described on this page (in data-protection terms, the “controller”). You can reach me at renstur[at]coopnet[dot]us.

When you read the blog

• Server logs. Like any website, the server records your IP address, the page you asked for, and your browser type. These logs keep the site running and secure, and are deleted automatically after a short time.
• Analytics. The blog uses Ghost’s built-in analytics. For each page view it records the page, the site that sent you here, your country, your language, and your browser, operating system and device type. Your country is worked out from your IP address, and the IP address itself isn’t stored. Visits are grouped using a code that changes every day, so an anonymous reader can’t be followed from one day to the next. If you’re signed in, your page views are linked to your account. The analytics set no cookies.
• Outside services. The sign-up, search and comment features load code from jsDelivr, a public code-hosting service. The payment features load code from Stripe. Both see your IP address when your browser fetches that code.
• Cookies. The blog sets no cookies of its own unless you sign in, in which case it sets one to keep you signed in. Because the blog accepts payments, Stripe sets two fraud-prevention cookies (__stripe_mid and __stripe_sid) on every page.
• Links to other sites have ?ref=blog.coopnet.us added, so those sites can see where the visit came from.

If you sign up

• I store your email address, your name if you give one, when you signed up, which page you signed up from, and your membership type.
• The blog doesn’t send newsletters. The only emails you’ll get are sign-in links and messages about your account or payments, sent through my own mail server using SMTP2GO, an email delivery service.
• Paid memberships and tips are handled by Stripe. Your card details go straight to Stripe and never reach this blog; I see your plan and payment status, not your card number. Stripe also uses payment information for its own fraud prevention, under its own privacy policy.

Comments

Comments are public: your name and your comment appear on the post for anyone to read. Please don’t post passwords, keys or other private details.

Fediverse and Bluesky

New posts are shared publicly to the fediverse as @renstur@blog.coopnet.us and to Bluesky as @blog.coopnet.us; the Bluesky account runs through a bridging service called Bridgy Fed. If you follow, like or reply from those networks, the blog keeps your public profile (name, handle and picture) and what you did. Your own server and Bridgy Fed have their own privacy policies.

Where your information is kept

The blog runs on servers I manage in the United States. Backups of the site are kept on my own storage. The analytics are stored by Tinybird and payments are handled by Stripe, both in the United States. If you read from outside the US, your information is transferred there and handled as described on this page.

How long it’s kept

• Server logs: a few days, then deleted automatically.
• Analytics: kept to show trends over time. They contain no IP addresses.
• Your account and comments: until you ask me to delete them. Backups take up to three weeks to cycle out.
• Payment records: as long as tax and accounting rules require.

Why I use it

• Server logs and analytics: to keep the site working and secure, and to see which posts are useful.
• Your account, comments and payments: to provide what you signed up for.
• Stripe’s cookies: to take payments safely and prevent fraud.

Your rights

Wherever you live, you can ask me to show you what I hold about you, correct it, delete it, or send it to you in a portable format. You can also ask me to stop or limit how it’s used. Email renstur[at]coopnet[dot]us and I’ll reply within 30 days. If you’re in the EU or the UK, you can also complain to your local data protection authority. If you’re in California: I don’t sell or share personal information.

Your choices

• Cancel a paid membership at any time from your account settings.
• To delete your account and comments, email me.
• You can block cookies and scripts and the posts are still readable; signing in, commenting and payments need them.

Children

This blog isn’t aimed at children under 16, and I don’t knowingly collect their information.

Changes

If this policy changes, the date below changes with it.

Last updated 31 October 2026.