Camera-first transformation record
Best fit when meals, workouts, body check-ins, and progress photos are the primary artifacts and a browser-local default is appealing.
A private journal app should make four things clear: where the first copy lives, who can decrypt a cloud copy, what a full export includes, and how access is protected. This source-linked comparison puts jurn.ee, Day One, Apple Journal, Journey, and Diarium side by side so you can choose for your actual threat model.
A photo progress journal is one focused use for a visual record.
Short answer: A private visual journal keeps photos with the date, context, and small corrections that make them useful later. A photo progress journal adds a repeatable way to compare moments over time—same angle, light, or activity—without treating a photo as a diagnosis.
jurn.ee is built for that narrow job: normal meal, workout, body, and progress entries start on the current device in the browser. There is no public feed. Optional Plus encrypted backup is a separate choice, so the comparison below can be read alongside the product’s current privacy boundaries.
Save five entries, add the context you will want later, export them with photos, and check the access and recovery path before committing years of records.
For the photo side, see the body progress photo app page for match shots and the repeatable progress-photo protocol for setup. Read the visual journal privacy guide for storage, access, backup, export, and deletion questions, or use the one-photo visual journal template if you prefer a lightweight alternative.
jurn.ee publishes this page and is one of the products in it. That conflict is explicit.
We selected general-purpose journal apps with strong photo support or a clear privacy/storage position. Claims come from first-party product, support, security, or privacy pages linked below. We omit fast-changing price comparisons and do not award an overall winner.
App makers and readers can send a direct source for a changed claim to the resource editor. Material corrections will update the review date.
Read across one row. A feature count hides the differences that matter.
| App | First / local copy | Optional cloud copy | Photos and media | Documented export | Access and platforms |
|---|---|---|---|---|---|
| jurn.ee publisher of this page | The journal starts on the current device in the browser. | Plus offers an optional encrypted backup. Journal content is encrypted before upload, and only the user has the recovery key. | Photo-first entries for meals, workouts, and body/progress moments. | Plus offers a downloadable backup that includes journal photos and stops if a photo cannot be included. | Installable web app. No journal-specific lock; access relies on device and browser controls. |
| Day One | Day One says entries are stored on the device and that account-free use can remain local. | New journals use end-to-end encrypted sync by default. Older journals may use Day One’s earlier encryption system; its documentation explains how recovery-key storage works. | Photos plus video and audio features, with plan-specific limits possible. | Day One documents multiple export options regardless of subscription status. | iPhone, Android, iPad, Mac, Apple Watch, and web; passcode and biometric safeguards documented. |
| Apple Journal | Native Apple app; Journal can be included in an encrypted local device backup. | Journal has an iCloud sync setting. Apple says entries are encrypted in transit and while stored in iCloud; the reviewed page does not label Journal sync end-to-end encrypted. | Photos, video, audio, places, and other entry context. | ZIP export includes photos, locations, and other media; entries can also be printed or saved as PDF. | iPhone, iPad, and Mac on supported software; Face ID, Touch ID, or passcode lock. |
| Journey | Journey describes a cross-platform journal with cloud sync and self-hosting options. | Journey Cloud Sync offers an end-to-end encryption option protected by a user passphrase. | Photo, video, and audio attachments. | Microsoft Word, ePub, and print-to-PDF exports are documented. | Android, iOS, Mac, Windows, Linux, web, and email; passcode/biometric options vary by platform. |
| Diarium | No account is required; entries can remain on the device. | Optional sync uses the user’s OneDrive, Google Drive, Dropbox, iCloud, or WebDAV. The reviewed product page does not claim journal-level end-to-end encryption. | Photos and other contextual integrations. | Word, plain text, web page, or JSON. | Windows, Android, iPhone, iPad, and Mac; password, PIN, or biometric protection. |
Best fit when meals, workouts, body check-ins, and progress photos are the primary artifacts and a browser-local default is appealing.
Best fit when rich media, mature native apps, broad device coverage, and encrypted sync for new journals matter more than a fitness-specific capture flow.
Best fit for people already centered on supported Apple devices who want system suggestions, media-rich entries, and Apple-native access controls.
Best fit when Windows, Linux, Android, Apple platforms, and web access need to coexist, with optional encryption and self-hosting choices.
Best fit when no app account and sync through a personal cloud provider are more important than a vendor-claimed journal-level E2EE design.
Add photos, export the journal, open the result outside the app, lock and unlock the journal, and test recovery on a second device before committing years of records.
Short answers for choosing a private journal around actual access and recovery needs.
A private visual journal keeps photos with their date, context, and small corrections. A photo progress journal uses repeatable photos to compare moments over time without treating a photo as a diagnosis.
Normal meal, workout, body, and progress entries start on the current device in the browser. jurn.ee does not receive the photo or note when a normal entry is saved. Optional meal scanning, selected sharing, and Plus encrypted backup are separate flows with their own disclosures.
No. jurn.ee’s normal web journal is local-first; Plus encrypted backup is optional. Local-first describes where the normal entry starts, not an unconditional promise that every feature works without a network connection.
Yes. Use repeatable framing, notes, and explicit measurements as context. Photos are evidence of the moment, not a reliable source of body fat, weight, health status, or diagnosis.