Privacy Policy

Precision Auto Clicker does not collect, transmit, sell or share any personal data. Everything it does happens inside your own browser. There is no account, no analytics, and no server that receives your settings or the pages you use it on.

What the extension stores

Your settings are saved locally in your browser using Chrome's own storage API (chrome.storage.local). That covers:

• clicking preferences — interval, step list, engine choice, saved sequences;
• the points you placed and where you dragged the floating panel;
• your hotkey bindings and any per-site profiles you created;
• a licence key, if you entered one, and the local record that it was valid.

This data never leaves your device. It is not synced to any server, and it is removed when you uninstall the extension or clear your browser data.

What the extension does not do

Practice	Status
Collecting personal information	Not done — no names, emails, addresses or identifiers are gathered.
Collecting browsing history	Not done — the extension never reads, records or uploads the pages you visit.
Analytics or telemetry	Not done — there is no analytics SDK and no usage reporting of any kind.
Sending data to a server	Twice, in two narrow cases — see below.
Advertising or tracking	Not done — no ads, no trackers, no affiliate links. There is a promotional panel in the popup, and it is switched off in this build; it loads nothing at all while it is off.
Sharing with third parties	Not done — there is nothing to share.
Selling data	Not done.

The two times it contacts a server

There are exactly two, they belong to the two ways of paying, and neither happens unless you enter a licence. If you never enter one, the extension makes no network requests at all.

A subscription licence

Checked against our payment provider, Dodo Payments, because they are the only party who knows whether a subscription is still being paid for.

• What triggers it: entering a subscription key, and then about once a week to confirm it is still active.
• What is sent: the licence key itself, and nothing else. No page you visited, no settings, no usage, and no identifier for you or your machine.
• Where it goes: Dodo Payments' licence validation endpoint (live.dodopayments.com).
• If it cannot connect: a subscription keeps working for two further weeks. Being offline, on a plane, or behind a firewall will never switch off something you paid for — and a failed check is never treated as a cancelled subscription.

A one-time licence

Verified on your machine against a public key that ships inside the extension — the key is a signed token, and the signature is what proves it is genuine. That check needs no server and never will.

It contacts our licence server once, at the moment you enter it, and never again. This is new: it used to make no request at all. The reason for the change is that a key that can be verified entirely offline also cannot be limited, so one buyer could publish their key and any number of people could use it. A one-time licence now works on three devices, and counting them requires asking the server once.

• What is sent: the licence key, and a random identifier for this browser profile. That identifier is generated by the extension itself — it is not derived from your hardware, your screen, your fonts or anything else about the machine, and it means nothing outside this one purpose.
• Where it goes: our own licence server (pac-licences.*.workers.dev), not a third party.
• After that: nothing. Every later use is the same offline signature check, forever. It works with no connection, on a plane, behind any firewall, and it does not check in again.
• If it cannot connect: the key is not activated, and the extension says so plainly — that it could not reach the server and to try again — rather than pretending the key was wrong. Nothing is used up by a failed attempt.
• Reinstalling does not cost a device. Activating the same browser profile again is free. If you genuinely run out, one of the old devices can be released and the slot reused.

Dodo Payments is the merchant of record for purchases. Their handling of the purchase itself is covered by their privacy policy; this page covers the extension.

Why the extension asks for its permissions

• Read and change your data on all websites (host_permissions) — the floating control panel has to appear on whatever page you want to act on, and the lightweight engine dispatches input events into that page. The extension does not read page content; it only inserts its own panel and sends input events.
• Access the page debugger backend (debugger) — used only while the precise engine is actually running. It lets the extension send mouse input through Chrome's own input pipeline so the input is treated as genuine. The debugger is detached the moment the run stops. Chrome shows its own “debugging this browser” notice while this is active; that notice is Chrome's, not ours, and cannot be hidden.
• Scripting — to place the control panel and run the sequence on the page you chose. This is also how the on/off switch works: switching the extension off unregisters the script, so pages opened afterwards do not load it at all.
• Storage — to save the settings listed above.
• Display notifications — not requested.

Children

The extension is a general-purpose desktop utility. It is not directed at children and collects no data from anyone.

Changes to this policy

If this policy ever changes, the new version will be published at this same address and the date at the top will be updated.

Contact

Questions about privacy: afunnylin@gmail.com.