Privacy
Privacy and access logs
Codex100 keeps limited technical access logs to operate, secure and improve the public tracker. We do not sell visitor data or use it to build advertising profiles.
What we record
Visit time, encrypted IP address, page path, selected campaign parameters, referring host, approximate country/region/city, device category, browser family, operating system, bot classification and Cloudflare Ray ID. When a visitor uses sharing tools, we also record an anonymous share code, the chosen sharing method, the public page being shared and high-intent actions such as opening official evidence or adding a community +1 request. If you request probability alerts, we store an encrypted email address, a keyed deduplication value, confirmation status and the 80% threshold. A business partnership application stores the product and contact details you submit so an operator can review, schedule and administer the placement.
What we never put in access logs
Cookies, passwords, session tokens, arbitrary form bodies, email contents and full query strings. Browsers do not reveal the destination app selected from a system share sheet, and downloaded images can be reposted anywhere, so Codex100 labels those channels as unknown instead of guessing.
Retention
Encrypted IP values are removed after 7 days. Detailed visits are removed after 30 days. Daily pseudonymous visitor keys and share-creator identity dimensions are removed after 180 days. Unconfirmed email subscriptions are removed after 7 days; unsubscribing removes the encrypted address immediately and the remaining suppression record after 30 days. Business partnership applications are retained as operational records for review and placement administration; contact us to request deletion. Non-identifying daily aggregates, anonymous share codes and action counts are retained for long-term trend analysis.
Why we process this data
Security investigation, abuse prevention, reliability diagnosis and understanding which public pages, sources and anonymous sharing paths are useful. Share creators can see aggregate impact counts for share codes retained by their own browser; visitor identities and IP addresses are never returned by that public impact view.
Questions or requests
Contact hello@codex100.com for privacy questions or a request concerning your data. Requests are evaluated under applicable law and may require enough information to locate the relevant records.