# Key concepts To understand why true privacy is difficult in standard browsers, it’s important to know how websites track users today. This page walks you through the fundamental challenges modern-day websites pose to true privacy and why you need an anti-detect browser to handle them. ### Multi-account management and true privacy Websites do more than serve you content. They quietly collect data about you with every action you take. Thus, when you manage multiple unrelated accounts, run parallel workflows, or operate across different locations, you face privacy risks that standard browsers are not designed to address. At a high level, this identification is driven by a small set of technical signals that websites use independently or together. The key ones include: | Tracking method | What is tracked | Why it is identifiable | | ------------------ | ------------------------------------------------------------ | ----------------------------------------------------------------------------- | | Cookies | Session identifiers, preferences, history | Persist identity across visits and sessions | | IP address | Network location, ISP, region | Used to derive location and link multiple requests to the same network source | | Browser attributes | Browser, OS, screen resolution, installed fonts, API's, etc. | Combined to form a unique fingerprint | Regulatory frameworks such as the GDPR[^1] attempt to limit parts of this behaviour by requiring your consent before cookies are stored or accessed. However, cookie consent mechanisms do not prevent technical correlation at the network (IP) or browser level. Conventional browsers are built around a single user identity. By default, all sessions share the same underlying environment, which makes [true isolation](#user-content-fn-2)[^2] difficult. ### IP Tracking and IP Masking Your IP address is one of the primary signals used to track you online. It reveals network-level information such as your geolocation and internet provider. Hence, platforms use IP-based signals to monitor activity, enforce regional restrictions, and block access based on where you appear to be connecting from. {% hint style="info" %} When multiple accounts appear to originate from the same IP address, they are commonly treated as a single user or grouped as related. {% endhint %} This explains why simply opening additional tabs or browser windows does not change how a platform perceives your activity. To avoid correlation at this level, each session needs to present a distinct network identity. This is where **IP-masking** technologies such as VPNs[^3] and Proxies come into play. ### VPNs and Proxies **A VPN** performs three core functions: it encrypts network traffic, tunnels that traffic securely to a remote server, and presents the server’s IP address instead of the original connection IP. VPNs are useful for basic privacy and location masking but typically operate at the system level. As a result, all browser sessions share the same network identity and browser environment. VPNs do not isolate browser-level attributes, which limits their effectiveness in multi-accounting scenarios. **A proxy** routes browser traffic through an intermediary server at the browser level, exposing the server’s IP address instead of the original connection. Each browser profile can use a different IP address, operate from a different location, and maintain independent network behaviour. {% hint style="info" %} VPNs apply network routing at the system level, while proxies route traffic at the browser level. Neither approach fully addresses browser-level identification on its own. {% endhint %} This makes proxies better suited than VPNs for managing multiple accounts or scaled workflows. However, network separation alone does not fully prevent session correlation. ### Browser fingerprinting Websites have moved beyond relying solely on IP addresses and now collect a wide range of [high-entropy browser attributes](#user-content-fn-4)[^4] to identify users. These include browser and operating system details, screen resolution, system settings, browser extensions, installed fonts, and hardware-related signals. In practice, it comes down to numbers. There are roughly 8.3 billion people on Earth. To find exactly you, a tracker just needs to "double" its way up to that number. $$ 2^{33} \approx 8,589,934,592 $$ This means a website only needs 33 bits of unique information to distinguish you from every other human being. More so, since these attributes are tied to your browser, and in turn your device, they remain largely unchanged when you open incognito or private browsing tabs. Consequently, incognito tabs in standard browsers do not prevent fingerprint-based tracking. {% hint style="info" %} Incognito mode limits local data storage and deletes session data, but the underlying browser fingerprint remains the same. {% endhint %} The key takeaway here is that even when IP addresses differ, tracking via browser fingerprinting is unaffected. This is why IP masking alone does not guarantee true isolation and true privacy. ### Anti-detect browser An anti-detect browser is a browser designed to run multiple fully isolated browser profiles. Each profile has its own storage, network identity, and browser fingerprint, allowing it to operate independently of other profiles. Instead of treating the browser as a single persistent identity, a reliable anti-detect browser gives you optimal control over the three primary tracking vectors used by websites: cookies, network identity, and browser fingerprint. Therefore, each profile is perceived as a separate device and user to websites. With an anti-detect browser, you can: * Isolate cookies and local storage per browser profile, preventing session data from leaking between accounts. * Attach proxies on a per-profile basis, so each session presents a distinct network identity. * Assign each profile a distinct set of browser parameters, solving correlation through fingerprinting. When these controls are applied together and consistently, each profile behaves as a fully independent browser environment. From a monitoring website’s perspective, each profile appears as a separate, stable user context. This is why anti-detect browsers are the most effective approach when you need reliable separation across multiple accounts or workflows. In the following sections, you will learn how Incogniton applies these principles to manage isolated browser profiles reliably. [^1]: General Data Protection Regulation. A comprehensive set of rules in the EU on data protection and privacy. [^2]: True isolation is achieved only when each profile runs consistently as an independent browser environment, with separate storage, network identity, and fingerprint attributes. [^3]: Virtual Private Networks [^4]: Attributes that are rare and highly specific. For example, if a website knows your exact screen resolution is 2560 × 1440, that you use a specific version of a graphics driver, and that you have the "Old English Text" font installed, that combination may be unique to your device. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.incogniton.com/welcome/key-concepts.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.