Three choices stop someone else reading a digital journal, and the order matters: pick an app whose provider cannot read the entries (end-to-end encryption), lock the account with a password-manager password and an authenticator app, and lock the device and the app itself so an unlocked phone in someone else’s hand does not open the journal. Everything after that (encrypting files before they sync, backups, emergency access, a quarterly check) protects against losing the journal; only the first three stop someone reading it. A few common measures are theatre, and they are named below.
Quick Answer: In order: choose an end-to-end encrypted app (Apple Journal, Day One with encryption on, Standard Notes, or Obsidian with Sync), lock the account with a unique password from a password manager plus an authenticator-app second factor, turn on device encryption and the app’s own lock, encrypt anything you sync through a general cloud folder, keep two encrypted backups with one off the device, write an emergency-access note, and check it all once a quarter.
Definition: Digital journal privacy is the set of app choices, account controls, device settings and habits that keep an electronic journal readable only by its owner and the people the owner names.
Key Evidence: Apple lists Journal data as end-to-end encrypted in iCloud under both standard and Advanced Data Protection. Day One’s encryption FAQ states that if the key is lost the encrypted journal cannot be decrypted and Day One never has the private key. NIST SP 800-63B says verifiers should not require passwords to be changed periodically, only after evidence of compromise.
Context: End-to-end encryption protects against the provider and against a breach of its servers. It does not protect against someone who knows your passcode, a shared device with no separate accounts, or a court order served on you.
Key Takeaways
- Step 1 decides who can read the journal: Apple Journal, Day One with encryption on, Standard Notes or Obsidian Sync.
- Do not rotate the password on a schedule. Change it only when Have I Been Pwned shows a breach, per NIST SP 800-63B.
- Use an authenticator app as the second factor. SMS codes follow the phone number, and numbers get ported.
- Lock the app as well as the device: Settings > Apps > Journal > Lock Journal on iPhone.
- Two backups, both encrypted, one off the device. Exports are plain text until you put them in a container.
- Write the emergency-access paragraph today. End-to-end apps have no recovery.
Ten minutes first: decide what you are protecting against
Answer three questions first; each points to the step that matters for you.
- Who could plausibly pick up my unlocked phone or laptop? If anyone, the device and app locks (step 3) are your real defence.
- Would I be harmed if the provider, or someone who breached the provider, read this? If yes, only an end-to-end encrypted app (step 1) or self-encrypted files (step 4) will do.
- Do I need this journal to survive me, or survive a lost password? If yes, emergency access (step 6) is mandatory, because the strongest apps have no recovery.
Step 1: Pick the app by who can read it
The single test is whether the provider holds a key to your entries. The table carries only the privacy columns; features and prices are compared in the secure journal app roundup.
| App | Can the provider read entries? | App-level lock | Export format | Metadata to watch |
|---|---|---|---|---|
| Apple Journal | No: Apple lists Journal data as end-to-end encrypted in iCloud | Yes: Settings > Apps > Journal > Lock Journal (Face ID, Touch ID or passcode) | Print or export from the app | Journaling Suggestions draw on other on-device data; review the setting under Privacy & Security |
| Day One | No, for journals with end-to-end encryption on (default for new journals since version 4.2; older journals must be converted) | Yes: passcode with Face ID or Touch ID, locks the whole app | JSON, plain text, PDF; exports are not encrypted | JSON export carries location and weather per entry |
| Standard Notes | No: only you hold the keys to decrypt your data | Yes: passcode lock plus biometrics | Encrypted backup, or decrypted zip of plain text files | Minimal; notes are text |
| Obsidian | Local Markdown files on your device; if you use Obsidian Sync, the remote vault is end-to-end encrypted, but Obsidian does not encrypt the local vault | No built-in lock; rely on the device lock | The files themselves | Whatever plugins you install can read the vault |
| Google Docs, Dropbox, Evernote, Notes folders | Yes: the provider holds the keys | Varies | Varies | Treat as readable by the provider unless you encrypt first (step 4) |
One caveat from the apps’ own documentation. Day One’s key lives on your device and, by default, in iCloud under your Apple ID; turn that off and lose the key, and “encrypted journal stored in the Day One Sync cannot be decrypted” because “Day One does not have access to the private key at any point.” Obsidian says the same: “We’re not able to recover your password, or any encrypted data for you.” That is the price of a provider that cannot read your journal, and it is why step 6 exists.
Step 2: Lock the account
Password. Let a password manager generate and store it, so it is long and used nowhere else. NIST SP 800-63B says verifiers “SHOULD NOT require memorized secrets to be changed arbitrarily (e.g., periodically)” but “SHALL force a change if there is evidence of compromise.” So change it only if it shows up in a breach, which you can check at Have I Been Pwned.
Second factor. Turn on two-factor authentication for the journal account and any cloud account that syncs it, with an authenticator app for the codes; NIST restricts the phone network (PSTN) as an out-of-band channel.
Step 3: Lock the device and the app
This is where most journals are actually read: an unlocked phone on the kitchen table.
- iPhone and iPad. Device encryption is on whenever a passcode is set. Lock the journal app itself: for Apple Journal, Settings > Apps > Journal > Lock Journal; for Day One, the in-app passcode with Face ID or Touch ID and a short “Require After” interval.
- Android. Set a screen lock, turn on the journal app’s own lock (Day One and Standard Notes both have one), and when handing the phone to someone, pin the screen to the app they need: Settings > Security > Advanced > App pinning on Pixel phones running Android 11 and later.
- Mac. Apple menu > System Settings > Privacy & Security > FileVault > Turn On, then choose whether iCloud or a recovery key can unlock it. Keep a separate user account on any shared Mac.
- Windows. Settings > Privacy & security > Device encryption on Windows Home; BitLocker on Pro, Enterprise and Education. The recovery key is attached to the Microsoft account you signed in with, so know which account that is. Keep a separate user account on a shared PC.
Step 4: Encrypt anything that syncs through a general cloud folder
If the journal lives in Google Drive, Dropbox or iCloud Drive as ordinary files, encrypt them on your device before they sync. Cryptomator creates an encrypted vault inside a cloud folder; VeraCrypt creates an encrypted container you mount as a drive. The provider then only ever stores ciphertext. Lose the vault password and nothing recovers it.
Step 5: Backups
Two copies, both encrypted, one off the device. A sync service is no backup, because a deletion syncs too. A Day One JSON export and a Standard Notes decrypted backup are plain text; put them inside an encrypted container before they go anywhere, and delete the unencrypted copy.
Step 6: Emergency access
Decide now who gets in when you cannot. Three documented mechanisms:
- Apple Legacy Contact. Settings > your name > Sign-In & Security > Legacy Contact. The contact needs the access key you generate plus your death certificate; they do not get iCloud Keychain passwords, so the journal app password must be handed over separately.
- Bitwarden Emergency Access (premium plans): a trusted contact requests access, waits out a period you set, then gets either view access to your vault or a full takeover.
- 1Password Emergency Kit: a PDF with your sign-in address, Secret Key and a space for the account password. 1Password suggests printing it and keeping it with your passport or with someone in your will.
Then write one paragraph and store it with the kit:
“If I am dead or unable to manage my accounts, [name] may read my journal. They may read all of it / only entries before [date] / only what is needed to settle my affairs. The journal is in [app]; the account password and the encryption key are in my [Bitwarden / 1Password] vault, and the emergency kit for that vault is in [place].”
The will line: “My digital records, including my journal, are to be handled by [name] as set out in the note stored with my [password manager] emergency kit.”
Step 7: Once a quarter
- Confirm automatic updates are on.
- Revoke any integration you no longer use.
- Check the account’s active sessions and sign out anything you do not recognise.
- Restore one entry from a backup, so you know the key still opens it.
- Confirm the emergency contact and where the kit is.
What is theatre
- An app-level password on an app that syncs plaintext. The provider and anyone who breaches it still read everything.
- Hiding entries in a file called “recipes”. Search finds it in seconds.
- A long password that you also use elsewhere. Length is irrelevant once it leaks from the other site.
- SMS two-factor on an account whose phone number can be ported. The code goes to whoever holds the number.
When this does not work
A shared family iPad. Apple’s Shared iPad exists only on managed devices with Managed Apple Accounts; a family tablet has no user accounts. You have the app lock and nothing else, so keep the journal on a phone that is yours alone.
A partner who knows your passcode. Apple Journal locks with the phone’s passcode; Day One’s PIN is separate. If the passcode is shared, change it, or accept that the journal is open to that person.
A court order. End-to-end encryption means the provider cannot hand over readable entries. An order served on you can still compel you to produce what you can decrypt; the EFF’s Surveillance Self-Defense guides cover that case.
A lost password on an end-to-end app. Standard Notes, Day One and Obsidian all document the same thing: no recovery. The emergency kit in step 6 is your own recovery mechanism, so write it today.
In The Art of Journaling, chapter 9, I say digital privacy risks can be substantially reduced with two-factor authentication, strong unique passwords and encryption, and I suggest looking for zero-knowledge encryption, where even the company cannot access your entries. This page is the settings-level version of that advice.
Why Digital Journal Privacy Matters
A journal is only useful if it is honest, and it is only honest if you are sure no one else will read it. Digital adds a second reason: the apps that keep the provider out do so by giving you the only key, and each says in its own documentation that a lost key is unrecoverable. Privacy and durability pull against each other, and the seven steps are the way to have both: the first four keep people out, the last three make sure you, and only the people you name, can get back in.
Related reading
- Best Secure Journal Apps
- How to Start Digital Journaling
- Journal Apps That Sync Across Devices
- Digital Versus Handwritten Journaling
Sources
- NIST SP 800-63B, Digital Identity Guidelines – no arbitrary periodic password changes, forced change on evidence of compromise, PSTN out-of-band authentication restricted
- Have I Been Pwned – breach lookup for passwords and email addresses
- Apple Support, Protect your journal entries on iPhone – the Settings > Apps > Journal > Lock Journal path and the Face ID, Touch ID or passcode options
- Apple Support, iCloud data security overview – Journal data listed as end-to-end encrypted under standard and Advanced Data Protection
- Day One, End-to-End Encryption FAQ – per-journal encryption on by default since version 4.2, key stored on device and optionally in iCloud, no recovery of a lost key, exports not encrypted
- Day One, Passcode and biometrics options for iOS – the in-app passcode, Face ID and Touch ID lock and the Require After interval
- Day One, Exporting entries – JSON, plain text and PDF export formats and the metadata the JSON export carries
- Standard Notes – end-to-end encryption; only the user holds the keys
- Standard Notes, How does Standard Notes encrypt data on my device? – passcode lock and biometrics
- Standard Notes, Creating and importing backups – encrypted backup versus decrypted zip of plain text files
- Standard Notes, I’ve forgotten my password – no password recovery on an end-to-end encrypted account
- Obsidian Help, Sync security and privacy – Sync is end-to-end encrypted, the local vault is not encrypted by Obsidian, lost passwords cannot be recovered
- Apple Support, Protect data on your Mac with FileVault – the System Settings > Privacy & Security > FileVault path
- Microsoft Support, Turn on device encryption – the Privacy & security > Device encryption path, BitLocker edition requirements, recovery key attached to the account
- Google Android Help, Pin and unpin screens – the app pinning setting on Pixel phones
- Apple Platform Deployment, Shared iPad overview – Shared iPad requires a device management service and Managed Apple Accounts
- Cryptomator – client-side encryption of cloud folders
- VeraCrypt – encrypted containers
- Apple Support, How to add a Legacy Contact – the settings path, the access key and death certificate requirement, and the Keychain exclusion
- Bitwarden Help, Emergency Access – premium requirement, grantor-set wait time, view or takeover access
- 1Password Support, Emergency Kit – contents of the kit and the advice to print it and share it with someone in your will
- EFF Surveillance Self-Defense – guidance on legal compulsion and device seizure