← Docket

Terms, in plain language

Everything you are agreeing to, in language you can read in one sitting. This is the licence agreement for Docket: the plain-language version is the agreement, and there is no second, meaner document behind it. Terms you cannot understand are terms you cannot agree to, so if a line below is unclear, that is our bug and we want to hear about it.

1 · What you are buying

You are buying a subscription to use Docket, a macOS app, on the machines you personally work on. What it pays for is the part that costs continuous work: keeping the connectors alive when Jira, Figma or Google change their APIs, and the updates that come from that. Purchases and billing are handled by Gumroad as merchant of record, whose checkout terms govern the payment itself; this page governs the product. Gumroad prices in euros and settles the charge in US dollars at its own rate, so your bank may add a foreign-transaction fee we neither receive nor can waive.

2 · Seats

One licence is one person, and you may activate it on every Mac you personally work on. A team plan is one licence per team member. What a seat is not: a pool of interchangeable logins, or one licence shared around a studio.

3 · The refund window

There is no trial. Instead, if Docket is not for you, tell us within 14 days of your first purchase and you get your money back. No form, no argument — the diagnostics paste from the app helps us fix what went wrong for the next person, but sending it is optional.

4 · The billing policy

Gumroad holds your card and runs the charges, so part of this is ours to promise and part of it is theirs to decide. Both are below, and which is which is said out loud.

• It renews on its own. A subscription keeps running until you stop it, and Gumroad charges the card on file on the same day of the period you first bought. Every charge produces a receipt by email.
• Nothing warns you before the charge, and we will not pretend otherwise. Gumroad decides which emails go out and when, and we cannot add one: Docket keeps no account for you and no server, so we do not know your renewal date. The receipt is the reliable signal, and it carries the link that cancels.
• The price you subscribed at is the price that renews. Gumroad can apply a new price to people who already bought, and we leave that switch off. If we ever turned it on, Gumroad emails existing members before the new price takes effect, and you can cancel first.
• You cancel it yourself. Open Subscription settings in your Gumroad receipt, or your Gumroad library, and stop it there. No form, nobody to email, no offer to sit through. The app keeps working to the end of the period you have already paid for. Cancelling does not refund that period; the refund window above is a separate promise, and that one is ours.
• A failed payment takes nothing away. If the card bounces, Gumroad may keep retrying it and may end the subscription; how often and for how long is Gumroad's call, not ours, so we will not put a number on it. On our side the licence stops validating and the connectors stop, while everything already synced stays readable and export keeps working, exactly as the next section says. Fix the card from that same Subscription settings link and the key works again on the next successful charge.
• Refunds. The refund window above is the promise. Ask, and the money goes back through Gumroad to the card you paid with.

If any of this turns out not to match what actually happened to you, mail us: either the words are wrong or the behaviour is, and both are ours to fix.

5 · If you stop paying

Your own work is never hostage to a payment state. When a subscription lapses:

1. Everything already synced stays readable, forever.
2. The export button keeps working, forever.
3. What stops is what costs us ongoing work: syncing, write-back, the planner and the AI drafting.

Offline is not lapsing: a validated licence keeps working for 14 days without reaching the licence server, because someone on a plane is a customer, not a suspect.

6 · Your data

Docket runs on your Mac. No server of ours holds your work, we hold no account for you, and we receive none of your work data. Besides the tools you connect, Docket reaches a few hosts on its own. The update check reads a small file from docketmac.com, which we run, and sends nothing about you; the licence check sends your licence key, the product id, and whether to count this Mac against the key, nothing else. The full list of network connections the app can make is on the security page, with an invitation to verify it yourself. There is no data-processing agreement to sign because there is no data processing to agree to.

When you record a meeting with Docket, you are responsible for getting consent to record from the other people on the call.

7 · Your tools and your credentials

Docket connects to your tools with credentials you create and own, such as an API token, and keeps them only on your Mac. Every read and write happens under your own account, so Docket can see and change exactly what you can, and each vendor's terms and your workspace's policies keep applying.

We never route your data through our servers, never sell it, and never write into your tools except on an action you took in Docket. Where those credentials are kept, and what that is and is not worth, is set out on the privacy page.

8 · What you may not do

Three things: resell, sublicense or redistribute the app; strip or defeat the licence mechanism; or present Docket as your own product. That is the whole list, and everything else you might do with it is fine.

9 · Honesty about liability

Docket is built by one person and sold at a price that reflects that. It is provided as-is; to the extent the law allows, liability is capped at what you paid in the last twelve months. What we owe you beyond that is effort and honesty: bugs get fixed in the open, and known limitations are documented rather than discovered.

10 · If Docket ends

If the product is ever discontinued, two things happen: the last version keeps working (no server of ours holds your work), and the source code is opened. The same pledge lives on the security page.

11 · Changes

If these terms change, the change is announced in the release notes and the old version stays in the repo history. Continuing to use the app after a change means accepting it; a change you do not accept is grounds for a pro-rata refund of the remaining period.

Governed by Dutch law. Questions about any of this, before or after you buy: hello@docketmac.com.