Privacy Policy — Luko

This Privacy Policy explains how we collect, use, share, and protect information when you use the Luko iOS app and related services (the “Service”).

Previous version: October 2, 2026

1. Who we are

Luko is a consumer wellness app focused on food logging, personal nutrition targets, optional guided workouts (“Workout with Luko”), and an Adventure destination called the Homestead Planet. You can complete onboarding, set a calorie/macro plan, log meals (photo, text, or voice description), see an AI note after a log, generate recipe ideas, get a Home briefing about today’s food and workout status, train with a daily plan and session, grow a Planet and unlock seasonal residents as you log meals or workouts, send private product feedback from Home, and manage your profile in Settings. Food and workout tools also appear under the More tab.

Luko Gold is an auto-renewable subscription required to enter the main app after the initial questionnaire and plan preview. Apple handles purchases, and we use RevenueCat to check and restore subscription access, as described in section 2.O.

Luko is not a medical device and does not provide medical advice, diagnosis, or treatment. Planet weather and daylight are decorative scene effects, not health readings or clinical assessments.

This version does not include a free-form daily context/condition journal, open-ended AI chat or voice coaching outside the flows described here. If we add those later, we will update this Policy.

2. Information we collect

A. Account & identity

When you create or sign in (via Clerk and supported sign-in methods), we may collect name, email address, authentication identifiers/tokens, and account settings (e.g., timezone). After onboarding, we ask you to create or sign in to an account so your plan and logs can be saved. The first-run subscription purchase can take place before sign-in.

B. Profile & wellness information you provide

During onboarding and in settings, you may provide age/birthday, sex, height, weight, goals (lose/maintain/gain), activity level, pace, dietary preferences, allergies, and disliked foods. This may be treated as health-related personal data under some laws. We use it to personalize calorie/macro targets and to seed workout preferences where applicable.

C. Food-logging content

Meal photos (camera or photo library), typed or spoken meal descriptions, structured meal logs, estimated calories/macros, meal history, and optional AI follow-up text/audio about a logged meal (“honest summary”).

D. Workout & fitness content

If you use Workout with Luko, we collect and store on our servers:

• Luko’s note — training preferences you set or ask us to update, such as training mix (e.g., strength, mobility, conditioning), workout length, focus areas, equipment, and optional context (e.g., low impact, prioritize recovery), including any short custom text you enter in those fields;
• Daily plans — generated exercise steps (exercise identifiers, sets, reps, load), plan status, coach lines, and related revisions;
• Session logs — when you finish, save and leave, or skip remaining work: timing, duration, completed and skipped exercises, and an estimated calorie burn (an estimate, not a sensor measurement);
• Home briefing — a short AI line (and emotion tag) about today’s food and workout status when that feature runs.

Workout with Luko does not use Apple Health / HealthKit, continuous heart-rate monitoring, or GPS to measure a session. Estimated burn is computed from the session snapshot above. Motion permission (if enabled) is only for the on-device Meal-token tumble animation described below — not for counting steps or measuring workouts.

Separately, if you allow Apple Health access for Adventure, we may read workout samples already stored in HealthKit to update Planet weather on your device (see section G). We do not write Luko workouts into Apple Health, and we do not use HealthKit to calculate the in-app estimated burn.

Exercise demonstration media (images/animations) may be loaded from a content delivery network so the session UI can show form references.

E. Recipe ideas

If you use Plan my meals / recipe ideas, we send your request (and any extra note you type) to our servers so we can return suggested meals.

F. Adventure / Homestead Planet progress

Adventure is Luko’s planet destination (the Homestead Planet first). Logging meals or workouts can advance season progress and unlock seasonal residents and world objects. We store season progress numbers, which seasons are available, and unlock-presentation receipts on your device so the Planet can grow and replay ceremonies.

When account sync is available, we may also save those progress and presentation values to your Luko account so the Planet can follow you across devices. That sync is progress state only — not HealthKit samples, body-weather details, or location.

Planet visuals (scene, weather look, daylight, dialogue presentation) are computed and stored on your device.

G. Apple Health / HealthKit (optional, iOS)

If you allow Apple Health access, Luko may read these HealthKit types so your Planet’s decorative “body weather” can reflect recent patterns:

• sleep;
• steps;
• active energy;
• workouts already stored in Apple Health;
• heart rate;
• heart rate variability (HRV).

We request read access only. Luko does not add, change, or delete data in Apple Health.

HealthKit samples, sync receipts, and the derived weather state are processed and stored on your device. We do not upload HealthKit samples, time series, or inferred weather causes to our servers, to analytics, to advertising measurement, or to other third parties. Android does not use HealthKit in this version.

After you grant access, iOS may wake the app in the background when those Health types update so Planet weather can stay current. We may show an optional local weather notice on your device. Those notices are generated on the device; they are not a remote push of health data.

Allowing HealthKit is optional. Declining it does not block Adventure, meal logging, or workouts. Planet weather then uses a permission-free fallback.

H. Approximate location (optional)

The first time you open Adventure, Luko may ask for approximate (coarse) location while using the app so Planet daylight can follow local sunrise and sunset. We do not request precise GPS, always-on location, or background location.

Location is used only to compute a sunrise/sunset window for that device-local day. It is not stored beyond what that computation needs and is not sent to our servers, analytics, or advertising partners. It is not used for maps, fitness tracking, or ads.

Declining location does not reduce features. Planet uses a fixed daylight window (6:00–20:00) instead.

I. Device & technical data

Device type and model, OS/app version, device identifiers (the identifier for vendor and, only if you allow tracking, the advertising identifier), IP address, diagnostics needed to operate and secure the Service, push notification tokens (if enabled), and local preferences on device.

J. Analytics (PostHog)

We send product-usage events to PostHog (for example: app opens, onboarding steps, meal-log funnel, workout and toolbox funnels, Home briefing readiness, Planet / Adventure presentation events, which settings were changed — not their values). We also store categorical onboarding answers as PostHog person properties: main goal, secondary goals, goal pace, activity level, sex, and self-reported install source. We may use PostHog to run in-app experiments (feature flags) that choose among complete product experiences; flags do not add extra personal data beyond the events and properties described here.

Subscription-related product events include paywall views, selected plans, checkout and restore outcomes, whether Gold access was granted, and trial-reminder choices.

We also receive Luko Gold subscription events from RevenueCat, for example trial started, trial converted, trial cancelled, renewal, cancellation, billing issue, expiration, and refund. These events include the product, price, currency, and App Store transaction identifiers. RevenueCat reports revenue converted to US dollars. The events are linked to the same analytics identifier the app uses: anonymous before sign-in, and your Luko account after sign-in. RevenueCat may also include identifiers and device information it holds for you: your PostHog and AppsFlyer identifiers, the advertising identifier (IDFA) only if you allow tracking, the identifier for vendor (IDFV), IP address, device model and OS version, and your App Tracking Transparency choice (see section 2.O).

Subscription events from the app or from RevenueCat do not include your Apple Account credentials, App Store receipt contents, or payment details.

We do not send to analytics: your name, age, height, weight, target weight, message/chat content, meal photos, voice transcripts, Luko’s note free-text, workout prescription details (sets, reps, loads), HealthKit samples, body-weather details, location, or feedback-board post text. Session replay (screen recording) is disabled.

PostHog may receive a technical identifier and, by default, IP address (from the app or in RevenueCat subscription events) used to infer an approximate location, such as country or region (not precise GPS).

K. Advertising measurement (AppsFlyer)

We use AppsFlyer to measure advertising effectiveness through install attribution and selected app interactions, including registration, onboarding, meal logging and scanning, workout starts and completions, return visits, engagement milestones, starting subscription checkout (including the selected monthly or yearly plan), starting a free trial, and Luko Gold purchases, trial conversions, and renewals (including the plan, price, and currency).

The app sends trial starts to AppsFlyer. RevenueCat sends purchases, trial conversions, and renewals to AppsFlyer on our behalf, server to server, with revenue converted to US dollars. RevenueCat does this only when the app has provided an AppsFlyer identifier for you. To help match these events to the ad that led to your install, RevenueCat may include the advertising identifier (IDFA) only if you allow tracking, the identifier for vendor (IDFV), and IP address. Cancellations and refunds may also be sent to AppsFlyer for measurement. Test (sandbox) purchases are not sent to AppsFlyer.

AppsFlyer may share trial starts and subscription purchases with the ad network that delivered the ad (for example, Meta or TikTok), so we can measure and optimize our campaigns. This is subject to your App Tracking Transparency choice. Cancellations and refunds are not shared with ad networks.

Events may be associated with device identifiers and, after sign-in, your Luko account ID. They do not include meal photos or descriptions, nutrition values, body measurements, exercise details, voice content, HealthKit data, or Planet weather and location data. Subscription events do not include your Apple Account, App Store receipt contents, or payment details.

On iOS, we request permission through Apple’s App Tracking Transparency framework for tracking. Declining does not limit the app’s features.

We do not show third-party ads in the app in this version.

L. Feedback portal (UserJot)

From Home (top-right chip) you can open an in-app feedback board hosted by UserJot. Submissions may include idea or bug text and, if you type one, an email address. Boards in this version are private: a post is visible only to you (as the author) and the Luko team — not a public feed. Image uploads are off. We do not pass your Luko/Clerk account identity into UserJot. Guest posting does not require a UserJot account. An email you type there is stored by UserJot and is not sent to PostHog or AppsFlyer.

M. Permissions (iOS)

You can change permissions in iOS Settings.

N. Children

We do not knowingly collect personal information from children under 13 (or the minimum age required in your country). Contact us to request deletion if needed.

O. Purchases & subscriptions (Apple and RevenueCat)

Apple processes Luko Gold payments. We use RevenueCat to retrieve subscription offers, check introductory-offer eligibility and active access, and confirm and restore purchases. Subscription checks can occur when you open the app, before you make a purchase.

RevenueCat processes an app user identifier: an anonymous identifier before sign-in and your Luko account identifier after sign-in. This allows subscription access to be associated with your account. RevenueCat also processes App Store purchase history and subscription records, such as product and transaction identifiers, purchase and expiration dates, trial status, active access, and renewal status. Technical information may include device type, operating system and app version, locale, and the last time the app contacted RevenueCat. We use these records to provide and restore Gold, handle subscription support, and understand subscription performance.

RevenueCat also processes the PostHog and AppsFlyer identifiers the app provides. When the app provides your AppsFlyer identifier, the RevenueCat SDK also collects device information: the advertising identifier (IDFA) only if you allow tracking (otherwise it is not available), the identifier for vendor (IDFV), IP address, and device model and OS version. RevenueCat also records your App Tracking Transparency choice. To attribute and measure subscriptions, RevenueCat uses this information to forward the subscription events described in sections 2.J and 2.K to PostHog and AppsFlyer, and may include it with those events.

We do not send your meal photos, voice content, body measurements, workout details, HealthKit data, or location to RevenueCat. Apple handles your payment method; Luko and RevenueCat do not receive your full payment-card details from Apple. See RevenueCat’s Privacy Policy for its data practices.

With notification permission, Luko may use the confirmed trial end date to schedule one on-device reminder two days before the trial ends. If notifications are already allowed, this can be scheduled automatically; otherwise the welcome screen offers a permission request. You can change notification permission in iOS Settings. Reminders do not manage or cancel your subscription.

3. How we use information

We use information to:

• provide the Service (account, plan targets, meal logging, recipe ideas, Workout with Luko plans and sessions, Home briefing, Homestead Planet progress, history, settings, optional feedback);
• analyze meals with AI to estimate nutrition and, after a log, generate a short spoken/text note;
• generate and update workout preferences, daily plans, coach lines, estimated burn, and Home briefing copy with AI and/or our servers;
• grow Planet season progress from meal and workout logs, and (if you allow it) derive on-device Planet weather from HealthKit and daylight from approximate location;
• authenticate and secure accounts;
• check subscription eligibility and access, confirm and restore purchases, and provide subscription support and analytics;
• send reminders or on-device weather notices when notifications are allowed, including a local Gold trial-end reminder;
• understand product usage, run in-app experiments, and improve reliability (PostHog);
• measure and optimize advertising campaigns, including attributing subscriptions to campaigns (AppsFlyer, with events from RevenueCat);
• host optional private product feedback (UserJot);
• comply with law and enforce our Terms.

We do not sell your personal information. We do not use HealthKit data for advertising, marketing, or data mining.

4. AI processing

When you log food by photo, text, or voice, relevant content may be sent to our servers and/or subprocessors so we can return nutrition estimates. After you confirm a log, we may generate a short AI note (text and, on iOS, spoken audio). Recipe-idea requests are also processed by AI.

For workouts, Luko’s note, plan generation, coach lines, estimated burn, Ask Luko to update, and Home briefing may be processed on our servers and/or by AI subprocessors using the preferences and session data described above.

Planet weather is computed on your device from HealthKit (if allowed). It is not sent to an AI provider.

Outputs are estimates and may be inaccurate. Do not rely on them for medical decisions or as a substitute for professional training advice.

5. How we share information

We may share information with:

• Service providers under contracts that limit use to serving us: hosting, Clerk (authentication), AI providers (meal analysis, honest summary, recipe ideas, workout planning / briefing), content delivery for exercise media, PostHog (product analytics and experiments), RevenueCat (subscription access, purchase records, subscription analytics, and subscription attribution), AppsFlyer (install and campaign measurement), UserJot (feedback board hosting), support;
• Apple for Sign in, speech recognition (if used), HealthKit (if you allow it — Apple already holds that health data), App Store operations (including subscription payments, renewals, restoration, and refunds), and SKAdNetwork attribution;
• legal/safety recipients when required by law or to protect rights, or in a merger/acquisition (with notice where required).

We do not share meal photos, health profile data, HealthKit samples, body-weather details, location, or workout prescription details for third-party advertising. AppsFlyer receives identifiers (including IDFA only if you allow tracking, IDFV, and IP address), selected app-interaction events, and subscription events for advertising measurement, and may share trial starts and subscription purchases with the ad network that delivered an ad, as described in section 2.K. We do not send meal content, body measurements, detailed workout records, or HealthKit data to AppsFlyer. Feedback text and any email typed in the portal are processed by UserJot as described in section 2.L; we do not send that content to PostHog or AppsFlyer.

6. Retention

We keep information while your account is active and as needed to provide the Service, resolve disputes, and meet legal obligations. Delete your account in-app (Settings → Accounts → Delete My Account) or by emailing us; we will delete or anonymize personal data except where law requires retention. Analytics and attribution vendors retain data under their own retention settings.

Purchase and subscription records may be retained as needed to provide and restore access, resolve billing issues, and meet legal obligations. RevenueCat processes these records on our behalf under our agreements; Apple maintains its own purchase records. Deleting your Luko account does not cancel your App Store subscription or automatically erase Apple’s purchase history. Contact us for requests concerning purchase-related personal data held by us or our service providers.

On-device HealthKit copies, Planet weather, location-derived daylight, and local Adventure presentation are removed when you delete the app or account data on the device. Account-synced Planet progress, if any, is deleted with your account.

Guest feedback posts are not tied to your Luko account. Deleting your Luko account does not automatically delete UserJot submissions. Email us from the address you used on the board (or describe the post) to request removal. UserJot retains data under its own settings.

7. Security

We use reasonable administrative, technical, and organizational measures (including encrypted transit and access controls). No method of transmission or storage is 100% secure.

8. Your choices & rights

Depending on your location, you may have rights to access, correct, delete, export, restrict, or object to certain processing, and to withdraw consent.

• Account deletion: Settings → Accounts → Delete My Account, or email us from your account email.
• Subscriptions: Profile → Settings → Subscription, Account → Manage subscription on the returning-user paywall, or your Apple Account’s subscription settings. Deleting your Luko account or the app does not cancel Apple billing.
• Feedback posts: email hu@zentarilabsinc.com to request deletion of UserJot submissions (especially guest posts).
• Apple Health: iOS Settings → Health → Data Access & Devices → Luko, or decline the in-app HealthKit sheet.
• Location: iOS Settings → Privacy & Security → Location Services → Luko.
• Tracking: decline Apple’s tracking prompt, or later iOS Settings → Privacy & Security → Tracking.
• Notifications, camera, photos, microphone, motion: iOS Settings.
• Sign out: Settings → Accounts.

9. International transfers

We may process data in the United States and other countries where we or our providers operate. Where required, we use appropriate transfer safeguards.

10. Changes

We may update this Policy when features or data practices change. We will post a new last-updated date. Continued use after changes means you accept the updated Policy where permitted by law.

11. Contact

hu@zentarilabsinc.com
Zentari Labs Inc.
650 California St, Fl 7
San Francisco, CA 94108