Subprocessors

These are the providers Egger, Inc. uses to run OpenRevenue, and what each one processes. This page is the subprocessor register referred to in our Data Processing Addendum.

Last updated: November 19, 2026

1. Current subprocessors

Each provider processes data only to deliver the purpose named here, under a contract with us. Where data leaves the EEA, UK, or Switzerland, the safeguards in the Privacy Policy (International transfers) and the DPA apply.

  • Vercel

    Purpose
    Hosts the OpenRevenue application, APIs, MCP server, and marketing site; provides the request geo headers used at ingest; Web Analytics and Speed Insights on openrevenue.com.
    Personal data processed
    Visitor events and IP addresses in transit at ingest; account and dashboard data in transit.
  • Hetzner (Falkenstein, Germany)

    Purpose
    Hosts our self-hosted ClickHouse server that stores and queries analytics and bot events.
    Personal data processed
    Stored visitor analytics events and bot events.
  • PlanetScale

    Purpose
    Managed Postgres for accounts, projects, billing state, settings, AI-assistant conversations, and related application data.
    Personal data processed
    Account, workspace, and project data; AI-assistant conversations.
  • Upstash

    Purpose
    Managed Redis for caching, rate limiting, the daily visitor-hash salt, and server-side sessions.
    Personal data processed
    IP addresses as rate-limit keys (about one minute); session IDs; cached aggregate reports.
  • Cloudflare

    Purpose
    Network proxy in front of the ClickHouse endpoint; transactional email (Email Service); R2 object storage (avatars, private temporary history-import ZIPs, and off-site database backups).
    Personal data processed
    Visitor analytics in transit and in backups; email addresses and email content; uploaded files.
  • Stripe

    Purpose
    Subscription billing for OpenRevenue plans and add-ons.
    Personal data processed
    Billing contact and payment details of customers.
  • Sentry (EU region)

    Purpose
    Error monitoring on openrevenue.com, with masked replays of sessions where an error occurs (sendDefaultPii off).
    Personal data processed
    Error reports and masked replays from sessions with errors on the dashboard and site.
  • Mapbox

    Purpose
    Map tiles for realtime globe visualizations in the product.
    Personal data processed
    IP address and browser details of the person viewing the map.
  • Vercel AI Gateway, OpenAI

    Purpose
    Answers in-dashboard AI assistant questions and runs the free AI generator tools, when you use them.
    Personal data processed
    Prompts and the aggregate analytics context needed to answer them.
  • Google

    Purpose
    Optional Google sign-in; PageSpeed Insights API for the free Core Web Vitals checker (the URL you enter).
    Personal data processed
    Sign-in identity; URLs entered in the free checker.
  • GitHub, Apple

    Purpose
    Optional sign-in with those accounts.
    Personal data processed
    Sign-in identity.
  • Telegram

    Purpose
    Delivers traffic and goal alerts to a Telegram chat the customer connects to our bot.
    Personal data processed
    Chat ID; alert text with project names and aggregate numbers.

2. Services you connect yourself

Some services only receive data because a customer connects them, and the customer chooses the provider. They are not OpenRevenue subprocessors: a customer's own revenue provider (Stripe, Paddle, Polar, Lemon Squeezy, Shopify, RevenueCat), a Slack webhook, Google Analytics or Search Console, Umami, Fathom, or Matomo accounts used for imports, AI assistants connected over MCP or the API, and Enterprise SSO identity providers.

3. How we announce changes

When we add or replace a subprocessor that processes customer personal data, we update this page, its date, and the change log below before the new provider starts processing.

A customer who objects to a new subprocessor on reasonable data-protection grounds can tell us at support@openrevenue.com. If we cannot offer a workable alternative, the customer may end the affected service, as section 7 of the DPA describes.

4. Change log

  • November 19, 2026: Sentry session replays limited to sessions where an error occurs; nothing stored in the browser.
  • November 19, 2026: list published as its own page. Providers unchanged from the Privacy Policy of the same date.

5. Contact

Egger, Inc., 2810 N Church St # 89471, Wilmington, DE 19802, United States. Questions about subprocessors: support@openrevenue.com.

These pages describe OpenRevenue's standard product and data practices. They are not legal advice. If your use case has special legal, regulatory, or contractual requirements, contact the OpenRevenue team so we can review the right setup with you.