How Emiko handles
your data.

Emiko helps with workouts, walking, food guidance, cravings support, recovery, and day-to-day support for women managing PCOS.

This page explains what we collect, what stays on your device, what gets stored on our servers, what tracking tools we use, and how we use that information. No smoke machines. No pretending the app can work without data. Personalization needs context, analytics needs events, and billing needs receipts.

1. Camera Processing and On-Device Movement Tracking

Emiko uses camera-based pose estimation to count reps, check form, and guide workouts. That processing happens on your device during normal use.

• No routine video storage: We do not store your workout video as part of normal use.
• No routine video upload: Camera footage used for live movement guidance is not uploaded to our servers in normal use.
• Derived workout information may be saved: We may save text-based outputs such as rep counts, workout completion, estimated calories burned, and similar session results.
• Motion and Fitness on iPhone: iOS walk tracking uses Apple's Motion & Fitness/Core Motion step data after permission. We use it to count walk progress, complete walking tasks, and sync step results.
• Browser motion: where the app runs in a browser or PWA, motion permissions and available sensor behavior depend on the device and browser.

2. Data We Collect

We collect the account, subscription, and text-based information we need to run the product and personalize it for you.

• Account information: name, email address, login details, and subscription or billing status.
• Authentication information: login provider identifiers and identity tokens from Google or Apple when you choose those sign-in methods.
• Questionnaire and onboarding data: answers you give about your goals, symptoms, routines, food patterns, cravings, recovery needs, schedule, and preferences.
• Profile and body data: information such as age, height, weight, and other details you provide for personalization and calorie estimates.
• Workout data: sessions started or completed, rep counts, estimated calories burned, minutes active, movement history, and related progress signals.
• Walk tracking data: step counts, walk session progress, completion status, pauses, resumes, and related device permission status.
• Food and lifestyle entries: meals, snacks, cravings, hunger notes, recovery inputs, and other logs you choose to enter.
• Coaching and support data: messages, feedback, and notes associated with coaching or continuity support features when those features are part of your plan.
• Billing data: subscription plan, provider, product ID, renewal/cancellation status, receipt or transaction references, and payment events. Full card details are handled by payment providers, not stored by Emiko.
• Notification data: notification settings, push tokens or web push subscriptions, delivery/open/error logs, and interaction records where notifications are enabled.
• Technical and usage data: device, app surface, browser, IP-derived country, diagnostics, crash information, page or route views, button/event activity, and general product analytics used to keep the app working.
• Attribution data: campaign links, landing page, referrer, UTM parameters, Meta click/browser identifiers such as fbc/fbp, and event IDs used to measure whether ads and onboarding are working.

3. Why We Use This Data

• To personalize workouts, food guidance, cravings support, recovery suggestions, and daily recommendations.
• To adjust what the app shows you based on your onboarding and questionnaire answers over time.
• To calculate activity summaries, rep counts, calorie estimates, and other progress indicators.
• To operate subscriptions, payments, customer support, and account security.
• To improve product quality, debug issues, and understand whether features are working properly.
• To measure marketing and attribution, including whether a signup, trial, purchase, or page view came from an ad or campaign.
• To send push notifications, reminders, and progress nudges when you choose to enable them.

We do not sell your personal data as a list of names to advertisers. We do use analytics and attribution tools, including Meta, because otherwise we are flying the product and the ads with the lights off.

4. Analytics, Attribution, and Tracking

• PostHog: we use PostHog for product analytics, route/page events, feature usage, user properties such as role/profile completion, and session replay. Session replay is configured to mask inputs, so typed form content is not meant to be visible in recordings.
• Meta Pixel and Conversions API: on the website and web/PWA surfaces, we use Meta Pixel and backend Meta Conversions API to track page views, leads, registration, trials, subscription events, campaign attribution, fbc/fbp identifiers, and event IDs.
• Meta Android SDK: in the Android app, we use Meta App Events SDK for native app events and ad attribution.
• Meta iOS SDK: in the iOS app, we use Meta App Events SDK when configured, along with backend CAPI, for native app events and attribution.
• Google Tag Manager: public website pages, including legal pages, may use Google Tag Manager to manage analytics and marketing tags.
• Device advertising controls: on iOS, tracking may also depend on Apple's App Tracking Transparency prompt and your device settings. On Android and web, platform/browser controls may limit certain identifiers.

5. AI, Food, and Coaching Processing

Emiko uses AI and software models to generate food guidance, workout suggestions, cravings support, onboarding interpretation, and coaching-style responses. To do that, the app may send relevant text, logs, questionnaire answers, goals, and context to AI infrastructure such as Groq or other service providers we use.

• AI outputs are guidance, not medical diagnosis or treatment.
• Food, calorie, workout, and recovery suggestions are estimates based on available information.
• Human coaches or support staff may access relevant logs and notes if your plan includes coaching or if support is needed.

6. Who Can Access Your Data

Access is limited to the people and service providers needed to run Emiko.

• Internal access: authorized team members may access relevant account, questionnaire, and usage data for support, operations, and safety.
• Coaching access: if your plan includes human coaching or continuity support, relevant coaches may be able to view the logs and questionnaire information needed to support you.
• Vendors: hosting, database, storage, analytics, attribution, payment, auth, push notification, AI, email/support, and infrastructure providers may process data on our behalf.
• Payment providers: Dodo Payments for web billing, Google Play Billing for Android subscriptions, and Apple In-App Purchase for iOS subscriptions when enabled.
• Platform providers: Apple, Google, Firebase, browser push services, and Meta may process data according to their own terms and privacy notices when their services are used.
• Legal requirements: we may disclose data if required by law or if reasonably necessary to protect users, our team, or the service.

7. Retention, Deletion, and Subscriptions

We keep data for as long as needed to run your account, provide continuity, meet legal obligations, and resolve disputes.

• Account closure: if you request deletion, we will remove or anonymize personal data unless we need to retain some records for legal, billing, fraud-prevention, or security reasons.
• Server-side text data: questionnaire answers, logs, and coaching records may remain until they are deleted or anonymized under our retention process.
• Billing records: subscription, tax, refund, chargeback, and fraud-prevention records may be retained as required by law and payment-provider rules.
• Deleting your account is not the same as cancelling your subscription: if your subscription is managed by Apple, Google, or another payment provider, you may also need to cancel renewal directly through that provider.

8. Your Choices and Rights

• Access and correction: you can request access to the personal data we hold about you and ask us to correct inaccurate information.
• Deletion: you can request deletion of your account and personal data.
• Withdrawal from optional inputs: you can choose not to provide certain questionnaire or logging data, but some personalization features may then work less well or not at all.
• Device permissions: you can manage camera, Motion & Fitness, notifications, photos, and tracking permissions in your device settings.
• Marketing and analytics controls: browser settings, ad platform settings, cookie controls, and Apple/Android privacy controls may limit certain tracking signals.

9. App Store Privacy Summary

For Apple App Privacy purposes, Emiko may collect or process categories such as contact information, identifiers, purchases, user content, health/fitness-related information you provide, usage data, diagnostics, and advertising/attribution data. Some data may be linked to your account. Some data may be used for tracking when Meta, attribution, or advertising measurement is active and permitted by platform rules.

10. Important Limits

Emiko is a wellness product, not a medical provider. Data collected through the app is used to personalize your experience, not to diagnose or treat a medical condition.

11. Contact

For privacy questions, access requests, or deletion requests, contact:
connect.emikofit@gmail.com