Data Policy

1. Analytics event data

OpenRevenue records web analytics events such as pageviews, custom events, referrers, paths, durations, browser, operating system, device, session and visitor identifiers, timestamps, and optional performance metrics (Core Web Vitals). Those events are stored in ClickHouse on Hetzner in Falkenstein, Germany.

Approximate geolocation (country, region, city, coordinates when available) is derived at ingest from infrastructure geo headers. IP addresses are processed for geo, security, and identifier fallback, and may be stored with events even though they are not surfaced as a primary dashboard column.

2. Browser storage

• First-party cookie _ova_vid and/or localStorage for a random visitor ID.
• sessionStorage _ova_sid for the current session.
• Server-side daily-rotating hash fallback when client storage is unavailable.

3. Data we do not want

Do not send the following. If a path may contain sensitive values, use blocked or masked pages, or change your application routing so those values never reach the collector.

• Passwords, session tokens, or API keys in URLs or events.
• Payment card numbers, bank data, or government identifiers.
• Health, biometric, or other special-category data.
• Private message contents or form field values.
• Advertising profiles or cross-site tracking graphs.

4. Project controls

OpenRevenue includes controls for allowed hostnames, blocked IP addresses, blocked pages, masked pages, public stats, team roles, API keys, widgets, and reporting timezone. Use them to keep collection scoped to useful traffic.

5. Optional connected data

Revenue attribution, Google / Plausible history imports, Search Console, Slack alerts, and Enterprise SSO only process additional data when you connect them or upload an export. Disconnect or roll back imports to stop new processing.

6. Accuracy

Analytics can be affected by ad blockers, privacy tools, DNT, GPC, network issues, bots, script placement, and sampling effects. OpenRevenue aims for useful directional insight, not a perfect census of every human action.

7. Access and sharing

Project owners and invited teammates see analytics according to their roles. Public stats and widgets are off unless you enable them; enabling them publishes the selected numbers to anyone with the link or embed.

8. Retention and deletion

Analytics history is intended to remain available while a project exists, subject to plan and operational practice. Deleting a project removes associated analytics access and data through our deletion workflows. Account deletion and billing/security retention follow the Privacy Policy.

9. Related documents

• Privacy Policy (/privacy) — full collection, subprocessors, transfers, and rights.
• DPA (/dpa) — processor terms for customer analytics data.
• GDPR (/gdpr) — practical GDPR mapping and customer checklist.
• Terms (/terms) — contract for using the service.