Security

Your data is encrypted on your device before it reaches the cloud. Only your authorized devices can unlock it—not even Unifile can read it.

How Unifile protects your data

Unifile is built so that we cannot read what you store. Your notes, photos, videos, audio, files, places and links are encrypted on your device (your phone, or your browser if you use the web app) before they leave it. What reaches our servers is scrambled data that only your devices can open. This page explains how, in enough detail to be checked.

What is protected

Encrypted on your device before upload: the content of every item (note text, photos, videos, audio, documents, scans, places, links), its title and description, the optional secure fields of a note (such as passwords and card numbers), a note's attachments, and the small preview pictures. The search index kept on your phone is encrypted too. The web app keeps its search index in memory only, never in browser storage.

What we can still see

Encryption does not hide everything, and we tell you what remains: your account details (email and name); the type of each item (note, photo, ...) and the kind of file (for example PDF or JPEG); its size and dates; a photo's or video's dimensions and a video's or recording's length; how many files are attached to a note and their total size; your tag names; how many items you have, how much storage you use and which plan you have; and the technical data any online service sees, such as your IP address when you connect. If you allow usage statistics, Google Analytics also receives which screens are opened and technical details of your phone, never your content. We never see the words in your notes, the pictures in your photos, or the names of your items.

How the keys work

  • Each account has one master key, made on your phone from the device's secure random number generator. It is stored in your phone's secure storage (iOS Keychain, Android Keystore). It is never sent to us. The web app never creates a key: when you unlock it, a copy is held in the memory of that browser tab only, and is never written to browser storage.
  • Each item gets its own random key, which is wrapped (encrypted) by your master key. Because items do not share a key, one exposed key exposes one item.
  • Items are encrypted with AES-256-GCM, which also detects tampering. Each encrypted piece is bound to the item it belongs to, so the server cannot swap one item's data for another's.

Adding another device

You sign in on the new device, which shows a QR code. On a device you already trust, you scan it and confirm. The two devices agree a key directly (X25519 key agreement, HKDF-SHA256), and your master key travels encrypted under it. The QR code also carries a one-time secret that is shown only on that screen and never passes through our servers; it is mixed into the key that protects the transfer, so even someone who controls our servers cannot substitute their own key. Our server only relays the encrypted package; it cannot open it. The code must be scanned in person, and the trusted device checks that the request belongs to your account and asks you to confirm. The web app unlocks the same way: the browser shows the code, and your phone scans it. When you close the tab, or the web app locks itself after the period of inactivity you set, the key is forgotten.

Recovery

When you set up your account you can create a 12-word recovery phrase. It is generated on your phone and shown once. We never see it and keep no copy. The phrase is stretched with Argon2id (a memory-hard function designed to slow password guessing: 64 MiB, 3 passes) and the result encrypts a copy of your master key, so you can restore your data on a new phone, or unlock the web app, with the phrase. If you lose every device and the phrase, nobody, including us, can recover your data. That is the price of not holding your keys.

On your phone

Search works offline from a small database on your phone. It is encrypted with SQLCipher (AES-256) under a random key held in your phone's secure storage; the database file lives in the app's cache area, outside app backups, is rebuilt if it is missing, and is deleted when you sign out. Temporary files made when you view or share an item are cleaned up automatically (and again at launch and sign-out). Your connection to our services uses TLS. We never put an access credential for our file storage in the app.

In your browser

The web app runs only on https://app.unifile.ca with a strict content security policy: it loads no advertising or third-party scripts, apart from the Google or Apple sign-in script, which loads only when you press that button. Decryption happens in your browser. Titles and search text are held in memory and discarded on lock or sign-out. Files are fetched without caching, shown from memory and not kept; a download is yours to protect. The web app may use Cloudflare and Google Web Analytics, which measures page loads and basic technical details, never your content.

The standards we use

PurposeStandard
Encrypting items, keys and recordsAES-256-GCM (NIST SP 800-38D)
Agreeing a key between devicesX25519 (RFC 7748)
Deriving keysHKDF with SHA-256 (RFC 5869)
Protecting the recovery keyArgon2id (RFC 9106), 12 words from the BIP-39 list
Local search databaseSQLCipher (AES-256)
NetworkTLS

We use published, widely reviewed algorithms and well-known open-source implementations. We did not invent any cryptography; what is ours is how the pieces are combined, which is why we publish it.

What encryption cannot do

  • It cannot protect a phone that is unlocked in someone else's hands, or malware on your phone.
  • Anything you copy, export or share from Unifile (a copied password, a shared photo) leaves protection and is yours to handle.
  • Someone who has both your account password and your recovery phrase can read your data. Keep the phrase offline and private.
  • Encryption protects what your items say, not that they are current. Someone who can change your account's records (for example with a stolen sign-in session) can delete an item or put back an older version of it. We detect forged or altered content, not a restored older copy.
  • Replacing your recovery phrase is for a lost or forgotten phrase. It does not change your master key, so if an old phrase and a copy of an old recovery record were both exposed, the old phrase could still unlock it. Changing the master key itself is not available yet.
  • A browser is only as safe as the computer it runs on. Malware or a malicious browser extension on that computer, or a computer left unlocked in someone else's hands, can read what an unlocked tab shows. Lock the web app or close the tab when you leave, and do not tick "Remember me" on a shared computer.
  • Metadata listed above stays visible to us.

Last updated: November 13, 2026. Unifile is a product of COMMbits Inc.