Fortly Consumer Health Data Privacy Policy

Effective date: October 5, 2026 ยท Last updated: October 2026

This policy explains how Fortly handles consumer health data, as Washington's My Health My Data Act, Nevada's consumer health data law and Connecticut's Data Privacy Act define it. Fortly is made by Wavista Apps, operated by William Tsao.

What we collect, and why

  • What you log, on your iPhone only. Your medication form and name, dose schedule, doses, dose labels and injection sites, weights and goal weight, activity level, protein and water goals, meals and meal photos, water, symptom check-ins and notes, and your weight from Apple Health if you turn it on. The app saves and processes these on your iPhone. They are never sent to us. Purpose: to show your logs, insights, reminders and the report you choose to make.
  • A meal photo and any note you add, only when you allow AI analysis and ask for an estimate. Purpose: to estimate the food in the photo. Our server holds them in memory during the estimate and does not store them. It keeps an encrypted copy of the estimate's answer (the foods and numbers, never the photo or note) for about 24 hours, so that if the connection drops, the app's retry gets the same answer without a second charge. Only the random key the app makes for that estimate can unlock it.
  • That you use Fortly, tied to an anonymous ID: your subscription status, and our server's request records under a scrambled form of that ID. Using a GLP-1 app could suggest that you take a GLP-1 medication. If the app offers a free estimate during setup and you take it, our server also keeps a count that it was used, under the scrambled ID, so it is given only once. That count has no end date, and Delete my data leaves it, because it holds only the scrambled ID and a number. Purpose: to provide your subscription, apply daily limits and measure how accurate estimates are.
  • Usage events, only if you turn on Share usage data: opening the app, the screens you see during setup and at the subscription offer, the steps of a purchase (started, cancelled, failed with an error code, or completed) and restores, and that you logged a meal, never what you logged. Purpose: to find problems and improve the app.

We do not use consumer health data for any other purpose. We do not use it, or any other personal data, to train large language models or other AI models.

Where it comes from

From you, from your use of the app, from Apple Health if you turn it on (this stays on your iPhone), from RevenueCat (your subscription status), and from Apple, through RevenueCat (which Apple Ads campaign and search keyword led to the install, only if you turn on Share usage data).

Who we share it with

We do not sell consumer health data, and we do not share it with anyone except these service providers, which process it only for us, under contract:

  • OpenAI: the meal photo and note, to make the estimate;
  • Fly.io and Supabase: our server and its database;
  • Cloudflare R2: encrypted backups of that database, which only we can read;
  • RevenueCat: your subscription. Only if you turn on Share usage data, and never for an account under 13 or treated as under 13, it also learns from Apple which Apple Ads campaign and search keyword led to the install. A keyword can name a medication (for example "semaglutide tracker"), which is why this waits for your choice. It is used only to measure our ads;
  • PostHog: usage events, only if you turn on Share usage data;
  • Sentry: crash reports, with the values you log removed;
  • Expo: app update checks, which show that an installation of Fortly asked for an update. They carry a random install ID that Expo creates and, if the app stopped with an error while starting, the text of that error. Apart from that text, they carry nothing you log.

No value you log (meals, doses, injection sites, weights, symptoms, notes or Apple Health data) ever reaches RevenueCat.

We have no affiliates. No third party collects your data across other apps or websites through Fortly.

Your rights

You can ask us to confirm whether we collect, share or sell your consumer health data, to get a copy of it with the list of everyone we shared it with and how to contact them, and to delete it. You can withdraw your consent at any time. You can review and change your logs in the app at any time.

  • To delete everything on your iPhone and withdraw your consent, use Settings, Delete my data. It also asks our server to delete what it holds, except today's usage count and, if you took one, a free setup estimate's count. Encrypted database backups made before then are deleted automatically within 35 days. It does not reach RevenueCat or Expo: email us to have RevenueCat's record deleted, including any Apple Ads attribution. Expo's update checks are tied only to Expo's own random install ID, which we never see, so we cannot find them.
  • To stop meal photos or usage events being sent, turn off Use AI analysis or Share usage data in Settings, Privacy.
  • For any other request, email support@wavistaapp.com from Contact support in the app, so the email includes the anonymous ID we need to find your data.

We reply within 30 days. If a request is complex and we need more time, we tell you within those 30 days and reply within 45 more days. Requests are free up to twice a year.

Appeals

If we turn down your request, you can appeal by replying with "Appeal" in the subject line. We answer in writing within 45 days. If we deny your appeal, you can contact the Attorney General of Washington, Nevada or Connecticut, and our answer will tell you how.

Changes to this policy

We post the new version on this page with a new date. Before we collect a new category of consumer health data, or use it for a new purpose, we ask for your consent in the app.

Contact

support@wavistaapp.com

Back to top