What can a website observe?
A site can observe information such as browser and operating-system details, language, timezone, screen properties and supported browser features. Rendering APIs such as Canvas and WebGL can contribute additional signals. No single setting describes the whole browser environment.
Some details come from JavaScript APIs, while others come from network requests or behavior. Changing one visible property does not necessarily change all related signals.
What an anti-detect browser changes
An anti-detect browser exposes controls for selected browser properties and lets you keep configurations separate between profiles. In Profileo, settings include Canvas, WebGL, Audio Context, Client Rects, language, timezone and WebRTC modes.
These controls are useful for managing authorized workspaces and testing browser behavior. They cannot guarantee anonymity, bypass every detection system, or change a platform’s account rules. Account details, network information and behavior can still associate sessions.
Build a consistent workspace
- Name a profile for the account or testing purpose it serves.
- Choose settings that make sense together instead of changing every property at random.
- Use a proxy only when the task requires it, and verify its actual behavior.
- Test the browser before logging in to an important account.
- Keep the configuration stable and record intentional changes.
Follow the Profileo fingerprint-settings guide for the relevant controls, or read the multi-account workflow for a complete setup.
Learn more
For browser-level background, see MDN’s explanation of fingerprinting. For the controls available in this application, use the Profileo documentation.