Evidence, not inference
Up to five public pages, each in a fresh Chromium context. Set-Cookie headers, the cookie jar, localStorage and sessionStorage keys, scripts, iframes, pixels and XHR — captured with the page and request that produced them.
ComplyMore scans your website, shows you every tracker it actually observed with the evidence behind it, and holds publishing until a person has decided the unclear cases. No dashboard green tick standing in for a legal opinion.
Try the complete workflow on one site for 14 days. No script tag needed until you publish.
Review queue
14 trackers observed on kirana-cart.in
| Observed | Suggested category | Confidence | Evidence |
|---|---|---|---|
_ga, _ga_* Set-Cookie · google-analytics.com |
Analytics | High | 4 of 5 pages |
_fbp Pixel · connect.facebook.net |
Advertising | High | /, /cart |
rzp_checkout_anon_id XHR · api.razorpay.com · reclassification needs a written reason |
Strictly necessary | Medium | /checkout |
__mrkt_sid localStorage · tags.mrkt-cdn.net |
Not in the knowledge base | Unrecognised | /, /offers |
wzrk_uuid Script · clevertap-prod.com |
Functional | Low | /account |
2 findings need a decision. Unrecognised and low-confidence items block publishing until someone categorises them.
Customer logo wall goes here once there are customers who have agreed to be named.
Placeholder is intentionally visible — see PRODUCT.md → Evidence on Hand.
Why it is built this way
A suggested category is a guess, and this product labels it as one. Anything the classifier is not sure about stays on screen, blocks publishing, and waits for a person who can be accountable for the decision.
Start free trialUp to five public pages, each in a fresh Chromium context. Set-Cookie headers, the cookie jar, localStorage and sessionStorage keys, scripts, iframes, pixels and XHR — captured with the page and request that produced them.
Every finding carries a suggested category, a confidence level and a plain-language rationale. Unrecognised and low-confidence items block publishing. Moving something into Strictly necessary requires a written reason that stays on the record.
Publishing uploads an immutable payload, writes the version row, then moves the active pointer — in that order, so a failure at any step leaves the live banner untouched. Consent receipts are append-only, with no IP address and no user agent stored.
The flow
Six steps, in order, each one refusing to skip ahead of the last. Select a step to see what it actually does.
The banner
The banner is generated from your site's own theme tokens, and it only ships in a language a person has reviewed. Both checks happen before publishing, not after.
The scanner extracts deterministic colour, type and border-radius tokens from your site and proposes three presets. Every foreground/background pair is contrast-checked as you edit, and a failure blocks publishing.
An incomplete or unreviewed language pack is refused at publish time rather than quietly falling back to English. We would rather tell you a language is not ready than serve a visitor a consent notice they cannot rely on.
Install
The banner SDK is framework-free with no build step. Tagged scripts do not execute until the matching category is consented to — the mechanism is the browser's own, not a monkey-patch.
<!-- one tag, async, nothing else -->
<script async
src="https://cdn.complymore.in/sdk/complymore.js"
data-cm-site="ste_8f21c4"></script>
The config payload is served from the storage CDN. Your banner keeps working even if the ComplyMore dashboard is down.
<!-- will not run until "analytics" is consented -->
<script
type="text/plain"
data-cm-category="analytics"
src="https://www.googletagmanager.com/gtag/js">
</script>
On consent, tagged scripts are activated in document order. On rejection, they are never inserted at all.
Stat band — median time to first publish, sites under management, receipts retained. Awaiting real telemetry. Do not estimate.
Two or three customer quotes with name, role and company. Needs written permission on file before it ships.
Pricing
Start with the permanent Free plan, or explore paid features with a 14-day free trial.
Evaluate ComplyMore on one production site from workspace activation through publishing and evidence export.
For one small site that needs essential scanning and consent-history tools.
For a small business operating one production website or Shopify store.
For growing businesses that need multiple sites, higher traffic and deeper evidence.
Initial and manual scans, tracker discovery and review, all 23 supported languages, theme matching, banner editing, accept/reject/customize/withdraw controls, explicit and known-source blocking, consent CSV export, Google Tag Manager and Consent Mode integration, material-change alerts, removable ComplyMore branding and an approval-gated cookie-policy draft.
Prices are in Indian rupees. Any applicable GST is shown at checkout and on the invoice.
Get started
Register one site, run a scan, and read the findings before you decide anything. The first scan is enough to judge whether the approach fits.
14 consecutive days · 1 site · 25,000 page views during the trial.