Is a Local AI Companion Private on a Shared Computer?

A local AI companion is not automatically private from the people who share your computer. If someone sits down at your signed-in account and can open the conversation, keeping the model on the machine does not stop them reading it.

That matters on a family PC, a laptop shared with a partner, or a machine owned by work. You may be comfortable sharing the hardware without wanting to share a conversation about a difficult relationship. Start with who can use your account, not where the model runs.

Your login arrangement determines the first privacy boundary

The short version: A shared login offers little separation. Separate OS accounts help against casual access; administrator access and device management require more trust.

Use this matrix before putting anything sensitive into a companion app:

These are access boundaries, not security guarantees. Separate accounts will not prevent someone looking over your shoulder or reading a screenshot you put in a shared folder.

The local and cloud companion choices address another question: which system processes a conversation. Your household login arrangement still matters whichever processing option you choose.

Separate OS accounts help when everyone respects the boundary

The short version: Give each person their own operating-system login and keep the credentials private; a second browser profile is not a substitute.

Apple’s Users & Groups documentation recommends an account for each person using a Mac. It distinguishes standard users from administrators, who can manage users, install apps, and change settings. Look in System Settings > Users & Groups.

Microsoft’s account guide explains that separate Windows accounts give users their own settings, documents, and applications. Account creation is under Settings > Accounts > Other users. Microsoft recommends standard accounts for everyday use and limiting the number of administrators.

For a family computer, agree that each person uses their own login rather than borrowing whichever desktop is already open. Use different passwords. Giving everyone your password defeats the separation even when their own accounts exist.

Keep private exports out of Public, Shared, or other deliberately shared folders. A separate account does not make every location private. Likewise, a browser profile separates browsing activity but does not establish a general OS permission boundary around a desktop app’s data.

This is reasonable protection against someone casually opening the wrong window. It is not a promise against someone actively trying to get around the rules.

Administrator access changes whom you must trust

The short version: Administrators have powerful ways to affect the machine, but that does not mean every administrator can automatically decrypt every protected item.

An administrator may be able to install software, change permissions, or arrange monitoring of future activity. Microsoft explicitly warns that administrators have complete control over the system. A separate standard account is therefore not enough to treat an untrusted administrator as harmless.

There are limits to that statement. Access to a particular protected file can depend on encryption, available keys, permissions, hardware protections, and the machine’s state. An administrator label does not magically reveal every secret. Equally, one inaccessible file does not prove the whole session is safe from monitoring.

On a work-managed laptop, you may not know which management agents are installed or what the organization collects. Read the device policy rather than testing ways around it. A personal OS account on company hardware does not transfer control of that hardware to you.

If someone in your household controls the computer and is deliberately monitoring you, this checklist cannot establish safety. Prefer a device you control; do not assume a new login will be invisible to its administrator.

Lock the session before someone else takes the chair

The short version: Locking blocks ordinary access to your desktop while you are away, provided other people cannot sign back in as you.

On Windows, press Windows+L. On a Mac, choose Apple menu > Lock Screen, as described in Apple’s screen-lock guide. Set a short automatic lock delay and require authentication promptly after sleep or the screen saver.

Try it with harmless content: lock the machine, wake it, and check what appears before authentication. A black display alone is not evidence that the session requires a password. If someone needs the computer, have them switch to their own account rather than reopen yours.

Disk encryption serves a different purpose. It is not a barrier to reading a chat through an accessible signed-in session. Closing the app also does not prove its stored conversations are inaccessible. Our FileVault and BitLocker guide covers disk protection separately; it does not replace account separation.

Previews and copied files can cross the account boundary

The short version: Check what is visible outside the conversation window and where you have created additional copies.

Look at notification previews, recent-file lists, task-switcher thumbnails, and any screen-sharing session. If an app sends notifications, inspect the OS controls available for that app and test what appears on the locked screen. This is an OS-level check, not a claim that Local Waifu has a particular notification switch or per-chat PIN.

Screenshots and copied text deserve the same care as the original conversation. A screenshot saved to a synced Desktop folder may reach another device. An export placed in OneDrive, iCloud Drive, or a shared backup location follows that location’s access rules. Check your actual sync settings; do not assume every local app database is automatically uploaded.

Ask who can sign into the backup account and who can restore its contents. Deleting the visible chat does not prove those separate copies disappeared. The chat data-flow guide explains why storage and copies need separate attention.

Before your next private conversation, check the handoff

The short version: Decide who can enter your account, see the screen, and retrieve copies before deciding what to share.

• Use your own OS account with credentials other household members do not know.
• Identify who has administrator access and whether the device is managed.
• Test the lock screen and automatic lock with harmless content.
• Hand the computer over through account switching, not your open desktop.
• Check previews, screen sharing, and who can physically see the display.
• Review shared folders, screenshots, exports, and synced or backed-up copies.
• If the machine’s owner or administrator is someone you cannot trust with the conversation, choose another device before typing it.

Questions people ask

Back to the blog