← Docket

Everything you would want to know first

There is no trial, so you are deciding on what you can read rather than on what you have tried. Here is the lot: what leaves your Mac and how to check it yourself, what Docket writes back to your tools, and what happens to your work if you stop paying or if we stop building. If your question is missing, mail us and it gets answered here.

What actually leaves my Mac?

The hosts you connected, and very little else. Docket talks to the addresses you typed, with the credentials you connected: your Jira, your Linear workspace, your Confluence, your Figma, your mailbox. Your calendar is not network traffic at all, because it comes from your Mac's own Calendar through Apple's EventKit. On top of that the app reaches out by itself for the licence and update checks, for the speech model, about 574 MB from huggingface.co the first time you record or dictate, after which transcription runs here, and for an AI engine you chose, when you ask for a draft. By default the AI runs on this Mac only. External engines are your choice. Not on the list, because it does not exist: analytics, crash reporting, a telemetry endpoint of any kind. The security page enumerates every connection the app can make and says what each one sends.

How do I check that for myself?

Run Docket behind an outbound firewall for a day. Little Snitch takes about five minutes to set up, and then the answer above is something you watched rather than something you read. The hosts Docket can reach are published as a plain file, hosts.json, served from this site, so you can diff it against what your own firewall saw; a lint fails the deploy if the security page and that file disagree in either direction. That machinery is there because the paragraph inviting this test was once incomplete, which is why the list is generated from a file now instead of kept in someone's head. You are checking the app, not our word for it.

The notetaker records my meetings. Where does the audio go?

Nowhere. The recording is written to your Mac, the transcription runs on your Mac (local whisper), and the action-item extraction works on the transcript, never the audio. By default the AI runs on this Mac only. External engines are your choice. The Sensitive box starts ticked for every recording and keeps that transcript on this Mac whatever you chose. Untick it while an external engine is chosen, and the transcript can go to that company, as the security page says. The comparison page lists the ten meeting tools we checked in September 2026 and where each one transcribes.

Does it work offline?

Your work is already on the Mac in front of you, so most of the day survives. Everything already synced stays readable, your notes and your plan keep working, and the standup is built from what is on this Mac, so a flight is a working day. What stops is what needs the network: syncing and write-back. Docket reads Jira, Figma, Confluence and your calendar over the wire, and no local-first app can pretend otherwise.

Is it open source?

No, and here is what you get in its place. Your data is plain local files you can read and take with you. The app makes exactly the network connections listed on the security page, which you can verify with Little Snitch in five minutes. And if the product is ever discontinued, the source will be opened, the pledge Obsidian made. Docket is a paid app built by one person who has another job, so the €18/month is what keeps the connectors alive when Jira, Figma or Linear change their APIs.

Why is there no free trial?

You get something better than a trial: a 14-day refund window. Buy it, put your real work through it, and if it is not for you, say so and get your money back. Nothing to remember to cancel. The trade is deliberate: one person can support a small number of paying users well, or a large trial funnel badly.

Why macOS only?

Because you get a Mac app rather than a web app in a window: your calendar through Apple's EventKit with no OAuth to set up, the AI on Apple's on-device models, dictation in every app you use, your tokens in the Keychain. None of that is portable, and all of it is the point. Windows and Linux are not planned, and that is a stance rather than a backlog item. Docket runs on macOS 26 or later, on a Mac with Apple silicon. The helpers that read your calendar, keep your tokens in the Keychain, record, transcribe, dictate and run the on-device AI are built for that release.

Where does my data live?

On your Mac, as plain JSON files you can open. No server of ours holds your work, no account exists, and Settings has an Export everything button that works with or without a licence, forever. The security page lists every connection the app can make.

What does the AI run on, and does it see my tickets?

By default the AI runs on this Mac only. Generation runs on Apple's on-device model, and on Ollama if you run it on your own machine. External engines are your choice: the Claude CLI if you have it installed and signed in, whose prompts go to Anthropic through it, or a Gemini or Claude key you configured. They answer only once you pick This Mac first or Any engine on the AI engine card in Sources. On This Mac first, the two local engines still go first. If your install already used an external engine before this default, we kept the position it had. Anything you mark sensitive stays on this Mac whatever that setting says, and the Sensitive box starts ticked for every recording. The same card names the engine that answered your last request, and names any engine that was handed the prompt even if it did not answer, so you can check this rather than trust it.

What can write-back do, and what can it never do?

Six verbs, on Jira and Linear alike: comment on an issue, assign it, move it to another status, open a new ticket, set an estimate, set a priority. Jira can also take a work log; Linear cannot, because Linear has no native time tracking, and offering a verb we cannot honour is worse than not offering it. Docket also replies to a Figma comment and puts a focus block on your calendar. What you send yourself, a comment or a status, is written when you send it. Proposals wait for your approval: drafts from Ask, voice proposals, plan blocks, meeting follow-ups and cards from outside. Settings, Automation, Assistant actions starts on Propose; set it to run automatically and Ask's writes go out without asking. What it never does: write to your mailbox, which is read-only by protocol. Writes you send or approve are queued and retried until they land, so one made while offline goes out on a later sync without asking again. The audit log records each one, because a tool that writes into your employer's systems should be able to show its work.

What renews, what does a failed card do, and how do I cancel?

The monthly plan renews each month and the yearly plan each year, on the day you bought. A failed card gets retried by Gumroad and you get an email; nothing is deleted while that happens. You cancel from the Gumroad receipt in one click, without asking us, and the plan runs to the end of the period you paid for. Everything already synced stays readable and export keeps working whatever the payment state. The exact wording is the billing policy on the terms page.

What happens if I stop paying?

Everything already synced stays readable, forever. Export keeps working, forever. What stops is what costs ongoing maintenance: syncing, write-back, the planner and AI drafting. Your own work is never hostage to a payment state, and the terms say so too.

What happens if you stop building it, or get hit by a bus?

The app keeps working, because no server of ours holds your work. Everything already synced stays readable, your files stay plain JSON on your Mac at ~/Library/Application Support/Cockpit, and Export everything keeps working with or without a licence. The discontinuation pledge then applies: if we ever stop maintaining Docket, the source gets opened. The same pledge is on the security page. What we will not do is put a date on any of it.

My company requires a security review / DPA. Can we buy?

You can buy it yourself, on your own card, and expense it. That is who Docket is sold to: people who can decide for themselves. What we cannot do is procurement. There is no data-processing agreement, because your work never reaches us to be processed, and we are not staffed for questionnaires and review calls. If the purchase has to clear a vendor review, this is not the tool to put through it.

What if my company blocks a tool?

Then Docket cannot reach it either. Docket talks to Jira, Confluence, Figma and the rest the way you do: from this Mac, with your own access, over the same network. If a source is blocked for you, it is blocked for Docket, and the source card says which one could not be reached and why. Docket works with what you can already reach. We do not claim to get past an IT policy, and a tool that did would not be one to trust with your employer's systems.

Which tools does it read?

Nine built in, plus a connector library, and they arrive as one list. Jira (several accounts at once, Cloud and self-hosted alike), Linear, your calendar, Confluence, Obsidian, your mail server (read-only), Figma comments (including the ones addressed to your teammates), Dovetail and Miro. On top of those, the connector library covers tools such as GitHub, Asana and Notion: paste a token, and the work assigned to you there counts in Needs you like a Jira issue. Any other JSON endpoint can be a feed, which shows on Today and is never counted. Writing back works for Jira and Linear (comment, assign, transition, create, estimate, priority, with work logging on Jira only), your calendar (focus blocks) and Figma (replies); connectors from the library and feeds only read. The setup page says what each credential can reach.