← Back to the privacy guide

PipelineOn · Interactive example

See what your privacy choices should change.

Try rejecting tracking, allowing analytics only, or allowing the optional purposes. The panel shows whether each purpose would be eligible under the guide's conservative setup.

This demonstration installs no tracking tags. No tracking requests are sent, even after acceptance. Choices stay in this page's memory and reset on reload. This is an educational example, not a production consent manager.

Necessary technologies keep the site working. Optional purposes include measuring visits, advertising, and associating website activity with contact or household information for follow-up.

Manage choices

No choice made. All optional purposes are off.

Example policy and notice wording

What would run?

Necessary site functionsAvailable
Optional analyticsBlocked
Advertising / follow-upBlocked
PipelineOn pixelBlocked

No GPC signal is active in this demonstration.

The pixel needs both marketing and visitor-identification permission. A sale/sharing opt-out or GPC overrides it. Every scenario assumes the business has separately approved the use and excluded sensitive journeys and known minors.

Try these three cases

  1. Choose Reject optional tracking. All optional purposes stay blocked.
  2. Open Manage choices, allow analytics only, and save. The pixel stays blocked.
  3. Accept optional tracking, then turn on simulated GPC. The marketing and identification paths become blocked, even though the earlier acceptance is still recorded.

This page changes eligibility indicators; it does not demonstrate teardown of a running vendor script. A production site also needs persisted choices, consent-change handling across pages/tabs, vendor shutdown, server-side enforcement, suppression, request handling, and testing.