If you don’t believe us, you can simply search “How to detect incognito mode” and you will find plenty of information about it, including tools that help developers know is a user is surfing in the supposedly private mode. This is particularly problematic in case we are using the incognito mode to look for flight tickets or an expensive product to avoid a price surge. However, this hasn’t gone down too well with Google and the search giant is working to fix this, as it has recently committed to Chromium’s Gerrit source code management.
However, the flaw that lets website developers know if a user is browsing their website in the incognito mode has been around for a very long time. We all know that most of the websites on the internet make money via advertising and they need to track their users’ activities for it in order to collect the required data. Currently, for tracking users in the Incognito Mode, developers try to access the Filesystem API, which is disabled by default when the user starts browsing in the incognito mode. However, if they are not able to access the Filesystem API, the user remains undetectable in the Incognito Mode. But now, this is set to change as reports suggest that Google will be removing the FileSystem API altogether. Instead, a virtual file system will be created using RAM when it is asked for a file system in the Incognito Mode. It is worth mentioning that the incognito detection prevention feature will be rolled out in Chrome 74, however, it will be behind a flag. So, those who do know how to use the flag system will be able to access and enable the function. However, if you want this function to be enabled automatically, you would have to wait for Chrome 76.
