Attention, not an account.

What stays in your browser

The Workbook is local to the browser you read in. There is no account system, no sync layer and no server database for your reading state.

• —Reading progress and the last chapter you opened.
• —The active bookmark and its return position.
• —Reflection entries and portfolio entries saved from chapters.
• —Frameworks you viewed or marked as practiced.
• —Annotations, highlights and margin notes.
• —Your theme and reading-size preferences.

All of it is stored in localStorage under keys that begin with tpa:. Clearing site data in your browser removes it.

What the site counts

Vercel Web Analytics and Vercel Speed Insights count page views and Core Web Vitals in aggregate. Both are cookieless and set no identifiers in your browser. A small set of events shows whether the book, the notes and the Field Kit are used:

Reading

Chapter entry

chapter_start · chapter, the page that led there

Continue reading

continue_reading · chapter, the page that led there

Framework use

framework_use · framework, action

Demonstration interaction

demo_interaction · demonstration, action

Field Notes

Skill download

skill_download · note code, skill name

Copy as markdown

markdown_copy · note code, copied or opened

Field Kit

Kit download

kit_download · no fields

GitHub link

github_click · which repository link

Contact

Contact-destination click

contact_click · email or LinkedIn, the page it was on

Newsletter sign-up

newsletter_signup · email link or sign-up form, where on the site

Workbook

Export result

export_notes · format, success or failure

Event fields are allowlisted. They name the public chapter, note, skill, framework or channel involved, and never include authored text, search queries, exported files, URL queries or fragments, or email addresses. A contact click is never recorded as an inquiry.

Skills, markdown and llms.txt

Skill and Field Kit downloads, the markdown version of every note and llms.txt are plain files. Fetching them sets no cookie and needs no account. The host’s request logs are how downloads and AI fetches are counted.

When the Field Kit repository is published on GitHub, stars, issues and downloads there fall under GitHub’s own privacy statement.

The Field Kit connector

The connector at softwarebehavior.com/mcp is read-only and needs no account. It receives what your AI tool sends (search words, a note code or a design moment) and answers from the published notes. It stores nothing, sets no cookies and runs no model; the host’s request logs are the only record of a call. Leave personal data out of anything you ask your tool to send.

If you subscribe

Subscribing works by email for now. Email to subscribe opens a message to joost@studio-jz.nl in your own email app; nothing is sent until you send it, and the site never receives your address. The newsletter_signup event records that the link was opened and where, never who opened it.

The newsletter is opt-in. Nothing on the site needs it.

Instagram, LinkedIn and GitHub

Links to these services open their own sites, under their own privacy terms. No page here embeds their posts, so their trackers never load on this site.

Export and import

The Workbook can export a JSON file with your reading progress, bookmark, reflections, framework practice, portfolio entries and annotations. Import takes the same file, so you can move to another browser without an account.

The export is a file you control. It is never sent to the site.

Who runs this site

Software Behavior is published by Joost van der Zwan, Studio JZ. Questions about this page or your data: joost@studio-jz.nl. The privacy posture should be legible without reading the source code.