We are updating our privacy policy
how we use your data to improve your experience
Your stack runs on other people's servers. Each one has its own policy, its own breach history and its own future owner.
We are updating our privacy policy
how we use your data to improve your experience
Updates to our privacy statement
and to the data processing addendum
We noticed a new login to your account
if this was not you, secure your account now
We have been acquired
your workspace moves to the new owner
Your AI is now connected to your computer
It can read and write your files and run commands on your behalf.
Their words, about your work. And now their AI, on your machine.
Notes in one tool. Numbers in another. Documents somewhere else. Files moving between them.
Each one is a company with a policy that can change, a breach history you did not read, and an owner who can be replaced.
Then you connect them, because scattered work is unusable. The integration layer holds the keys to every account it joins. One more silo, holding more than any tool it connects, and the one people forget to count.
The risk is not one bad vendor. It is that your work sits in places you cannot inspect, under terms you did not write.
You already trust three things with your life. Local software asks for nothing more.
You trust it with your bank. The app runs here, keeps working offline, and is the layer between the AI and your machine: a Guardian reaches the folder you connected and nothing else, and it cannot run commands.
You trust it with everything you have written. The files land here, in a folder, readable by anything, with or without us.
You trust it with your photographs. One click and it holds the copy of your work, on your account, following you to the next device.
Type it once in a sheet. It reads into the report and onto the page without being copied or retyped. Your data becomes connected, and it stays under your fingers.
What reaches Donezo is your email, your plan and your licence. We cannot leak what we never hold.
Every important file travels the same way. You make a copy. It sits on your computer, then in your cloud, then in a mail server neither of you controls, then on their side, wherever that is. Four places at once, and every one of them can leak.
A sealed file takes the same trip locked. In every one of those four places it is unreadable. Only the person you meant can open it.
Docs, Grid, Make or Can. A document, a sheet, a tool, a piece of code.
Sealing is a Donezo Connected feature. The original stays untouched; you get a locked copy.
Four plain words the app generates, or the vault key of the person you are sending to.
Any channel you like. A four-word file opens in Donezo with no account and no plan.
For healthcare, government, or a client's security review: the mechanism above is the answer, not a promise. A password on a spreadsheet is a formality. This is the encryption used to protect data in transit and at rest across the industry, applied by you, to a copy you control.
Saved to your device. Connect a folder and what you make in Donezo starts saving to it, as ordinary files you can open with anything. If something did not make it to the folder, it is still in your browser's own database, and you can export it at any time.
One click, or your own way. Connect your drive and your work mirrors there and follows you to another device. Or export the vault and keep it wherever you keep important things. The tradeoff is honest: your own backup does not sync. You make it when you decide.
Build on your own work. A tool you build on your vault reaches the same apps and the same backup. It starts with the architecture already under it. See the four apps.
In testing mirroring to your own serverpublishing to your own domainreal-time syncSpace, for teams
Export your files wherever you can, as they are or as JSON. Bring them into Donezo, put them in the right workspace and project, and watch them connect on Donezo Connected. A number in a sheet becomes the number in the report and the number on the page, and all three answer to one file on your machine.
Then bring your agents with you, into one place you control: your key, your folder, a memory you can read.
Where next