Takivo_pages

Privacy Policy — Takivo

Effective date: May 13, 2026

Takivo (“the App”) is a supplement, medication, and injection reminder for Apple devices. This policy explains what data the App handles and how.


Data Collection by Product Version

Current Version

Takivo does not collect, sell, or share personal data with us. The App has no Takivo account system, no third-party analytics or advertising SDKs, and no Takivo-operated server-side storage for your health entries.

When iCloud is available for Takivo, the App uses Apple’s CloudKit service to sync your app data through your private iCloud database. This is controlled by your Apple ID and iCloud settings. Takivo does not receive your Apple ID and does not operate a separate sync backend.

Takivo Pro subscriptions are purchased and managed through Apple’s StoreKit and App Store subscription systems. Apple processes purchases, renewals, refunds, and subscription management. Takivo receives StoreKit entitlement status on-device so the App can unlock Pro features, but Takivo does not receive your payment card details.

Future Versions

Future releases may add optional diagnostic tooling, product analytics, Apple HealthKit integration, or schedule sharing with designated contacts to improve reliability, usability, and health tracking. If that happens, this policy will be updated before or at release to describe:

Any future analytics use will be limited to app quality and product improvement. Takivo will not use analytics data for advertising personalization or cross-app tracking.


Data Stored on Your Device

All information you enter — supplement, medication, and injection names; schedules; dose history; notes; reminder settings; and app settings — is stored locally on your device using Apple’s SwiftData framework.

When iCloud is available for Takivo, this app data is also mirrored through CloudKit in your private iCloud database so it can sync across Apple devices signed into the same Apple ID. If iCloud is unavailable, restricted, or not signed in, Takivo continues to work locally on that device.

Apple-managed backup features, such as iCloud Backup or iTunes/Finder backup, may also include local app data if you enable them in your Apple account settings.

Future versions may allow you to share your schedule with designated family members or caregivers. If introduced, this policy will explain what is transferred, where it is stored, who can access it, and what controls are available.

iCloud Sync

Takivo uses CloudKit only for app data sync and backup through your private iCloud database. Synced data can include:

Takivo does not run a separate cloud server for this data. Apple provides and controls iCloud and CloudKit under your Apple ID settings. You can control iCloud availability for Takivo in iOS Settings.

CloudKit sync is separate from local notification permission. A second synced device still needs its own notification permission before it can schedule local reminders.


Local Notifications

Takivo uses Apple’s local notification system to send reminders you schedule. These notifications are generated on-device and are not sent through a Takivo server. Notification permission is device-specific, so a second synced device still needs its own notification permission grant.

Notification actions such as Done and Skip update local app data and may then sync through iCloud if iCloud is available.


Widgets, App Groups, and Apple Watch

Takivo provides widgets and Apple Watch surfaces for at-a-glance reminder information.

The iOS widgets and Apple Watch complications read small snapshot files written by the App into Apple’s local App Group storage. These snapshots can include today’s planned dose names, dose amounts, scheduled times, and status such as upcoming, overdue, done, skipped, or postponed. The widget extensions do not open the SwiftData or CloudKit database directly.

The Apple Watch app uses Apple’s WatchConnectivity framework to receive today’s plan from the iPhone and to send dose actions, such as Done, Skip, and Postpone, back to the iPhone. The iPhone remains the source of truth for saving dose events and rescheduling reminders. Takivo does not operate a server for Apple Watch transport.


Health Data Boundaries

Takivo is designed so your supplement, medication, and injection content (item names, dosage details, schedules, and dose history) stays under your control: locally on your device, and in your private iCloud database when iCloud sync is available.

Future versions may optionally integrate with Apple HealthKit to read workout data or write supplement and medication intake records, with your explicit permission. HealthKit data is governed by Apple’s HealthKit privacy requirements and is never used for advertising or shared without your consent.

If a future release introduces analytics, diagnostics, sharing features, or HealthKit integration, data collection and processing will be scoped to the minimum needed for quality, product insights, and any user-enabled functionality. This policy will explicitly state whether any health-related fields are included. If a category is not explicitly listed here, it is not intentionally collected.


Third-Party Services

The current version of Takivo does not integrate third-party analytics, advertising, or profiling SDKs. It uses Apple’s SwiftData, local notifications, StoreKit, CloudKit, WidgetKit, App Groups, and WatchConnectivity frameworks for app functionality.

If future versions add third-party processors for diagnostics, analytics, storage, or sync, they will be disclosed in this policy, along with their role and applicable safeguards.


Children’s Privacy

Takivo does not knowingly collect personal information from children under 13 in the current version. If future versions introduce optional data services, this section will be updated with any age-specific protections that apply.


Changes to This Policy

If this policy changes, the updated version will be published at this URL with a revised effective date. Material changes (including any new analytics or diagnostics collection) will be clearly described in the updated text.


Contact

Questions about this privacy policy?

Email: ivan.balaksha@gmail.com