Jabbook — Privacy Policy

Solutio Lab

Last updated: 30 October 2026

Your injection log stays on your phone. This policy covers Jabbook on iPhone and on Android. Jabbook has no account, no sign-in, and no server that stores your doses, vials, schedules, or body measurements.

Health information you enter, and where it stays

You may enter the following into the app:

• names you give to the compounds you use, their colors and notes;
• vials: the amount per vial you type in, mix date, expiry date and low-stock threshold;
• schedules and the default dose you type in for each compound;
• each dose you log: amount, date and time, injection site and notes;
• body weight entries.

All of it is written to storage on your own device. It is never sent to us or to any third party, and we cannot see it. The app does not read anything from Apple Health or Health Connect.

Jabbook does not calculate, convert or recommend doses. Every number in it is one you entered yourself. It is a logbook, not medical advice; talk to your doctor about your treatment.

Reminders

Reminders are local notifications scheduled on your device by its operating system. No push server is involved and no reminder content leaves your phone.

App lock

If you turn on the app lock, Jabbook asks your phone to check your Face ID, fingerprint or passcode. The check is done by the operating system; the app only learns whether it succeeded and never receives your biometric data.

Backups and exports you make

You can export your log as a CSV file or save a backup file through your phone's share sheet. These files contain your health information and are not encrypted by the app. They go only where you choose to send them. Your device's own iCloud or computer backup may include the app's data, under Apple's terms; the app itself does not store your health information in iCloud. On Android, your device's own Google backup may include the app's data, under Google's terms.

Data we do receive

Usage analytics (PostHog). To learn which parts of the app work, the app sends anonymous usage events to PostHog — for example "a dose was logged", "a vial was added", "the paywall was shown" — together with counts such as how many doses have been logged and an anonymous random identifier created on install. These events never contain compound names, dose amounts, dates of your doses, injection sites, notes or weight. They are not linked to your identity and are not used for advertising or tracking. See PostHog's privacy policy.

Purchases (Apple, Google Play and RevenueCat). The one-time purchase is processed by Apple on iPhone and by Google Play on Android. We use RevenueCat to confirm that a purchase is valid and to restore it on a new device. RevenueCat receives the purchase record and an anonymous app user identifier. On iPhone, when you install the app from an Apple Search Ads advertisement, Apple may provide an attribution token that tells us which ad campaign the install came from; it does not identify you. We do not receive your name, email or payment details. See RevenueCat's privacy policy.

What Jabbook does not do

• No advertising inside the app and no advertising identifier (IDFA on iPhone, advertising ID on Android).
• No tracking across other companies' apps or websites.
• No selling or sharing of your health information.
• No access to contacts, photos, location, microphone or camera.

Deleting your data

Deleting a record in the app removes it. Uninstalling the app removes everything it stored on the device. Anonymous analytics events are kept by PostHog for a limited period and cannot be tied back to you; if you want them removed, write to the address below with the date you installed the app.

Children

Jabbook is not directed at children under 13 and does not knowingly collect information from them.

Changes to this policy

If a future version handles data differently, this page will be updated before that version ships, and the date above will change.