Privacy Policy
Last updated 5 September 2026
UsageBox is a usage metering and billing service. This page describes what we collect, why, where it lives, and how to get it removed.
What we collect
- Account data — your email address, display name, sign-in provider, and the plan you are on. Collected so you can sign in and be billed.
- Catalog data — the products, meters, plans, charges, subscriptions and customers you configure.
- Usage events — whatever you send to
POST /api/v1/usage: a numeric or string value, an optional timestamp, and the ingest keys identifying which meter it belongs to. We also record the source IP and user-agent of the request for abuse investigation. - Operational logs — request paths, status codes, account ids and error details, used to diagnose failures.
You control what is in a usage event
UsageBox does not require any personal data in a usage event. If you use a unique_count meter you choose what the distinct value is — send a hashed or pseudonymous identifier rather than an email address or a raw user id wherever you can. We treat the contents of your events as your data and do not inspect them for any purpose other than metering.
Where your data is stored
Account, catalog and usage data is stored in Google Cloud Firestore in the European Union (multi-region eur3). The API compute that reads and writes it currently runs in the United States, so data is transmitted between the EU and the US in the course of serving requests.
Subprocessors
| Provider | Purpose | Location |
|---|---|---|
| Google Cloud (Firestore, Firebase Auth, Firebase Hosting) | Account data, catalog, usage events, authentication | European Union (eur3) |
| Hetzner Online GmbH | API compute | United States (Ashburn, VA) |
| Cloudflare | DNS, TLS and edge for usagebox.com | Global edge |
| Upstash | Cache (accounts, API-key lookups, profile aggregates) | Managed |
| Stripe | Payment processing for paid plans | Global |
| Mailjet | Transactional email | European Union |
| RapidAPI | Marketplace distribution and gateway metering | Global |
Analytics
The marketing site uses Statcounter for aggregate page-view statistics. The signed-in dashboard carries no third-party analytics and no advertising trackers.
How long we keep it
- Usage events and rollups — retained for as long as your account is open, because they are the evidence behind an invoice.
- Idempotency markers — 14 days.
- Event deduplication keys and unique-count membership — 45 days.
- Caches — 5 to 30 minutes.
Your rights
You can access and export your data through the API at any time. To correct, restrict or delete it — including a GDPR erasure request covering an end user whose identifier appears in your events — email [email protected]. We will respond within 30 days. If UsageBox is acting as a processor for your customers' data, you are the controller and we act on your instructions.
Security
Traffic is TLS-encrypted end to end. API keys are stored as SHA-256 hashes and cannot be recovered after creation, only rotated. Direct client access to the database is denied outright; every read and write goes through the API, which scopes it to your account.
Changes
Material changes to this policy will be announced by email to account holders before they take effect. See also the terms of service.