Do Not Track

1. What is Do Not Track in Browser Fingerprinting

The Do Not Track HTTP header (often mirrored in JavaScript through navigator.doNotTrack) tells websites whether a user has opted out of being tracked. While originally intended as a privacy mechanism, this signal has become valuable to anti-bot, multi-accounting, and tracking fingerprint systems.

Fingerprinting libraries and detection AI can use DNT values for:

• Cross-referencing user intentions with behavioral data
• Assessing consistency with privacy settings from cookies or localStorage
• Determining spoofed behavior if DNT value unexpectedly changes or is removed

Common Do Not Track values include:

• "unspecified" (User has not set a DNT preference)
• "1" (Tracking is declined)
• "0" (User allows tracking)

Tracking consistency between DNT, cookie consent banners, and fingerprint profiles enables behavioral coherence monitoring, which is commonly seen in KYC, ad fraud, or privacy compliance tech systems.

2. How Platforms Detect Do Not Track Fingerprints

Sites and anti-fingerprint platforms collect and analyze the DNT flag using:

1. JavaScript Access – by reading the navigator.doNotTrack property directly.
2. HTTP Request Header Inspection – by reading the DNT: 1 (or DNT: 0) request header in backend logs.
3. Consistency Checks – if JavaScript and HTTP headers report different DNT values, it may indicate spoofing or synthetic usage (e.g., automation).
4. Behavioral Correlation – platforms analyze whether the session behaves like a real user according to their DNT state. For instance, a user with DNT=1 but who allows cookies may appear suspicious.

In a fingerprint detection context, the DNT status is often scored, and unexpected deviations from known user-device clusters can affect identity trust level, especially in finance, streaming, and social media moderation systems.

3. How FlashID Controls Do Not Track Fingerprints

FlashID allows users to fully customize the Do Not Track behavior — both at the JavaScript context and the HTTP request level. That ensures seamless identity management and a coherent privacy fingerprint across all browser profiles.

FlashID’s DNT controls include:

1. Do Not Track Mode Setting – toggle whether each browser instance reports "1", "0" or "unspecified".
2. DNT Layer Consistency – FlashID synchronizes navigator.doNotTrack, the HTTP Request DNT header, and system-level privacy settings to prevent mismatches.
3. Spoofing of Privacy Intent – simulate different privacy preferences across browser profiles to reflect natural user variation and avoid fingerprint correlation.
4. Comply or Spoof – users can set real DNT values for compliance, or fake values to break behavioral fingerprint linking — all based on their needs.
5. Session Memory Persistence – Each profile’s DNT setting is preserved automatically, helping user sessions retain their behavioral profile across launch instances.
6. Smart Default Fallback Handling – if profile is missing a DNT setting, FlashID applies intelligent logic to generate natural defaults that align with browser, locale, and proxy combinations.

By giving users precise control over the Do Not Track fingerprint and making it fully configurable per browser profile, FlashID helps prevent association between identities and reduces the linkability of multi-accounting data driven by tracking preference inconsistency.

You May Also Like