Pricing

One pageview on a protected site. Not one ad slot, not one impression, not one beacon. A page with six ad slots is one hit. We can bill this way because of how the tag reports: a single summary beacon fires per pageview carrying exact counts computed locally on the page — impressions, violations and blocks, broken down by policy — rather than a sample we then extrapolate from. Your invoice is derived from a count your reader's browser actually made. Billing a customer from a statistical estimate is indefensible; we do not do it, and this is why.

We email you at 80% and at 100% of your included volume, and then we bill the overage at your plan's rate. We do not turn off protection for a billing problem. Past a hard limit we reduce clean-impression sampling and lock report export — the blocking keeps running. Degrading a security control because an invoice is late converts a payment issue into a malvertising incident, and it is your readers who pay for it. That is a product decision, not a courtesy, and it is written down in our architecture document.

Upgrade whenever you like: it takes effect immediately and your pre-upgrade usage is prorated onto the next invoice rather than discarded. Downgrades take effect at the end of the current period, so you keep what you paid for. Plan changes happen in our own interface; the Stripe billing portal handles payment method, invoices and cancellation. Annual plans are two months free and are billed up front.