Version 2026-09-03 · effective 2026-09-03 · generated from in-repo configuration
Every tag the site can load, what it transmits, the consent it waits for, and how universal opt-out signals are honoured.
No tag on this list loads on page view. Each one waits for every consent scope named against it, and a Global Privacy Control signal suppresses all of them regardless of any stored choice. A tag with no configured account id is not loadable at all. This is enforced in code — the loader is the only path to a third-party origin, and the build fails if a tag is hardcoded anywhere else.
Collect my consumer health data
I consent to TortOS collecting consumer health data about me (such as the injury, condition, treatment or medication I describe on this site) through this website.
Covers only the collection of health-related information you enter or that this site observes. It does not permit sharing that information with anyone else.
Basis: RCW 19.373.030(1)(a) — consent to collect · default off · never bundled with another choice
Share my consumer health data with third parties
I consent to TortOS sharing my consumer health data with the third parties named in the Consumer Health Data Privacy Policy. This consent is separate from, and not required by, my consent to collect.
A separate and distinct decision from collection. Leaving this off does not affect your case or your access to the Services.
Basis: RCW 19.373.030(1)(b) — consent to share, separate and distinct from consent to collect · default off · never bundled with another choice
Non-essential analytics and advertising
I consent to non-essential analytics and advertising technologies (such as measurement pixels, session analytics and experimentation tools) running on this site.
Nothing in this category runs before you turn it on. Turning it off leaves the site fully functional.
Basis: Spec §4.1 analytics_tracking — default off · default off · never bundled with another choice
Tag register, generated from the loader registry
| Vendor | Purpose | Receives | Loads only after |
|---|---|---|---|
| Google LLC (Google Analytics 4)analyticshttps://www.googletagmanager.com | Aggregate site measurement: page views, funnel step completion, traffic source. | page URL and title; referrer; IP address; device and browser metadata; first-party client id cookie | Non-essential analytics and advertisingAfter analytics_tracking is granted in the consent manager. Never on page load. |
| Google LLC (Google Ads conversion tag)advertisinghttps://www.googletagmanager.com | Browser-side conversion attribution for paid search and display. | page URL; IP address; click identifiers (gclid); conversion event name | Non-essential analytics and advertising + Share my consumer health data with third partiesAfter analytics_tracking AND chd_sharing are both granted. |
| Meta Platforms, Inc. (Meta Pixel)advertisinghttps://connect.facebook.net | Browser-side conversion attribution and audience building for paid social. | page URL; IP address; browser id cookies (_fbp/_fbc); event name | Non-essential analytics and advertising + Share my consumer health data with third partiesAfter analytics_tracking AND chd_sharing are both granted. |
| Microsoft Corporation (Clarity)session recordinghttps://www.clarity.ms | Session replay and heatmaps for funnel diagnosis. | DOM snapshots of visited pages; mouse and scroll interaction; IP address; browser metadata | Non-essential analytics and advertising + Collect my consumer health data + Share my consumer health data with third partiesAfter analytics_tracking, chd_collection AND chd_sharing are all granted. |
| Intercom, Inc.chathttps://widget.intercom.io | Live chat widget on marketing surfaces. | message content typed by the visitor; page URL; IP address; browser metadata | Collect my consumer health data + Share my consumer health data with third partiesAfter chd_collection AND chd_sharing are both granted. |
The machine-readable version of this register lives at compliance/tag-inventory.yaml and is generated from the same source, so the two cannot disagree.
We honour the Global Privacy Control signal, sent either by your browser or by an extension. When it is present we record an opt-out for you and no non-essential technology runs — a stored grant does not override it.
| State | Statute as configured | Names GPC expressly |
|---|---|---|
| California (CA) | CCPA/CPRA, Cal. Civ. Code §1798.135 | Yes |
| Colorado (CO) | Colorado Privacy Act, C.R.S. §6-1-1306 | Yes |
| Connecticut (CT) | CTDPA, Conn. Gen. Stat. §42-518 | Yes |
| Delaware (DE) | Delaware Personal Data Privacy Act | No — generic universal opt-out mechanism |
| Maryland (MD) | Maryland Online Data Privacy Act | No — generic universal opt-out mechanism |
| Minnesota (MN) | Minnesota Consumer Data Privacy Act | No — generic universal opt-out mechanism |
| Montana (MT) | Montana Consumer Data Privacy Act | No — generic universal opt-out mechanism |
| Nebraska (NE) | Nebraska Data Privacy Act | No — generic universal opt-out mechanism |
| New Hampshire (NH) | NH RSA 507-H | No — generic universal opt-out mechanism |
| New Jersey (NJ) | New Jersey Data Privacy Act | No — generic universal opt-out mechanism |
| Oregon (OR) | Oregon Consumer Privacy Act | No — generic universal opt-out mechanism |
| Texas (TX) | Texas Data Privacy and Security Act | No — generic universal opt-out mechanism |
The privacy control at the bottom of every page shows what is currently enabled and changes any choice, including switching everything back off. Withdrawal stops future processing in that scope; it does not undo a disclosure that has already happened.
Privacy choices: 0 of 3 optional technologies enabled.