YULA Lab
← Privacy
LifeOS

LifeOS privacy policy

Last updated: 2026-10-20

One-line summary

LifeOS is an offline-first app built around on-device data storage. Data processed for accounts, purchase state, crash reporting and optional cloud backup is described separately below. Content kept on your device is distinct from the account and service data sent to those services.

Content stored on your device

  • Health data (read from Apple Health / Health Connect: steps, heart rate, sleep, exercise)
  • Financial records (income, expenses, goals)
  • Learning and goal tracking
  • Voice journal and Z-Report entries (speech recognition uses the operating system's service)
  • Photos and other attachments

The main database's encrypted-storage coverage depends on the app version and platform. The database key is managed through the platform's secure storage service. Audio, photos, exports and other attachments may be separate files; database encryption does not mean that it covers every one of those files.

Data sent to our servers

  • Account information: Email and device ID (only if you create an account). You can use the app with most features without creating an account.
  • Crash reports: Sentry is used for crash reporting. You can check and change your reporting preference in Settings > Privacy. When reporting is enabled, diagnostic data about application errors is sent to Sentry.
  • Purchase state: Apple App Store / Google Play receipt validation. We only store active/inactive and tier (Plus / Pro).
  • Cloud sync (optional): If you enable cloud sync, records included in sync may be transferred to Supabase. Encryption of the database on your device does not mean that the cloud copy is end-to-end encrypted. Check the in-app information for your version for the data included and the available encryption features; you can ask support for clarification before sending personal content.

HealthKit / Health Connect

We request Apple HealthKit (iOS) and Android Health Connect permissions to read health data. You grant these optionally. Health data is processed on-device, is NOT sent to any server, and is NOT used for model training.

Third parties

  • Supabase: Account registration and optional cloud backup. Hosted on EU (Frankfurt) servers.
  • Apple HealthKit / Health Connect: Health data read permission (optional).
  • Apple App Store / Google Play: Subscription payments and receipt validation.
  • Sentry: Crash reports, subject to your reporting preference in the app.

Data retention

Device data is kept until you delete it. Deleting an account and removing files from your device are separate actions. Receipts documenting completion of an account deletion may retain the user identifier after the account has been deleted. We therefore do not give a blanket guarantee that all server-side records are removed within 30 days. For the scope and retention period of records associated with your account, or a deletion request, contact support@yulalab.com.

Children

If you suspect that a child's data is being processed, contact support@yulalab.com. We assess the request and applicable deletion or retention duties; we do not give a blanket guarantee that every record is erased immediately.

Medical disclaimer

LifeOS is a health tracking tool and does NOT provide medical advice. Please consult a licensed health professional for medical decisions. The app is not intended to diagnose, treat, or prevent any disease.

Your rights

Contact support@yulalab.com to exercise your rights under Article 11 of the Turkish data protection law (KVKK). Where GDPR applies, the rights in Articles 15–22, including portability and objection, have their own statutory conditions. KVKK requests are answered as soon as possible and within 30 days; GDPR requests without undue delay and normally within one month. If a justified extension under GDPR applies, you will be informed of it and its reasons within the first month.

Account deletion steps and the request path outside the app: Delete your LifeOS account and data.

Data security

Check the main database's encrypted-storage coverage for your app version and platform; keys are managed through the platform's secure storage service. This protection has a different scope from separate attachments and optional cloud sync. This page does not guarantee end-to-end encryption or server unreadability of cloud sync data across all versions.

Changes

We may update this policy from time to time. Significant changes will be announced via in-app notice and reflected in the 'Last updated' date.

Contact

Data Controller: YULA Lab — Mustafa Kaan Koçak
Email: support@yulalab.com
Location: Türkiye