Encrypted health data — with the AI explained

Start anonymously — no email, no name

This one gets over-complicated in most write-ups, so start here: Encryption is not one thing. In transit, at rest, and end-to-end are three different promises — and only one of them means the vendor can't read your entries. What the model actually receives, what it returns, and why the prompt is deliberately thin. The rest of this page is the detail behind that claim, plus how to verify it yourself.

Encrypted health data — with the AI explained

With the AI in the picture, encrypted health data comes down to prompt content. The brief needs cycle day, phase and recent tags to be useful. It does not need your name, and Avoria doesn't put one in the prompt — there isn't one to put. Avoria's AI prompt carries cycle context only — no identity fields — and responses aren't used to train third-party models.

How it actually works

Avoria stores your journal in an encrypted local store, then syncs a ciphertext blob to the cloud vault. The AES key is derived on-device; the server holds ciphertext and metadata it cannot decrypt. Restoring on a new device requires your Recovery Key, which never leaves the phone in plaintext. Avoria's cloud vault is encrypted with a key derived on your device from your Recovery Key.

Why it matters

TLS-only 'encryption in transit' means the vendor's database still holds readable rows — available to staff, to an attacker with credentials and to any lawful request. End-to-end changes what is possible, not just what is promised. Framed for with the AI explained, the practical consequence is that fewer parties end up holding a copy of a health record you never intended to publish, and the copies that do exist are harder to join back to you.

What Avoria does about it

Three concrete things. First, Local store encrypted at rest on the device. Second, Cloud vault holds ciphertext keyed to a device-derived secret. Third, Lose the Recovery Key and even Avoria cannot restore the vault — that's the point. None of that is gated behind an email address — the anonymous account is the full product, not a preview tier.

The AI part, without the hand-waving

Avoria's daily brief is generated by a language model that receives cycle context and nothing else: cycle day, phase, recent symptom tags and your stated goal. No name, no email, no device id enter the prompt, and responses aren't recycled into third-party training sets. The output is deliberately unexciting — an energy read, a focus window, a food angle and a movement suggestion — because a brief that shouts is a brief optimised for engagement rather than for you.

What you get besides privacy

Privacy on its own is a feature nobody opens an app for. Avoria pairs it with the working parts: a cycle calendar that models your own variance instead of a 28-day template, phase-aware nutrition and training guidance, symptom logging with 1–5 severity charted against cycle day, wearable sync scoped to the metrics the model actually uses, one-click imports from Flo and Clue, CSV and JSON export, and calm reminders you configure once. All of it available on an account with no identity attached.

Do this next

Generate one daily brief and read it critically. If it tells you something you couldn't have guessed from the calendar, the context is doing real work. Avoria is educational and is not medical advice. For diagnosis or treatment, please talk to a clinician.

Signals this applies to you

Look for three things this week: does the app ask for more data than it uses, does it explain why a prediction shifted, and does it treat a heavy day differently from a light one. Two 'no's mean you'll get more from a tool built around your phase, not a generic 28-day loop. On encrypted health data (with the AI explained) specifically, these signals show up faster than most people expect — usually inside two cycles, sometimes inside one. Write them down the moment you notice, because the memory of a rough day compresses fast and the log is the only honest record you'll have when you re-read the month at the end. If none of the signals apply and you're just curious, keep reading anyway — the plan below is a decent baseline for anyone tracking a cycle at all.

What the science actually says

The peer-reviewed picture is clearer than app marketing suggests: symptom clustering (mood + skin + sleep) has stronger predictive power than any single log, and the follicular-to-luteal shift in energy is now well-mapped in exercise-physiology literature. Apps that treat every day the same are ignoring twenty years of endocrinology. Avoria is built around the shift, not around 28 identical squares on a calendar. That's the reference frame Avoria's daily brief works from when it talks about encrypted health data (with the AI explained), and it's why the answer for with the ai explained rarely matches the answer for someone on a perfectly textbook 28-day loop. The corollary matters too: any advice that ignores your phase, your history and your logged variance is population-level advice being sold as personal advice. It might still be right for you, but you'll only know from your own two-cycle log — not from the marketing.

Your 7-day Avoria plan

Do this for seven days and re-evaluate: Day 7 — re-read the week's briefs together; the pattern will be obvious. Day 1 — log one mood + one energy score (1–5) at the time you already unlock your phone. Day 2 — export your last six months from your current app; keep the CSV somewhere you'll find it. Day 3 — read Avoria's daily brief once, in bed, no scrolling after. Day 4 — tag your workout with phase + energy; skip the heavy lift if energy is under 3. Day 5 — log skin, sleep and libido on the same screen; it takes under a minute. Day 6 — turn off every notification except the daily brief. By day seven you'll have enough signal to see whether Flo — or any tracker — actually helps with encrypted health data (with the AI explained), or whether it's just been logging around it. Nothing on this list takes more than five minutes. The point is not a heroic new routine; it's a small honest baseline you can compare against next month. Re-run the same seven days one cycle from now and the diff will tell you more than any single insight card ever could.

What not to do

Three things to skip: don't chase a perfect log — three fields a day beats twenty fields twice a week; don't compare your cycle to a friend's — variance is normal and the average is a mathematical fiction; and don't grant health-app permissions you don't use — every extra scope is another surface someone else can query. The temptation with encrypted health data (with the AI explained) is to add more tools; the fix is almost always fewer, better ones. A second app you check twice a week isn't a backup — it's a second surface leaking the same data, plus a second notification queue eating your attention. Uninstall the ones you don't open. Cycle tracking works when it disappears into your routine and shows up only when it's useful. Everything else is the app monetising your attention.

A quick self-check

A quick self-check before you commit to any tracker: does it show you the raw data, does it let you export the raw data, and does it explain — in one sentence — how a prediction shifted when it did? Three yeses means the tool respects you. One 'no' is a warning; two is a reason to move. Avoria answers yes to all three by design, and that's the standard worth applying to the rest of your health stack too — sleep, nutrition, activity. The specific answer for encrypted health data (with the AI explained) will land in your daily brief; the pattern for with the ai explained will emerge in the weekly recap. Don't optimise week one — just log honestly.

Avoria is not medical advice. For diagnosis or treatment, please talk to a clinician.