A shared computer changes the account-security problem. The next person may use the same browser, the machine may be managed by someone else, and downloaded files can remain after a tab is closed. A private browsing window helps with some local browsing state, but it does not turn an untrusted computer into a trusted one.
Decide whether the task belongs on this device
Reading a public Oernoe guide or running a public Search query usually requires less trust than signing into a workspace that contains personal records. If the task involves sensitive health information, recovery codes, confidential messages, or important account changes, prefer a device you control. Convenience is not the only consideration.
Do not use a machine that shows signs of tampering, unexpected remote-control software, or browser certificate warnings. You cannot reliably inspect every possible risk by looking at the desktop. If you do not trust the owner or management of the device, avoid entering credentials rather than trying to compensate with a different browser mode.
Understand private browsing precisely
A private window generally separates its cookies and browsing history from ordinary windows and removes some of that local session state when all private windows are closed. It is not an anonymity guarantee. The website, the network operator, installed software, and the device owner may still have relevant visibility or control.
Downloads and bookmarks can persist outside the private session. A document saved to Downloads is not necessarily removed when the window closes. A screenshot saved to the desktop is a separate file. Think about the artifacts the task creates, not only the website's sign-in cookie.
Keep account identities separate
Before signing in, check whether the browser is already using another person's account or an organization-managed profile. Do not save your password into that person's browser profile. If a password manager belonging to someone else offers a credential, do not use or inspect it. Start from your verified sign-in destination and follow only your own authentication method.
When a product sends you to Oernoe Account, confirm the hostname and the account identity before continuing. A shared browser may remember a previous user's login. Seeing a familiar product dashboard does not prove it is your workspace. Stop if the displayed identity is not yours.
Avoid creating unnecessary local copies
If you only need to read a record, do not export it to the shared machine without a reason. If an export is necessary, choose its destination deliberately and know how you will remove or transfer it afterward. Check whether the operating system synchronizes Desktop or Downloads to someone else's cloud account.
Be especially careful with clipboard contents. A copied password, recovery link, or private paragraph can remain available to another application or person. Avoid copying secrets when the product supports a safer normal interaction. Do not assume that closing the tab clears the operating system's clipboard history.
Finish with sign-out, not only a closed tab
Use the service's sign-out control when you finish. If you used several product hosts and Account, check the relevant sessions rather than assuming one tab controls all of them. A unified login can make movement convenient, but the exact sign-out scope depends on implementation. This article does not claim a tested network-wide logout behavior.
Close all private windows if you used private browsing. Remove local files you created according to the device owner's rules, remembering that deleting a file may move it to a recoverable trash location. Do not empty a shared trash folder or remove another person's files. If sensitive material remains, ask the responsible administrator for an appropriate cleanup process.
Review from your own device afterward
Once you are back on a trusted device, review available account sessions and security settings. End access associated with the shared machine if the service offers that control. If you accidentally saved a password into someone else's profile or entered it on a suspicious page, treat that as possible exposure and change it through a verified route.
A useful closing checklist is simple: correct identity, no saved credential in another person's profile, no unintended download, explicit sign-out, and no overlooked private window. If you cannot complete those checks confidently, the better decision may have been to postpone the sensitive task.
Further reading: NCSC's password-manager exercise. Recommendations here are general device hygiene; no shared-computer cleanup or Oernoe global logout was tested. Prepared with AI assistance.
Oernoe
Writes for the Oernoe Journal. Questions about this article can go to the contact page.
Get in touchRelated Articles
Want to Learn More?
Explore our complete guides and knowledge base for more insights on privacy, technology, and best practices.
Browse Our Guides