Journal Encryption Metadata: What Can Still Be Seen?

Encryption can hide the words inside a journal entry without making the whole record invisible. Dates, sizes, identifiers, and other metadata may remain readable because the service needs them to store, order, or deliver the page.

Content and metadata answer different questions

Content is what you deliberately write or attach: the title, body, photograph, link, or file. Metadata describes the record around it: when it was created, which account owns it, how large a file is, or whether the page is private or public.

Encrypting content can keep the story unreadable. Metadata may still show that a record exists and how the product should handle it.

Common metadata that may remain visible

• Account, journal, and record identifiers.
• Creation and update timestamps.
• Protection and publication state.
• Attachment filenames, content types, and file sizes.
• Reminder dates or delivery details.
• Tags or titles used for server-side organization.

The exact list depends on the architecture. Ask the service to name it. The broader guide to whether a journaling app can read your entries gives a seven-question framework.

Why some fields stay outside encryption

A server needs a timestamp to order pages without opening their content. It may need a file size to enforce upload limits or a reminder date to send a message later. Search and filtering can also depend on a readable title, tag, or index unless that work happens locally.

These trade-offs are not automatically bad. The risk comes from hiding them behind a broad “everything is encrypted” claim. For the implementation-level boundary, read the Inpages.me end-to-end encryption threat model.

The current Inpages.me boundary

For an Inpages.me Memory using Encrypted writing & files, the title, content, links, keepsakes, and inline-image bytes are encrypted in the browser. Hashtags, record IDs, timestamps, filenames, and file sizes remain metadata outside that promise.

Daily Check-ins use a separate boundary. The note, location, people, and new photographs can be encrypted; mood and emotion remain readable in both modes. Learn why these distinctions matter in the guide to encrypted journal search.

Write sensitive detail in the protected field

If a tag remains readable, use “travel” instead of a private diagnosis, dispute, or person’s full name. If filenames remain visible, rename a file before upload when its original name reveals more than necessary.

Metadata awareness should not make journaling anxious. It simply helps you put each detail in the field whose protection you understand. Use the full digital journal privacy checklist when reviewing your setup.