Check it yourself

You do not have to take the privacy page at its word. Your browser can show you every request this site makes, and you can turn the network off and carry on writing. Here is how, and what you should and should not see.

On a computer: watch the Network tab

1. Open parts cowork in Chrome, Edge, Firefox or Safari. In Safari, first turn on "Show features for web developers" in Settings, under Advanced.
2. Open the browser's developer tools: F12, or Ctrl+Shift+I, or Cmd+Option+I on a Mac. Pick the Network tab.
3. Clear the list (the button with a circle and a line through it), so it shows only what happens from now on.
4. Now use the app on that page: write a note in the journal, take the steps of a walk and save it, tap a Self check and keep it.
5. Watch the list while you do.

What should happen: nothing new appears while you write, tap and save. Saving goes into this browser's own storage, which is not the network. When you move to another page, that page and its files appear in the list, each from this site's own address.

What should not happen: a request to any other address, or a request that carries anything you wrote. To see each request's address, right-click the column headings and add the Domain column.

On a phone: airplane mode

1. Open parts cowork, and open the pages you want to use first, each in its own tab: the journal, the walk you mean to take, a Self check.
2. Switch on airplane mode, and check Wi-Fi is off too: on some phones airplane mode leaves it on.
3. Write, walk and save, in the tabs you already have open, without moving to another page.
4. Switch the network back on. Nothing is waiting to be sent, because nothing was going to be.

What should happen: writing, walking and saving all work, because they happen in this phone's browser. What should not happen: an error when you save, or a message that something will be sent later.

What will not work offline, and why

This is a site of separate pages, and the browser fetches each one from the site the first time you open it. From then on this browser keeps a copy of that page and its files, so a page you opened before usually opens again offline for a while (a phone may clear it when space runs low, or after a week unused unless parts cowork is on the Home Screen), as it was when you last saw it online. The first visit to a page still needs the network: offline, a page not yet opened here shows a short page saying you are offline. What it keeps is this site's own pages and files, the same for everyone; nothing you have written is in it, and nothing you have saved is lost either way.

A walk started from the map or from a part's page goes back there when you save it. Offline, the walk is saved first, and the page it goes back to opens only if you opened it before.

A few pieces load the first time you use them, not with the page, so offline they will not open unless you used them earlier while online:

• the sheet for catching a trailhead;
• the tables a mad lib uses to read what you bring: without them it says so, and goes by your words alone;
• the walks the Party Line guide reads into a room;
• saving a map as a file;
• the sample system, from the welcome page.

Each of these is a file from this site, fetched with nothing of yours in it. When one will not load, it says so, and what you were writing stays where it was.

What the network is used for

Only loading this site's own pages and files: the page itself, its scripts and styles, its pictures and cover videos, and the pieces above when you first use them. Nothing you write is sent, except a note you choose to send from Send a note. Besides the pages you open, the only requests are this site's own files being re-checked so a kept copy does not go stale.

Desk Sync, for your other devices, is being tested and is not switched on in this copy of the site.

One request carries words you typed: pressing Send on Send a note posts that note to this same site, at /api/feedback, which emails it on. You will see it in the Network tab as that one request.

A link to another site, if you tap one, leaves this site the way any link does.

The rule the browser holds the site to

Every page here comes with a content security policy: a short list of rules, written into the page, that the browser itself enforces, whatever the page's own code tries. This one allows the browser to load scripts, styles, pictures, sounds and video only from this site's own address, to connect only to this site, and nothing else, plus a few small scripts and styles written into the page that the build pins by their exact contents. Pictures written inside the page itself are allowed too. Plugins are not, and no form can send anywhere.

To read it, view the page's source (Ctrl+U, or Cmd+Option+U on a Mac) and find the line that begins <meta http-equiv="content-security-policy". 'self' in it means this site's own address. Separately, the build of the site fails if any page links to or loads a file from another site, apart from the help lines.

What this page does not do

It does not test anything or show a score. A page that told you it was private would be the thing you are checking. The proof is your browser's own tools, which this site cannot change.

Two things outside the site are outside this check: the web host sees an internet address and which page was asked for, as the privacy page says; and a browser extension you installed can see the pages you open, here as anywhere.

Updated 28 October 2026. What this is, and is not.