Docket / Privacy

Privacy policy

By Matt Kerr·Published ·Updated

Docket is desktop software that runs on your Mac. This policy covers both the application and this website.

Docket for Windows is the same application and makes the same requests. Where this policy says Mac, read the Windows PC you run it on.

The application

Nothing about the sites you audit reaches us, Kerr & Company: the crawl and the report stay on your Mac. The requests that do leave it are listed below with who receives each one, and the only ones that come to us are for two public files on this website. What our payment provider receives on our behalf is your licence key and a name for each Mac you activate it on. There is no account, no telemetry and no crash reporting. The licence key is checked with our payment provider when you activate it and about once a day after that.

An earlier version of this policy said the only network requests the app makes are to the website you ask it to audit, and the next one named three kinds of destination. Neither was accurate, and a privacy policy is the last document that should be approximately true. This is every request the shipped app makes, read from its code, starting with the ones it makes unless you switch them off.

What it does by default

What turns each off

The offline switch turns off five of these together: PageSpeed Insights, the deliverability lookups, topic suggestions, the knowledge refresh and the edge-access checks. In the app it is the box labelled “Keep it private: only contact this site”, and on the command line it is --offline. It also keeps stylesheet fetches to the site you audit. It does not turn off the licence check, the update check, the link check or rendering. Unticking “Also check that links to other sites still work” in the app, or --no-link-check, turns off the link check, and rendering can be turned off only on the command line, with --render 0. There is no separate switch for each of the five: the offline switch is the one control. These runs ignore it, and always make the five checks and render pages as usual: re-audits of the sites you save, whether on their schedule, which runs only while Docket is open, or from “Check now”; docket diff; and docket logs --url.

What it does only when you ask

Audit results, your saved-site list and any crash reports are stored on your machine in ~/.docket/ as plain JSON files. They are never transmitted. Deleting that folder removes them permanently.

This website

This site is static and runs four third-party scripts. The first is Plausible, which counts page views. Plausible states that it uses no cookies, collects no personal data and does not track visitors across sites; it is hosted in the EU. Nothing about your audits reaches it. Audits run on your Mac and this website never sees them. Standard server logs may record IP addresses and requested URLs, which are used only to keep the site running.

The second is the chat assistant in the corner of the page, which answers questions about Docket. Its script is loaded from kerr-lead-agent.kerrco.workers.dev, a server we run. The assistant stores nothing in your browser (no cookie of its own, no local storage, no session storage), and it reads nothing about your device. It draws itself in an isolated shadow root, so it cannot see or change the rest of the page. If you type a question into it, that question is sent to that server so it can be answered; if you never open it, nothing is sent. It knows only published facts about Docket, and the price it quotes comes from the payment provider rather than from this page, so it cannot quote you a price the checkout will not honour.

The third is on the front page only: the founding-offer bar across the top of the page, loaded from kerr-lead-agent.kerrco.workers.dev, the same server as the assistant. When the page loads it asks that server whether the offer is still open, and the only thing it sends is this site's name. If you close the bar, the time you closed it is kept in your browser's local storage so the bar stays away for seven days; nothing else is stored and it sets no cookie. It draws itself in an isolated shadow root, like the assistant.

The fourth is on every page: a small script loaded from kerr-affiliate-hub.kerrco.workers.dev, a server we run, which is where our Download and Buy links point. It does three things. When you click a Download or Buy link, it marks the click as made by a person, because a crawler that only follows the address never makes a click, so we can count people apart from crawlers. If you arrive through an affiliate or partner link, with an id such as ref or via in the address, it keeps that id in this site's local storage for thirty days and adds it to the Buy link, so the person who recommended Docket is credited if you buy; it sets no cookie. And it adds where you came from, from the same short list as below, to Download links. It sends nothing itself. The server it points at counts downloads and Buy clicks per day, per page tag and country, and whether the click looked like a person; it stores no IP address and no user agent. If a content blocker stops the script, the links still work.

Until Docket for Windows was released, a form for visitors on Windows was written into this site's front page, download page and pricing page. It sent an address only when one was typed and the button pressed, to kerr-subscribe.kerrco.workers.dev, a server we run. The form is gone. The addresses it collected are used once, to say Docket for Windows is ready, and for nothing else.

One more thing runs here, written into this site's own pages rather than loaded from anywhere. If you arrive from a link that says where it was shared, such as ?ref=producthunt, from a fixed list of such names (Product Hunt, Hacker News, Reddit, a newsletter and the like), the page keeps that one word in your browser's session storage for this visit and adds it to its Download and Buy links, so we can count how many downloads came from a launch. It is never an affiliate id, nothing else is stored, and it is gone when you close the tab. Arrive any other way and it does nothing at all.

These paragraphs have been rewritten three times as the answer changed. They once said the site “sets no cookies” and runs “one third-party script”; both were true until Sled was added. The line calling Sled the only thing here that can set a cookie was true until Meta's advertising tracker was added. The count said three until the chat assistant was added, and the description on this page still said three after the body said four. Our own audit caught that, and it was corrected to five, which is when the Windows form on the front page was counted too. It said five while the front page loaded six: the founding-offer bar was missed until a count of every script on every built page was checked against this list, and that count now runs before every deploy. It said six until the click-counting script was added on every page. It went back to five on 2 November 2026, when Sled was retired; affiliate credit is kept by the click-counting script, without a cookie. It went to four four days later, when Meta's advertising tracker was removed: it sent every visit here to Meta and set a cookie to do it. This paragraph is the reason that was noticed: each correction is made above rather than quietly deleted. A privacy page that enumerates what a site does not do is only worth reading if the enumeration stays complete.

If you would rather not be counted, any content blocker stops it, and nothing on this site depends on it loading.

Data you give us

The free checkers send the address you type, and nothing else about you, to ai-crawler-check.kerrco.workers.dev, a server we run. Nothing is sent until you press the button. The AI crawler checker and the robots.txt tester make that server fetch the site's robots.txt. The SEO checker, the title and meta tag checker and the JSON-LD checker make it fetch the page at that address, read its title, meta tags, headings and structured data, and send back only the result of the checks, not the page. The redirect checker and the HTTP header checker make it follow the address hop by hop and send back each hop's address and status code and the final page's headers, never its cookies. The search result preview sends nothing: it runs in your browser. The server names itself in each request, keeps a copy of what it fetched for a few minutes so repeated checks do not hit the site again, counts checks per connection for a minute to stop floods, and keeps nothing else. The pages set no cookie and store nothing in your browser.

After a purchase, the page you return to asks kerr-affiliate-hub.kerrco.workers.dev, a server we run, what that payment came to, sending only the payment’s id, so our own sales count shows what you actually paid rather than the list price. Nothing about you is sent or returned.

The home page has one email field. Leave your address and we will email you once, when the free audit is ready. It is not a newsletter and there is no series to subscribe to. The form sends exactly two things, and only when you press the button: the address you type, and a hidden field naming which of our sites it came from. Nothing is sent if you never use it.

What is kept is that address, the site name, and the date. No IP address, no user agent, no referer, no fingerprint: the write stores those three columns and reads nothing from the request. To be removed, ask and the row is deleted.

This section said “there is no contact form and no mailing list” until 2026-08-24. The field went live on 2026-08-18, so the denial stood for six days while addresses were being collected. It is corrected here rather than quietly rewritten, for the reason given two paragraphs above: an enumeration of what a site does not do is worth nothing unless it is kept complete, and this is the enumeration failing.

If you open an issue on GitHub, that issue is public and GitHub's privacy policy applies to it; we hold nothing separately.

The Chrome extension

Docket page check, the free Chrome extension, has its own short page: what it reads and what it sends. It sends nothing to us.

Changes

If this policy changes, the updated version appears on this page.

Contact

Questions about privacy or anything else: get in touch.