Security

What the policies are

Chock adds friction. It is not a security boundary. A policy refuses a risky action, asks you about it, warns on it or flags it. It does not make the action impossible. An agent can ignore advisory text, and a determined agent can get around a block on the shell. Each policy's label says which of these it does.

What the site does

The site is static files: nothing you pick leaves your machine, and the builder runs in your browser. Your selection lives in the URL fragment after the #, which browsers never send to a server. The author page saves a policy you draft only in this browser's localStorage. The page never sends it anywhere. Its share link holds the agent and catalog ids, and never your draft. There is no cookie and no account. The site counts a few actions and no page views, with no personal data. The list is at the end of this page.

Why the command is safe to read before running

The command fetches one pinned catalog commit and checks every policy against its sha256. That is the same hash shown on the policy's page. If the pack does not match, the install fails and chock writes nothing. The commit must be on a branch or tag the catalog publishes, so a link cannot point at a fork's code.

How to report a problem

Report it as a security issue in the chock-catalog repository. Do not open a public issue in the engine or site repositories.

Report a security issue →

What this site counts

The site counts page views and the few actions below, to learn which tools people use. Each action count carries only the action's name and the ids listed with it: never the address of the page, your selection, a share code, a policy you wrote or anything you typed. The site sets no cookie and stores no id. It stores no IP address, browser or account with a count. If your browser sends Global Privacy Control or Do Not Track, the site counts nothing. The chock command line tool sends nothing at all. Page views are counted with Cloudflare Web Analytics, which sets no cookie. It records the page address, referrer, country and browser type in aggregate. It does not load when your browser sends Global Privacy Control or Do Not Track.

The actions counted:

• Copying the install command in the builder, with the agent.
• Copying a share link in the builder.
• Downloading a selection file from the builder.
• Answering the builder's questions to the end.
• Picking a preset in the builder, with the preset.
• Downloading a setup script for a new policy, with its kind and agent.
• Opening an issue form from the Report an issue page, with the form.
• Clicking "Build for" an agent on a policy page, with the policy id and the agent.