# FAQ: Consent Management *Audience: prospects evaluating Relyance, and new customers getting started.* ## What is Relyance Consent Management? It's a consent management platform (CMP) built directly into the Relyance AI platform. It discovers the tracking technologies (cookies, pixels, SDKs, storage, fingerprinting scripts) actually running on your websites and apps, lets you configure the correct consent rules per jurisdiction, enforces those rules live in the visitor's browser, and logs every decision for audit purposes. Because it's part of the same platform as Relyance's broader data mapping and governance tools, discovery and enforcement stay connected - you're not maintaining a separate tracker inventory in one tool and consent rules in another. ## How does it find tracking technologies on my site? The **Domain Analyzer** crawls your domain (using your sitemap where available), inspects individual pages for cookies, storage, pixels, scripts, and similar mechanisms, and evaluates what each one actually does before mapping it to a purpose and, where recognizable, a known vendor. Results land in a review queue (Tracking Technology Management) where your team approves or disregards each one. See the [Admin Configuration Guide](/docs/consent-management/admin-configuration-guide/#domain-analyzer) for the full walkthrough. ## What regions and regulations can it help me comply with? Region Group configuration in Relyance is fully customizable, so it can be configured to meet requirements across a wide range of regulations - including the EU/UK (GDPR), US state laws (CCPA/CPRA, VCDPA, CPA, and similar), Brazil (LGPD), Canada (PIPEDA/Quebec Law 25), South Korea (PIPA), Japan (APPI), Turkey (KVKK), Switzerland (nFADP), Singapore (PDPA), India (DPDPA), Australia/New Zealand (Privacy Act), and several Latin American markets (Mexico, Colombia, Chile, Peru). These aren't pre-loaded into your account; the [Regional and Jurisdiction Reference](/docs/consent-management/regional-and-jurisdiction-reference/) gives you a market-standards reference for configuring each one. ## What happens for a country I haven't explicitly configured? Every domain has a **Global** fallback Region Group. The market-standard pattern for this fallback is a notice-only configuration - see the [Regional and Jurisdiction Reference](/docs/consent-management/regional-and-jurisdiction-reference/) for details and how to adapt it to your own risk posture. ## How is consent actually enforced - is this just a banner? No - the banner is the visible part, but enforcement happens underneath it. Once a visitor makes (or doesn't make) a choice, the Relyance Consent Agent - a script installed on your site - actively blocks or allows each tracking technology based on that choice: it intercepts script/iframe loading, cookie writes, local/session storage writes, outbound network requests, tracking pixels, and beacon calls, and re-evaluates all of it the moment consent changes. See the [Technical Implementation Guide](/docs/consent-management/technical-implementation-guide/#6-how-enforcement-works) for the technical detail. ## Is it Global Privacy Control (GPC) compliant? Yes. GPC is a browser-level opt-out signal that's legally required to be honored in California, Colorado, and Connecticut, and increasingly expected elsewhere. Relyance detects the signal automatically and can honor it globally or on a per-purpose basis, per Region Group - no extra engineering work is required once the base agent is installed. ## Can I customize the look and branding of the banner and preference center? Yes - colors (including separate light/dark theme variants), fonts, button styles, copy, and translations are all configurable through the Interface Builder, with a live preview and an accessibility contrast check built in. There's no free-form custom-CSS injection; styling goes through the discrete controls provided, which keeps things WCAG-friendly by default. See the [Admin Configuration Guide](/docs/consent-management/admin-configuration-guide/#interface-builder). ## Can visitors change their mind after the initial banner? Yes - every implementation includes a preference center visitors can reopen at any time, either through your own link/button (via `Relyance.showPreferenceCenter()`) or through the banner's "Manage Preferences" option. ## Does consent carry across a visitor's devices? If your site has authenticated users, yes - Relyance supports **Authenticated Consent**, which ties a visitor's consent to their logged-in identity rather than only their browser. Once your engineering team adds two small calls at login/logout, consent set on one device is available the next time that user logs in anywhere else. See the [Technical Implementation Guide](/docs/consent-management/technical-implementation-guide/#11-authenticated-consent-and-cross-device-sync). ## Do I need a developer to implement this? For the initial rollout, yes - installing the Consent Agent script requires a one-time code change (adding a script tag to your site's ``, ideally very early in the page load). Everything else - configuring regions, designing the banner, reviewing tracking technologies, viewing/exporting logs - is handled by admins in the Relyance platform with no code required. See the phased rollout in the [Overview and Implementation Guide](/docs/consent-management/overview-and-implementation-guide/#implementation-roadmap). ## How long does implementation typically take? It depends on the number of domains and jurisdictions involved, but the rollout generally moves through discovery (running the Domain Analyzer), categorization (reviewing discovered trackers), legal configuration (region rules), design (banner/preference center), a one-time engineering deployment, testing, and go-live. Straightforward single-domain rollouts can move quickly; multi-domain, multi-jurisdiction rollouts take longer mainly because of legal review cycles, not platform limitations. ## What data does the consent log store, and for how long? Each consent event records a device or user identifier, timestamp, region, IP address (optionally anonymized), browser information (optionally minimized to browser type only), GPC signal status, and a full per-purpose accept/reject breakdown. You control retention and can export a given date range (up to 32 days per export) as CSV or XLSX for audits, DSARs, or regulator requests. See [Consent Logs and Reporting](/docs/consent-management/consent-logs-and-reporting/). ## What if my site already enforces a strict Content Security Policy (CSP)? You'll need to allowlist the Consent Agent's script and connection hosts in your CSP. The standard directives are documented in the [Technical Implementation Guide](/docs/consent-management/technical-implementation-guide/#10-content-security-policy-csp); if you're on a region-specific deployment, confirm exact hostnames with your Relyance contact. ## Troubleshooting: my domain scan found zero tracking technologies This almost always means a firewall, WAF, or CDN bot-protection rule is blocking the Relyance scanning crawler before it can complete. Allowlist the Relyance scanner IPs - see the [Admin Configuration Guide](/docs/consent-management/admin-configuration-guide/#allowing-the-relyance-domain-analyzer-ips). ## Troubleshooting: installing the agent broke a third-party script on our site This usually means a script your site actually needs got caught by the consent interceptor because it wasn't mapped as "strictly necessary." Two fixes, in order of preference: map it to a strictly-necessary processing activity in Tracking Technology Management, or exclude its URL from interception entirely using the `data-relyance-skip-url-patterns` attribute. Full walkthrough in the [Technical Implementation Guide](/docs/consent-management/technical-implementation-guide/#13-troubleshooting). ## Where can I get more help? Reach out to your Relyance CSM or account team, or consult the deeper guides linked throughout this FAQ: - [Overview and Implementation Guide](/docs/consent-management/overview-and-implementation-guide/) - [Legal and Compliance Guide](/docs/consent-management/legal-and-compliance-guide/) - [Technical Implementation Guide](/docs/consent-management/technical-implementation-guide/) - [Admin Configuration Guide](/docs/consent-management/admin-configuration-guide/) - [Consent Logs and Reporting](/docs/consent-management/consent-logs-and-reporting/) - [Regional and Jurisdiction Reference](/docs/consent-management/regional-and-jurisdiction-reference/)