Where Your Data Actually Goes
I built Insights to hold the most sensitive data I have: what I eat, where I go, how I sleep, what I write in my journal. So I want to explain — plainly, and specifically — where that data goes when you use it. Not the reassuring version. The actual version.
The honest architecture
Insights is a synced service, not a local-only app. Your entries live on your device and in your account on our servers (hosted on Google Cloud), so your phone and the web portal see the same history. Data is encrypted in transit. It is not end-to-end encrypted — our systems can read it, because that’s what makes sync, AI analysis, and the web portal work.
I say this first because most privacy pages won’t. If you need a tool where the provider cannot technically read your data, Insights today is not that tool, and I’d rather tell you than imply otherwise.
Here’s what I can promise instead, and back up.
No one is buying your data, because no one can
There are no ads in Insights, no advertising SDKs, and no third-party analytics trackers in the app. We do not sell personal data — to brokers, to advertisers, to anyone. The business model is the subscription. You pay for the product; you are not the product.
Data leaves our systems only to power features you actively use, and every processor is named in the privacy policy: when you photograph a meal, the image goes to an AI provider for analysis; when you record a journal entry, the audio goes to a transcription service; when you pay, Stripe or the app stores handle it. Nothing is shared for any purpose other than delivering the feature you just invoked.
Deletion is a button, not a support ticket
Account deletion is in the app: Settings → Danger Zone → Delete Account. It removes your account-linked data from our active systems and triggers cleanup requests to the external processors. We keep only the minimal non-personal records the law requires (tax and accounting). You don’t have to email anyone, explain yourself, or wait for a human to get around to it.
Retention is pricing, and I’ll say so
Different plans keep different history windows — 30 days on Free, a year on Standard, three years on Premium. I want to be straight about what that is: it’s pricing, not privacy. Deep history is what makes Insights useful, and it’s part of what you pay for. The full breakdown is on the data retention page rather than buried in fine print.
Check my work
Everything above is stated as fact, not aspiration, and it’s all in the privacy policy in specifics — every data category we hold, every processor we use, every legal basis. If you find a gap between what this post claims and what the product does, I want to know: privacy@jwbsystems.com.
A privacy promise you can’t verify is just marketing. This one is written so you can check it.