Encrypted on your device.
Private content is protected before it reaches our storage systems.
Privacy & trustYour reflections.
Your reflections.
Protected end to end.
Your private writing and encrypted map content are end-to-end encrypted for storage and sync. AI features process relevant readable text separately, after your agreement.
How end-to-end encryption worksYour key opens it.
Your unlocked devices can read the saved content. Our storage systems cannot.
Clear AI boundaries.
We explain when readable text is sent for AI processing and how consent works.
What end-to-end encryption means.
The private content you save is made unreadable on your device before it is sent to storage. When you open it on an authorised, unlocked device, your encryption key makes it readable again.
This means the systems that store and sync your encrypted history do not need to be able to read it. A copy of that stored data, on its own, does not provide the key needed to open it.
- 01 · YOUR DEVICE
Encrypted before it leaves.
Trueform encrypts your private content on your device, using your encryption key, before sending it to storage.
- 02 · STORAGE & SYNC
Stored as encrypted data.
Our storage and sync systems keep the encrypted copy, without a readable copy of the key needed to open it.
- 03 · YOUR UNLOCKED DEVICE
Readable when you unlock.
Your authorised device uses your key to open the saved content, so you can read and explore it again.
These protections describe Trueform’s current password-protected private accounts. Earlier beta accounts can have different key setups or older data formats; your Account settings and the full privacy notice explain those differences.
Technical details
Private content uses AES-256-GCM encryption. The account key is created and unlocked on your device. Account services can hold encrypted content and protected key material, without holding the readable key used to open your private history. Existing web and native account formats use their own supported unlock and recovery flows.
This describes storage and sync. Readable content on an unlocked device, a recovery-key export and a consented AI-processing request have their own boundaries, explained below.
What’s protected—and what the service still needs.
Your writing and its meaning.
Reflections and Glimmers, along with private text in your Constellation, Insights and Journey, are encrypted before storage. The full notice lists the protected fields and earlier-account conversion details.
What keeps the account working.
Sign-in and contact details, record identifiers, dates, structural links and some operational information remain readable to the service. Feedback you choose to send to support is also readable.
End-to-end encryption protects the private content described here. It does not make every account detail or every use of information invisible.
See the detailed information breakdownWhere AI fits.
AI needs readable text to offer guided replies and suggest connections. After your agreement, your unlocked app sends relevant writing and supporting context over HTTPS through Trueform’s server to OpenAI.
Encrypted history. Readable AI requests.
The text in an AI request is readable to the processing services while they handle it. That request is separate from the encrypted copy of your history held for storage and sync, and does not give those services your encryption key.
Your AI agreement covers reflection analysis, guided replies and reviews of earlier writing. Eligible daily reviews start when you open and unlock the app; others start when you request them. Once accepted, an Insights review can finish in the background. Its result is encrypted for your app to retrieve after unlock; temporary processing records have a short expiry explained in the privacy notice.
You can withdraw AI consent in Account. This stops future AI requests and pauses new reflections; existing history, export and deletion remain available. A request already underway may finish. Provider processing and retention are explained in the full privacy notice.
Your key—and keeping access to it.
For a password-protected private account, your password unlocks the encryption key on your device. This lets a supported new device open the same history without giving our storage services a readable key.
Keep a working password or trusted device, and save a recovery key where your account offers one. If you forget your password, verified email must be combined with a saved recovery key or a working remembered device to reopen your encrypted history. Your Account settings show the recovery options available to you.
If every usable password, device and recovery-key path is lost, Trueform cannot restore that encrypted history. Store a recovery key somewhere secure: someone with the key and encrypted content could read that content.
Encryption also cannot protect text already visible on an unlocked screen, or prevent malicious software on an unlocked device from reading it.
A record you can return to and control.
Your account provides controls for AI agreement, access, export and deletion. You can revisit original sources, question an interpretation and decide what fits your experience.
A readable export contains private information outside the app’s encryption, so keep it somewhere secure. Account deletion removes stored content from the active service; provider logs, backups and files you have downloaded have separate retention and deletion boundaries.
Read about export and deletionA straightforward waitlist.
Joining adds your email immediately, with your consent for access emails and occasional meaningful product updates. No verification step and no weekly newsletter. You can unsubscribe at any time.
Your waitlist address is service information, rather than end-to-end encrypted journal content. A campaign label is kept for this browser session to understand how people find the waitlist; it contains no writing or account information. Details are in the full privacy notice.
Questions deserve a clear answer.
Adam Humphrey operates Trueform in the UK. Contact support@mytrueform.app about your information or a privacy question. You do not need to send private writing, your password or your encryption key to ask for help.
Read the full privacy noticeTerms of use