Security you can reason about
We handle your visitors’ consent choices, so that data is encrypted, logically segregated per customer and never sold.
It sits lightly on your page
With tracker blocking on, the script loads first in your <head>, not async, so it can hold analytics until the visitor agrees: a one-time wait of a few tens of KB. With blocking off, it can load async.
The controls behind the promise
Encryption in transit and at rest
TLS 1.2 or higher in transit, provider-managed encryption at rest.
Least-privilege access
Production access is limited to named people. Secrets live in encrypted provider settings, never in code.
Per-customer separation
Customer data is logically segregated, with access controls designed to prevent one customer from accessing another customer’s data.
Works with your CSP
An allowlist policy, or a nonce-based one when you pass your nonce on the script tag.
Pseudonymous consent logs
Enough to record that a choice was made, without profiling the visitor.
Customer Personal Data stays out of ad tech
We don't sell Customer Personal Data or share it with ad networks.
Reliability
Served from a global edge network, with your settings cached there. If ComplyMo can't be reached, your site keeps working; if our script can't load, the banner and tracker blocking don't run on that page view.
Responsible disclosure
Found something? Email security@complymo.com and we'll acknowledge, investigate and keep you updated.
Add it to your site with one script
14-day free trial · card needed to start, cancel before day 14 and you pay nothing

