Privacy, with the edges visible
Your work stays yours. We count only the signal.
LocalConvert keeps tool content in your browser. To learn which tools deserve more investment, we retain only daily aggregate counts.
Updated September 26, 202601Daily anonymous counts
Each counter answers one product question without creating an individual activity history.
Public beta figures begin at the configured launch instant and exclude owner testing before it.
- Bulk UTM export browser-days and returning export browser-days
- An optional quote-purpose or next-feature response was submitted
- The worked quote example was opened or its builder link was clicked
- A non-example quote PDF was exported again on a later UTC day
- Interest in a future paid quote feature was expressed
- A tool page was opened
- A tool produced a valid output
- An export or download was started, or Bulk UTM links were successfully copied
- An optional Bulk UTM feature preference was submitted
- The Token Contrast Pro/CI beta interest panel was opened
- A visit came from a new or returning browser
02What never enters analytics
The LocalConvert event payload and D1 aggregate table accept only a fixed tool name and a fixed action name. Extra fields are rejected.
- Files, file names, image bytes, or image metadata
- URLs, UTM values, QR content, email fields, or contact details
- YAML, JSON, text, copied values, or generated output
- Names, email addresses, stable visitor identifiers, or fingerprints
03Hosting and request delivery
Hosting infrastructure can process ordinary request metadata, such as IP address, referrer, or device information, to deliver requests, prevent abuse, and keep operational logs. LocalConvert does not add those values to its event payload or D1 analytics table.
04How returning visits work
Your browser keeps one local ‘has visited’ flag. On a later tab it sends only the category ‘returning’—never a browser ID. Clearing site data resets that flag. Quote repeat-use keeps only a last-export date locally and sends only the action category, once per later UTC day. Quote interest keeps a local yes/no flag. Neither value is sent. Clearing site data resets these flags. Bulk UTM also keeps a temporary “response sent” flag in tab storage to avoid asking again. These flags are not visitor IDs. Quote feedback keeps a local response-sent flag per question to reduce repeat prompts. Only the selected fixed answer category is sent; no quote or customer details are included. Bulk UTM export-day estimates store only the last qualifying export date locally. Copying or starting a download sends a fixed export-day category at most once per UTC day, plus a repeat-use category on a later day. The date is never sent. Clearing site data resets this estimate; blocked storage skips it.
05180-day limit
Rows older than 180 days are removed on the next valid analytics write. There is no raw event history to replay or connect to a person.
⌁LOCAL BY DESIGN
Your control
Blocking browser storage or /api/events does not disable any tool. Conversion, generation, copying, and downloads continue normally. Quote drafts, including costs, are saved on this device. Starting a new quote replaces the draft; clearing site data removes it. Private draft backups include costs, so share only the customer PDF.