Skiff Review: The Logic of Private Sovereign Collaboration and the Workspace Unhack

You’re three people deep in a shared doc, building the thing that’s supposed to give you an edge — the strategy, the cap table, the product nobody’s seen yet. It feels private. It’s just your team, after all, on a quiet Tuesday. But the doc lives on a server you don’t own, and somewhere in a 40-page terms-of-service you scrolled past, you agreed that the company holding it can read it for “compliance,” hand it over on a subpoena, and feed it to a model in training. The work that was meant to be your secret weapon is sitting, in plain text, in someone else’s building.

The short version: Skiff was an end-to-end encrypted workspace — mail, documents, and file storage — built so the platform itself could never read your content. Every keystroke was encrypted on your device with AES-256 before it reached Skiff’s servers, which is what “zero-knowledge” means: even Skiff’s own staff couldn’t decrypt your data, because the keys never left you. Important caveat: Skiff was acquired by Notion in 2024 and the standalone product was wound down, so you can’t sign up today. What’s still worth keeping is the architecture — it’s the exact checklist for judging any private workspace you do adopt (Proton, Tresorit, Sync.com and others). The lesson outlives the product: in a normal cloud office, privacy is a promise; in a zero-knowledge one, it’s mathematics.

Why standard workspaces like Google Workspace leak your secrets

Start with the assumption almost everyone makes and almost nobody examines: that logging in with a corporate account makes your data private. It does the opposite. It makes your data accessible — to the provider, on terms you don’t control.

This isn’t your carelessness — it’s the system working as designed, against you. Centralised platforms — Google Workspace, Microsoft 365 — keep your intellectual property on servers they own and operate, and that ownership cuts two ways. First, readability: the provider can audit, analyse, or copy what you store; a government agency can subpoena it; and increasingly, their AI training pipelines can learn from it. None of that is a data incident. It’s the documented arrangement these companies wrote into the terms you accepted. Second, lockout: the same platform that holds your office can lock you out of it — over a policy dispute, a flagged payment, a change in your jurisdiction. Stop blaming yourself for trusting the obvious tool. You don’t own your workspace. You rent it from a landlord who keeps a key to every room and a clause that lets them in.

For a team trading on a disruptive plan, a capital move, or a product nobody’s shipped yet, that’s not a footnote. Your own tools become the leak.

The reframe: zero-knowledge turns privacy from a promise into a proof

Here’s the idea that reorganises everything, and it’s worth slowing down for. The privacy you get from Google or Microsoft is a policy promise — “we won’t look unless we have to.” It depends on corporate goodwill, on legal compliance, on no rogue employee and no court order. It can be revoked, overridden, or quietly amended in an update you’ll never read.

Zero-knowledge architecture replaces that promise with something colder and far more reliable: a mathematical fact. Your data is encrypted on your device, with a key derived from your passphrase, before it ever touches the server. The server stores ciphertext — noise. The question stops being “will they look?” and becomes “can they?” — and the honest answer becomes no, not because they’re nice, but because they don’t hold the key. Skiff’s staff couldn’t read your mail if a subpoena demanded it, because there was nothing on their end to decrypt. That’s the whole shift: from trusting people to trusting math.

Once you’ve seen that distinction, you can never un-see it — and it’s the single lens that tells you whether any “private” tool is actually private or just politely promising to be.

How Skiff’s encryption architecture worked

Skiff stacked four layers, and they’re worth naming because they’re the template you’ll measure alternatives against.

• Private-key root. Your login passphrase derived a unique encryption key that only you held — not stored on the server, ever.
• Client-side encryption. Every keystroke was encrypted on your device with AES-256 before it reached Skiff’s servers.
• Team synchronisation. Teammates’ devices received the encrypted data and decrypted it with their own keys, shared by invite — so collaboration happened without the server ever seeing cleartext.
• Decentralised storage. Files were fragmented and distributed across IPFS nodes rather than sitting whole on one controllable server.

The result was the part that made it usable: the same real-time editing feel as Google Docs, with a server that never saw a word of your content. Privacy that costs you the product’s usability gets abandoned by Friday — the architecture only matters because it didn’t.

Mail, Pages, and Drive: encryption without the friction

Three pieces, each closing a specific leak.

Skiff Mail encrypted the subject line, attachments, and metadata at the same strength as the body — which matters, because the subject line is often where the deal actually lives. Unlike raw PGP, it didn’t make you hand-manage keys; you sent to a teammate’s address and the clients negotiated encryption transparently. That’s the difference between encryption a normal team will use and encryption that stays a security blogger’s hobby.

Skiff Pages let several people edit one encrypted document at once, in real time, using conflict-free replicated data types (CRDTs) — a structure that can merge everyone’s edits without the server reading the content. Google Docs collaboration without Alphabet reading your strategy.

Skiff Drive fragmented files across IPFS nodes, so no single party — including Skiff — could quietly delete your data or gate your access to it.

How to evaluate any private workspace: the checklist Skiff leaves behind

Since you can’t adopt Skiff today, here’s the durable payoff — the exact questions its design answers, turned into a test you can run on Proton, Tresorit, Sync.com, or whatever you’re weighing. Start with the smallest possible move: read the provider’s encryption page and look for the words “client-side” and “zero-knowledge.” If they’re missing, you have your answer.

Does encryption happen on your device, before upload? That’s the line between zero-knowledge and “encrypted at rest” (which the provider can still read). Do you hold the keys, or do they? If they can reset your password and recover your data, they can read your data. Is there a recovery phrase you control? Skiff issued one like a crypto-wallet seed — print it, store it in a physical vault, never on the drive it’s protecting. Can you mandate hardware 2FA? Keys like a Purism Librem Key or a YubiKey can’t be phished or remotely lifted. Can you export and leave? Real sovereignty means a clean exit; Skiff exported to PDF and DOCX, decrypting locally on the way out.

And the honest trade-offs, because a tool that hides them is selling you something: a genuine learning curve (keys, recovery phrases, 2FA — an hour of training, not five minutes), fewer integrations than the Google/Microsoft ecosystem, mobile apps that tend to trail the polish of Gmail, and vendor lock-in risk — which Skiff’s own shutdown just proved is real, not theoretical. Keep a monthly encrypted backup to independent storage like Proton Drive so no single provider’s fate is your fate.

Frequently asked questions

Can I still sign up for Skiff?
No. Skiff was acquired by Notion in 2024 and the standalone encrypted workspace was discontinued, with existing users guided to migrate. This review is kept as an architecture reference — the zero-knowledge model it pioneered is the standard to look for in the alternatives you can still use today.

What happens if I lose the password on a zero-knowledge service?
This is the trade-off of holding your own keys: there’s usually no “reset” the provider can perform, because they can’t decrypt your data either. Recovery depends on the phrase the service issued at signup — which is exactly why printing it and storing it physically is non-negotiable, not optional.

Could a provider’s employees read my data if they wanted to?
On a true zero-knowledge platform, no — your data is encrypted on your device before it reaches their servers, and they don’t hold your private key. The protection is mathematical, not a policy they promise to honour. On a conventional platform that encrypts only “at rest,” the answer is yes, because the provider holds the keys.

Does end-to-end encrypted collaboration work offline?
Generally no for live editing — real-time sync needs connectivity so devices can exchange encrypted updates. You can usually read cached documents offline, but creating or merging changes waits for a connection. That’s a property of synced collaboration, not a flaw unique to any one tool.

How do I move my data out if a service shuts down?
Choose tools that export to standard formats (PDF, DOCX) and decrypt locally during export, so you keep control of the plaintext copy. Skiff’s own wind-down is the cautionary tale here: a clean export path and an independent encrypted backup are what turn a discontinued product from a disaster into an inconvenience.

You came in believing a corporate login was a locked door. It was a window with the blinds up. The thing worth taking from Skiff isn’t a signup link — it’s the moment you understood the difference between a company promising not to read your work and a system that mathematically can’t. That lens is yours now, and it doesn’t expire when a product does. Run the checklist on whatever you store your real secrets in. Hold your own keys. Keep your own exit. You’re not a tenant in someone else’s office anymore — you’re the one who owns the lock.

—

Related reading on TUH: Purism Librem Key Review, Proton Drive Review.