Back to blog

Can You Still Be Identified After Rejecting Cookies? Identity Resolution and Browser Fingerprints

Safari recently added privacy protections aimed at identity-resolution infrastructure, bringing back the question of why people may still be linked after rejecting cookies. This article distinguishes cookies, browser fingerprints, and identity resolution based on information such as email addresses. It explains how multi-brand teams can organize business identities, authorization, and browser environments together.

Rejecting one category of cookies does not make every piece of identity-related information disappear. A website may provide services through the account you are currently signed into, and other mechanisms may also link visits. To understand what happened, first distinguish cookies, browser fingerprints, and identity resolution.

For teams managing several brands, the more useful questions are: which information represents a business identity, which data belongs to a browser environment, and who maintains those relationships?

On October 19, 2026, WebKit published Blocking Identity Resolution Infrastructure. It describes domain-level blocking of network access to identity-resolution infrastructure in Safari and WebKit on iOS, iPadOS, macOS, and visionOS 27 to reduce cross-site tracking. These are the systems and browsers specifically named in the article. Original WebKit post

The mechanism described is that some third parties collect email addresses when people sign in or subscribe, link them to persistent identifiers, and then use those identifiers to match activity across sites. The article distinguishes this kind of tracking from first-party personalization provided by a website itself. Understanding the distinction helps avoid conflating normal recognition after sign-in, advertising-based linkage, and device identification.

The direct implication of this update is not that “websites will no longer recognize visitors.” Rather, browsers are adding protections against specific data flows. Actual experiences still depend on browser versions, website implementations, and user choices.

Cookies, fingerprints, and identity resolution involve different information

Use this table to separate the concepts.

MechanismMain information involvedWhat a team should check
Cookies and other site stateSite data stored by the browser and sent according to its rulesWhich account’s session is retained in this environment?
Browser fingerprintA combination of browser and device characteristics observed by a pageDo the current parameters match the environment plan?
Identity resolution based on personal informationEmail addresses, phone numbers, and related identifiersWho provided the data, why is it used, and who receives it?
A website’s own account recognitionA business account the user actively signed intoWhich entity is signed in, and what permissions does it have?

Public identity systems can help clarify the third row. For example, the official UID2 API documentation describes mappings between email addresses or phone numbers (or their hashes) and identifiers. This shows that identity-based identifiers are a different data dimension from device parameters. The documentation describes one specific system; it does not establish that all identity services work, disclose, or obtain authorization in the same way. UID2 official documentation

Suppose you clear an old browser session and then actively sign in with the same work email. If the website recognizes the corresponding account, that is normal account-service behavior. Whether the site can link anonymous visits from device parameters is a separate question.

For multi-brand operations, start by listing business identities

When one team serves several brands, a common management problem is scattered information: a login email is in one spreadsheet, the owner is in chat history, and another teammate holds the recovery details.

Create a business-identity list that puts these details in one record:

  • The brand or customer entity and its platform.
  • Authorized business accounts and work email addresses.
  • The account owner, recovery-information owner, and collaborators.
  • The name or identifier of the corresponding browser environment.
  • The account’s business purpose and the handoff date.

Store passwords, verification codes, and complete session files using the team’s approved secure method. The day-to-day list only needs identifiers and owners. When switching to another work email, use the account-information process allowed by the platform and update recovery and notification arrangements as well.

The goal is to make business ownership and authorization clear. If a website asks for real information about the account holder, use accurate, authorized information for that business. Do not treat an environment name as the account holder’s identity.

Connect the identity list to working environments in PurpleMark

Once the information is organized, apply the list in the client. In PurpleMark, create groups by brand or customer, then create an environment for each business and bind the relevant account. Environment names can include “brand-platform-purpose” so members can confirm the target before opening it.

Next, review the environment’s proxy and relevant fingerprint settings, then arrange environment sharing or permission groups according to team roles. Operators can use the list to find an environment and then confirm account ownership from the environment record. Existing users can start organizing in the client; a new team can download the PurpleMark client.

For example, one member may read campaign data for Brand A while another maintains product pages for Brand B. Assign each task to its own environment and authorization scope. During handoff, the team can check each item instead of relying on someone’s memory of which account is signed in.

How to investigate an experience where you are “still recognized”

Describe what you observed first, then decide which type of information to check.

ObservationCheck firstSuggested action
The page shows the previous account nameIs the account still signed in?Check the current account and its environment assignment
Personal settings return after sign-inAre these settings stored with that account on the site?Review the website’s account settings
Similar recommendations appear on different sitesIs there enough evidence to identify a linking mechanism?Record the pages, times, and privacy settings; avoid jumping to a cause
You changed an email address but still receive old noticesWhich notification or recovery fields on the platform still need updating?Review the account settings one by one
A teammate opened another brand’s accountDo the list, environment name, and sharing scope agree?Update the business record and member permissions

A single instance of similar recommendations does not prove that a particular identity-resolution technology is in use. For a closer review of data collection, start with the website’s privacy notice, site information provided by the browser, and relevant public documentation.

Frequently asked questions

Does clearing cookies delete account information stored on the website’s servers?

Manage browser-local data separately from account information stored by the website. To change account details, subscriptions, or privacy choices, use the relevant service’s settings and verify the result.

How should we manage one business account across multiple browser environments?

First confirm the use case and the collaboration methods allowed by the platform, then assign an owner and environment. Give each environment a clear purpose, and check both the signed-in account and authorization when handing work off.

What is the most useful piece of organization a team can do now?

Choose one brand and connect four items: “business entity — work account — owner — browser environment.” Confirm that another teammate can use the record to find the correct working environment, then extend the approach to other brands.