The basic idea
A browser fingerprint is a combination of observable browser and device characteristics. A website may use those signals together to recognize a browsing environment. This is a general web concept, distinct from logging in to an account.
Possible signals include browser version, language, time zone, and display characteristics. You can read the technical definition in MDN’s fingerprinting glossary.
Cookies, profiles, and network routing
These terms describe different parts of browsing. Understanding the distinction makes product conversations more useful.
| Concept | What it concerns | Question to ask |
|---|---|---|
| Cookies | Site data that can help a website remember a session or preference. | How is site data stored and managed? |
| Browser profile | A working context for browser configuration and data; exact behavior depends on the product. | What is separated between profiles? |
| Network routing | The path a connection takes, including a proxy or VPN when configured. | Which connection options are supported? |
For more on session data, see MDN’s guide to HTTP cookies.
Know the limits
Changing a browser environment is not a guarantee of anonymity. Websites can evaluate account activity, sign-in history, network information, and other signals. A browser also cannot give you permission to access an account or override a platform’s rules.
Keep your expectations specific. Evaluate the settings and workflow you actually need, rather than relying on a broad promise of being “undetectable.”
Questions to bring to a product conversation
- Which browser characteristics can the current release configure?
- How are sessions, cookies, and other local data handled?
- Which systems, browser versions, and network configurations are supported?
- What happens when a browser version or configuration changes?
Use these questions as a starting point when you contact our team.