Skip to main content
Mauvely Cloud stores files it cannot read. Encryption happens in your browser before anything is uploaded, using keys that never reach the server in a form it could use. Open it at cloud.mauvely.com. There is nothing to install.

​
The four states

Being signed in and being able to read your files are different things, and Cloud shows both: The server cannot move you from locked to unlocked. It holds no key that could.

​
Getting around

A storage meter sits at the bottom of the sidebar.

​
What you can do

Set up your vault

Create your keys and save your 24-word recovery phrase. Do this first.

Upload files

Up to 5 GB per file, encrypted in chunks as they leave your browser.

Organise

Folders, renaming, moving, search, previews and the trash.

Version history

Keep and restore previous versions of a file, on Pro and Max.

Share

With a named person, or by link with a password, an expiry and a download cap.

Workspaces

A shared drive for a team, with its own storage and its own encrypted chat. Pro and Max.

Security

The key hierarchy, and exactly what the server can still see.

​
The trade you are making

Because Mauvely holds no key to your files, Mauvely cannot get you back into them. There is no administrative override and no password reset that recovers data — either would mean a key we hold, which would make the whole claim false. Two things open your vault: your password, and your 24-word recovery phrase. Either works, and neither reveals the other. Lose both and the files are unrecoverable, by construction.
Write your recovery phrase down and keep it somewhere you would still have it if your laptop were stolen. Cloud keeps prompting you until you have confirmed you saved it, because an unconfirmed phrase plus a forgotten password is permanently lost data.

​
Encryption in one paragraph

Your password is stretched into a key inside your browser and used to unwrap a master key. Every folder’s key is wrapped under its parent’s key, and every file’s content key under its folder’s — so handing someone a folder key gives them that folder and everything under it, and nothing above it. File contents are encrypted in 4 MiB chunks; names, MIME types, thumbnails and folder names are encrypted too. The full detail, including what is not protected →

​
Planned

Designed, but not built:
  • Shared team workspaces with members and roles. Today, sharing is per file or per folder with named people or by link.
  • Per-app syncing from Compose and Snap, so a course or a capture library backs itself up.
  • Native desktop and mobile clients. The web app is responsive, but a signed native binary is also a genuinely stronger security position than browser-delivered encryption.
  • rclone compatibility, which realistically means a local daemon holding your key rather than a plain S3 endpoint.
If a feature is not on the pages in this section, it is not there.