Sharing a computer? Give each person their own space.

Use your own operating-system account and check which browser profile and website account are active. A familiar avatar is not proof that the intended email or cloud account is selected. Avoid saving your credentials or enabling browser sync in another person’s session.

Google explains that another device user can switch Chrome profiles. A different profile helps organise bookmarks and sessions; it does not lock another person out of a profile inside the same accessible OS session.

Private or Incognito browsing limits some local browsing records after all private windows close, but it does not hide activity from every website, employer or network provider. Downloaded files and bookmarks can remain. Sign out of websites when finished, close all private windows and check downloads you created. Do not clear another user’s history, saved passwords or files to tidy a shared browser.

Keep personal documents in the intended user’s private workspace. Use an agreed shared location only for files the relevant people should access. Check permissions with a harmless sample rather than open somebody else’s real document. Avoid granting Everyone full control to solve one access error.

Check which cloud account is connected before synchronising or importing files. Do not add a personal cloud account to a common OS session or redirect all folders without understanding who can then see the material. Our cloud setup guide separates account ownership, folder scope and file availability.

Have a separate usable backup for files that matter; account separation and sync do not establish one. Do not move or delete somebody else’s data or disconnect their cloud account as a privacy fix. Ask the owner or IT contact about the intended sharing arrangement first.

Keep the operating system, browser and applications on supported update paths. Leave legitimate security protection, backups and management tools enabled. An ordinary shared PC is not made safe by installing several competing security products or using a cleaner recommended by a pop-up.

Agree who checks updates and responds to security warnings, including a suitable time for restarts. Windows 10’s ordinary free support ended in October2025; confirm any applicable ongoing support arrangement rather than assume the device is covered. Preserve accessible settings people rely on.

For an account-access problem, follow the appropriate recovery path rather than use password-bypass tools or a reset that risks another person’s data. If compromise is suspected, stop sensitive activity and use a separate trusted device and the malware guidance for next steps.

With the owner and users’ agreement, create a harmless test file in the intended personal location and another in the intended shared location. Save and end the session normally. Have the next person sign into their own account and confirm only the intended shared test file is available through the agreed path.

Check that the correct browser/website account is used and that lock or sign-out behaves as expected. Do not test by guessing someone else’s password, bypassing permissions or opening their real documents. An unexpected access result needs the owner or IT team to review the configuration.

Record the handover routine and who handles changes. Confirm needed work and backups remain accessible to their rightful owner. If the planned separation works, stop changing permissions. This check reduces accidental exposure; it is not a penetration test or a guarantee against an administrator or compromised system.

Get help when users can access material they should not, no authorised administrator can manage the computer, business and personal accounts are mixed together, or a change could remove someone’s only copy of important files. Keep a list of users, required tasks and the unexpected behaviour without sharing credentials.

Our data protection and security support can discuss appropriate access and file-handling arrangements. A workplace shared terminal may need centrally managed accounts, application access or a kiosk design; follow the responsible organisation’s requirements rather than adapt a home-computer recipe.

A suspected account or device compromise requires assessment beyond adding another browser profile. Keep legitimate access intact and use the appropriate trusted-device recovery or incident process.