You don't own your Notion data (and it matters)

A brief history of disappearing data

Google Reader: dead. Millions of curated RSS feeds, gone. Sunrise Calendar: acquired by Microsoft, shut down. Wunderlist: same fate. Google Stadia: customers who "bought" games lost access to everything. Evernote: still alive, barely — but how many people have years of notes trapped in a proprietary format they can't easily move?

This isn't hypothetical. Every cloud-only tool is a bet that the company behind it will outlive your need for the data. That's a risky bet when the average tech company lifespan is shorter than the average career.

Export is not ownership

Notion lets you export your data. So does Evernote, Coda, and most modern SaaS tools. Problem solved, right?

Not really. Try exporting a complex Notion workspace. You'll get a zip file of markdown files with broken internal links, database views flattened into CSV files that lose all their metadata, and images downloaded into random folders. The structure — the thing that makes your workspace useful — doesn't survive the export.

Export is an emergency exit, not a door. Real ownership means your data is always yours — no export step needed. It's the difference between "you can take your furniture when you leave" and "we'll throw your belongings in garbage bags and leave them on the curb." Technically your stuff is there. Practically, it's a mess.

What local-first actually means

Local-first is a software architecture principle, not a marketing term. It was formalized by Ink & Switch in their influential 2019 paper. The core ideas:

• Your data lives on your device — not on a server you don't control
• The app works offline — no internet required for core functionality
• Sync is optional — when you do sync, it's peer-to-peer or through servers you choose
• Open formats — your data is readable without the app that created it

This isn't anti-cloud. Cloud sync is useful for backup and collaboration. But in a local-first architecture, the cloud is a convenience, not a dependency. If the sync server disappears, your data doesn't.

Kleppmann et al., "Local-First Software: You Own Your Data, in spite of the Cloud," Ink & Switch, 2019.

The speed you forgot was possible

There's a practical benefit to local-first that people don't talk about enough: speed.

When your data lives on your machine, everything is instant. Opening a workspace: instant. Searching your notes: instant. No loading spinners. No "syncing..." progress bars. No degraded experience on a plane or in a cafe with bad WiFi.

We've normalized the idea that apps need loading states. We've accepted that clicking a note should take 200-500ms because it needs to be fetched from a server. Local-first software reminds you that your computer is actually fast — the network was the bottleneck all along.

How Depli handles data

Depli is local-first by design, not by afterthought. Your workspaces are files on your machine, in open formats. You can read them, back them up, version them with git, or move them to another computer with a USB drive.

When collaboration is needed, Depli syncs through a relay — but the relay doesn't store your data permanently. It's a pipe, not a vault. If Depli the company disappears tomorrow, your files are still on your machine, in formats you can open with other tools.

This is what data ownership actually looks like. Not "we promise not to look at your data" — but "your data never leaves your machine unless you explicitly choose to share it."