Dash LogoDash Notes
Guide

What AES-256 Encryption Actually Does

Every notes app says “encrypted”. Here is what the word covers, what it does not, and precisely how a note is encrypted in Dash.

Updated September 2026 · Dash team

“Encrypted” is doing a lot of work in most product pages. It can mean the connection to a server is encrypted, that the server’s disk is encrypted, or that the content itself is encrypted with a key only you hold. Those are three very different promises, and only the last one keeps a company from reading your notes.

This guide explains the pieces, then shows exactly what happens when you lock a note in Dash.

AES-256-GCM, piece by piece

AES is a block cipher: it turns a fixed-size chunk of data into ciphertext using a key, and back again. It has been the standard since 2001 and is implemented in hardware on every modern processor, which is why encrypting a note is instant.

256 is the key size in bits. The number of possible keys is 2 to the power of 256, which is a number with 78 digits. Brute force is not a threat model; it is a thought experiment.

GCM, Galois/Counter Mode, is how the cipher is applied to data longer than one block. It also produces an authentication tag. If a single byte of the ciphertext changes, decryption fails loudly rather than returning garbage. That protects you from a whole class of tampering attacks.

Why your password is not the key

Keys are 256 random bits. Passwords are short, memorable and drawn from a much smaller space. Handing a password straight to a cipher would throw away most of its strength, so a key derivation function stands in between.

Dash uses PBKDF2-SHA256 with 600,000 iterations and a unique random salt for every note. The iterations make each attempt slow: an attacker testing a million candidate passwords pays that cost a million times. The salt means a precomputed table cannot be reused across notes, or across users.

What happens when you lock a note

  1. A salt is generated from the platform’s cryptographically secure random number generator, unique to that note.
  2. Your password is stretched through PBKDF2-SHA256 at 600,000 iterations with that salt, producing a 256-bit key.
  3. The note is encrypted with AES-256-GCM under that key, producing ciphertext and an authentication tag.
  4. Only the ciphertext, salt and tag are written to disk. The password and the derived key are never stored and never transmitted.
  5. To open it, Dash repeats the derivation with your password and the stored salt. Wrong password, wrong key, failed authentication, no plaintext.

Touch ID and Face ID do not replace this. They release the stored secret from the platform’s secure enclave so the same derivation can run, which is why biometrics are a convenience layer over real encryption rather than a substitute for it.

What encryption does not protect against

  • A weak password. Six characters stretched 600,000 times is still six characters.
  • A compromised device. Malware that reads your screen or keyboard sees the plaintext you see.
  • An unlocked note. While it is open, it is open.
  • Metadata. A locked note still has a title, a size and timestamps. Do not put the secret in the title.
  • Coercion. Encryption does not resist someone who can compel a password. That is what the duress password is for.

Do not trust this page

Everything above is a claim on a vendor’s website, which is worth very little on its own. Dash is open source under the MIT licence, so the encryption code is on GitHub and can be read by you or anyone you trust. For a security claim, that is the difference between evidence and marketing.

Frequently asked questions

Encryption you can read the source of.

$14.99 once on Mac. Free on iPhone.

Download Dash Notes