Is it safe to journal with AI?

Quick answer

Yes — if the product treats the page as a secret, not as fuel. On DiraX, entries are encrypted in the database. Keys are secret and rotated. Staff cannot browse your pages. We decrypt a page only while the product is doing the work you asked for: saving, showing, commenting, Insights, or chat. We take strict care with personal identifiers. We do not train public models on diaries. You do not need a laundry list of processors to decide; you need those facts, plus the right to export or delete. I am Gavin Fan. I would not ship a journal I would not write in myself.

Safety, for a diary, is not a vibe. It is a short list of promises you can hold us to. I wrote this as the founder of DiraX, not as a lawyer reciting vendors. The privacy policy is the legal document. This page is the human one: what is actually going on when you type a night you would never put on a feed.

What is the core of DiraX privacy?

Encryption in the database. Keys held as secrets and rotated. Staff who cannot browse your journal like a folder. Decrypt only while the product is doing the work you asked for. Strict PII care. No training of public models on diaries.

That is the core. I will keep repeating it because marketing pages love to hide it under a fog of brand names. You do not need a processor laundry list to decide whether a journal is safe enough to try. You need to know whether a human on my team can go sightseeing in your pages (they cannot), whether the stored copy sits encrypted (it does), whether we use your diary to teach a public model (we do not), and whether you can leave with a copy (you can, from Settings).

When the product needs the text — to save it, to show it back to you, to let a companion comment, to run Insights, to continue a chat — it decrypts for that job, then the stored copy stays locked. That is not a confession that “someone is always reading.” That is how a working journal exists at all. A page that could never be processed could never comment, track, or show a pattern. The rule is purpose: the work you asked for, not a standing human-readable archive for staff.

We also ask you to keep government IDs, home street addresses, bank details, and passwords off the page. The journal is for days and feelings. Strict PII care is a partnership. We engineer for it. You write like someone who wants a diary, not a copy of your wallet.

If you want a public, independent frame for thinking about privacy programs, the NIST Privacy Framework is a solid map. We are a small product, not a government program, but the instinct matches: know what you collect, limit why you use it, and treat sensitive text as sensitive.

What should you write, and what should you never type?

Write the night. Write the dinner you left too early. Write the name of the feeling, the topic that ate the week, the person who keeps appearing. That is what Insights is for — emotion, topics, people — and what companions reply to.

Do not type:

• government identification numbers

• a full home street address

• bank or card numbers, or passwords

• secrets that are not yours to put in any product

That list is not because we want a boring diary. It is because strict PII care means we do not want those strings in the system, even encrypted, if you can avoid it. A journal about a fight with your sister is the job. A journal that is a photocopy of your identity documents is not.

You can export your writing from Settings. You can delete the account there too. Leaving should not require a scavenger hunt. If you need a formal privacy request, the policy names how to reach us.

Age: 13+. This is not a toy for small children, and it is not a stealth social app for them either.

Does Free or Premium change our privacy promise?

No. Free and Premium change how much of the product you can use. They do not change the privacy promise: entries stay encrypted, keys stay secret and rotated, and people on the team cannot browse your pages.

FAQ

Can people at DiraX open my journal whenever they want?

No. Staff cannot browse pages. Entries sit encrypted in the database. Keys are secret and rotated. A page is decrypted only while the product is doing the work you asked for — saving, showing, commenting, Insights, or chat — not as a standing archive for humans on the team.

Do you train public models on my diary?

No. We do not train public models on diaries. We use the text to run DiraX: companions, Insights, chat, the features you turned on by writing. That is product work, not a public training corpus.

What if I want my words out of DiraX?

Export from Settings. Delete the account from Settings. For rights requests, use the contact path in the privacy policy. Your pages should travel with you, not stay behind as a souvenir for us.