Last reviewed: 2026-06-03
MeterBox is a data processor under your Data Processing Agreement (DPA). You are the data controller for your end-customers. We process personal data only on your documented instructions (Art. 28(3)(a) GDPR) — billing the customers you tell us to bill, metering the usage you tell us to meter, sending the transactional emails you configure.
We use strictly necessary cookies only — bp_sid for the authenticated session and bp_csrf for cross-site request forgery protection. Both are set after you log in. No analytics, advertising, tracking, or third-party pixels are loaded on any MeterBox page. No cookie consent banner is required under ePrivacy / GDPR Art. 5(3) recital 30.
Lawful basis: contract necessity (Art. 6(1)(b)) for billing operations and legitimate interest (Art. 6(1)(f)) for the audit trail required to defend against fraud + meet SOC 2 / ISO 27001 control requirements.
Articles 15 (export) and 17 (erasure) are served from the same admin API your team already uses:
GET /v1/customers/{id}/dsar/export — JSON bundle of everything we hold on the subjectPOST /v1/customers/{id}/dsar/erase — anonymizes PII (name → [erased], email cleared), stamps erased_at, blocks further metering. Financial records are retained under the legal-obligation exception (Art. 17(3)(b))CCPA "Right to Know" + "Right to Delete" map onto the same two endpoints — same underlying flow, different statutory framing.
See the public list at /subprocessors. Material changes are notified at least 30 days in advance per Art. 28(2) GDPR.
Each tenant runs on a single-tenant data plane pod pinned to one region. Cloud and Managed tier customers pick the region at provisioning; Self-Managed deployments inherit your cluster's region. See docs and the Deployment tiers section on the home page.
DPA, privacy, or compliance questions: contact@meterbox.ai. Security disclosures: see /security.