Privacy Policy

The short version: nothing about the processes, ports, projects or file paths on your machine is ever sent to us. The app is not a telemetry product, and there is no account to create. The one thing that can leave your Mac is a project you deliberately share — and that goes to your own network, never through us.

What the app sends

Localdock runs entirely on your Mac. It reads your own processes to show them to you, and that data stays local — it is never transmitted, stored remotely, or shared.

The app sends us one kind of request that carries anything about you, for licensing:

• Your license key, so we can check it is valid.
• An instance ID — a random identifier generated on first launch to enforce the single-device limit. It is not derived from your hardware and identifies nothing but the installation.
• Your device name (for example “Dmytro’s MacBook Pro”), so you can recognise which machine to deactivate when you migrate.

That request goes to localdock.dev and is forwarded to Creem, who manage licensing. Nothing else is attached to it — no list of your projects, no ports, no paths, no usage counts.

The app also asks localdock.dev which version is current, when you pick “Check for Updates…” — a plain request for a version number that carries no information about you or your machine.

Your licence key is stored in your macOS Keychain so you only have to paste it once. There is no trial timer and nothing else is kept locally about your licence.

When you share a project

Sharing is off for every project until you switch it on, one project at a time. While a project is shared, two things happen on your own network and nowhere else:

• The name you gave that project is announced on your local network (as name.local), so other devices can find it. This is the same mechanism macOS already uses to announce your Mac by name. Only the projects you switched on are announced.
• That project answers requests from devices on your network. Anything not on your allowlist is refused without revealing whether it exists, and the page that lists your dev servers is never served beyond your own Mac.

None of this passes through us and none of it is recorded anywhere. Switch sharing off, or quit the app, and it stops.

When you share a project on the internet

This is a separate switch from Wi-Fi sharing, also off by default and also per project. When you turn it on:

• The first time ever on that Mac, the app asks us for a permanent web address. That request carries your licence key and instance ID — the same two things the licence check already sends — and nothing else. It does not include your project name, your port, or your file paths. The address we hand back is randomly generated and means nothing.
• Every share after that involves us not at all. The address is kept in your Keychain, so no request is made and there is no record anywhere of when you share, what you share, or whether anyone opened the link.
• The traffic goes through Cloudflare, not through us. The tunnel runs between your Mac and Cloudflare's network; they carry the requests and terminate the HTTPS, which means they are technically able to see that traffic. We are not, and never are.
• Cloudflare stores a one-way hash of your licence key alongside the address, which is how we cap how many addresses one Mac can hold without keeping a database. It cannot be turned back into your key.

The link carries a secret key and expires after an hour. Anyone reaching the address without the key is refused with a page that names nothing. What you choose to put on the public internet, and who you send the link to, is your decision and your responsibility.

What this website collects

• Vercel Analytics and Speed Insights — aggregate page views and performance timings, without cookies.
• DataFast — visitor analytics, which sets a datafast_visitor_id cookie so we can tell which channel a purchase came from. It records pages viewed and, on purchase, the sale amount. It does not profile you across other websites.
• Creem — when you buy, they collect the billing details needed to take payment and issue an invoice. They are the merchant of record and their privacy policy governs that data; we never see or store your card number.

We keep no customer database of our own. If you email us, we have your email in a mailbox, like any other correspondence.

Your choices

Blocking analytics scripts does not affect the product. To have any record of your purchase deleted, or to ask what is held, email hey@localdock.dev and we will action it and confirm within 3 business days. Payment records Creem must retain for tax and accounting purposes are governed by their retention rules, not ours.

Changes

If this policy changes in a way that affects what leaves your machine, we will say so here and date it. The commitment in the first paragraph is not something we intend to walk back.