Privacy policy

What stays on your device.

Last updated: 24 October 2026

The app has no account system and no Kovus-operated server for your log. Your compounds, vial details, entered amounts, schedules, notes, injection sites, and weight entries are stored in the app's on-device SQLite database. Each device has its own local database; Vialtally does not automatically sync records between devices.

Who we are

Vialtally is developed by Josh Waller, trading as Kovus, in Perth, Western Australia. Contact josh@kovus.dev for privacy questions or requests.

Data stored on your device

The app stores the information you choose to enter, which may include:

• compound names and labels;
• vial amounts, units, balances, expiry dates and costs;
• logged amounts;
• schedules and reminders;
• injection-site history;
• notes and local weight entries; and
• app settings and export history.

Older records may retain historical reconstitution fields and saved draw volumes for data compatibility. The current app does not request those inputs or display conversion outputs.

Primary records remain in the app's on-device SQLite database. When widgets are enabled, a limited display summary is shared with the widget on the same device. Standard iPhone or iPad backups may include app data according to your Apple backup settings. Export and import are user-initiated through Apple's standard Files and share controls: you may save an export file directly into any Files destination, including a cloud storage provider, or share it, and may import a previously exported file.

Analytics and crash reporting

Vialtally does not include an analytics SDK, advertising SDK, session replay, or remote crash-reporting SDK. App activity and user-entered records are not sent to Kovus for analytics or diagnostics.

Purchases

Pro purchases are sold through Apple's in-app purchase system and managed in the app through RevenueCat. Apple and RevenueCat process an anonymous app identifier, purchase history and entitlement status, and basic app/device metadata needed to provide, manage, and restore Pro. Kovus does not receive your full payment-card details.

Third parties and network destinations

The production app is designed to contact only:

• Apple services for App Store purchases and operating-system features;
• RevenueCat for an anonymous app identifier, purchase history and entitlement status, and basic app/device metadata used to provide and restore Pro.

No analytics, advertising, or remote crash-reporting service is used. If that changes in a future release, this page and the App Store privacy disclosure will be updated before the change ships.

Third-party protection

For the purchase data Vialtally shares, Apple and RevenueCat provide the same or equal protection as described in this policy and required by Apple's App Review Guidelines.

We use RevenueCat under its standard terms and Data Processing Addendum. The published DPA sets out processing on the developer's instructions, security safeguards, and subprocessor agreements with protections no less protective than that addendum, subject to its applicable scope. Apple handles App Store account, payment and purchase data under its Privacy Policy and App Store & Privacy notice. This purchase processing is separate from your on-device log.

Notifications

Dose and vial reminders are scheduled locally on your device. Notification content can be made discreet so the lock screen shows Dose due instead of a compound label.

Export, import, and deletion

You control manual exports and where they are shared. Import uses a preview and explicit confirmation before replacing current data, and the app creates a local safety snapshot first.

You can remove app records from inside the app. The in-app delete-all flow also clears the shared widget summary. Deleting the app removes its local container from the device, subject to copies you chose to export and backups controlled through your Apple settings.

Purchase-data retention and requests

Removing local records, deleting the app, or cancelling Pro does not automatically remove purchase records held by Apple or RevenueCat. RevenueCat's published DPA describes retention for the term of its service agreement with the developer, with deletion or return at the developer's request when that agreement ends, subject to backup and archival practices. RevenueCat also supports individual customer deletion requests; legal retention obligations may limit deletion.

To request deletion of RevenueCat-held purchase data, or withdraw consent where processing relies on consent, email josh@kovus.dev. We handle deletion requests when the anonymous record can be identified, and may ask for limited purchase information to locate it. Please do not send your app export, compound names, doses, vials, payment-card details or Apple Account password. A deletion request does not cancel an Apple subscription; manage subscriptions with Apple.

Apple retains purchase records for service and financial-reporting requirements, with periods that vary by region; some records remain even after an Apple Account is closed. Requests about Apple-held data can be made through Apple's Data and Privacy page or Apple's privacy contact. Kovus cannot delete Apple's legally required financial records.

Children

The app is not designed for children. The App Store age-rating questionnaire is answered honestly based on the app's content and Apple's current descriptors.

Changes and contact

If this policy changes, the updated date and wording will be published at this address. Material changes will be reflected in the App Store privacy answers where required. Email josh@kovus.dev with a question or request.

Read the terms of use or visit Vialtally support.