Privacy policy

Last updated: 14 September 2026

1. Controller

Klaus-E. Klingner, operating as SilverDay Media, c/o IP-Management #6585, Ludwig-Erhard-Str. 18, 20459 Hamburg, Germany. Contact: klingner@silverday.de.

2. What ClearStats processes

For a pageview, the tracked site sends the site identifier, page path, referrer domain, event type, and optional bounded campaign or custom-event values. The ClearStats server receives the request IP and User-Agent as part of normal HTTP processing.

3. What is not retained

The raw IP address and raw User-Agent are used only transiently to derive a daily, site-specific HMAC visitor hash. They are discarded before the event enters the Redis queue or database. ClearStats does not store cookies, persistent browser IDs, localStorage/sessionStorage identifiers, fingerprints, names, email addresses, or cross-day visitor identity.

4. Aggregated analytics

Short-lived raw events are rolled into daily aggregates: pageviews, daily unique visitor hashes, ephemeral sessions, engagement and bounce metrics, pages, referrers, countries, devices, campaigns, and named events. Raw events are purged per site retention policy.

5. GeoIP

When configured, a local MaxMind country database resolves a country code in memory. Only the two-letter code is retained. A trusted proxy country header may be used as fallback. The GeoIP database is operated by the site owner.

6. Hosting and operators

ClearStats is self-hosted. The organization operating a ClearStats instance controls its hosting, database, Redis service, backups, access logs, and retention settings. This notice describes the ClearStats software model; the operator must adapt it to the actual deployment.

7. Rights and requests

For questions about this ClearStats installation or requests concerning operator-managed account data, contact the installation operator. For software questions, contact klingner@silverday.de. You may also have rights under applicable data protection law, including access, rectification, deletion, restriction, objection, and complaint to a supervisory authority.

8. Changes

This policy may be updated when the software, deployment, or legal requirements change.