openCenter LogoopenCenter
Back to Home
Trust
Public overview

Subprocessor List

The current public list of third parties used to support the openCenter website and related service workflows.

This page focuses on subprocessors evidenced by the current website implementation. Customer-specific managed-service or deployment vendors may be disclosed separately based on the actual service scope.

A public subprocessor page only helps buyers if it stays specific. Each listed vendor below is tied to a concrete website-facing function today.

Subprocessor List
Last updated May 21, 2026

Purpose

Discloses known subprocessors, what they do, and how change management should work for buyer trust reviews.

Primary audience
Legal, compliance, procurement, privacy teams
Scope
Public website analytics and contact-form delivery workflows
Update model
Material changes should be reflected on this page before or when they go live
Questions
Use the contact form for vendor or transfer questions tied to an active evaluation
Website-specific list

Only vendors supported by the current repository are listed here, which keeps the page credible and easier to maintain.

Transparent processing purpose

Each vendor entry explains what data category it touches and why the service exists in the stack.

Procurement follow-up

Enterprise or managed-service subprocessors may require a deeper customer-facing register during contracting.

Current Public Website Subprocessors

PostHog

Purpose: optional website analytics unless a visitor opts out. Data categories: usage and device metadata collected before opt-out. Region: depends on the configured PostHog host for the site.

Mailgun

Purpose: delivery of website contact-form submissions to openCenter. Data categories: name, email address, and message content supplied by the visitor. Region: US or EU depending on the configured account region.

How Changes Are Managed

When openCenter adds or replaces a public website subprocessor, this page should be updated as part of the rollout so buyers and visitors do not have to reverse-engineer the stack from source code or browser traffic.

Customer-specific service vendors, cloud providers, or support subprocessors should be disclosed in the trust package that matches the purchased service scope.