The Product Architect

Privacy

The book asks for attention, not an account. Reader state stays local unless you choose to export it.

Local first

What stays in your browser

The Workbook is local to the browser you use to read. 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 light, dark, or system theme preference.

This data is stored with `localStorage` keys that begin with `tpa:`. Clearing site data in your browser removes it.

Analytics

What the site may measure

Production deployments may load the Google tag for aggregate traffic analytics. That measurement is used to understand whether pages are being found and read. It does not receive your Workbook entries, annotations, bookmark text, or theme preference.

The tag is only loaded on the production Vercel deployment when a Google tag id is configured. It starts with analytics storage, ad storage, ad user data, and ad personalization denied; Google signals and ad personalization signals are disabled.

Your copy

Export and import

The Workbook can export a JSON file that contains your local reading progress, bookmark, reflections, framework practice, portfolio entries, and annotations. Import uses the same JSON shape so you can move that state to another browser without creating an account.

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

Contact

Questions

If something about the data model feels unclear, use the contact details on the About page. The privacy posture should be legible without reading the source code.