Your Data
Where does your data go?
FlowPad is local-first: your sessions, skills, and context live on your machine. When you collaborate, you pick how far your data travels. Our cloud is optional at every step.
The design principle
Your machine is the trust zone.
FlowPad is built to run completely independent of any cloud, including ours. Agents, sessions, skills, and the knowledge they produce stay on your computer, where you already trust yourself completely.
Sharing that work with someone else is a question of trust: do you trust the other side, do you trust the network, do you trust us? Instead of answering for you, FlowPad gives you a dial. Each level up trades a little more trust for more speed and convenience. The dial only moves when you move it.
Three ways your data can travel.
fig. 1.0 · the trust dialYou choose the level. The first two never route through our cloud at all.
Files. Fully offline.
Every FlowPad message is a file you can download, carry, and upload on the other side. Two FlowPads can collaborate with no network at all. Built for finance, insurance, healthcare, and defense teams whose machines never touch the public internet.
▸ Nothing leaves your machine unless you physically move it.
Your git. Your infrastructure.
Collaboration syncs through a git repository you already trust: GitHub, or any git server you run. One side pushes, the other pulls. You can lock your firewall down to git traffic only.
▸ FlowPad’s cloud is never in the data path.
FlowPad cloud. As far as you choose.
Two modes. Metadata-only: our cloud relays a notification that an update is waiting in your git, without ever seeing the content. Full messages: bodies pass through our cloud so you get real-time collaboration and your inbox on your phone. You turn that on when you want the mobility.
▸ Even at full trust, our job is simply moving your messages.
note: speed of collaboration runs opposite to trust required. That trade-off is yours to make, not ours.
What our cloud can see, level by level.
| Transport | Your content | Metadata |
|---|---|---|
| Files / offline | Never | Never |
| Your git | Never | Never |
| Cloud, metadata mode | Never | Relayed, so peers know to pull |
| Cloud, full messages (opt-in) | Held securely for delivery & mobile | Relayed |
SOC 2 certified
Security and privacy controls audited by an independent third party, down to an audit trail on every code change.
GDPR compliant
Personal data is handled in line with GDPR. Your data-subject rights, plus CCPA and Israeli privacy law, are detailed in our privacy policy.
Open source
The code that handles your data is on GitHub, inspectable end to end. You don’t have to take our word for any of this.
Plain answers to the questions we actually get.
I work under NDA. Can I use FlowPad?
Yes. This page exists because a customer asked exactly that. Keep client work on the file or git layers and no content ever reaches our infrastructure. Your confidentiality posture stays whatever your client requires.
Can anyone at FlowPad read my data?
On the file and git layers there is nothing on our side to read. In metadata mode our cloud sees only that an update exists, not what it says. With full messages enabled, content passes through our cloud for delivery, and transferring your messages is the whole job.
Can FlowPad work with no internet at all?
Yes. Collaboration packets are built for offline use. Every message is a file you can move by hand, so two FlowPads can exchange work even with no network between them.
Start local. Turn the dial when you’re ready.
FlowPad is free, open source, and local-first. Everything runs on your machine from day one. Each step toward the cloud is a choice you make later, on your terms.