Glossary of Consent and Privacy Terms
This glossary defines the terms used across the Captain Compliance help center. Each entry links to an article where the term is explained in context.
Term | Meaning | Learn more |
|---|---|---|
Auto blocking | A list of scripts, iframes, and inline scripts, each assigned a consent category, that are held until the visitor allows that category. | |
Banner configuration | One version of a domain’s consent banner, aimed at a region, a set of countries, or particular states or provinces. A domain can have several. | |
Bucket mode | A banner option that replaces the standard category toggles with custom toggles. Each one groups categories and sets how it responds to Global Privacy Control. | |
ComplianceShield | Captain Compliance’s guarantee that covers eligible customers for fines or penalties related to web tracking, subject to its terms and eligibility requirements. | |
Consent banner | The on-page notice that asks visitors for their tracking choices and records them. | |
Consent category | A group of technologies that a visitor can allow or reject. Captain Compliance uses Strictly Necessary, Functionality, Performance, and Targeting. Scanned items that are not yet assigned are Unclassified. | |
Consent Initialization | The Google Tag Manager trigger that fires before all others. The Captain Compliance CMP tag uses it to set consent defaults before other tags run. | |
Consent management platform (CMP) | Software that collects, stores, and signals visitor consent. Captain Compliance is a CMP. | |
Content Security Policy (CSP) | An HTTP response header that tells browsers which origins may load resources on a site. | |
Cookie transparency page | A hosted public page that lists the cookies a site uses, grouped by category. | |
Data layer | The JavaScript array that Google Tag Manager reads events and values from. The consent banner pushes its consent events to it. | |
Data subject request (DSR) | A request from an individual to exercise privacy rights over their personal data, such as access, deletion, or opting out. | |
Execution gating | Preventing a script from running at all until the required consent is granted, as opposed to only blocking its cookies. | |
Global Privacy Control (GPC) | A browser signal that communicates a visitor’s opt-out preference automatically to the sites they visit. | |
Google Consent Mode | Google’s framework for passing consent state to Google tags through signals such as | |
Google Tag Manager (GTM) | Google’s tag management system, and the recommended way to deploy the consent banner and control when other tags fire. | |
Non-essential technologies | Cookies, scripts, and similar technologies that are not required for the site to function, such as analytics, advertising, and personalization tools. | |
Opt-in model | A consent model in which non-essential technologies do not run unless the visitor affirmatively consents. | |
Opt-out model | A consent model in which non-essential technologies may run by default until the visitor rejects them or adjusts preferences. | |
Patrol | Captain Compliance’s website audit tool. It scans any public web page and reports how the page handles consent, cookies, and trackers. Patrol is a separate application with its own sign-in. | |
Privacy notice | The public statement that describes how an organization collects, uses, and shares personal data. Often called a privacy policy. | |
Strict mode | A blocking model, also called WRAP, that intercepts scripts before they run and holds them until consent allows them. | |
Strictly Necessary | The category for technologies the site needs in order to function, such as security features and the consent banner itself. It is always granted and has no toggle. |
