A note from the workshop
The sunglasses icon is doing a lot of public relations.
Private browsing is useful for limiting some traces left in a browser session. It is not a general invisibility switch. Match the feature to the problem you actually have before trusting it with a task it was never designed to solve.
Three useful checks
- Name the audience: Are you limiting local history, website tracking, or network visibility?
- Read the browser’s description: Check what private mode saves and what it does not hide.
- Use a trusted device: Private mode does not make a borrowed or compromised computer safe.
Put it into practice
Try an ordinary non-sensitive page in a private window on your own device. Notice that the browser may start without the same signed-in session. That can be convenient for testing a public page, but logging into a website still tells that website which account you used.
Mozilla explains that Firefox Private Browsing does not make you anonymous to websites or your network provider. It also distinguishes browsing history from downloaded files and bookmarks. Read the documentation for your browser rather than assuming another product uses identical rules.
Write down the result as a capability statement: for example, a separate temporary session for a non-sensitive task. If your problem is someone accessing the computer itself, use appropriate account and screen-lock controls. If your problem is site identity, signing into the same account is an important part of the picture.
Name the observer before choosing the feature
Privacy is easier to reason about when you name who you want to learn less. Another person casually opening your browser history is a different observer from a website you log into. A network operator is a third case. One browser feature does not answer all three questions in the same way.
Mozilla says private browsing does not make you anonymous online and does not protect you from spyware on the computer. Use that boundary when planning the exercise. A private session can be useful for checking a public page without your usual signed-in state; it is not a reason to enter sensitive credentials on an unfamiliar machine. The icon is a control label, not a witness-protection program.
Compare ordinary and private sessions with a harmless page
Use your own trusted device and a public page with no sensitive information. Notice whether your normal session is signed in, then open a private window through the browser’s real controls and visit the same page. Record the difference you actually see. You do not need to disclose anything new to learn whether the starting session changed.
Before signing into anything, predict what that action would mean. If you sign into your account in the private window, the site is being told which account you are using. A separate local browsing context does not turn an account login into an anonymous visit.
- Write down the observer you are trying to limit: another local user, a website, or a network operator.
- Read the current documentation for your browser’s private mode.
- Compare a harmless public page in an ordinary window and a private window.
- Close all private windows at the end, following the browser’s documented session behavior.
- Record only the feature behavior you observed, without calling it an anonymity test.
Why downloads and device trust still matter
Review the browser’s explanation of what it keeps and what it does not. A downloaded file can remain on the computer even after the private session ends; private browsing is not a file-disposal procedure. Avoid downloading anything sensitive as part of this exercise. A new bookmark is another action worth checking separately from page history.
If the computer itself is untrusted, changing the window type does not make the computer trustworthy. Stop before entering passwords rather than trying to layer confidence onto a device you cannot assess. If your goal concerns network visibility or another specific observer, investigate tools designed for that goal and their limitations instead of stretching the meaning of private mode.
Write a privacy statement you can defend
An accurate note might say: “The private window started without my normal account session; I did not test network anonymity.” That is more useful than private mode works. Keep the observer, the behavior checked, and the remaining question together. This gives you a practical reason to use the feature when it fits, and a clear signal to choose a different approach when it does not.
Know the limits
This is a feature review, not a test of network anonymity. Do not use a private window as permission to trust an unfamiliar computer with sensitive credentials.
Replace one vague privacy assumption with a specific documented behavior.
Print the private field sheet. Record actions and observations, not passwords, recovery codes, or private documents.
Keep exploring: the offline AI experiment, lost-phone recovery, or the Recovery Drill.
About this field note
Original CRYPT1K editorial guidance. Sources reviewed October 21, 2026. Procedures are reader exercises; no unperformed hardware, account, or AI test results are claimed. Character and artwork are fictional and AI-assisted.