No backend
No central task server
Driftboard does not need a hosted app database to store your board content.
Local data
Your workspace stays local
Board data is stored on your own device, and syncing only happens when you choose to connect peers.
P2P sharing
Share only with trusted peers
Anyone with access to a workspace invite can participate, so room codes should be treated like private links.
Security model
Driftboard is designed around a smaller trust surface: local storage, peer-to-peer sync, and no Driftboard-hosted workspace backend. That means there is no central Driftboard account database holding your boards.
What this protects against
- Accidental exposure through a hosted project-management account.
- Dependency on a third-party backend just to open your own boards.
- Cloud lock-in for personal task data.
What you still control
- Keep your device secure because local board data lives there.
- Share invite/room codes only with people you trust.
- Use self-hosted signaling if you want tighter control over the connection process.
Privacy by design
The simplest privacy policy is not collecting board content in the first place. Driftboard’s public site and app description should make that clear, and the full privacy page is available at /privacy/.
Next step
Security and usability together.
Read the docs to understand how workspace sharing, signaling, and CRDT sync work.