Shared CryptLock Spaces.
Share access — never your keys.
A sealed container you can invite other people into. Every member holds their own key to the space, with a role that says what they may do there. Nobody hands over a password, and no one — including us — holds a master key over the space.
Why it matters
Sharing usually means surrendering control. Here it doesn't.
Everyone keeps their own key
Inviting someone gives them their own sealed access to the space — your key never leaves your device, and revoking a member never means changing your secrets.
Roles, not blind trust
Owner, Admin, Writer, Reader, Signer — each member gets exactly the capability you grant. A reader can read; only you and your admins shape the space.
No master account above it
The space is sealed by CryptLock — the same guarantee as everything else. There is no operator override that can open it, because none can exist.
How it protects you
CryptLock is step 3 of the security walkthrough — this is it in daily use.
A CryptLock is a sealed space with members. Content inside is encrypted once for the space; each member's personal key unwraps their own access to it. That's why membership can change without re-sending secrets — see the CryptLock step of the walkthrough for the model.
And the honest limit: a member you invite can read what their role allows — and nothing stops a person you trusted from copying what they can legitimately see. Choose members, not miracles. The full boundary list is in the whitepaper.
Share with people. Not with the world.
Shared CryptLock Spaces ship with Sharp#Soft 1.0 in 2026, Windows first.