Help Center

Installing the UserGuard snippet: One script tag in the head of every page. Where to get it, why it must load synchronously, and how UserGuard confirms it is working.
Your first cookie scan: What the scanner actually does on its first pass, which three kinds of evidence make a cookie, and how to read the results without guessing.

Cookie categories and the approval gate: Four categories, one gate: how categorization, provenance, and human approval decide what reaches your published cookie policy, and why a hand edit clears an approval.
How AI scan review works: What the AI drafts after a scan, how confidence works, why every draft waits in the review queue for a person, and how the monthly budget behaves.
Adding cookies the scan can’t see: A cookie set after login is real and belongs in your policy, but no logged-out scan will ever see it. Here is how to add it by hand and what happens to it afterwards.

Customizing the consent banner: Every visual and behavioral setting lives in one full-screen customizer with a real-render preview. Nothing reaches visitors until you publish, and every publish is versioned.
Banner translations: Translate the banner in language mode inside the banner customizer, let the embed match each visitor's browser language, and prove which language every consent was collected in.
How blocking works, and how to edit the rules: With blocking on, known trackers wait for an answer. Here is how the hold works, how rules are written and edited, and where the mechanism has honest limits.
Google Consent Mode, basic and advanced: Google's tags read consent signals, not the banner. UserGuard sets them on every site with no setting. Here is what they say, what basic and advanced mean, and how to see them in Google.

The Do Not Sell or Share link (CCPA): The CCPA opt-out is a separate tool from the cookie banner because the regulation says it must be. Where the link renders, what it records, and why.
The consent log, receipts, and export: Every banner decision becomes a record you can inspect and export. Here is what each record contains, why those fields were chosen, and how long they stick around.

Billing, refunds, and how pricing works: What the 30-day money-back guarantee covers, how per-site volume pricing works, what happens mid-cycle, and why a lapsed card never takes your banner down.

The accessibility widget, honestly framed: What the visitor panel does, where choices are stored, how to customize it, and the one thing an overlay widget cannot do for you.

Team, roles, and organizations: Four roles from viewer to owner, one team per account, and organizations as folders for client sites: who can do what, how invites work, and what grouping changes — and what it does not.
Renaming, re-homing, archiving, and deleting a site: Four controls with three weights: a rename changes a label, a domain change moves your evidence without losing it, archiving stops the bill, and deleting destroys the one record nothing can rebuild.
Notifications and the attention list: One bell, two lists: a feed of things that happened, which you read, and a live list of things that are true right now, which you fix. How each works, and why they are kept apart.

Monthly reports: Last month for one site, or for all of a client’s sites, as a page a client can read — what it contains, how to print it, and why nothing is stored.

Documents and the document editor: The cookie policy, accessibility statement, and Do Not Sell notice are generated drafts: how the editor shows you the real page as you type, what each document takes, and how publishing, versions, and delivery work.

All guides