No guide matches “”. Ask us.
Help center
Eighteen guides cover the whole workflow, from install to export. If they don't answer your question, talk to a person.
All guides
Getting started
- Installing the UserGuard snippet
- Where to get the one script tag that goes in the head of every page, why it has to load synchronously, and how UserGuard confirms it's working.
- Your first cookie scan
- What the scanner does on its first pass, which three kinds of evidence make a cookie, and how to read the results without guessing.
Cookies & review
- Cookie categories and the approval gate
- The four cookie categories, 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 that's set after login belongs in your policy even though no logged-out scan will ever see it. Here's how to add it by hand and what happens to it afterward.
The banner
- Customizing the consent banner
- All the visual and behavioral settings are in one full-screen customizer with a live preview. Nothing reaches visitors until you publish, and every publish is versioned.
- Banner translations
- Add translations in language mode inside the banner customizer. The embed matches each visitor's browser language, and every consent record shows which language it was collected in.
- How blocking works, and how to edit the rules
- With blocking on, known trackers wait until the visitor answers. Here's how the hold works, how rules are written and edited, and where the mechanism has limits.
- Google Consent Mode, basic and advanced
- Google's tags go by consent signals on the page and don't read the banner. UserGuard sets those signals on every site, and there's no setting to turn on. Here's what they say, what basic and advanced mean, and how to see them in Google.
Privacy rights
- 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. This guide covers 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's what each record contains, why we chose those fields, and how long records are kept.
Billing
- 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.
Accessibility
- The accessibility widget
- What the visitor panel does, where choices are stored, how to customize it, and why an overlay widget can't make a site WCAG-compliant.
Workspace
- Team, roles, and organizations
- UserGuard has four roles from viewer to owner, one team per account, and organizations that work as folders for client sites. Read on for who can do what, how invites work, and what grouping does and doesn't change.
- Renaming, re-homing, archiving, and deleting a site
- These four controls do very different things. A rename changes a label, a domain change moves your evidence without losing it, archiving stops the bill, and deleting destroys the consent log, the one record nothing can rebuild.
- Notifications and the attention list
- The bell opens 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. This guide explains how each one works and why we keep them apart.
Reports
- Monthly reports
- A monthly report shows last month for one site, or for all of a client’s sites, on a page a client can read. This guide covers what it contains, how to print it, and why nothing is stored.
Documents
- Documents and the document editor
- The cookie policy, accessibility statement and Do Not Sell notice are generated drafts. This guide covers how the editor shows you the real page as you type, what each document takes, and how publishing, versions and delivery work.