Privacy Policy
Last Updated: February 14, 2026
Everline Holdings LLC (“we,” “us,” or “our”) operates the Kova mobile application, its companion Apple Watch application, and the withkova.com website (collectively, the “Service”). This Privacy Policy describes how we collect, use, store, and protect your information when you use the Service.
1. Information We Collect
Account Information
- Email address
- Name
- Account type (regular user or personal trainer)
- Profile photo (optional)
- Trainer bio and specializations (trainers only)
- Expo push notification token (for delivering notifications to your device)
Beta Waitlist Information
If you apply for beta access through our website, we collect the information you provide in the application form, including your name, email address, user type, fitness apps you currently use, fitness goals, logging frequency, and any optional details you share. This data is used solely to evaluate your application and contact you about beta access.
Body & Health Data
- Body weight and height
- Sex and date of birth
- Body measurements (chest, waist, hips, shoulders, neck, biceps, thighs, calves, body fat percentage)
- Fitness goals
- Dietary restrictions and preferences
- Progress photos
Fitness & Nutrition Data
- Workout logs (exercises, sets, reps, weight, duration, distance, RPE)
- Workout templates and schedules
- Custom exercises you create
- Food and nutrition entries (calories, macronutrients, meal type)
- Macro targets and TDEE calculations
- Water intake
- Restaurant nutrition lookups (chain restaurant data only — no personal data sent)
AI-Powered Food Recognition
When you use the photo-based food logging feature, photos of food you take or select are sent to Google's Gemini API (via our secure server) for nutritional analysis. The photo is processed to identify food items and estimate portion sizes. We do not store the photos on Google's servers — they are used for real-time analysis only and are subject to Google's API Terms of Service.
Food searches may also query the USDA Food Data Central API and Open Food Facts API. Only the search term or barcode is sent — no personal information is included in these requests.
Running & Location Data
- GPS route data during tracked runs (latitude, longitude, altitude, speed, timestamps)
- Pace, distance, elevation, and split data
- Personal records (fastest times, longest distances)
- Saved routes and route performance records
Location data is collected only during active run tracking — either on your phone or Apple Watch — and only when you have granted location permission. We do not track your location in the background outside of active runs.
Apple Watch Data
If you use the companion Apple Watch app, the following data may be collected on the watch and transmitted to your phone:
- Workout controls: Exercise name, set number, weight, and reps adjustments made on the watch
- GPS run data: Route coordinates, pace, distance, elevation, and splits from watch-tracked runs
- Heart rate and calories: Collected via HealthKit during watch-tracked runs
- Water intake: Amounts added via the watch
Data is transmitted between the watch and phone using Apple's encrypted WatchConnectivity framework. Watch-tracked run data (including GPS routes) is transferred to your phone for storage when a run is completed. The Apple Watch does not independently communicate with our servers.
Health Platform Data
With your explicit permission, the App may read from and write to:
- Apple Health (iOS): Steps, body weight, heart rate, active energy, workouts
- Health Connect (Android): Steps, body weight, heart rate, active energy, workouts
This integration is optional and requires your explicit consent through the platform's permission dialogs. Health platform data is used solely to sync your fitness data between the App and your device's health platform. Health sync settings are stored locally on your device and are not sent to our servers.
Third-Party Fitness Platform Data
With your explicit action, the App can sync activity data with the following third-party fitness platforms:
- Strava
- Garmin Connect
- Fitbit
When you connect a platform, the following data may be shared:
| Data | Strava | Garmin | Fitbit |
|---|---|---|---|
| Activity name & type | Yes | Yes | Yes |
| Start time & duration | Yes | Yes | Yes |
| Distance | Yes | Yes | Yes |
| Calories | Yes | Yes | Yes |
| GPS route & elevation | Yes | Yes | No |
| Heart rate | Yes | Yes | Yes (runs only) |
| Splits/laps | Yes | Yes | No |
| Workout exercise details | Yes (summary) | Yes (summary) | No |
Strava import: If you enable Strava import, the App can also retrieve your activity history from Strava (activity names, distances, durations, routes, heart rate, and calories) and store it as run logs.
Connecting to these platforms requires you to authenticate through each platform's own login screen. See Section 4 for details on how authentication tokens are handled.
Strava API usage monitoring: Strava may collect data about your use of Kova's Strava integration, including API usage metrics. This data is collected by Strava and is subject to Strava's Privacy Policy.
Motion & Sensor Data
- Step count data via device motion sensors (pedometer), used for daily step tracking
Reproductive Health Data (Primarily Local)
The App includes an optional reproductive health tracker. This data is stored on your device by default and is not transmitted to our servers. This includes:
- Menstrual cycle dates and flow intensity
- Basal body temperature readings
- Symptoms, mood, and discharge logs
- Sexual activity and contraception logs
- Pregnancy journal data (kick counts, contractions, appointments, weight)
- HRT/medication logs and lab results
- Menopause symptom logs (hot flash frequency and severity, symptom scales)
This data is encrypted on your device using keys stored in your device's secure enclave (iOS Keychain / Android Keystore). See Section 3 for details.
Voluntary sharing with a trainer or partner: If you explicitly choose to share cycle or pregnancy information with a connected trainer or partner, a limited summary (cycle phase and day, or pregnancy week and due date) is transmitted to our servers. This shared data auto-expires after 48 hours and is deleted immediately if you revoke sharing or disconnect. Full detailed logs (symptoms, temperatures, discharge, etc.) are never shared — only high-level summaries.
Optional encrypted cloud backup: You may choose to back up your reproductive health data to our servers. If you enable this feature, your data is encrypted on your device with a password you set before it leaves your device. We cannot read, decrypt, or access the contents of these backups. See Section 3 for details.
Messaging Data
If you use the messaging feature (trainer–client or partner communication):
- Text messages and their timestamps
- Shared images and voice notes
- Workout and nutrition summary cards shared in conversation
- Check-in prompts and responses
- Message reactions (emoji)
- Read status timestamps
You may enable auto-deletion of message history (30, 60, or 90 days) in your settings.
Subscription & Purchase Data
In-app purchases and subscriptions are processed through Apple's App Store or Google Play. We use RevenueCat to manage subscription status. RevenueCat receives your anonymized app user ID and purchase receipts from the app store — we do not receive or store your payment card details. See RevenueCat's Privacy Policy for details.
Analytics & Usage Data
We use PostHog to collect anonymous usage analytics to understand how the App is used and improve the experience. This includes:
- Screen views and feature usage patterns
- App performance data
- Device type, operating system, and app version
PostHog is configured to mask all text and images in session recordings and block sensitive fields (weight, height, email, coordinates, period data, messages, photos). You can opt out of analytics in the App's settings. See PostHog's Privacy Policy for details.
Device & Technical Data
- Device type and operating system
- App version and runtime version (for over-the-air updates via Expo)
- Camera access (for barcode scanning, progress photos, and AI food logging — only when you grant permission)
- Microphone access (for voice notes in messaging — only when you grant permission)
2. How We Use Your Information
We use the information we collect to:
- Provide and maintain the App's core functionality
- Store your workout history, nutrition logs, and progress data
- Display your progress charts and analytics
- Track running routes and compute pace, distance, and personal records
- Analyze food photos to estimate nutritional content (via Google Gemini API)
- Sync fitness data with Apple Health or Health Connect (with your permission)
- Sync activities to Strava, Garmin Connect, or Fitbit (with your explicit action)
- Import activities from Strava (with your explicit action)
- Count daily steps using device motion sensors
- Enable workout template sharing between users
- Enable trainers to view client data (with the client's explicit permission)
- Enable partner sharing of cycle phase and pregnancy summaries (with your explicit action)
- Send push notifications (workout reminders, hydration reminders, trainer assignment alerts)
- Process and manage in-app subscriptions (via RevenueCat)
- Authenticate your identity and secure your account
- Relay workout, run, and water data between your phone and Apple Watch
- Display maps for run tracking (via Google Maps)
- Analyze anonymous usage patterns to improve the App (via PostHog)
- Evaluate beta applications and contact applicants about beta access
We do not:
- Use your data for advertising
- Sell your data to third parties
- Share your data with third parties for marketing purposes
- Transmit reproductive health data to any server or third party (unless you explicitly enable encrypted cloud backup or share a cycle/pregnancy summary with a trainer or partner)
- Track your location outside of active run sessions
- Have access to your third-party fitness platform login credentials
- Store food photos used for AI analysis beyond the duration of the request
3. Data Storage & Security
Cloud Data
Most app data is stored on servers provided by Supabase (a cloud database provider). We use the following security measures:
- Row-Level Security (RLS): Database policies ensure you can only access your own data
- Permission-based trainer access: Trainers can only view client data for which the client has explicitly granted permission (workouts, nutrition, body stats, or photos — each controlled independently)
- Encrypted connections: All data transmitted between the App and our servers uses HTTPS/TLS encryption
- Authenticated access: All data requests require a valid authenticated session
- Private photo storage: Progress photos are stored in private, user-scoped storage buckets accessible only to you (and your trainer, if permitted) via time-limited signed URLs (1-hour expiry)
- Column mutation guards: Database triggers prevent unauthorized modification of relationship fields (e.g., trainer/client IDs)
- Sync metadata only: For third-party platform syncs, our servers store only sync metadata (which activity was synced, to which platform, and status) — not copies of your activity data
Local-Only Data (Reproductive Health)
Reproductive health data is stored on your device using encrypted SQLite:
- Encryption: Database encrypted via SQLCipher (AES-256)
- Key storage: Encryption keys stored in your device's secure hardware (iOS Keychain with
WHEN_UNLOCKED_THIS_DEVICE_ONLY, Android Keystore) - Biometric/PIN protection: Access requires Face ID, Touch ID, fingerprint, or a user-set PIN
- No cloud sync by default: This data does not leave your device unless you explicitly enable encrypted cloud backup or share a cycle/pregnancy summary with a trainer or partner
- iCloud/backup exclusion: The database file is excluded from device backups
- Screenshot protection: Screenshots are blocked while viewing reproductive health data
- User-controlled export: You may export this data as an encrypted file protected by a password you set, for device migration purposes only
Encrypted Cloud Backup (Reproductive Health — Optional)
If you enable cloud backup for your reproductive health data:
- Client-side encryption: Your data is encrypted on your device using a password you create before it is transmitted
- Zero-knowledge: We cannot read, decrypt, or access the contents of your backups — only you have the password
- Encryption details: PBKDF2-HMAC-SHA256 key derivation (100,000 iterations) with AES-256-GCM encryption
- Purpose: Backup and recovery only — encrypted backups are stored on our Supabase servers and are only retrievable by your authenticated account
- Deletion: Backups are deleted when you disable cloud backup or delete your account
Third-Party Platform Tokens
When you connect to Strava, Garmin Connect, or Fitbit:
- Authentication tokens are stored locally on your device in platform-native secure storage (iOS Keychain / Android Keystore) — they are not sent to or stored on our servers
- Exception: Garmin Connect uses OAuth 1.0a, which requires server-side request signing. Token exchange for Garmin is facilitated through our secure edge functions, but your Garmin credentials are never stored on our servers beyond the duration of the authentication exchange
- Token lifecycle: Tokens are automatically refreshed when they expire (Strava and Fitbit). All tokens are deleted from your device when you disconnect a platform or sign out of the App
- OAuth scopes: We request only the minimum permissions needed — activity read/write for Strava, activity and heart rate for Fitbit, and activity upload for Garmin
Apple Watch Data
- Data transmitted between your phone and Apple Watch uses Apple's encrypted WatchConnectivity framework
- The Apple Watch app does not independently communicate with our servers or any third party
- Health data collected by the Apple Watch (heart rate, calories) during runs is written to Apple Health on the watch and transmitted to your phone only as part of the run completion summary
4. Third-Party Services
The App uses the following third-party services:
| Service | Purpose | Data Shared |
|---|---|---|
| Supabase | Authentication, database, file storage, edge functions | Account and app data (excluding reproductive health data, unless encrypted cloud backup is enabled or cycle/pregnancy summary is shared) |
| Google Sign-In | Optional login method | Email, name (from Google) |
| Apple Sign-In | Optional login method | Email, name (from Apple) |
| Google Gemini API | AI-powered food photo recognition | Food photos (processed in real-time, not stored by us) |
| Open Food Facts | Food/nutrition database lookups | Search queries, barcode scans (no user-identifiable data) |
| USDA Food Data Central | Food/nutrition database lookups | Search queries (no user-identifiable data) |
| Google Maps | Map display for run tracking | Map tile requests with viewport coordinates (no user-identifiable data) |
| RevenueCat | Subscription and purchase management | Anonymized app user ID, purchase receipts from app stores |
| PostHog | Anonymous usage analytics | Feature usage events, device type, app version (PII masked, opt-out available) |
| Expo Push Notifications | Delivering push notifications | Expo push token, notification content |
| Expo Application Services | App updates (over-the-air) | Device platform, app version, runtime version |
| Apple Health / Health Connect | Optional health data sync | Steps, weight, heart rate, workouts (only with your explicit permission) |
| Strava | Optional activity sync & import | Run/workout data including GPS routes, heart rate, and exercise summaries (only with your explicit action) |
| Garmin Connect | Optional activity sync | Run/workout data including GPS routes and heart rate (only with your explicit action) |
| Fitbit | Optional activity sync | Run/workout summaries including duration, distance, and calories (only with your explicit action) |
Each third-party service has its own privacy policy governing how it handles data. In particular, data obtained from Strava is also subject to Strava's Privacy Policy. We encourage you to review the privacy policies of all connected services.
5. Trainer–Client Data Sharing
If you connect with a personal trainer through the App:
- As a client: You control exactly which data categories your trainer can view. You can independently enable or disable trainer access to: workouts, nutrition, body stats, progress photos, and cycle phase summaries. Your trainer cannot access your full reproductive health logs (symptoms, temperatures, discharge details, etc.) under any circumstances — only a high-level cycle phase summary if you explicitly enable it.
- As a trainer: You may view client data only for categories each client has explicitly permitted. Access is revoked immediately when a client changes their permissions or ends the relationship.
6. Partner Sharing
You may optionally link a partner account for mutual sharing. Partner sharing is controlled independently from trainer sharing. You can choose to share:
- Cycle phase (high-level summary only, auto-expires after 48 hours)
- Pregnancy summary (week and due date only)
- Workout activity
- Streak data
All partner sharing can be disabled at any time. Disconnecting a partner immediately revokes all shared data access.
7. Push Notifications
The App may send push notifications for:
- Workout reminders based on your schedule
- Hydration and meal reminders
- Trainer assignment alerts
- Message notifications
- Streak milestone celebrations
You can disable any or all notification categories within the App's settings. Your Expo push token is stored on our servers and deleted when you sign out or delete your account.
Notifications related to reproductive health use intentionally vague titles and descriptions to protect your privacy if your lock screen is visible to others.
8. Data Retention & Deletion
- Your cloud data is retained for as long as your account is active.
- Reproductive health data is retained on your device until you manually delete it through the App's data destruction feature or uninstall the App.
- Encrypted cloud backups of reproductive health data (if enabled) are retained until you disable cloud backup or delete your account.
- Shared cycle phase and pregnancy summaries auto-expire after 48 hours and are deleted immediately on disconnect.
- Message history is retained until you enable auto-deletion (30, 60, or 90 days) or delete your account.
- Beta waitlist data is retained until you are accepted or rejected, or until you request deletion.
- Third-party platform authentication tokens are retained on your device until you disconnect the platform or sign out.
- When you disconnect a third-party fitness platform (such as Strava) or request deletion of data obtained from that platform, we will delete the associated data from our systems within 48 hours.
- You may delete your account at any time through the App's Profile screen. Upon account deletion, all associated cloud data (workout logs, nutrition entries, progress photos, body measurements, push tokens, sync records, encrypted backups, messages, and profile information) will be permanently deleted from our servers.
- Workout templates you have shared with other users via share codes may persist in those users' accounts after your account is deleted.
- Data you have synced to third-party platforms (Strava, Garmin, Fitbit) is governed by those platforms' retention policies and is not deleted by us.
- To request account and data deletion outside the App, email us at the address in Section 14.
9. Your Rights
You have the right to:
- Access your data through the App at any time
- Update your personal information through the Profile screen
- Delete your account and all associated cloud data
- Delete your local reproductive health data independently via the App's data destruction feature
- Export your reproductive health data as an encrypted file
- Control which data categories your trainer or partner can view
- Revoke health platform (Apple Health / Health Connect) permissions at any time through your device settings
- Connect and disconnect third-party fitness platforms (Strava, Garmin, Fitbit) at any time
- Control sync direction (push, import, or off) for each connected platform
- Opt out of anonymous analytics in the App's settings
To exercise any of these rights, contact us at the email address below.
10. Children's Privacy
The App is not intended for use by anyone under the age of 13. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided us with personal data, please contact us and we will delete it.
11. Health Disclaimer
The App is a fitness tracking tool and does not provide medical advice. Workout suggestions, nutrition calculations (including TDEE and macro targets), AI-powered food recognition estimates, body composition data, cycle predictions, fertility window estimates, menopause symptom tracking, and pregnancy tracking features are for informational purposes only and should not be used as a method of contraception or medical diagnosis. Consult a qualified healthcare professional before beginning any exercise or nutrition program, and for all reproductive health decisions.
12. Beta Software Disclaimer
The App is currently in beta and provided on an “as-is” basis. While we implement the security measures described in this policy, beta software may contain bugs or vulnerabilities. To the fullest extent permitted by applicable law, we disclaim liability for any data loss, unauthorized access, or other damages arising from the use of pre-release versions of the App. By participating in the beta, you acknowledge and accept these risks.
13. Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of material changes by posting the updated policy within the App and on our website. Your continued use of the Service after changes are posted constitutes acceptance of the updated policy.
14. Contact Us
If you have questions about this Privacy Policy, your data, or wish to request account deletion, contact us at:
Everline Holdings LLC
Email: privacy@everlineholdings.com
This privacy policy applies to the Kova mobile application, its companion Apple Watch application, and the withkova.com website.