Every tool works with measurement off. Hosted pages ask permission before sending any usage count. Your choice lasts only for the current page; no cookie, local-storage value or visitor identifier is created. Stop sharing at any time. Browser Do Not Track and Global Privacy Control signals keep measurement off.
No addresses, amounts, file names, file contents, pasted text, hashes, payment-request links, query strings, URL fragments, IP addresses, user-agent strings or stable user IDs are stored in the application analytics database. Input processing remains local. The hosting provider receives normal HTTP connection details and may maintain its own access logs.
These are optional event counts, not unique people, total visitors, sessions or verified human activity. Repeat actions can count more than once. Examples are separate from completed user-input actions. Downloads count a click, not completion. Donation-button clicks are not donations. Bots and synthetic events cannot be eliminated reliably without more invasive tracking.
Counts are aggregated by tool and UTC day. Arrival categories are counted only for participating page views. Aggregate rows older than 90 days are removed when a new valid event arrives. There is no public analytics report endpoint; the operator reads aggregates through the hosting database tools.
Downloaded offline editions omit the measurement script entirely. Their usage cannot be measured. Server collection uses only a fixed allowlist of event names and refuses payloads containing extra fields. For reproducible testing, ?ff_qa=1 records only in the separate QA counters after consent; do not count that traffic as growth.