Dosehue
Dose tracking with a visual site log
iOS app
Privacy policy
Last updated: September 27, 2026. Dosehue 1.4 added optional symptom writing to Apple Health, background weight import, supply reminders, and widget privacy controls, described below.
Dosehue is made by Giray Batıtürk. Your medication plan and dose history stay in the app's storage on your device. The app does not send those records to the developer or another server, sell them, or use them for advertising.
This policy distinguishes the iPhone app from the support and privacy web pages and any email you choose to send.
Your plan and records
Dosehue stores the medication name, dose, unit, schedule, reminder time, injection sites, dates, and other record details you enter locally on your iPhone. There is no account to create.
Dosehue shows no ads inside the app and does not access location, contacts, camera, or microphone. It uses Apple Health only after a separate permission request, RevenueCat for Dosehue Plus purchases, Meta's and Google's SDKs for ad measurement as described below, and first-party PostHog product analytics as described below.
Apple Health
Apple Health connection is optional. If you grant access, Dosehue can read the weight you chose to share, and medication information on supported iOS versions. Dosehue never writes medication or injection records to Health. If you separately turn on “Save my new weights to Health” in Weight, new weight entries you type into Dosehue are also written to Health. Weight auto-import turns on automatically, once, the next time you open Dosehue whenever it has already asked for weight-read access, including a new install that asked for that access during setup, not only an existing user, you can turn it off again in Weight settings, and it does not turn back on by itself afterward. Once on, Dosehue reads your weight history from Apple Health automatically, including through background delivery, so new weigh-ins can appear without opening the app. Apple does not tell the app whether read access was denied, so an empty value may mean either no matching data or no permission.
Side-effect entries you log in Dosehue (1.4) are stored only on your device. If you separately turn on saving symptoms to Apple Health, each logged symptom is written to Health as a symptom sample, but only for the 11 symptom types Dosehue's catalog maps to a Health symptom type (nausea, vomiting, diarrhea, constipation, stomach pain, heartburn, bloating, decreased appetite, tiredness, headache, dizziness). Injection site reaction and anything you enter as your own custom wording have no Health equivalent and always stay in Dosehue only. Deleting a symptom entry in Dosehue deletes the matching sample Dosehue wrote to Health. Using “Delete all data” in Privacy removes Dosehue's on-device records but does not delete symptom or weight samples already saved to Apple Health; remove those directly in the Health app.
Health data is processed on your device. Dosehue does not include Apple Health data in its encrypted export, send it to PostHog or RevenueCat, use it for advertising, or sell it.
Supply reminders and widgets
Pen/needle supply setup and refill reminders (1.4) are local notifications scheduled on your device; Dosehue does not send this information anywhere.
Home Screen and Lock Screen widgets show your next dose from a snapshot kept on your device; nothing is sent to build or refresh a widget. By default, a widget shows the suggested injection site along with the countdown to your next dose. The Privacy screen's “Hide details in widgets” option hides the injection site only; the countdown still shows. The Control Center button only opens “Log dose”, it never shows your next dose or a countdown. Asking Siri to log a dose, and tapping “Log dose” on a Dosehue notification or from Control Center, write the dose itself on your device only, but, like logging from the app, they also send a coarse analytics event (see Product analytics below), subject to the usage-data switch.
Notifications
Notification permission is requested only to show local reminders. Neither the title nor the body of any Dosehue notification ever names your medication or dose. This covers the dose reminder, its “Snooze 1 hour” repeat, the pen/needle refill reminder (1.4), and the “Couldn't log your dose” failure notice shown when the reminder's “Log dose” action cannot write the dose. Notifications are scheduled on your device, not routed through a developer server. You can manage Lock Screen previews or disable Dosehue notifications in iOS Settings. You can use your plan and history without notification permission.
Backups and deletion
If iCloud device backup is enabled, app data may be included in Apple's device backup. Dosehue does not provide automatic cloud sync.
You can manually export a password-protected encrypted backup and choose where to save it, including a Files location you control. Since 1.4, the backup includes your medication plan, dose history, logged symptoms, and pen/needle supply tracking. It does not include Apple Health, purchase, or analytics data. Dosehue does not receive the file or password and cannot recover a forgotten password.
You can delete individual dose records in the app, and Privacy's “Delete all data” removes your plan, dose history, side effects and weight records from your device and cancels reminders; it does not remove symptom or weight data already saved to Apple Health. Choosing “Delete App” in iOS removes local app data; “Offload App” retains documents and data. Existing Apple backups are managed through your Apple and iCloud settings. See Apple's iPhone storage guide.
Dosehue Plus and purchases
Dose tracking, reminders, injection-site rotation, history, Apple Health connection, and encrypted backup remain available without a subscription. Dosehue Plus is an auto-renewing subscription, billed monthly or yearly, that unlocks advanced monthly charts, injection-site distribution, and PDF reports.
Apple processes payment. RevenueCat is used to show the paywall, verify purchase status, restore purchases, and manage access to Plus. For those purposes RevenueCat may process a random app user identifier, purchase and subscription history, transaction identifiers, app and device information, and interactions with its payment screen. Dosehue does not send your medication plan, dose records, injection sites, notes, encrypted backup, or Apple Health data to RevenueCat.
Apple and RevenueCat process purchase data separately from PostHog product analytics. You can manage or cancel the subscription in your Apple Account subscription settings.
Product analytics
The Privacy screen's “Share anonymous usage data” switch controls this. It is on by default, an install that never opens Privacy keeps analytics running, and turning it off stops sending to PostHog immediately and removes the local random identifier.
While it is on, each event carries a random analytics identifier, a separate random event identifier, its timestamp, and fixed app_version/build/distribution/environment fields (the app's own version and how it was installed, App Store, TestFlight, or debug, never your device model or OS version). The event names cover: app open, onboarding start/completion and each onboarding step, everyday screens (Today, History, Settings, site picker), a dose being logged (with which entry point, the app, Siri, a widget, or a notification action, never the dose itself), a dose being edited or deleted, plan edits, reminders being turned on or their settings opened, weight being added, its history viewed, or its goal set, a symptom being logged or deleted (never which symptom, severity or note), pen/needle supply being set up, a new pen started, or a refill reminder turned on (never the stock count), the Apple Health permission prompt being completed, saving symptoms to Apple Health or weight auto-import being turned on/off and whether a Health write or sync succeeded or failed, a widget or the Control Center button opening the app, “Hide details in widgets” being switched on/off, viewing the Reports screen or the “Estimated medication level” chart (with whether that section was shown locked or unlocked) and its info sheet, exporting a Reports PDF, the Dosehue Plus paywall/purchase/restore funnel (with where it was opened from), a backup being exported or restored, and the value-upsell sheet. Test builds are marked separately.
A failure event (for example a failed purchase, restore, Health write, or weight sync) also sends a closed diagnostic shape: which step failed, an allowlisted error domain, its integer code, and a closed error category, never an error message, product, receipt, customer identifier, or symptom/weight value.
Dosehue does not send medication names, dose amounts, dates, injection sites, notes, notification settings, exported reports, encrypted backups, Apple Health data, advertising identifiers, precise location, or screen recordings to PostHog. Analytics is not used for advertising or cross-app tracking.
To request deletion of analytics associated with your current installation, contact merhaba@tasarim.io before deleting the app so we can explain the available identification steps. Deleting the app removes its local random identifier. PostHog processes analytics in its European Union cloud environment.
Advertising measurement (Meta)
Dosehue uses the Meta (Facebook) SDK for one purpose: measuring which Meta ads bring people to install the app. On every launch it automatically sends Meta standard events: app install/first open, app launch, and App Store purchase or subscription events for Dosehue Plus, along with device and app information (device model, OS version, app version, SDK data). Dosehue never sends Meta a custom event.
Meta's automatic app-events logging is on, so the events above are sent regardless of your tracking choice. After you finish setting up your plan, Dosehue shows a short explanation screen once, and then iOS asks whether Dosehue can track you (the App Tracking Transparency prompt). If you tap "Allow", your advertising identifier (IDFA) is included with those events. If you choose "Ask App Not to Track", the same events are still sent, but without the IDFA, and Meta separately receives aggregated, privacy-preserving measurement (Aggregated Event Measurement / SKAdNetwork). Dosehue works identically either way, your choice never unlocks or hides any feature, and you can change it anytime in iOS Settings → Privacy & Security → Tracking. See Meta's data policy.
Dosehue never sends Meta your medication name, dose, injection sites, schedule, notes, encrypted backup, or any Apple Health data. Health information is never used for advertising and is never shared with Meta, under any circumstance.
Advertising measurement (Google Analytics for Firebase)
Dosehue also uses Google Analytics for Firebase to measure which Google ads bring people to install the app. It automatically collects Firebase's standard events: app install/first open, app sessions, app updates, and App Store purchase or subscription events for Dosehue Plus, plus device and app information. Dosehue does not report screen names to Google.
The same App Tracking Transparency choice above controls Google's ad-related signals: if you tap "Allow", ad-related consent (ad storage, ad user data, ad personalization) is granted; if you choose "Ask App Not to Track", those signals stay off and only basic analytics consent is granted. Firebase Installations (its own random installation identifier) and Firebase's automatic events work regardless of your tracking choice; only the IDFA and Google's ad-related consent signals depend on your ATT choice. Consistent with that, Dosehue's privacy manifest declares Firebase's app-measurement.com a tracking domain. See Google's data policy.
Dosehue never sends Google your medication name, dose, injection sites, schedule, notes, encrypted backup, or any Apple Health data. Health information is never used for advertising and is never shared with Google, under any circumstance.
Support email
If you email merhaba@tasarim.io, we receive the sender name and email address provided by your email service, your message, and any attachments you choose to include. This is a voluntary submission, not an automatic transfer of your local medication records.
Email reaches the developer's mailbox through Cloudflare Email Routing. We use support correspondence to answer your request and follow up on the reported issue, not for advertising or a mailing list.
Avoid including sensitive health details unless needed. You can ask about or request deletion of your support correspondence by writing to the same address. We do not have access to your local Dosehue records and cannot delete them remotely.
These web pages
Dosehue's support and privacy pages open in your browser. The app does not attach your medication plan or dose history to these links.
These pages do not load analytics, advertising tags, tracking scripts, or the site's contact form. They do not set analytics or advertising cookies. Other pages on tasarim.io may use different website features, described in the website privacy policy.
The pages are hosted on Cloudflare Pages. Serving them involves normal web requests; Cloudflare may process IP addresses and browser information for delivery and infrastructure security. This is separate from the app's local health records.
The pages use the Instrument Sans typeface to match the site's typography. The font files are served from tasarim.io itself; the pages make no request to Google Fonts or any other third-party font service.
App purpose
Dosehue does not provide medical advice, diagnosis, treatment, or dose recommendations. It helps you record the plan supplied by your healthcare professional.
Changes and contact
If the app or these support services change how they handle information, this policy and its update date will be revised. Service providers may retain operational records for the periods needed to provide their services, meet legal obligations, prevent fraud, and resolve disputes.
For privacy or app-support questions, contact Giray Batıtürk at merhaba@tasarim.io. Help with app features is on the support page.