- What counts as a capture?
- One completed upload. Asking for PNG, PDF and SVG in the same call is one capture, not three — the page is only rendered once, so charging three times would be daft.
- What happens when I go over?
- Captures stop. Your users see the export fail until the month resets or you add capacity, so we warn you well before it happens — by email, with enough left to do something about it: 100 remaining on Free, 1,000 on Pro, 5,000 on Business. Adding a pack restores them immediately.
- Why stop rather than bill me for the overage?
- Because a surprise invoice is worse than a surprise error. An export button that fails is visible in minutes and fixed in one click; an unexpected bill is found weeks later and argued about. If you'd rather it never stopped, buy a pack ahead of the month — they stack and they don't expire mid-month.
- Do packs and plans stack?
- Yes. Packs add to whatever your plan already allows, and you can hold several — Pro plus a 50k and a 10k is 85,000 captures. That is the answer to volume between the tiers, and it needs no conversation with us.
- Where are the files stored?
- In our Supabase storage bucket, in the EU, private, served through signed URLs that expire with the capture. Captures are deleted after three days by default and seven at the most.
- Do captures leave the browser before my user confirms?
- No. Rendering, annotation and redaction all happen client-side. Nothing uploads until the user hits Send — and redacted regions are destroyed before encoding, so the original pixels are never in the file at all.
- Can I self-host?
- Not as a supported product today. The SDK is the part that matters and it runs entirely in your users’ browsers; the API is a thin upload-and-notify layer.
- How do I cancel?
- One button in the dashboard, no email required. Your keys keep working until the end of the period you paid for.