Verify privacy settings from the perspective of whoever can observe the data. The next user of a shared computer, a website where you sign in, an embedded service, your DNS resolver and your Google Account can see different things. Decide which record you want to reduce before choosing a setting and a test. This guide reflects sources available on November 12, 2026. The procedures are for readers to repeat, and external observations retain their original versions and scope.
Google's overview of privacy in Chrome · ACM CCS 2026 Firefox fingerprinting research
Record your version, device and profile first
The Chrome team announced stable patches on November 11. Windows and macOS receive 157.0.8103.78/.79 and Linux receives 157.0.8103.78, with gradual rollout. The Android announcement lists 157.0.8103.78 with separate app-store distribution. On desktop, use Help → About Google Chrome to check your build and relaunch when prompted after updating. On mobile, note the app version, operating system and test date.
Chrome November 11 desktop stable patch · Chrome November 11 Android patch · Google Chrome security controls
| Platform | Where to look | What can differ |
|---|---|---|
| Windows, macOS, Linux | Settings → Privacy and security and site information by the address bar | Operating-system permissions, networks and enterprise policies can affect results |
| Android | Chrome Settings → Site settings or Privacy and security, plus OS app permissions | Use Android Help for cookie controls and temporary exceptions |
| iPhone and iPad | Chrome Settings → Privacy and security and iOS app permissions | Use iOS instructions for Incognito and data controls. Desktop internal pages do not establish the mobile UI |
| ChromeOS / managed browser | Chrome Privacy and security plus system or administrator settings when needed | Secure DNS and other controls may be managed at system or policy level |
Google Chrome security controls · Google's site permission guide · Google Android cookie settings · Google iPhone and iPad Incognito guide
Create a separate desktop Chrome profile for testing and keep your usual working profile. Note whether Chrome is signed in, extensions are present, a policy applies and the window is regular or Incognito. Leave profile paths, account identifiers and full diagnostic screenshots out of forum posts. Useful settings search terms include third-party cookies, secure DNS and site settings.
Google Chrome profiles · Google's overview of privacy in Chrome
Review the Privacy and security page item by item
| Control | What it covers | How to check or reverse |
|---|---|---|
| Safety Check | Updates, dangerous extensions, password risks and some site grants | Review the actual alerts and recheck grants needed for a site |
| Privacy Guide | A walkthrough of selected existing settings | Check the final value on each settings page |
| Delete browsing data | Selected history, cache, cookies and other data within a time range | Check selected categories and sync scope. Start with one site for troubleshooting |
| Third-party cookies and site data | Default restrictions, site exceptions and stored data | Reload the same embed and test again after removing the exception |
| Security | Safe Browsing, HTTPS, Secure DNS and related controls | Check warnings, DNS resolution and the available settings separately |
| Site settings | Site grants and content rules for camera, location, notifications and more | Reset a single site's permission, then check its global default |
Google Chrome security controls · Google Privacy Guide introduction · Google's browsing data deletion guide · Google desktop cookie settings · Google's site permission guide
Safety Check reports password, version, extension, notification and unused permission findings. Privacy Guide helps you find several important choices. After the walkthrough, inspect the actual toggles, exception lists and management notices. A green Safety Check shows that the check presented no item to resolve. Inspect routing, activity and fingerprints with their own tests.
Google Chrome security controls · Google Privacy Guide introduction
When a single site is in an unexpected state, open Cookies and site data in its site-information panel or search Settings for See all site data and permissions. Find the affected domain. Note whether clearing data will require signing in again or rebuilding preferences. For a broader deletion, review the time range and selected categories. Deleting synced data may affect copies in your Google Account. Treat the browser record and a site's server records separately.
Google desktop cookie settings · Google's browsing data deletion guide · Google Chrome account storage and sync
Third-party cookies, exceptions and on-device site data
First-party cookies can keep logins, carts and preferences in the current site context. A third-party scenario arises when one site embeds another, such as a login provider, comment box or video. Compare the schemeful sites of the top page and embed, usually by scheme and registrable domain. On desktop, find Third-party cookies or Third-party cookies & site data under Settings → Privacy and security. Select blocking if you want to reduce cross-site cookies and then test your usual sites.
Google desktop cookie settings · Google Do Not Track · Chrome CHIPS documentation
If login or payment fails, try the service directly or use its supported separate sign-in page to see whether the problem is confined to the embed. If you need a temporary exception, use the desktop address-bar control for the current top-level site. Google documents up to 90 days in regular browsing unless you turn it off sooner, and the current session for a temporary Incognito grant. An entry manually added to the exceptions list follows its own rules and can apply in both modes. On Android, a temporary grant made in regular mode can carry into Incognito. Remove it in regular mode.
Google desktop cookie settings · Google Android cookie settings
Review local site data, third-party cookies and embedded content grants individually. First-party state and server records can remain after blocking third-party cookies. An embedded service may also ask to use data it already saved in a limited context. Check the top-level page and embedded origin before allowing it. Afterward, remove the Embedded content grant in site information or settings and check the general exceptions list.
Google desktop cookie settings · Google's site permission guide
Do Not Track sends a request. Google says most sites and services do not change their behavior in response. Chrome also offers an opt-out request concerning use of your data in eligible regions. Google currently lists California and says availability is gradual. Eligibility is determined per profile and can be affected by VPN use, typical location and account region. A toggle or observed signal records the request. Verify the site's handling separately.
Google Do Not Track · Google opt-out requests in eligible regions
CHIPS keeps embedded state separate by top-level site
CHIPS lets a site opt a cookie into partitioned storage with the Partitioned attribute. A single embedded origin can then hold different state under different top-level sites. A support widget can use this to remember independent state on two customer sites. The website requests partitioning. A user's third-party exception will not convert an ordinary cookie into a partitioned one. Requests can still expose network signals such as IP addresses.
Set-Cookie: lab_unpartitioned=sample; Path=/; Secure; SameSite=None
Set-Cookie: lab_partitioned=sample; Path=/; Secure; SameSite=None; PartitionedUse three HTTPS sites you control. Embed the same test origin on two different top-level sites, A and B. In A, load an endpoint that only writes test state. Then call a read-only endpoint from A and from B, where you have not written any state. Use the same widget origin and cookie name on both. A should receive its successfully stored partitioned cookie, while B should have no access to A's value. When third-party cookies are blocked, use DevTools to see the reason for an unpartitioned control's rejection. Keep the read endpoint read-only. Without a controlled service, record only the cookie attributes you can observe.
Chrome CHIPS documentation · Chrome DevTools cookie inspection
In DevTools, open Privacy and security to see allowed and blocked third-party cookies and reload to apply changes. In Application → Storage → Cookies, inspect Partition Key. You can also select a request in Network and inspect Cookies and any issue reason. Change global settings, site exceptions or DevTools temporary controls one at a time. Record statuses and partition keys. Keep full session cookie values out of logs.
Chrome DevTools Privacy and security · Chrome DevTools cookie inspection
In ioBroker issue #698, opened July 7, 2026, a user reported a cross-site iframe login failure on Chromium-based browsers with third-party cookies allowed. The discussion traced it to SameSite and the TLS requirements for a secure cookie. A maintainer offered an opt-in embedding setting. Microsoft's MSAL docs separately describe silent sign-in in identity-provider frames and browser partitioning restrictions. These are reasons to isolate the failing stage before looking for a site fix or using a supported sign-in flow.
ioBroker embedded login issue #698 · Microsoft MSAL official iframe documentation
What changed in Privacy Sandbox and where to check now
In April 2025, Google said Chrome would retain its approach to third-party cookie choice and drop the proposed standalone prompt. It later announced the retirement of several Privacy Sandbox technologies. The current status page distinguishes continuing support, retirement and proposals that did not launch. When reading an older guide, check whether it describes a browser setting, a particular Web API or a site's own ads or sign-in implementation.
Google's third-party cookie choice announcement · Privacy Sandbox feature status
| Technology | Current documented status | How to verify |
|---|---|---|
| CHIPS, FedCM, Storage Access and storage partitioning | Continued support | Check requests, partition keys or the actual consent prompt |
| Topics, Attribution Reporting, Protected Audience, Shared Storage and Related Website Sets | Deprecation or removal | Check the release and status for each API. Milestones can differ |
| IP Protection | Discontinued | Check connection routes and system networking separately |
Privacy Sandbox feature status · Chrome 152 stable release notes · Chrome 153 stable release notes
The Chrome 152 release notes list Private Aggregation removal. The Chrome 153 notes list deprecation and removal entries for Protected Audience, Related Website Sets, Shared Storage, requestStorageAccessFor and Attribution Reporting. Some Help pages still mention older advertising settings or related-site groups. In July 2026, a user reported that Ad Privacy disappeared in 150.0.7871.47. That is a public observation of one build. For 157, use your actual settings and current release documentation.
Google desktop cookie settings · Chrome 152 stable release notes · Chrome 153 stable release notes · Reddit report of the missing Ad Privacy control
Incognito, profiles and what remains on the device
On desktop, open Incognito with Ctrl+Shift+N, or Command+Shift+N on macOS. When all Incognito windows close, Chrome discards session site data and history as described for the mode. Closing one tab leaves the session alive if other Incognito windows remain open. Downloaded files and saved bookmarks remain. On iPhone or iPad, check the official instructions for hiding or locking Incognito tabs. A lock controls local access. End the session by closing all its tabs.
Google desktop Incognito guide · Google iPhone and iPad Incognito guide
Incognito generally does not sign you into Google or other sites automatically. If you sign in, the service can identify activity by account. Network providers, schools and employers can still observe network activity, and websites can see network and page signals. Separate Chrome profiles separate history, extensions and site data. Shared accounts, devices and networks can still provide other links.
To verify the local session behavior, visit an ordinary test page in the test profile and set a harmless preference in regular and Incognito windows. Close all Incognito windows and reopen. Check preference persistence and local history separately. When comparing site-visible signals, keep the page, sign-in state and network fixed. A login prompt by itself is one observation.
Google desktop Incognito guide · Google Chrome profiles · TweakTown single-device regular and Incognito observations
Safe Browsing levels and the data they send
On desktop, Settings → Privacy and security → Security offers Standard protection, Enhanced protection or no protection. Standard checks dangerous websites, downloads and extensions. Google describes local checks followed where needed by an obfuscated part of a URL sent through a privacy server, with more data possible for some incidents. Enhanced protection sends more information in real time, including visited URLs and samples of page, download, extension or system information. Choose the level based on the security coverage and data sharing you need.
Google Chrome security controls · Google Safe Browsing data handling
Safety Check and HTTPS certificate warnings are different signals. When a download or certificate looks suspicious, verify the address and trusted publisher before testing settings on a separate sample. Keep browser protection active while diagnosing cookies or login. The Security page may offer Manage JavaScript optimization & security. Restricting optimizers can reduce some security risks and affect performance or compatibility. Site JavaScript permission, cross-site cookies and fingerprints have separate controls and tests.
Google Chrome security controls · Google Safe Browsing data handling · Google's site permission guide
Verify Secure DNS, HTTPS, proxies and WebRTC separately
Secure DNS on the Security page controls encryption for Chrome's name lookups. Automatic mode can fall back to unencrypted lookup. A custom provider does not use that default fallback, so a failure may appear as an IP address lookup error. Check the network and internal names before changing the provider. On ChromeOS, look in the OS settings. Managed devices or parental controls may limit the option. A DNS test records the path used for those queries. Chrome, the system, a VPN and other applications may use different paths.
Always use secure connections tries HTTPS and warns before visiting an unsupported site. Chrome Enterprise notes document the gradual Chrome 154 default for public sites. That scope typically excludes private IP addresses and short intranet names. On 157, verify the mode and any policy that applies to you. HTTPS protects transport between browser and site. The site can process what you submit and networks can still retain their own connection records.
Google Chrome security controls · Chrome Enterprise previous release notes
| Question | Observation | What it establishes |
|---|---|---|
| Page HTTPS | Connection information or DevTools security details | Protocol and certificate for the connection tested |
| Browser DNS | Read the setting and use a trusted resolver diagnostic or test domain you control | Resolver and failures during that test |
| IPv4 / IPv6 egress | Use a trusted or self-controlled HTTPS echo for each address family | The browser, address family, routing state and time tested |
| WebRTC media | Inspect local webrtc-internals and ICE types during a consented test session | Record host, srflx and relay separately. Missing candidates leave that path untested |
Google Chrome security controls · IETF RFC 8828 WebRTC IP address handling
WebRTC gathers ICE candidates for media connections. Host candidates may use mDNS names, srflx can show a mapping seen by STUN, and relay identifies a relayed path. Camera permission and network candidates answer separate questions. Record HTTP egress, DNS and a WebRTC session independently. Before using a third-party diagnostic, read what information it receives. This guide documents procedures, with no public-route observations taken from the reader's browser, network or VPN.
IETF RFC 8828 WebRTC IP address handling · Google's site permission guide
Tighten site grants and restore them one site at a time
In Site settings, review defaults and site lists for location, camera, microphone and notifications. Remove persistent allowances you no longer need. On an affected site, use the site-information button next to the address bar to grant only what the task requires. Use an Allow this time option where offered. To restore the default, reset the site permissions and reload. Verify that the operating system also grants Chrome the necessary access.
Google's site permission guide · Google Chrome security controls
| Permission or content | Default approach | What to verify when needed |
|---|---|---|
| Location | Ask first or block sites that do not need it | Allow the target site only and check whether the page still infers location from the network |
| Camera and microphone | Grant access for the meeting or recording | Check OS privacy and the chosen device. Remove a persistent grant after use |
| Notifications | Remove unused or suspicious sites | Check browser and OS notification settings |
| Popups, redirects, embedded content and automatic downloads | Use a site exception for a specific action | Reload after one change and remove the exception afterward |
| Device interfaces, local network, clipboard and insecure content | Check why the specific site needs access | Inspect OS, version and site settings before using an exception |
Google's site permission guide · Google Chrome security controls
After denying the location API, a site may still infer a region from your IP address, account settings or information you entered. Camera permission leaves microphone permission separate. A grant changes the named capability. Test it when the target page requests that capability and review existing exceptions for the same site.
Google's site permission guide · Google's overview of privacy in Chrome
Device and content permissions in Site settings
On desktop Chrome, open Settings → Privacy and security → Site settings to review global rules. Some controls appear under Additional permissions or Additional content settings. For just one site, open it, then select View site information to the left of the address → Site settings. Labels, menus, and availability can vary by platform, version, and administrator policy.
| Setting | What it lets the site do | What can change after revocation or blocking |
|---|---|---|
| Background sync | A site that supports it can try to finish a queued action after you leave, such as sending a message or uploading a photo. | You may need to reopen the page to finish pending work. |
| Automatic downloads | A site can download several related files in one action, such as a batch export. | A batch may need individual confirmation. Previously downloaded files remain on the device. |
| File editing | An editor can read or write local files or folders you select and grant, for example to save a draft automatically. | Saving directly may ask for access again. Save your current edits before revoking access. |
| Clipboard | A site can read the clipboard when granted access, for example to preserve formatting. | Automatic reading may stop. You can paste manually in a trusted field when needed. |
| Local network access | A site can connect to devices on your network or services running on your own device, such as a device dashboard. | The site may lose local discovery or control. |
| USB devices | A site can pair with a compatible USB device you select, such as a label printer or development board. | The site may need to pair again before it can use that device through this web interface. |
| Serial ports | A site can use a selected serial port to exchange data with a terminal, configuration tool, or development board. | A web-based configuration or debugging session may need to reconnect. |
| HID devices | A site can access a selected Human Interface Device, such as a specialty keyboard or game controller. | Specialized in-page controls or device interactions may stop working. |
| Bluetooth devices | A site can communicate with a selected compatible Bluetooth peripheral, such as a sensor. | The site loses access to that peripheral and may need a fresh grant. |
| MIDI device control and reprogramming | A web music tool can interact with MIDI gear. Supported devices and grants may also permit a firmware update. | Web MIDI controls or a device update may require a new grant. |
| Window management | A permitted site can see information about multiple displays and place its windows on a specific screen. | A web dashboard or presentation may fall back to one screen. |
| Protected Content IDs | Some services may use a device identifier to authorize playback of copyright-protected media. | Some movies or audio may stop playing, depending on the service. |
| Automatic picture-in-picture | An eligible site can open media in a floating window automatically. | The permission no longer opens that window automatically. Manual picture-in-picture may still be available. |
| Insecure content | A site exception may let an HTTPS page load certain unencrypted embedded resources. | Removing the exception can block those resources again. Ask the site to serve them over HTTPS. |
To undo a change, remove the exception for that setting on that site so the current global rule applies again. You can remove a particular USB, serial, or HID device in the site's address-bar information. Reset permissions also restores other changed permissions for that site. Reload and check the original task. Revoking access affects future use. Handle any files already uploaded or messages already sent in the service that received them.
Google account storage, activity, diagnostics and preloading
A Chrome profile, signing in to a Google website and saving browser data to a Google Account involve separate settings. Under You and Google on desktop, check Chrome sign-in and account storage or sync for history, tabs, bookmarks and passwords. After signing out or stopping future sync, review items already saved in the account's data controls. Deleting synced data can affect other devices. Identify the copy you intend to change first.
Google Chrome account storage and sync · Google Chrome profiles · Google's browsing data deletion guide
Open your Google Account → Data & privacy → Web & App Activity. Review the main switch and the option to include Chrome history and activity from sites, apps and devices that use Google services. Chrome history also depends on Chrome sign-in and the relevant history storage setting. Check future saving and existing activity separately. Browser data clearing does not carry out deletion on other services' servers.
Google Web & App Activity · Google Chrome account storage and sync · Google's browsing data deletion guide
Back in Chrome under You and Google → Google services, review usage statistics and crash reports. Google says enabling reporting can send feature-use and diagnostic data, and crash reports can include URLs or memory fragments. Make searches and browsing better is a separate setting. If you want to inspect early requests, find Preload pages under Performance and compare off, Standard and Extended. Restore each recorded value and check page loading and the sync features you need.
Google Chrome usage statistics and crash reports · Google Chrome performance and preloading
Review extension site access and keep a clean comparison profile
In Manage extensions → Details, check Incognito access, permission to read or change site data and its scope. Use on-click or specific-site access when the extension supports it. Lower-level VPN and proxy features may follow separate controls. Start in a test profile with no extensions. Enable just one and record its version, permission scope and page behavior.
Playwright issue #43517, opened October 19, 2026, reports a debugger disconnect when a password manager inserted an inline iframe on macOS with Chrome 155.0.8059.82 and specified extension versions. The reported behavior depends on the particular automation, extension and page. Try the clean test profile and restore individual features to isolate a conflict. Research also shows that some custom ad-filter selections are distinguishable. Recording each extension's behavior and compatibility is easier to verify than installing several at once.
Playwright extension issue #43517 · USENIX Security 2025 ad-blocker fingerprinting study · Google extension management
Read research and single-device results at their stated scope
A fingerprint combines page-visible attributes such as viewport, language, time zone, fonts, graphics output and platform capabilities. Changing cookies may remove one state identifier while other attributes remain available. On October 6, a TweakTown author compared regular and Incognito Chrome 154.0.8037.98 on one Windows 11 machine, maximized at 100% zoom. Several reported Canvas, WebGL, font and hardware values matched while the overall test label shifted on reruns. Use it to design a comparison, with no population estimate for Chrome 157 from this sample.
TweakTown single-device regular and Incognito observations · EFF Cover Your Tracks methodology introduction
A 2026 PoPETs paper analyzes how normalized entropy can mislead when comparing differently sized datasets and discusses an alternative metric. The ACM CCS research publicly described on November 10 measured nearly 25 million Firefox release users and evaluated feature combinations and mitigations under three modeled fingerprinting services. The two studies show why the metric, sample, threat model and population matter. Firefox population percentages cannot be transferred to Chrome or interpreted as one reader's identification probability.
PoPETs 2026 paper on fingerprint entropy · ACM CCS 2026 Firefox fingerprinting research
Hold the page, device, network and window size fixed when comparing regular, Incognito and clean profiles. Record which raw fields stay the same and which change, alongside any unique or protected label. Start a separate record for a new browser or device. External test scripts, populations and scoring can change. Each result describes what that page collected in the observed session, with other correlation channels outside the test.
EFF Cover Your Tracks methodology introduction · PoPETs 2026 paper on fingerprint entropy · TweakTown single-device regular and Incognito observations
Keep a repeatable log and restore one change at a time
date,platform,chrome_version,profile,mode,setting_changed,test,expected,observed,rollback
2026-11-12,example,157.x,lab,regular,none,baseline,record,pending,none
2026-11-12,example,157.x,lab,regular,third_party_cookies,embed,record,pending,restore_baseline
2026-11-12,example,157.x,lab,incognito,none,local_signal,record,pending,close_all_incognitoRecord a baseline, then change one option at a time. Start with a local Incognito session, check an embed that uses no important account, then verify permissions and normal browsing. For external networking checks, record separate conditions for IPv4, IPv6, DNS and media candidates. When something breaks, reverse the latest change and reload the original page to see whether it recovers.
Google desktop Incognito guide · Chrome DevTools Privacy and security · IETF RFC 8828 WebRTC IP address handling
If a frame stays blank, check network failure, certificate errors, CSP or frame-ancestors, and whether the cookie was sent. If switching accounts is the only failure, identify whether it involves Chrome sign-in, the website session or an embedded identity provider. At the end, remove test exceptions, turn off test extensions and restore the settings you recorded. Confirm login, meetings and notifications still behave as expected.
Chrome DevTools Privacy and security · Chrome DevTools cookie inspection · Microsoft MSAL official iframe documentation · Google's site permission guide
Compare browser signals locally
Keep the version, profile, address and window size fixed. Measure twice with the original settings to see which readings vary on their own, then set one as baseline A. Change one setting and measure B. If you need another window or a restart, paste the JSON for A into the comparison field and record the window change as a variable.
The tool compares language, time zone, screen and viewport size, pixel ratio, logical processor hints, low entropy UA-CH, WebGL capability and a digest of a fixed Canvas drawing. A match means the readings agreed in those runs. A change, missing value or failed read needs the browser version, environment and setting for context. Use the same downloaded HTML file for both runs to test offline. API availability can differ between HTTPS and a local file.
Turn one settings change into an observable result
- Record the platform, build and profile
- Run the baseline test
- Change one toggle or site exception
- Reload and record the feature and observable signal
- Reverse the change and repeat the same test
- Note the evidence source and the paths still untested
Use this checklist to reduce specific observable data. Keep the original setting, action, target site and test result together. After an update or account change, start by rechecking the affected control.
Google's overview of privacy in Chrome · Chrome November 11 desktop stable patch