Security and control
Useful context needs a hard boundary.
Delta is designed so each person enters through their own account, uses their own available context, and retains control over any operation that reaches beyond the conversation.
Account isolation
Same intelligence. Separate principals.
Delta's product behavior can be shared while personal context remains separate. The web workspace derives each chat request identity from the authenticated session, and anonymous access does not receive private account data.
The private preview currently restores account context through the Delta backend. Durable, thread-by-thread transcript restoration is a separate product capability and is not implied by the website interface.
Four boundaries
Private by design, explicit by action.
Your account is the web workspace boundary
The web chat proxy verifies the signed-in session and constructs request identity server-side. A browser-provided account ID cannot select another person's context through this path.
Context is not blanket permission
Remembered information can improve a response. It cannot authorize outreach, publication, purchases, provider writes, or another consequential operation.
Connections remain separate
A connected source is available only within its approved scope. Provider credentials remain outside the conversation and are never returned to the model or browser.
Internal operations stay internal
Owner workspaces, engineering evidence, and development consoles are not customer chat surfaces and do not become visible through an ordinary Delta account.
Product controls
What the interface must make visible.
Conversation versus memory
A transcript and durable remembered context are different records. Future memory controls will make review, correction, and deletion explicit rather than hiding them behind chat.
Temporary conversation
Temporary mode will provide a clear no-history, no-memory-write path. It will not quietly behave like a remembered session.
Scoped approval
When a supported tool could create an external effect, Delta must identify the exact action and request approval at that boundary. General chat access is never sufficient authority.
Your account. Your context.
Continue the conversation.
Private preview. Account-scoped context. Explicit approval for actions.