HTTPClarity does not track reading behavior

The launch model uses synthetic checks and sanitized operations data, not visitor analytics, accounts, advertising, or saved Lab requests.

Data not collected

HTTPClarity does not collect page views, sessions, search terms, scroll behavior, Lab completion, referral clicks, returning-reader identifiers, advertising identifiers, or device fingerprints. It has no accounts and stores no request history.

Limited operational evidence

VMCSoft Digital may record build and deployment outcomes, synthetic test results, aggregate infrastructure usage, and sanitized Lab route outcome, latency, exception, or rate-limit events. Operational events exclude IP address histories, bodies, raw fields, cookies, credentials, full query strings, fingerprints, and visitor-provided URLs. The current Workers Logs retention is three days and may never exceed 30 days under the launch policy.

Deliberate correction reports

Correction and feedback reports deliberately emailed to [email protected] are separate from behavioral analytics. The report, sender address, and reply thread are limited to the VMCSoft Digital maintainers handling it and are deleted when no longer needed, no later than twelve months after resolution unless a legal or security obligation requires longer. No HTTPClarity account is required, and reporter identity is not published without permission. Read thecorrection process.

Changes require a new decision

Adding behavioral analytics requires an explicit architecture decision defining purpose, fields, retention, access, privacy impact, and removal. It does not happen automatically after launch.