Does an enabled signal stop tracking?

No. These values communicate a preference; they do not themselves block requests, storage or scripts.

Why is a signal unavailable?

The browser may not implement the property, a setting may be unset, or privacy controls may restrict access. This tool cannot distinguish all of those cases.

Does this tool inspect DNT or Sec-GPC headers?

No. Client-side JavaScript cannot use these navigator properties to prove which HTTP headers a server received.

Does a reported GPC value prove compliance?

No. This tool does not observe how another site handles the signal or assess legal obligations.

Browser Privacy Signals

Read the Do Not Track and Global Privacy Control values exposed by your browser. This local check does not inspect HTTP request headers or site compliance.

Read the Do Not Track and Global Privacy Control values exposed by your browser. This local check does not inspect HTTP request headers or site compliance. Click Check Signals to read the browser properties. Review the exact navigator.doNotTrack and navigator.globalPrivacyControl values, when available. Treat a missing value as unavailable or not reported, not as proof that the setting is disabled. Remember that this page cannot verify request headers, whether another site honored a preference, or legal compliance. Reads browser-reported DNT and GPC JavaScript properties locally after you start the check. It does not capture outgoing request headers.