GLP-1.app

Beanly Privacy Policy

Effective date: November 5, 2026 (optional account and backup added; AI providers named)

Beanly is a mobile app for iPhone and Android made by Minh Truong, an individual developer ("I", "me"). This policy explains what happens to your information when you use Beanly. The short version: your log stays on your phone. The only exceptions are the optional account and cloud backup (section 1a), the optional AI features (when you use one, the meal photo or a few weekly numbers are sent to answer you, and are not stored), if you buy Premium, a check of your purchase with Apple or Google (section 4), and app usage analytics and ad measurement that never include anything you log (section 2a).

1. What Beanly stores, and where

Everything you enter in Beanly is stored only on your device, inside the app's private storage. This includes your medication, doses and schedule, injection sites, weight, height, goal, protein and water, side effects, notes, visit dates and settings.

  • You don't need an account or sign-up to use Beanly.
  • Unless you sign in for the optional backup (section 1a), your log is not uploaded or synced anywhere. The AI features in section 4a send only what each answer needs, and only when you tap them.
  • Without a backup, I cannot see, access, recover or delete your log, because I never receive it.
  • If your phone is backed up by Apple (iCloud Backup) or Google (Android backup), the app's data may be included in that backup under their terms.

1a. Optional account and cloud backup

You can choose to sign in with Apple (iPhone) or Google (iPhone and Android) under You > Sign in to back up. If you do:

  • What I receive from Apple or Google: an account identifier, and the email address and name they share (with Sign in with Apple you can hide your email behind a private relay address). I don't receive your password.
  • Your backup: a copy of your Beanly log (the same content as an export file, see section 1) is uploaded to my server when you sign in and again shortly after you change something, so you can restore it on a new phone. It is stored encrypted at rest and is linked to your account. Apple Health data is never uploaded.
  • Premium on all your devices: purchases made on a device you sign in on are linked to your account so Premium works on your other devices too.
  • Emails: only if you tick "Email me tips and Beanly news". You can untick it any time in the app or use the unsubscribe link.

The backup is used only to restore your log for you. It is never used for advertising, never sent to analytics or advertising services, and never sold. You can sign out or delete the account at any time (section 7).

2. What Beanly does not do

  • No ads inside the app.
  • No sending of your health log (medication, doses, weight, side effects, protein, water, notes, photos) to analytics or advertising services, ever.
  • No selling or renting of your data to anyone.
  • No personalized advertising based on your health, and no cross-app tracking on iPhone (Beanly does not ask for App Tracking Transparency permission).

2a. Usage analytics and ad measurement

To understand how the app is used and whether my ads work, Beanly uses these services:

  • Google Analytics for Firebase (Google LLC): app events that say that something happened, such as the app being opened, a screen viewed, onboarding finished, "a weight was logged", the paywall shown or a purchase started. Events never include the values you logged. Google receives an app-instance ID and device information such as model, OS version, language, country and app version.
  • Google Ads and Meta (Facebook) App Events (Google LLC, Meta Platforms, Inc.): only installs, app opens, starting a free trial and subscribing, so I can tell which ad campaigns bring people who keep using Beanly. On Android this uses the device's advertising ID, which you can reset or delete in Android Settings > Privacy > Ads. On iPhone the advertising identifier is not collected; Apple's privacy-preserving ad measurement (SKAdNetwork) is used instead.
  • Firebase Cloud Messaging (Google LLC): delivers occasional tips and offers (section 6). It uses a push token for your device and the topics the app joins (language, platform, and whether you have Premium).

Ad personalization is turned off in all of these. In the EU, EEA, UK and Switzerland, ad measurement and advertising storage are off (only basic usage analytics run). These providers process data under their own privacy policies (Google, Meta), may process it in the United States, and keep analytics data for up to 14 months.

3. Apple Health (HealthKit, iPhone only)

If you turn it on, Beanly can read and write your body weight (and height, if you allow it) in Apple Health so your weight stays in sync.

  • You choose what to allow in the iOS permission screen, and you can change it any time in the Health app or iOS Settings.
  • Health data is read and written only on your device. It is never sent to me or to any third party.
  • Health data is never used for advertising, marketing or data mining, and is never sold.
  • Beanly writes only values you entered yourself, and does not store Apple Health data in iCloud.

4. Purchases

Premium purchases are processed by Apple (App Store) or Google (Google Play). I never see your payment details, and unless you sign in (section 1a) I don't see your name or email either.

To check whether you have Premium, when you buy, restore or open the app Beanly sends my server the store's proof of purchase (the App Store receipt or the Google Play purchase token) together with a random install ID created on your device. My server checks it directly with Apple or Google and keeps a purchase record:

  • the random install ID (stored hashed);
  • the product (yearly, monthly or lifetime), expiry date, trial and refund status, the store's transaction ID, and the receipt or purchase token (stored encrypted).

No health data, weight, doses or notes are part of this. The record is used only to unlock Premium on your devices. The app also keeps the last answer on your phone, so Premium works offline. No third-party purchase service is involved. (Your purchase being made is also counted as an event in section 2a, without the receipt.)

4a. AI features (optional)

Two features use a third-party AI service. Nothing is sent until you tap one of them and allow it in the "Send this to AI?" prompt, which says what is sent and to whom. You can withdraw that permission any time in You > Share with AI features.

Who receives it: the request goes over an encrypted connection to my server, then to OpenRouter, Inc. (an AI routing service, USA), which passes it to Google's Gemini model (Google LLC) to produce the answer. No other AI service receives it.

  • Meal photo. What is sent: the meal photo you snap or pick, and your app language. Use: to estimate the protein in that meal. The photo is processed in memory and is not stored by me; it is not linked to your name, Apple Account or Google Account.
  • Weekly note. What is sent: a short set of numbers from the last 7 days (days logged, doses taken vs planned, weight change, average protein and water, and side-effect names with how often they happened) and your app language. Use: to write a few friendly lines about your week. No medication name, notes, dates, photos or identifiers are sent. The answer is saved only on your phone.

The data is used only to produce that one answer. It is never used for ads, never sold, and never sent to analytics or advertising services.

How the AI services protect it: I use OpenRouter and Gemini through their paid API terms, under which prompts and photos are not used to train models and are not kept beyond what the provider needs to answer and to prevent abuse. They are required to protect this data at least as well as this policy does. If I ever change AI provider, I will update this section and the in-app prompt first.

To keep the free allowance fair, the server keeps a count of uses per install, tied to a random install ID (stored hashed). The server does not keep your photos, numbers or the AI's answers, and never logs their content.

5. Exports and doctor reports

Beanly creates an export file or a PDF report only when you ask for it. The file is created on your device, and you choose where to send it (for example, Files, Mail or AirDrop). Once you share it, the receiving app or person controls that copy.

6. Notifications

Dose reminders are local notifications scheduled on your device. They do not pass through any server.

Beanly may also send occasional tips and offers through Firebase Cloud Messaging (section 2a). They never contain anything you logged. The app keeps them in its notifications list on your phone. You can turn them off in your phone's notification settings (on Android, the "Tips and updates" category), without turning off dose reminders.

7. Deleting your data

Use You > Erase all data in Beanly, or delete the app, to remove the log on your phone. If you signed in, use You > Delete account: it deletes your account, its cloud backup and your sign-in sessions from my server right away, and, for Sign in with Apple, asks Apple to revoke Beanly's access where it can. Without an account I hold no copy of your log. To remove the purchase record described in section 4, email me and I will delete it (Premium then needs a restore to unlock again).

8. Children

Beanly is for adults using prescribed medication. It is not directed to children under 13 (or the equivalent age in your country), and I do not knowingly collect information from children.

9. Health data laws

Beanly is a consumer app, not a health care provider, so HIPAA does not apply. In the US, the FTC Health Breach Notification Rule covers apps like Beanly that handle personal health records. Your log never leaves your device unless you turn on the optional backup (section 1a), which is stored encrypted; AI requests are not stored. If identifiable health information I hold (such as a backup) is ever accessed without authorization, I will notify affected users, the FTC and, where required, the media, as the Rule requires. Consumer health privacy laws in some US states (such as Washington's My Health My Data Act) are respected in the same way: your health entries are collected by me only if you choose the backup, are never shared with analytics or advertising services, and I never sell data. The usage and ad-measurement events in section 2a do not include them.

10. Your rights

Depending on where you live (for example under the GDPR, UK GDPR or California law), you may have the right to access, correct, delete or move your personal data, and to object to processing. Your health entries are under your full control on your device; if you use the backup, you can delete it with your account in the app (section 7). For the purchase record described in section 4 or your account data, contact me. For analytics data (section 2a), you can also reset your advertising ID on Android, or delete the app, which ends collection; to ask me to delete analytics data linked to your app instance, email me. You can also complain to your local data protection authority.

For EU/UK users: the legal basis for processing purchase data and your account and backup is performance of the contract (providing Premium and the backup you asked for); for emails it is your consent; for basic usage analytics it is my legitimate interest in keeping the app working and improving it, and ad measurement is not used where you are. The purchase record is kept on my server and checked with Apple or Google, which may process it in the United States under appropriate safeguards.

11. Changes

If this policy changes, I will update the effective date above and, for important changes, tell you in the app before they apply.

12. Contact

Minh Truong, developer of Beanly
Email: support@glp-1.app