Privacy Policy — Android

This policy covers the Android version of DripLine distributed on Google Play. The iOS version is a separate build with a separate policy — see the DripLine Privacy Policy for iOS.

Everything you type into DripLine stays on your device. There is no account, no sign-in, and no server of ours. The app makes no network request of its own — the only thing that leaves your phone is the pseudonymous usage analytics described below, which never carries a timer's name, its room, or its note.

DripLine stores your infusion timers in a database inside the app's own private storage directory. Each timer can hold:

• A label you give the timer, a room, and a free-text note
• Volume, duration, drop factor, mL per hour, drops per minute
• Start, end, and completion times, and the timer’s status

The app also keeps your settings — custom drop factors, language, notification state, and whether you have acknowledged the safety notice — and an internal journal of the notifications it has scheduled.

Please do not enter patient-identifying information. The label, room, and note fields are free text and DripLine cannot tell what you put in them. They are stored unencrypted in the app's private storage, and although nothing is transmitted, anyone with access to an unlocked device could read them. Use a room or a bed number rather than a name. Keep your device locked.

DripLine does not read from or write to Health Connect or any other health platform, and it declares no health, activity-recognition, or body-sensor permission. It calculates and times an infusion from numbers you type in; it measures nothing and connects to no device or pump.

To understand how the app is used and to improve it, DripLine sends usage events to an analytics service that Pentarab runs itself. It is not Google Analytics, and the data is not passed on to any third party. The events record which screens you open and which features you use. This is the complete list of what that service receives:

• The app identifier, the platform, and the app version and build number.
• An install identifier — a random value the app generates on first launch. It is not derived from your device, your Google account, or any advertising identifier, and reinstalling the app produces a new one.
• A session identifier, so one run of the app can be told apart from the next.
• Screen names, and how long each screen was open. The duration is measured from a matching open and close, not guessed from the gap between events.
• The UTC time of each event, plus your time-zone offset so local time can be reconstructed.
• Device information: the operating system and its version, the screen size, and the locale. The device model is not sent.
• A country. This is worked out by the receiving server from the connection itself — the app never sends it, and it is country-level only.

A few events carry a numeric detail so we can see which settings are actually used — the drop factor selected, the duration in minutes, and whether a completion alert was enabled. No timer name, room, or note is ever included in an analytics event, and DripLine has no account, so nothing in the analytics stream identifies you or a patient.

The service does not store your IP address. It is read at the edge only to derive the country and is then discarded. It collects no advertising identifier, no precise location, and no personal identifier such as a name, email address, or phone number. Apart from the numeric settings described above, nothing you create or enter in DripLine is part of an analytics event.

DripLine does not collect the Android Advertising ID. Both advertising-ID permissions (com.google.android.gms.permission.AD_ID and android.permission.ACCESS_ADSERVICES_AD_ID) are explicitly removed from the app's manifest and are absent from the build published on Google Play. There are no ads, no crash reporting, and no performance monitoring.

• Notifications — so the app can alert you when an infusion is due to finish. Requested when you first schedule an alert; decline it and the timers still run, but you will not be alerted while the app is in the background.
• Alarms & reminders (exact alarm) — so the completion alert fires at the right minute rather than whenever the system next wakes. If it is not granted, DripLine falls back to an inexact alarm.
• Run at startup — so scheduled alerts survive a reboot. An ordinary permission; no prompt.
• Vibrate — for the alert. An ordinary permission; no prompt.

There is no camera, microphone, photo, storage, location, contacts, calendar, or body-sensor permission. The app does declare the ordinary internet permission — it is what the analytics events described above are sent over, and it is the app's only use of the network. It shows no prompt.

The Clinical References screen opens published guidance — INS Standards of Practice, NICE, ISMP, WHO, and others — in your browser. DripLine hands the address to Android and takes no further part; it does not fetch, proxy, or log those pages, and those sites have their own privacy policies.

DripLine is a paid app: you buy it once on Google Play. There are no in-app purchases, no subscriptions, and no ads. Payment is handled entirely by Google — Pentarab never sees your card details, your Google account details, or your billing address.

Open Settings → Delete all data in the app. After a confirmation prompt this permanently removes every local timer and its associated record.

Uninstalling the app, or clearing its data from Android Settings → Apps → DripLine → Storage, removes everything. Because nothing is held on a server, there is no server-side copy for us to delete and no deletion request to submit.

DripLine is a professional tool intended for clinicians and students, not for children. We do not knowingly collect personal information from children.

We may update this policy from time to time. Changes will be posted on this page with an updated revision date.

Questions about this policy? Email us: