Plans & billing
What exactly counts as a tracked event?
One event is one action you send us with a timestamp and a user reference — a checkout completed, a document shared, a background job finishing. Page views count once per load, not once per scroll.
Properties attached to an event are free, however many you send, and identity merges never bill twice for the same person.
What happens the month we go over our ceiling?
Nothing stops. We keep ingesting, flag the overage in your workspace banner at 90%, and invoice the excess at your tier's per-event rate on the next cycle. Two grace months a year come standard.
Can we move up or down a tier mid-cycle?
Yes, from the workspace settings, on any day. Upgrades take effect immediately and we prorate to the hour; downgrades hold until the cycle closes so nobody loses a dashboard mid-quarter.
Is annual billing cheaper than paying monthly?
An annual commitment lands about 17.5% under twelve monthly invoices, and it locks your per-event rate for the term. Purchase orders, wire transfer and card all work; net-30 terms are available above the growth tier.
Do early-stage teams get a reduced rate?
Companies under four years old that have raised less than $9M get their first twelve months on the growth tier at no cost. Apply with your incorporation date and a cap table summary — approvals usually come back in three days.
Data & access
Where does our event data physically live?
You pick a residency region when the workspace is created — Oregon, Frankfurt or Singapore — and raw events never leave it. Backups replicate inside the same region only, which is what keeps GDPR reviews short.
How far back do you keep raw history?
Free workspaces query the trailing 18 months. Paid tiers keep raw events for five years and rolled-up daily aggregates indefinitely, so year-over-year charts survive long after the underlying rows are archived.
Can we stream events into our own warehouse?
Yes. Continuous export writes newline-delimited JSON or columnar files to your own object storage on a fifteen-minute cadence, with a schema file per stream. Reverse sync back into a workspace is available on request.
How do permissions work once a team grows?
Projects are the boundary. Each one carries its own viewer, editor and owner roles, and sensitive properties can be masked so support staff see behaviour without ever reading an address or a phone number.