This page is written from the code as it runs today, not from a template. Where a claim has a technical backing, the backing is named so it can be checked.
The date at the bottom changes whenever the substance does.
The Belief System Audit runs entirely in your browser. Nothing you answer is sent anywhere: not a score, not a label, not a note. That is enforced by the page rather than promised by it. The audit carries this Content Security Policy:
default-src 'none'; style-src 'unsafe-inline'; script-src 'unsafe-inline'; img-src data:; base-uri 'none'; form-action 'self'
default-src 'none' instructs the browser to refuse every network request the page's code could make: no script, stylesheet, font or image from any server, and no connection to any address. The only things allowed are the styles and script written inside the file itself, and images built on the device for the share card. The file contains no fetch, no XMLHttpRequest and no sendBeacon, so there is no code path to a server, and the policy means one could not be added without changing the policy first. form-action 'self' permits exactly one kind of request: a form posting to this site's own address. That is the email box described next, and it is the only way anything leaves the page. The page also sends no referrer when you leave it.
The one exception is the optional email box at the end of a result. It sends only the address you type and the consent tick, to the same place the download form goes, and only when you press the button. It never sends your answers. Leave it empty and nothing is sent at all; the result is yours either way. The Router carries the stricter policy, with form-action 'none' in place of 'self': it has no email box, so it can post nothing to anywhere.
The share buttons on the result screen act only when you press them. On a phone the button hands the card, caption and link to your device's own share sheet. On a desktop it downloads the card and opens X or LinkedIn in a new tab with a caption you can read first; LinkedIn does not accept prefilled text, so that caption is copied to your clipboard for you to paste. Downloading the image, the Markdown file or the calendar reminder writes to your device and nowhere else.
The audit keeps two entries in your browser's local storage, so you can close the tab and come back, and so a retake can be set beside an earlier run. Local storage lives in your browser profile on this device. It is not a cookie, it is never attached to a request, and nothing at Impart can read it.
impart.beliefsystems.v1Your completed runs, up to the last 24. Each one holds the date, the depth you chose, your four scores and your lowest element, the label you typed for what you were scoring the run against, every answer you picked with any note you wrote, and a random id for that run. The id is made fresh for every run, never for the browser, so runs are not linked into a profile. If you arrived through a link that carried a source tag, the tag is kept with the run.
impart.beliefsystems.draft.v1An unfinished run: the label you typed, the depth you chose, your answers so far and where you stopped. It is removed when you finish or discard the run, and it expires on its own after 30 days.
impart.router.draft.v1An unfinished Router run: the endeavor you named, your answers so far and where you stopped. It is removed when you finish or discard the run, and it expires on its own after 30 days.
impart.router.v1Your last eight routes, including the decision you named, so the Router can show it back and ask whether it is the same one.
To erase an unfinished audit run, open the audit and choose Start over on the resume prompt, or Discard on the exit prompt. The audit has no control of its own for erasing completed runs: to remove those, clear this site's data in your browser settings. That removes every entry above at once, it takes effect immediately, and nothing can be recovered afterwards, because there was never a copy anywhere else. The Router has its own erase control, which removes only what the Router stored.
Three things on this site send anything to a server: the three forms. Two are described here; the third, the book list, has its own section below. All three go to Netlify Forms. Netlify hosts the site, and every submission sits in its dashboard until it is deleted there. The download form goes one step further: Netlify forwards each submission to a small script running in Google Apps Script, which records it in a Google Sheet and sends the download email through Gmail. So for the download form, Google is a second place your address is held. The contact form is not forwarded anywhere; it is read in Netlify by one person.
Your name, email, organization, role, the kind of program you run, and your answer to the question about where your people stop. It is read by one person and used to reply to you about a pilot. It is not added to a list and it is not used for anything else.
Your email, which of two roles you chose (using the files yourself, or running a program), and the acknowledgement you ticked. It is used to send the download email and, later, the next instrument. Nothing else.
All three forms also carry fields a person never sees: the form's own name, on the download form the role (picked with the two buttons on the get-the-files page, set to individual at the end of an audit) and a tag saying which page the form was on, and one empty trap field that catches automated submissions. Netlify's own handling of the submissions it holds is described in Netlify's privacy policy. To have a submission deleted, write to the address at the foot of this page.
When the download form goes through, one email is sent, once, to the address you entered. It carries the instructions for using the folder and the folder itself as one zip. While copies are issued by hand, the email says so and the zip follows directly within a day.
The address is used for that email and for the next instrument when one ships. To stop them, reply to any one of them with the word stop; the reply reaches a person, not a queue, and no further email is sent. Every one of them can be replied to for any other reason too.
The form on the book page, named book-news, is a second list and a separate one. It takes your email and one tick, whose label is the whole promise: news about the book when there is some, nothing else. Its submissions sit in their own form in Netlify, and if they are ever copied to a sheet it is a sheet of their own; they are never joined to the download list or to the email box at the end of an audit result: a person on the book list is not sent the download email or the next instrument, and a person on the download list is not sent book news. Neither list is ever used to look up the other. To leave it, reply to any email from it with the word stop, or write to the address at the foot of this page.
There is no analytics script on any page, no pixel, no tag manager, no session recording, no fingerprinting, and no cookie set by the site. This is a choice for this phase, not an omission. The site is built so that what it collects can be checked by reading its source, and each script added would make that harder to check.
If measurement of any kind is ever added, this page will say exactly what it is, and the date below will change.
Every page that carries this header and footer loads two typefaces from Google Fonts: Source Serif 4 and Barlow. That is one request to fonts.googleapis.com for a stylesheet, then requests to fonts.gstatic.com for the font files. Like any request, it carries your IP address and browser details to the server that answers it. It is the only thing a site page asks any third party for.
The instruments make no such request. Their policy forbids it, and they use the typefaces already on your device instead. Beyond that, the only server involved anywhere is Netlify, which serves the pages and receives the three forms. The events page is the one exception to the rule above: it asks a small function on this site for the dates of upcoming sessions, and that function asks Eventbrite; and while a session is on sale it loads Eventbrite's checkout script from eventbrite.com so a ticket can be bought without leaving the page. Nothing you type on this site goes to Eventbrite. Buying a ticket happens with Eventbrite, under Eventbrite's own privacy policy, and the ticket confirmation that follows is sent through the same Google Apps Script and Gmail route as the download email.
Write to Julianf@fitzfirm.net. It is the address the two forms fall back to when a submission does not go through, and it is the address for questions about this page, including a request to delete a form submission.
Version 2026-10-18. Changing the substance of this page means changing this date.