![]() So, when the user closes the last private browsing window, we clear our in-memory caches of data from the sites the user visited. In the Firefox UI, the user ends their private session with a website when they close ALL their private windows. ![]() We should not write any full or partial addresses or site data from Private Browsing page visits in a way that shows them in the local regular Firefox UI. A feature now better accomplished with the Multi-Account Containers add-on.) (Note that a by-product of these protections allowed users to sign into a website with 2 accounts. We highlight these aspects in the goal descriptions below. To achieve all these goals, we concentrate on: local privacy, session isolation, and site isolation. In 2018, we officially added the 3rd goal to Private Browsing design scope. In 2015, we added Tracking Protection to Firefox to help protect users from online adversaries. Research shows that users expect Private Browsing to protect them from online adversaries - e.g., websites, trackers, data brokers etc. The initial design concentrated on isolating Private Browsing mode from regular browsing mode. Private Browsing was initially designed with just these two goals in mind. The first 2 goals focus on a local adversary - someone with direct access to Firefox. Protects the session's data from online tracking.Prevents the session's data from writing to persistent storage.Doesn’t save the browsing history or display it in the Firefox UI.We target Private Browsing to 3 privacy goals in a Private Browsing session, Firefox:
0 Comments
Leave a Reply. |