Privacy Policy

Who this policy covers

OpenRevenue is a privacy-focused web analytics service for website owners, product teams, and creators. This policy covers the OpenRevenue website, dashboard, tracker, APIs, billing pages, support channels, and related product features.

When a customer installs the OpenRevenue tracker on their own website or app, that customer controls the site, the project settings, and the data they choose to send to OpenRevenue. OpenRevenue processes that analytics data so the customer can view dashboards, realtime activity, performance metrics, and reports.

Account data we collect

When you create or use a OpenRevenue account, we may collect your email address, name, profile image, authentication sessions, one-time login codes, passkeys (WebAuthn credentials), authenticator app secrets and backup codes when you enable two-factor authentication, timezone, onboarding state, account preferences, team membership, invitations, support messages, and security-related logs.

We also store project information such as project names, domains, public stats settings, API key metadata, usage limits, plan status, billing status, and configuration needed to run analytics, realtime dashboards, and performance tracking.

Analytics data we process

For customer projects, OpenRevenue may process analytics events such as page views, custom events, page paths, referrers, timestamps, visit duration, session identifiers, visitor identifiers, browser, operating system, device type, country, city, region, approximate coordinates, and performance metrics such as loading and interaction timing.

The tracker is built for product analytics, not advertising. Customers should not send passwords, payment details, private messages, health data, government identifiers, or other sensitive personal information in page paths, event names, custom properties, or metadata.

Identifiers and cookies

OpenRevenue does not run an advertising network, sell visitor profiles, or use third-party marketing cookies inside the tracker. The tracker may use a first-party visitor or session identifier, such as browser storage or a first-party cookie, so customers can measure visits without relying on invasive cross-site tracking.

OpenRevenue does not intentionally build browser fingerprints for advertising or cross-site profiling. Our own OpenRevenue business analytics are also configured to avoid recording logged-in customer app browsing beyond the project root path, so we do not inspect what customers view inside their own project dashboards.

How we use data

We use account and product data to authenticate users, operate the dashboard, create and manage projects, calculate usage, enforce plan limits, provide public stats when enabled, respond to support requests, secure the service, and communicate important product or billing updates.

We use analytics data to generate reports, charts, realtime views, visitor counts, pages and source breakdowns, device and location summaries, performance insights, and aggregated usage trends for the customer who owns the project.

Billing and payments

If you subscribe to a paid plan, we may process billing contact details, plan selection, invoice history, subscription state, usage volume, and payment status. Payment processing may be handled by a third-party payment provider.

OpenRevenue does not need to store full payment card numbers to operate the service. Payment providers may process payment details according to their own security and privacy practices.

Sharing and subprocessors

We do not sell personal information. We share data only when needed to operate OpenRevenue, such as with hosting, database, email, payment, security, monitoring, and infrastructure providers, or when required by law.

When public stats are enabled for a project, selected analytics information may be visible to people with access to that public page. Customers control whether public stats are enabled for their projects.

Uploaded files and media

OpenRevenue is not a general file-hosting service. Website visitors cannot upload files through the tracker. Signed-in users may optionally upload an account profile image (avatar) and a project icon for branding in the dashboard.

Account avatars are stored in Cloudflare R2 object storage. OpenRevenue keeps the public URL on your user profile. Project icons are stored with the project in our primary database as an image data URL when a custom icon is set; otherwise we use the project's domain favicon.

We accept common image formats for these uploads. Do not upload passwords, payment details, identity documents, or other sensitive files. You can replace or remove avatars and project icons from the dashboard. More detail is available at /docs/advanced/uploads.

Retention and deletion

We keep account data for as long as your account remains active or as needed for billing, security, legal, support, and operational reasons. Analytics retention may depend on your plan, project settings, and the technical needs of the service.

You can delete projects, rotate API keys, disable public stats, and manage team access from the dashboard. Some records, such as invoices, security logs, backups, or aggregated data that no longer identifies an individual, may be retained for a limited period where needed.

Your rights and choices

Depending on where you live, you may have rights to access, correct, delete, export, or object to certain processing of your personal data. You can make many account and project changes directly in OpenRevenue, or contact us for help with a privacy request.

Website visitors should contact the owner of the website that uses OpenRevenue if they have questions about that site's analytics configuration. OpenRevenue helps our customers process analytics data, but the customer decides what to track on their own website.

Security and reliability

OpenRevenue uses technical and organizational safeguards designed to protect data, including authentication, access controls, encryption in transit, operational monitoring, abuse prevention, and limited access based on role and need.

No internet service is perfectly secure. We work to reduce risk, investigate security issues responsibly, and improve our systems as the product grows.

International processing

OpenRevenue and its providers may process data in countries where we or our service providers operate. When required, we use appropriate safeguards for international transfers and service provider access.

Customers are responsible for using OpenRevenue in a way that matches the laws and notices that apply to their own websites, visitors, and analytics configuration.

Changes to this policy

We may update this Privacy Policy when OpenRevenue changes, when we add new features, or when legal or operational requirements change. The date at the top shows when the policy was last updated.

For material changes, we may provide notice through the dashboard, email, or the OpenRevenue website.