Per-account encryption
Each account will have its own encryption boundary, instead of the service holding what unlocks all stored content.
Your data
Who owns it, who could read it today, and what we are building next — in plain words.
Everything you put in, and everything the workers make for you, is yours. We do not own it and we do not sell it.
One machine serves the product and holds the record. Verified copies sit on our other machines.
Today, we hold what unlocks stored content on our machines. That means the people who run the service could read it.
Every account made by sign-up or invite is private. The product walls one account off from another, and the operator's own sign-in stops at those private accounts. Those walls limit what the product lets us open; they do not change the fact that we hold what unlocks the stored content.
These are planned, with no date. We would rather say where they stand than turn a plan into a promise.
Each account will have its own encryption boundary, instead of the service holding what unlocks all stored content.
A way to run Productivity Sweet locally, so the work can stay on your own computer.