Simple activity counts, without visitor profiles

These free tools automatically send small aggregate measurement events unless you disable them or your browser sends Global Privacy Control or Do Not Track.

What is counted

Tool page loads, completed tasks, built-in examples, tool errors, prepared downloads, donation-button actions and successfully copied donation addresses. A completed task is a result produced by the tool, not a guarantee that it is correct for your situation. A download count means an export was prepared or initiated, not that the browser saved it. Donation clicks and copies are interest signals, not donations or income.

Each page load can count once toward a successful-use, donation-click or donation-copy conversion rate. Repeated successful actions are counted separately. Examples do not count as real task completions. Collection and guide pages are excluded from tool conversion totals. Explicit QA and browser-declared automation counts are separate. Automation that does not declare itself can still appear in ordinary counts.

What is sent and stored

The measurement payload contains only a fixed site label, a fixed event label, the UTC day of the page load, a test-mode flag and a first-action flag. No entered text, addresses, file contents, filenames, full URLs, referrers, visitor identifiers, fingerprints or cross-site IDs are included. The measurement code does not store IP addresses, user agents or individual event records. Hosting providers still process standard network information, such as IP addresses, when serving pages and receiving requests.

The measurement code creates no cookies or visitor-tracking storage. Hosting infrastructure may use its own security cookies. If you choose Disable counts, one ordinary browser preference is stored only on that site: measurement disabled. It contains no identifier or timestamp. Other tool-specific local saving remains described by each tool.

Your choice

Use Disable counts on this site in the page’s measurement panel. It stops future sends, cancels queued requests and remembers your choice where browser storage works. Your tools keep working. Already aggregated counts cannot be associated with you or individually erased; a request already received cannot be recalled. Clearing site storage clears this preference. To re-enable, use Allow counts on next page load, then reload. Global Privacy Control and Do Not Track always take priority.

Limits and retention

These are recorded page loads, not unique people, sessions or proven human visitors. Reloads count again. Offline/downloaded copies do not report activity. Blocking scripts, browser privacy settings, disabling measurement, connection failures and bots affect counts. A page sends at most 100 events and stops after 24 hours. Delivery failures are not retried, so some counts may be missing. Public counters cannot prove human use or prevent all forged requests.

Reports show a rolling 90-day window. Older aggregate rows are deleted when the next valid measurement event is accepted; deletion can therefore be delayed if no events arrive. Counters are capped at 100,000 per site, day and metric. Legacy opt-in measurements are kept separate from current conversion reporting. This notice describes the implementation, not a certification of legal compliance.

Return to the tool