Different Visitor identifier in Brave browser private window
Scenario
- What's the scenario, what happens and what did you expect to happen?
I'm testing FingerprintJS using the official demo page.
When accessing the page from a regular Brave browser window, FingerprintJS generates one visitorId.
When accessing the same page from a Brave Private Window, FingerprintJS generates a different visitorId.
I expected the same device and browser installation to produce the same visitorId, regardless of whether the page is opened in a regular or private window. If this behavior is expected, I'd appreciate clarification on why the identifiers differ.
Steps to reproduce:
- Open Brave Browser.
- Visit https://fingerprintjs.github.io/fingerprintjs/ in a regular window.
- Note the generated
visitorId. - Open a Brave Private Window.
- Visit the same page.
- Compare the generated
visitorId.
Actual result
The visitorId differs between the regular window and the Private Window.
Expected result
I expected the same visitorId to be generated for both windows, or documentation indicating that different identifiers between regular and private browsing are expected.
Device and browser
- OS: Windows 10 (64-bit)
- Browser: Brave Browser
FingerprintJS Version
- Latest version available on the official demo page: https://fingerprintjs.github.io/fingerprintjs/
Fingerprint data
Regular Window
- Visitor ID:
61485987a09131062a693e1efba626a3
Private Window
- Visitor ID:
63aa838cc7e1abfda2f6a6ed31c0952b
Could you clarify whether this is expected behavior?
Source: fingerprintjs/fingerprintjs