July 23, 2026

Why Other Users' AI Context Does Not Mix When Switching Accounts

When using account A on the same computer and switching to account B, what should happen to the previous user's AI context?

Account A's Saved and Anchor should not be visible to account B. A Handoff prepared in account A should not be used in account B's new conversation.

Account switching is not just changing the name on screen but changing the ownership boundary of AI memory.

Mixing Is Not a Simple Display Error

AI conversations may contain business ideas, code, customer information, and personal judgments.

If another user's context is visible or delivered to a new conversation, it is not only a privacy exposure but also incorrect judgments may be connected as if they were one's own records.

What Must Be Separated by Account

The following data and states must follow the same user boundary.

Raw conversation records
Pack
Saved
Anchor
Graph View nodes and connection relationships
Handoff preparation and execution state
Local cache and pending requests
Usage and account display

Even if only server data is separated and browser state remains, problems can occur.

The Server Must Verify Data Ownership

The browser may send a user ID in the request body, but the server should not trust that value as is.

Only the user obtained by the server checking the current authentication state should become the data owner.

Knowing a specific Anchor ID alone does not grant permission to read that Anchor.

Web and Extension Must Use the Same Login Authority

If the website is account B but the extension uses the old state of account A, data may be saved to the wrong account.

In 5BY.AI, the web and extension should not have independent login authorities. Popup, conversation collection, Saved, Anchor, Handoff, and API requests must all use the same user state verified by the server.

A Single 5BY.AI Account State Is Shared Within the Same Chrome Profile

Multiple windows and tabs in the same Chrome profile use the same web cookies and extension storage area.

Therefore, within the same profile, a single 5BY.AI login state and extension connection is shared.

To use different 5BY.AI accounts simultaneously, using different Chrome profiles is the clearest approach.

When Switching Accounts Within the Same Profile

When logging out of account A and logging into account B, the following must transition together.

Deactivation of account A's session
Initialization of popup and AI page state
Per-user cache separation
Blocking of stale pending requests
Confirmation of account B's login state
Re-fetching of account B's data

A save request started in account A should not be reinterpreted as account B's request.

Graph View Must Also Show Only Current Account Data

5BY.AI Graph View should show only Pack, Saved, and Anchor owned by the currently logged-in user.

Even if a different user ID is in the URL or request, the server must verify ownership.

Data that briefly appears on screen and then disappears is also an exposure, so local cache must also be separated per user.

Handoff Requires Stricter Verification

Handoff delivers the context of a past Anchor to a new AI conversation.

If another user's Handoff remains, it causes a bigger problem than simple list exposure. It must be usable only when the current user is the owner of the Anchor and has explicitly executed it.

Isolation and Deletion Are Different

When switching to account B, account A's data is not deleted.

It becomes inaccessible to account B. When logging back into account A later, the original Pack, Saved, and Anchor should be findable again.

Trust in AI memory is not created solely by the ability to preserve for a long time.

The ability to accurately distinguish whose memory it is and prevent other users' conversations and judgments from mixing is also needed.