sha.chatSeparate spaces
Personal and Professional are designed to keep keys, contacts, caches and notifications separate. Professional policies must preserve personal privacy.
Isolation requirementMost of this page is still in English. Its Kugg text is being written.
Security · Architecture and release requirements
Private by design.
Verified before release.
Protection belongs inside both worlds: private conversations, separate spaces and explicit control over keys and actions.
The interactive preview needs JavaScript.
preview · sample
Private messages and calls
End-to-end encryption is a core requirement. Device verification, session recovery and call privacy must pass release checks before availability.
Release verification requiredPost-quantum messaging
The selected chat profile is PQXDH with ML-KEM-1024 and the Double Ratchet. ML-DSA-87 is the selected profile for Professional control signatures and the Z<>W gateway.
Selected profiles · implementation verification pendingKeys under local control
Wallet actions require scoped permissions and explicit review before signing. Self-custody, device recovery and gateway isolation remain verification requirements.
Review before executionScoped agents and models
Agentic team management → Orchestrator → Agentic team follows the active space. Tool access, delegated permissions and approval of consequential actions must remain explicit.
Bounded accessEvidence before release
Build checks, isolated active security testing, recovery tests and device-based end-to-end checks support release decisions. Independent audit completion is not claimed.
Active developmentPrivacy in everyday use
The boundary should be visible
before an action happens.
Security requirements become useful when they explain an ordinary moment: opening a Professional conversation, inviting an assistant, replacing a phone or reviewing a transfer.
Professional context stays in Professional.
A professional contact opens in the professional directory. Its messages, notifications, model context and permissions should follow that space, while personal conversations remain separate.
- Visible active-space indicator
- Separate keys, caches and notification rules
- Explicit warning at a cross-space boundary
Help without unrestricted access.
A model should receive the context and tools permitted for the active task. An orchestrator coordinates the agentic team inside those limits; an instruction in a message must not grant new permissions.
- Opt-in model access and scoped retrieval
- Bounded tool permissions and revocation
- Review before consequential side effects
Recovery is part of privacy.
The recovery design must let a legitimate participant restore access while limiting what a lost or compromised device can still do. Device registration, revocation and encrypted backups need end-to-end verification.
- Device and session inventory
- Explicit recovery policy
- Tests for revoked and stale credentials
Intent is separate from a signature.
An optional wallet or agent may prepare an action. The review should show the recipient, network, asset, amount, fees and applicable permissions before local signing is allowed.
- Scoped wallet permissions
- Reviewable transaction details
- Receipts and replay protection
A conversation can carry an intention.
It should not silently grant authority.
What verification needs to establish
More than a list of algorithms.
Encryption and identity
Session establishment, participant verification, key changes and recovery must behave correctly together. Post-quantum profile selection alone does not establish that the complete product is secure.
Calls and networks
Media protection, authenticated relays, reconnection and device permissions need checks on working builds and real network paths.
Metadata and services
End-to-end encryption does not conceal every routing or operational signal. Data minimization, retention rules and service access remain separate requirements.
Independent assessment
Automated checks and isolated active testing support development. The current release does not claim that an independent cryptographic audit has been completed.
Security contact
Report a concern.
Contact champion@sha.chat to arrange a report. Keep credentials and sensitive evidence out of the first message.
Contact the team ↗