Compliance & Data Control

Compliance and data control built into the dealer platform

Privacy-aware tracking, consent-dependent analytics, lead form controls, search-alert double opt-in and retention settings, all configured by the dealer or agency team inside WordPress, not buried in an external console.

Back to Features View Analytics & Tracking

Governance & control

Practical control over the settings that matter

The dealer or agency team owns the controls that govern how visitor and lead data is handled, privacy-aware tracking, consent-dependent analytics, and clear responsibility inside the WordPress admin.

Privacy-aware

Privacy-aware analytics

No IP addresses, user IDs or cookies stored server-side. Tracking is off by default and can be gated behind a consent signal from the site's consent solution.

Activation

Controlled tracking activation

Each tracking layer, page views, business intelligence events, search-alert opt-ins, is enabled deliberately, never silently turned on.

Visibility

Governance visibility

Settings, retention windows and data categories are documented and visible to administrators, not hidden behind a third-party dashboard.

Ownership

Owned inside WordPress

Lead, analytics and search-alert data live in the dealer's own WordPress database, governed through familiar WordPress roles and capabilities.

Settings you actually manage

Real settings, in the WordPress admin

A representative look at the privacy and data controls the dealer or agency team configures directly inside the plugin, analytics behavior, lead form consent, search-alert opt-in, retention and processing transparency.

Settings → Analytics Privacy-aware

Analytics & event tracking

Off by default. Page views, BI events and consent gating are independent toggles.

  • Master switch Analytics enabled
  • Extended events BI tracking (filter / contact / lead)
  • Consent gating Require visitor consent before tracking
  • Data minimization Strip free-text search values from logs
Analytics retention 180 days Daily WP-Cron cleanup
No IP stored No user IDs On-demand purge
Settings → Lead form Consent-ready

Lead form & consent

Field visibility, consent checkbox and privacy notice URL are configured per site, wording stays with the operator.

  • Form field Phone field visible
  • Form field Message field visible
  • Consent Consent checkbox enabled
  • Anti-abuse Rate limiting (5 / IP / 5 min)
Privacy page URL /privacy Linked from the consent label
Submitter IP not stored CSV export Operator-owned wording
Settings → Search alerts Enforced

Search alerts · double opt-in

  • Visitor submits search criteria No active subscription yet
  • Confirmation email sent Single-use signed link
  • Visitor confirms via link Subscription becomes active

No activity until the visitor confirms, the workflow is enforced and cannot be bypassed in settings.

Settings → Privacy notice Documented

Data processing transparency

  • Jurisdiction label GDPR · DSGVO · revDSG
  • Stored on server No IP · no user ID · no cookie
  • Data processor WordPress site (operator)
  • On uninstall Analytics table dropped

A documented surface area, what is stored, where, and how to remove it, is part of the product.

Mockups are illustrative previews of real plugin settings. Compliance support, not legal advice.

Inside WordPress, not in a black box

Compliance control where the team already works

When data and consent settings live in an external console, the dealer team can see neither the rules nor the data. ADP Car Market Hub keeps the controls, and the audit surface, inside the WordPress admin.

Fragmented external setup

Settings spread across vendors

  • Tracking behavior decided in an external dashboard the dealer cannot audit
  • Consent enforcement depends on vendor defaults that change without notice
  • Lead form copy and consent wording stuck inside a third-party widget
  • No clear answer to "what is stored, where, for how long" without a vendor ticket
  • Removing data means contacting support, not clicking a button

ADP Car Market Hub · WordPress-native

One controlled surface inside WordPress

  • Tracking off by default, with explicit toggles for each event family
  • Consent gating attached to a documented filter the site's consent solution can drive
  • Lead form fields, consent label and privacy URL configured by the operator
  • A documented inventory of stored data categories and retention windows
  • On-demand purge for analytics data; full table drop on uninstall

Operational safeguards

Documented behavior, predictable defaults

A reassuring product surface: tracking is off by default, retention is bounded, search alerts require explicit confirmation, and every data category is documented for the operator and the privacy review.

Privacy-aware defaults

Safer choices, before anyone touches a setting

Sensitive features ship in their safest state, analytics off, search alerts unconfirmed, lead consent shown, so the operator opts in to each capability rather than discovering it after the fact.

  • Analytics off by default; explicit master switch required to enable
  • Search-alert subscriptions require a confirmed double opt-in
  • Daily WP-Cron retention cleanup, with on-demand purge for administrators

Why it matters

Practical benefits for dealers and agencies

A compliance and data-control surface that is part of the platform, not a separate workstream, removes ambiguity and keeps responsibility where it belongs.

Better internal governance

A documented map of settings, defaults, retention and roles makes internal reviews and handovers concrete instead of guesswork.

Confidence during implementation

Privacy-aware defaults and explicit consent toggles let agencies launch dealer sites without piecing together compliance posture from third-party docs.

Transparent customer-data handling

Lead consent wording, privacy URL and field visibility are configured by the dealer team, so the experience customers see matches the privacy notice.

Less ambiguity around behavior

No surprise events, no hidden tracking, no opaque data flows, just settings the team can read, change and document on the same site they manage.

Continue exploring

Where to go next in the showcase

Compliance and data control connect to the rest of the platform, explore the surrounding feature pages for the wider product story.

01 Platform foundation Core Platform The product foundation behind every capability, including the data and operational controls described on this page. 02 Native foundation WordPress Architecture How role-based access, hooks and the WordPress database make these controls native instead of bolted on. 03 Where signals come from Analytics & Tracking See the analytics surface these privacy controls govern, events, retention and the consent integration filter. 04 Operational visibility Admin Operations The operational surface, imports, leads, logs, that creates the audit trail referenced in this page.

Compliance support, not legal advice

A controlled, enterprise-ready WordPress platform

Explore the rest of the platform or talk to the team about how the data control surface fits into a real dealer or agency setup.

Back to Features View Analytics & Tracking Contact us