{"id":8477,"date":"2021-08-12T21:26:02","date_gmt":"2021-08-12T19:26:02","guid":{"rendered":"http:\/\/plus.maciejpiasecki.info\/index.php\/2021\/08\/12\/locking-chrome-incognito-tabs-could-soon-bolster-privacy-for-android\/"},"modified":"2021-08-12T22:07:06","modified_gmt":"2021-08-12T20:07:06","slug":"locking-chrome-incognito-tabs-could-soon-bolster-privacy-for-android","status":"publish","type":"post","link":"https:\/\/plus.maciejpiasecki.info\/index.php\/2021\/08\/12\/locking-chrome-incognito-tabs-could-soon-bolster-privacy-for-android\/","title":{"rendered":"Locking Chrome Incognito Tabs Could Soon Bolster Privacy For Android"},"content":{"rendered":"<p>Quite aside from visual updates like Material You in Chrome for Android and behind-the-scenes security changes, Googlers are also working to ensure privacy, including adding locking Incognito Mode tabs. That\u2019s based on recent reports stemming from changes spotted in the Chromium Gerrit code repository.<br \/>\nAs might be expected, the code doesn\u2019t reveal a whole lot. And it\u2019s far from ready for release. But it does point to intriguing features, at the very least for mobile users.<br \/>\nWhat would locking Incognito Mode tabs do for Chrome Android?<br \/>\nNow, the gist of the changes is straightforward. The code change is labeled \u201cEnable device reauthentication for Incognito\u201d in the repository. And its descriptor points to a new option in Settings under Privacy and Security. Namely, an option that requires \u201cauthentication\u201d in order to access existing \u201cIncognito tabs\u201d on Android.<br \/>\nUltimately, this change appears in line with another update recently released for iOS users. One that locks access to Incognito tabs behind verification using Apple\u2019s biometrics. Namely, Face ID. But it may work a bit differently for Android users.<br \/>\nNot least of all, not every Android handset supports facial recognition or even fingerprint scanning. So Android may also come with additional, non-biometric-based options. Such as a password or PIN. Or it may ultimately require users to have one of those two biometrics hardware options to gain access. In either case, what this does is presumably block anybody from opening Incognito tabs in Chrome that are already in use unless the user proves that they\u2019re the phone\u2019s owner.<br \/>\nThis is still a long way out<br \/>\nAs of this writing, however, the new feature is still tucked behind a flag setting found at the \u201cchrome:\/\/flags\u201d URL. And that flag setting doesn\u2019t actually turn anything on just yet either, in addition to only being available on the Canary Channel. Indicating that this feature is still very much in the early stages of testing. As such, users probably shouldn\u2019t expect that it will arrive on Android in the near future. With at least an update or two likely separating this test period and release.<br \/>\nAs for other platforms, there\u2019s also been no indication that this will be pushed on desktop platforms, including Chrome OS. Although that does seem as though it would be the next logical step for Google to take.<br \/>\nThe post Locking Chrome Incognito Tabs Could Soon Bolster Privacy For Android appeared first on Android Headlines.&#013;<br \/>\n<img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/plus.maciejpiasecki.info\/wp-content\/uploads\/2021\/08\/chrome-beta-86-icons-overflow-Android-DG-AH-2020.jpg\" width=\"1920\" height=\"1080\">&#013;<br \/>\nSource: ndroidheadlines.com&#013;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Quite aside from visual updates like Material You in Chrome for Android and behind-the-scenes security changes, Googlers are also working [&hellip;]<\/p>\n","protected":false},"author":6,"featured_media":8478,"comment_status":"false","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-8477","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-bez-kategorii"],"_links":{"self":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts\/8477","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/comments?post=8477"}],"version-history":[{"count":1,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts\/8477\/revisions"}],"predecessor-version":[{"id":8479,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts\/8477\/revisions\/8479"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/media\/8478"}],"wp:attachment":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/media?parent=8477"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/categories?post=8477"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/tags?post=8477"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}