01What we collect, and what we do not
Google Analytics counts anonymous visits here and sets a cookie in your browser. Beyond that: no ad code, no other third-party trackers, no browser local storage, and no accounts or registration.
More specifically:
- One analytics tool, nothing more. Google Analytics records aggregate figures — page views, referrers, device type — so we can tell which articles get read. Google handles that data under its own privacy policy; what we see is an aggregate report that cannot be traced back to you as an individual. A blocker extension or a tracking-protection setting stops it loading, and nothing on this site stops working if you do.
- Only the analytics cookie. This site sets no cookies of its own; the analytics tool above sets one that distinguishes visitors. There are no advertising or personalisation cookies.
- No local storage. Checklist state exists only in the current page's memory and clears on refresh.
- No accounts. No registration, no login, no way for us to know who you are.
- No form submissions. Every input on this site is processed inside your browser and sent nowhere.
02Server logs
Like any website, the server hosting this one produces access logs when responding to requests, typically containing an IP address, a timestamp, the requested path, a referrer and a browser identifier. That is how web serving works and we cannot switch it off.
- It is used only for keeping the site available and diagnosing faults.
- We do not use it to build profiles, and we do not join it to any other dataset.
- We do not sell or share these logs with third parties.
- The site is served through a content delivery network, whose provider also records comparable technical information in the course of delivering it.
03How the tools handle what you type
Everything is computed in your browser and nothing you enter leaves your device. You can disconnect from the internet and the tools produce identical results.
- Address format validator: decoding and checksum computation live in a JavaScript file served by this site, executed locally, and nothing you paste is sent to any server.
- Seed backup self-check and approval risk self-check: tick state is summed in memory, with no cookies, no local storage and no upload.
- Glossary: filtering happens locally, and the entries are written into the page's HTML to begin with.
No page and no tool on this site accepts a seed phrase or a private key, and we will never ask for one through any channel. That is not a formality in a privacy policy; it is a design premise of the site.
04Third-party resources and external links
Every resource a page here loads — stylesheet, image, font, the scripts behind the tools — comes from this site's own domain, with one exception: the Google Analytics script described above, which is served by Google.
Which means that apart from that one script, your browser makes no requests to any other company's servers while you read this site. We use no external font service either; body text renders in fonts already present on your device.
The site does contain links out to other sites (exchange official pages, public specifications). Once you follow one and leave, that site's privacy practices are its own and nothing to do with us. Two of those links carry our referral code; exactly which two is set out in Risk & disclosure.
05Your rights, and how to reach us
This site collects nothing that identifies an individual and builds no user records of its own; the analytics data sits with Google, and what reaches us is an aggregate report, so there is normally no personal data of yours for us to access or erase.
If you have a question about how data is handled here, or believe this site has processed your personal information in some way, write to notes@seedknot.com and we will look into it and reply.
If this page changes, the update date above changes with it, and significant revisions are also logged on the corrections page.