For ecommerce, privacy, and agency teams
Find cookie-consent risk before it gets expensive
Cirv turns cookie and tracker checks into a plain score, grade, and issue list for EU ecommerce sites. Use it to see which stores may be loading trackers too early, what changed over time, and where to review consent setup first.
For store owners
See whether your homepage shows obvious cookie or tracker red flags before a privacy review, redesign, or ad-tech change creates cleanup work.
For agencies
Scan client portfolios, find risky consent setups, and turn the results into monthly privacy and ecommerce reports.
For teams
Monitor after tag manager, analytics, ad pixel, CMP, theme, or checkout changes so regressions do not sit unnoticed.
100 requests/day, no card required. Your key is shown once and can be copied with one click.
Plans
Free
Validate the fit before paying.
- 100 requests / day
- Scores & grades
- Per-site findings
- Community support
Starter
Cheaper than one hour of manual triage.
- 5,000 requests / day
- Full named dataset
- Per-site findings
- Email support
Pro
Built for ongoing monitoring.
- 50,000 requests / day
- Everything in Starter
- History & trends
- Priority support
Bulk
For agencies and larger portfolios.
- 500,000 requests / day
- Everything in Pro
- Bulk export
- SLA on request
- Pull a ranked list of stores and identify who may need consent review.
- Look up one domain and see the score, grade, failed signals, and top issue.
- Feed cookie-consent scores into dashboards, client reports, lead scoring, or privacy QA workflows.
- Compare competitors or client sites without manually opening every homepage.
Endpoints
| Method | Path | Returns |
|---|---|---|
| GET | /v1/sites | Ranked scores |
| GET | /v1/sites/:domain | Full report + findings |
| GET | /v1/usage | Your tier + limit |
Authenticate with Authorization: Bearer <key>. Keys are stored hashed; payments run through Stripe. Full docs: README.
FAQ
Is this a full legal cookie audit?
No. It is a static homepage scan that catches common cookie and tracker signals. It helps prioritize review, but it is not legal advice or a compliance guarantee.
Why should a non-developer care?
Cookie and tracker mistakes can affect customer trust, privacy review, advertising operations, and remediation cost. The score gives business teams a simple way to see where review is needed.
Why use an API instead of checking one page manually?
The API is for repeated checks: portfolios, client lists, dashboards, monitoring, exports, and trend reports. If you only need one site once, start with the free key.
Does a high score mean we are compliant?
No. A high score means no obvious static red flags were found on the homepage. JavaScript-injected trackers and legal consent details still need manual review.
Can agencies use this for clients?
Yes. Agencies can use it to find which client sites need consent review, support monthly reports, and show progress after fixes.