Truple Logo Truple Support
search  /  articles  /  android  /  android-incognito-private-browser-alerts

Incognito / Private browser alerts

Example alert for incognito / private browser on Android

Last updated: October 6, 2021

Truple will capture screenshots when incognito or private browsing mode is used across all platforms except on Android.


The Truple app analyzes each screenshot to determine if incognito or private mode was used when the screenshot was taken. If it detects that incognito/private browsing was in use, it will immediately send a tamper email out to all email recipients (accountability partners) including the website that was being visited while incognito mode was used. Below you can see an example of what the email looks like.

Truple provides complete internet accountability on Android as well, so every website visited is always captured and reviewable by accountability partners.

~2 years ago Google Chrome started using the Secure Flag whenever incognito/private mode is used on Android. No other platform currently behaves this way. Since that time a number of other browsers have followed suit. When the secure flag is declared no app or user can capture the contents of the screen (even you can't, try it out!). It's typically used for banking and financial apps--with good reason.

Legitimate Incognito Uses

Sometimes there are legitimate reasons to use incognito mode. Firefox on Android has yet to declare the secure flag when private mode is used. We recommend you use it if you wish to have a good private/incognito experience while using Truple.

False positive incognito alerts

Truple needs to analyze screenshots in order to identify incognito/private browser use. It looks for a specific pattern within the screenshot--primarily a mostly black screen. There are times when phones can "glitch" and produce a screenshot that looks identical to an incognito/private browser screenshot, even though incognito wasn't being used. This will result in false positive alerts being sent out. From what we've seen this happens rarely when it does happen, and we'd prefer to deal with the false positive alerts (which contain the website being visited within them when possible) instead of not alerting at all. We'll continue to look for ways to improve the accuracy, but for now false positives, while rare, can occur. When they do have accountability partners check the website being visited and as long as it's clean then there's nothing to worry about.

Still need help?