Your journal should be readable to you, not everyone running the server.

Encryption should be explained plainly

People should not need a security degree to understand what happens to their journal. In PYD, your account sign-in identifies you, but your journal password protects the private journal key that unlocks your writing.

When journal content is saved, the title, body text, and tags are encrypted in the browser before they are written to cloud storage. The cloud stores encrypted payloads for sync, not readable journal prose.

What PYD encrypts

PYD encrypts the parts of the journal that reveal what you wrote: journal titles, entry text, and tags. This matters because tags can be personal too. A tag like "therapy", "grief", "work stress", or "family" can say a lot even before anyone reads the entry.

What PYD still needs to store

Private journaling still needs normal product data. PYD stores account identity, subscription information, sync account IDs, timestamps, and other operational data needed for login, billing checks, and journal sync. Good privacy language should say this clearly instead of pretending every byte is invisible.

Why the journal password matters

If a product cannot read your journal, it also cannot magically recover private journal content without the secret that unlocks it. PYD supports a recovery key flow for the journal key, but users should treat journal passwords and recovery keys seriously.

Private, useful, and affordable

Encryption is not the whole product. A private journal still needs to feel good enough to use every day. PYD combines encrypted journal sync with search, tags, autosave, mobile writing, web reading, and a pricing direction built to stay accessible.