Stateless
log in

privacy

I don't believe in the benevolence of the state any more than I do in that of big tech companies. This site is maintained and hosted with the maximum of privacy-friendly and open-source technologies.

This page explains, in plain words, what happens when you browse stateless, and how I handle your personal data if you interact with the site.

The short version

  • You can browse a good chunk of the site without signing up.
  • If you create an account, you give neither your name nor your email. All I do is generate a random key, which you need to keep somewhere safe to sign back in next time.
  • The club is paid in bitcoin, with no KYC on my side. Getting your hands on some bitcoin is up to you.

What we DON'T do

  • No tracking cookies.
  • No pixels (Facebook, Google, etc.)
  • No shitty analytics scripts (Google Analytics, etc.)
  • No affiliate links.
  • No email asked for, ever.

When you browse

Two technical cookies are used: a session cookie (it remembers your language and currency, and keeps you signed in if you are a member) and the anti-forgery token that protects forms. Both are strictly necessary, carry no identity, and never follow you anywhere.

I use:

  • Umami Analytics to know my audience statistics: cookieless, aggregated counts per page, country and browser. No fingerprinting, no profile, nothing that follows you from one site to another.
  • Cloudflare to protect my server. Like any proxy it sees your IP address on the way in; it is used for security, not for profiling.
  • An error monitoring service that receives crash reports (the page, the error, the technical trace) with personal data collection switched off.

Servers also write short-lived technical logs (IP address, requested page, timestamp) that help me keep an eye on the technical side of things.

When you are a member

Here is everything the members table holds about you: a pseudonym I generate at random, the hash of your key (not the key itself: I cannot read it back, and neither can an attacker), the date you joined, the date of your last sign-in, and whether and when you joined the club. That is all.

This is deliberate: it means I cannot recover a lost key, and it means I cannot identify you even if asked to. If you tick "remember me", a long-lived cookie keeps you signed in on that browser until you sign out.

When you pay

The club is paid in bitcoin through a bitcoin payment processor. For each payment I keep: the invoice reference, the amount and currency, its status, and the technical details the processor returns once it is paid (transaction id, address, payment hash). Those are public blockchain data, not identity data.

The processor does not ask you for any identification. It has its own privacy policy for the little it handles (the invoice and the payment).

If you have no bitcoin, the pay page points you to wallets and exchanges where you can buy some. Whatever you do there happens under their terms and their privacy policy, not mine: I see none of it, only the bitcoin landing on the invoice.

When you join a waiting list

Some upcoming features have an email box. If you use it, your email goes to Brevo, the newsletter tool, in a list dedicated to that one feature. It is used for that announcement and nothing else. Every email has an unsubscribe link, and you can ask me to delete the address at any time.

Where the data lives, and for how long

The site is published by a company registered in the United States and runs on servers located in the United States. If you live in the European Union or elsewhere, your data crosses borders to get there; I keep it to the minimum described on this page.

  • Session: two hours of inactivity, or until you sign out.
  • Member account: for as long as you keep it. Ask and I delete it.
  • Payments: for as long as accounting and tax rules require me to keep records of sales.
  • Waiting-list emails: until you unsubscribe or ask for deletion.
  • Technical logs and crash reports: a few days to a few weeks, then automatically wiped.
  • Analytics: aggregated counts, kept indefinitely; there is nothing personal in them.

Your rights

Wherever you live, you can ask me what I hold about you, have it corrected or deleted, object to a use, or get a copy. The EU GDPR, the UK GDPR and several US state laws make this a legal right; I apply it to everyone.

Write to [email protected]. One practical thing: since an account carries no identity, I need proof that you hold the key (for instance, write from the account page while signed in, or quote your pseudonym and a recent payment reference). I answer within 30 days. If you are in the EU and unhappy with my answer, you can complain to your national data protection authority.

Publisher

Responsible
The Borderless Network Company LLC (Wyoming, USA)
Contact
[email protected]

Changes

This policy may evolve. Check it regularly.

When something material changes (a new tool, a new kind of data), the date below moves and the change is written here, not hidden in a mailing.

Last updated: September 12, 2026.