How it works
How a file is stored, encryption and what the site sees.
Data
Files are encrypted on your device. An encrypted file is split into 14 pieces, and each piece is kept on a different user's device. Any 8 of the 14 pieces are enough to read the file. A file can only be lost if 7 pieces vanish at once, and the system rebuilds missing pieces by itself.
What the site sees
- Your email and the binding of nodes to your account.
- Public keys of nodes and devices.
- Device reports: version, space, time online, check results. No file names or sizes.
- The site cannot read files or take a copy: it has no encryption keys.
What the site cannot do
The app calls the site; there are no inbound connections. Site commands are a closed list; the site cannot control your device. Anything that reduces data or contribution is confirmed on the app page. If the site is down, writing and reading keep working; only new devices cannot join and emails stop.
Updates
Updates are signed with a separate key and installed inside the app. It does not ask for control of your device. Updates roll out in waves: 5%, 25%, 100%; if a check fails, the previous version returns.