Nine questions to ask a journal app before you trust it with your days
A diary is the most personal file you will ever make. Here is what to check before you put years of your life into somebody else's product, and what the answers mean.
A diary is an unusual thing to hand over. Most of what you put into software is either dull or already shared with somebody — your email has another person on the end of it, your photos were taken in public, your bank already knows. A diary has no second party at all. It is the one file where the honest version lives.
So it is reasonable to be careful about where you keep it, and it is reasonable to want something better than a reassuring sentence on a landing page. Below are the questions actually worth asking, what a good answer looks like, and what it means when you cannot find one.
This applies to us too. Where it is useful, our own answers are at the end.
1. Can anyone at the company read my entries?
Start here, because it is the question people mean when they ask whether something is private.
Almost always the honest answer is that someone could, technically, because the data sits in a database that engineers maintain. What varies is whether anything prevents it as a matter of routine: access controls, audit logs, a rule that support cannot open an account's content, encryption that the company itself cannot undo.
A good answer is specific about the mechanism. A bad answer is the word "secure", which means nothing, or a promise about intent rather than capability.
2. Where does the audio live, if I record?
Spoken diaries have two artefacts, and people forget about the first. The transcript may be handled carefully while the original recording sits in a storage bucket that is open to anyone with the link.
Ask whether recordings are in private storage, whether a URL to one works for somebody who is not signed in, and how long they are kept. A file that is only "unlisted" is a file that is public to anyone who guesses it.
3. Is my content used to train models?
This is the one that has changed most in the last few years, and the one most worth reading the actual terms about rather than the marketing page.
What you want is a plain statement that your entries are not used to train anything, with no carve-out for "anonymised" or "aggregated" content. A diary cannot be meaningfully anonymised — it is full of names, places and the specific shape of one life.
Note that a product can send your text to a model in order to do something for you, right now, without that text being used to train anything. Those are different, and a straight answer distinguishes them.
4. What is written to the logs?
An unglamorous question with real consequences. Applications log things when they go wrong, and if an entry's text is in the log line, then your diary is also in a log aggregation service, with a different and usually much weaker set of controls around it, often for months.
The answer you want is that content never reaches the logs — only identifiers, timings and errors. Very few companies will have thought about this, which is itself informative.
5. Can I get everything out?
Export is the question that decides whether you own your diary or are renting access to it. You are making something intended to last decades, and no product is going to last decades.
Check that you can export the full text, with dates, in a format that will open in anything — plain text, Markdown, JSON — and the original audio as files. "Print to PDF" is not an export. An export that requires emailing support is a half-answer.
6. What happens if the company shuts down?
Related, and worth a moment's thought rather than a shrug. A small product may not be here in five years. That is survivable if you can export and if your entries are not in a format that only makes sense inside the app. It is not survivable if everything is locked in a proprietary store and the shutdown notice gives you thirty days.
The practical defence is to export once a year and keep it somewhere of your own. Do this even with a product you trust completely.
7. What exactly is free, and what happens to what I have made if I stop paying?
Pricing is a privacy question in disguise, because it determines what pressure a product is under. Something free with no plausible way of making money is a product that will eventually look for one, and the asset it is sitting on is your diary.
The specific thing to check is what happens at the end of a trial or a subscription. Does the diary become read-only? Does it lock entirely? Are old entries deleted after some period? A product that holds your entries hostage has told you something about how it sees them.
8. Can I delete something, and is it actually gone?
Both halves matter. You should be able to delete a single entry and the whole account, and the deletion should reach the audio as well as the text. Ask how long backups hold a deleted entry — thirty days is normal and fine, indefinitely is not.
9. Does the company make claims it has no business making?
This one is about judgement rather than infrastructure, and it is a surprisingly good signal.
Journalling products have a persistent habit of drifting into territory they are not qualified for: promising that writing things down will treat a condition, offering what amounts to a diagnosis from a few paragraphs of text, dressing up word counts as clinical findings. A diary is a record of your days. Software that reads one can count what came up and show you patterns in your own words; it cannot assess you, and anything built on the premise that it can has already decided to say whatever converts.
If a product is loose about that, it is likely to be loose about the rest. Carefulness is not usually a thing people apply in one place only.
Our answers
Afterthoughts is a voice diary: you talk for as long as you like, it writes the night out, notes who and what came up, and keeps it on a timeline you can search. In the same order as above:
Recordings live in a private bucket, reachable only through a signed request made for your own account. Every table has row-level security, so one account cannot read another's rows — not as a policy but as a database rule. Transcripts are never written to our logs. Nothing you record is used to train any model. Entries are sent to a model to be written out and tagged, at the moment you record them, and that is all.
Two of the answers we do not like yet, and would rather say than leave you to discover: there is no one-click export, and no button that deletes a single night. Both are being built. Until they exist, that is a real gap, and by the standard set out above it counts against us — a diary you cannot take out is a diary you do not fully hold.
Recording, transcripts, the timeline, search, letters to future you, chapters and the Monday note are free, permanently, because a diary you cannot record into is not a diary. Two sections are paid at $4 a month or $36 a year — Ask, which answers a question about your own nights and shows you which ones it drew from, and Insights, which counts what came up over a week or a month. If you stop paying, those two close and everything else keeps working exactly as before. Nothing is deleted and nothing becomes read-only.
And on the last question: Insights tells you what you mentioned and how often. It does not tell you what is wrong with you, because it does not know, and neither does any other product that counts the words in a diary.
The short version
If you only ask three, ask these: is my content used for training, can I export everything including the audio, and what happens to my entries if I stop paying. The answers take two minutes to find in a product that has thought about it, and are conspicuously absent from one that has not.