Privacy Policy

Updated November 13, 2026

1. WHO WE ARE AND WHAT THIS POLICY COVERS

LifeWave, LLC (“LifeWave,” “we,” “us,” or “our”) provides my ECG Pro and its related website and support services. This policy explains how information is handled when you browse our website, use the app, connect Apple Health (iPhone) or Health Connect (Android), import a document, request AI Insights, purchase a subscription, or contact us. “Personal information” means information about an identified or identifiable person. “Health information” includes ECG recordings, symptoms and other information relating to health, including relevant inferences.

Contact us at support@cardiobyte.app or LifeWave, LLC, 2292 Faraday Ave, Suite 63, Carlsbad, CA 92008, USA. Where data protection law uses the term, LifeWave is the controller for processing whose purposes and means we determine. Apple, Google and other providers may separately control information they process for their own services.

This policy describes the app and services; it does not replace the notices of Apple Health, Health Connect, the App Store, Google Play, your healthcare provider, or services you independently choose when exporting information. Accepting our Terms does not by itself provide consent to optional analytics or disclosure of health information for AI processing.

2. INFORMATION YOU ENTER OR IMPORT

Profile and preferences. You may enter your name and birth year and choose display, context and other preferences. These settings are stored on your device. Profile information may appear in a report you generate. Please check a report before sharing it.

Journal and recordings. The app handles ECG dates, waveforms and associated measurements, recorded rhythm classifications, symptoms, activities, notes, flags and other context you choose to record. Imported ECG PDFs or images may contain a name, date of birth, provider details or other information embedded in the document. The app saves the original imported file locally. Optional date recognition for supported imports runs on your device; a suggested date is not a verified clinical finding.

Support. When you email us, we receive your email address, message, attachments and information you voluntarily provide. We may ask for the app version, device model, operating system and a description of the issue. Do not send passwords, full payment details or health records unless they are necessary to your request. Where possible, remove identifying details from screenshots.

3. APPLE HEALTH ACCESS (IPHONE)

With your permission, my ECG Pro reads selected information from Apple Health to display recordings and health context. Depending on your permissions and available data, categories can include ECGs; heart rate, resting and walking heart rate, heart-rate variability and rhythm alerts; workouts, steps, movement, distance, energy, exercise and standing; sleep and mindful sessions; nutrition, water, caffeine and alcohol; blood pressure, glucose, oxygen saturation, respiratory rate, temperature, fitness estimates and birth information.

The app may also save journal or symptom information to Apple Health with write permission. In the current implementation, journal entries are stored using HealthKit mindful-session records with associated metadata. Information written to Apple Health can become available to Apple and other apps according to your Apple Health permissions and settings.

You control access through Apple Health and your device settings. Refusing or withdrawing permission can limit related features. Withdrawal prevents future authorized access; it does not automatically erase information already imported, previously shared, stored in backups or retained by another service. Delete Apple Health records through Apple Health where appropriate. Removing the app does not delete your Apple Health history.

We do not use Apple Health data for advertising, marketing profiles or data brokerage. Access to health information is not permission to sell it or use it for unrelated purposes.

On Android, the app reads from Health Connect instead of Apple Health; see section 14.

4. OPTIONAL AI INSIGHTS: WHAT LEAVES YOUR DEVICE

AI Insights is optional and uses a separate in-app disclosure and agreement before submitting the selected information. Requests are sent through Google Firebase infrastructure to OpenAI to generate informational observations. The submitted information includes the complete image of the selected ECG strip, its date, average heart rate, recorded rhythm, selected symptoms and activities, your questions and recent conversation context. The strip image contains your ECG waveform even though raw numeric waveform samples are not sent as a separate array.

The structured request excludes your profile, internal record identifiers and free-text journal notes. This is data minimization, not a guarantee of anonymity: dates, health details, the image and anything you type may still identify you. Avoid adding names, contact information, account numbers or information about another person. AI responses may contain health-related inferences and may be inaccurate.

Firebase creates an anonymous service identity to authenticate requests. “Anonymous” means you do not need to give that service a name or email to use this flow; it does not mean that technical identifiers cannot be associated with a device or activity. Security controls validate app requests and maintain request counts and timing to limit abuse. Internet services also necessarily process connection information, such as an IP address.

Our request is configured not to store the response as retrievable OpenAI application state. This is not a promise of zero retention. OpenAI may retain content in abuse-monitoring logs, generally for up to 30 days under its default API controls, with exceptions for legal or safety reasons; other limited technical processing may apply. Its API data is not used for model training by default. See https://developers.openai.com/api/docs/guides/your-data for its current controls. We have not represented that a special zero-retention arrangement applies.

You can decline Insights and continue using available non-AI features. Stop submitting requests to stop future AI disclosures. Withdrawal cannot recall processing that has already occurred. Contact us about information already submitted. Insights does not make decisions about treatment, insurance, employment or eligibility and is not a substitute for professional assessment.

5. OPTIONAL ANALYTICS, CRASH AND PERFORMANCE DATA

If you allow analytics, the app uses Google Firebase Analytics, Crashlytics and Performance to understand feature usage, diagnose failures and measure performance. This can include app and operating-system versions, device characteristics, installation or service identifiers, screen names, fixed feature events, crash diagnostics and operation timing. Examples of feature events include opening a report, submitting a search or starting Insights; the event does not include the search text or the report itself.

Our custom analytics events exclude ECG recordings, symptoms, journal text, profile details, imported filenames and chat content. Sanitized operation labels are used for custom failure reports. Diagnostic metadata can still be personal information; we do not describe all telemetry as anonymous.

This reporting is optional and can be changed in Profile. Turning it off disables future optional collection through these controls, resets local analytics data and deletes unsent crash reports. It does not automatically delete information already transmitted. Essential subscription verification, security and a requested AI operation are separate from this optional analytics choice. Advertising storage and personalization consent are disabled in the app’s current telemetry configuration. On Android, the app does not use the Android advertising ID and removes the advertising-ID permission.

6. PURCHASES AND SUBSCRIPTIONS

Apple processes App Store payments and Google processes Google Play payments. We do not receive your full payment-card number through an App Store or Google Play purchase. Apple or Google, and Adapty, provide purchase and subscription functionality, including product and transaction information, subscription status, renewals, expiration, restoration and technical profile or device identifiers needed to manage access. Adapty also supports presentation and evaluation of purchase screens.

The current Adapty configuration disables advertising-identifier and IP-address collection options. That setting does not mean that no technical data is processed by the provider or network. The app does not send your ECG records, journal content or profile name to Adapty as part of the purchase integration. Apple’s, Google’s and Adapty’s privacy notices describe their respective services.

7. WEBSITE AND COOKIES

Our website is hosted with Webflow. Visiting it involves processing technical connection and browser information, including IP address, requested pages, time, browser and device information, and information needed to deliver content and protect the website. Necessary storage or cookies may support site operation. Following an external link takes you to a service with its own practices.

Browser controls can restrict or delete cookies; this can affect site features and does not control the app’s separate analytics settings. Any nonessential website tracking must be assessed and, where required, offered through an appropriate consent mechanism before activation. This draft does not claim that a particular advertising pixel, analytics tag or consent-management platform is currently installed.

8. WHY WE PROCESS INFORMATION

We process information to provide the features you request; display and organize your records; create exports; generate optional Insights; verify purchases; respond to support requests; maintain security and reliability; investigate misuse; comply with legal obligations; and resolve disputes. Optional telemetry helps us prioritize improvements without including the health content listed above.

Where the GDPR or similar law applies, ordinary service processing may rely on performance of our agreement, legal obligations or legitimate interests in security and support, as appropriate. Optional processing relies on consent when required. Health data receives additional protection: we rely on explicit consent or another specific legal condition that actually applies, rather than treating ordinary contractual necessity as sufficient authorization for sensitive health processing. You may withdraw consent without affecting the lawfulness of earlier processing.

9. DISCLOSURES AND SERVICE PROVIDERS

We disclose only information appropriate to a purpose described here. Relevant recipients include Apple for Health and App Store services; Google for Health Connect, Google Play billing, Play Integrity and on-device ML Kit features; Google/Firebase for requested AI infrastructure, authentication, security and optional telemetry; OpenAI for requested Insights; Adapty for subscriptions and purchase screens; Webflow for website hosting; and the email service used to handle your support correspondence. Their roles and the information they receive differ; these providers do not all receive your health records.

A report is shared with a recipient only when you choose a sharing destination. Email, cloud drives, messaging services and clinicians then handle the copy under their own arrangements. We cannot recall that copy or control the recipient’s later use.

We may disclose information when legally required, to respond to valid legal process, protect rights or safety, investigate fraud or security incidents, or obtain professional advice under appropriate confidentiality obligations. A proposed merger or business transfer may require limited due diligence or transfer of necessary records, subject to applicable restrictions and notice requirements. This does not authorize an unrestricted sale of health information or override a required consent.

LifeWave does not sell your personal or health information. We do not provide health information for targeted advertising or cross-context behavioral advertising. Any materially different future use would require an updated notice and any additional permission required by law.

10. RETENTION AND DELETION

Different categories are retained differently. Locally imported files and profile preferences remain until you remove them or the relevant app data. Apple Health data follows your Apple Health controls, and Health Connect data follows your Health Connect controls. Your device or operating-system backup settings can preserve copies independently of this app; uninstalling the app is not a request to erase every copy held elsewhere.

Our Insights backend is designed to process health requests without maintaining a permanent library of your ECGs or conversations. Security and quota records retain service identifiers, counts and timing separately from health payloads. Provider diagnostics and AI records have their own retention rules. Support correspondence is retained for handling the issue and necessary follow-up; transaction records may need to be kept for accounting, fraud prevention and legal obligations.

Retention is limited according to the purpose, sensitivity, operational need and applicable legal requirements. Information subject to a legitimate legal hold may be retained longer. We do not promise a single deletion period for every category. Upon a valid request, we will delete or de-identify information we control where required and direct relevant processors to act, subject to lawful exceptions and applicable backup-deletion rules. We will explain material limitations that affect your request.

11. SECURITY AND INTERNATIONAL PROCESSING

We use technical and organizational safeguards appropriate to the service, including protected network connections, access controls, app-request validation and device file-protection features. No device, network or storage system is completely secure. Protect your device and your Apple Account or Google Account, keep software updated, and review recipients before sharing a health report.

LifeWave is based in the United States. The current AI backend runs in a United States region, and providers may process information in other countries. Protections and government-access rules may differ from those where you live. Where legally required, transfers need an applicable safeguard, such as approved contractual terms, or another valid transfer mechanism. Contact us for information about safeguards applicable to your data. This policy does not itself create a transfer agreement or claim a certification.

If a security incident creates notification obligations, we will provide the notices required by applicable law. The app is a consumer health tool; this policy does not promise that every use or provider relationship is covered by HIPAA or a business associate agreement.

12. YOUR CHOICES AND PRIVACY REQUESTS

You can manage Apple Health or Health Connect permissions, choose whether to use Insights, change optional analytics in Profile, edit available profile and journal fields, delete supported imported records and choose whether to export a report. To request access, correction, a copy, deletion, restriction, objection or consent withdrawal for information LifeWave controls, email support@cardiobyte.app with “Privacy request” and describe the request and the service involved.

Do not include an ECG or identity document in the first message. We may need proportionate verification and details that help locate the relevant records. We will not require more information than reasonably necessary. An authorized agent may make a request where allowed, subject to verification of their authority. Device-only data may not be accessible to us; we can explain the available device controls instead of claiming to retrieve it from a company database.

We respond within the period required by the law that applies. If we cannot fulfill a request, we will explain the reason and available review or appeal process. Exercise of a privacy right will not result in unlawful discrimination, although withdrawing information necessary for a particular feature may prevent that feature from working.

13. REGIONAL AND CONSUMER HEALTH RIGHTS

California and other United States residents may have rights to know or access data, correct it, delete it, obtain a portable copy, and opt out of certain uses where the applicable statute covers our processing. California law can also provide rights concerning sensitive information and authorized agents. The categories, sources, purposes and recipient types are described above. Where applicable, California requests generally receive a response within 45 days, with a permitted extension explained to you. We do not sell or share information for cross-context behavioral advertising as described above. We will honor legally applicable preference signals for processing to which those signals apply.

Consumer health laws, including Washington’s My Health My Data Act where applicable, may provide additional rights to confirm collection, access health data, receive information about recipients, withdraw collection or sharing consent, and request deletion. The health-data categories are in sections 2–4; sources are you, your permitted Apple Health or Health Connect connection and generated feature outputs; purposes and recipient categories are described in sections 4, 8 and 9. We do not sell consumer health data. Submit requests or an appeal to the privacy email above. If an appeal is denied, you may contact your state attorney general, including the Washington Attorney General at https://www.atg.wa.gov/.

If European Economic Area, United Kingdom or Swiss data-protection law applies, you may request access, rectification, erasure, portability or restriction, object to processing where available, withdraw consent and complain to your competent supervisory authority. You do not have to contact us before making a regulatory complaint. Regional rights and exceptions depend on the applicable law; this section does not assume every statute applies to every user.

14. ANDROID APP: HEALTH CONNECT, GOOGLE PLAY AND ANDROID DATA FLOWS

This section applies to my ECG Pro for Android (package com.lifewave.ecgpro). Except where this section says otherwise, the other sections of this policy apply to the Android app in the same way as to the iPhone app.

14.1 ECGs on Android come from files you import. Health Connect does not store ECG recordings, so the Android app does not read ECGs from your watch or phone. You add ECGs by importing a PDF or image, taking a photo of a paper ECG, or sharing a file into the app. The original file and the details you enter are stored in the app's private storage on your device. Optional date suggestions are produced on your device using Google ML Kit text recognition; the file is not uploaded for this. The app's search can use Google's on-device Gemini Nano model through ML Kit, where your device supports it, to interpret a search phrase; your search and records are processed on the device and are not sent to us.

14.2 Health Connect. With your permission, the app reads the following from Health Connect to show context around a recording and, if you choose, in a PDF report: heart rate; heart rate variability (RMSSD); steps; exercise sessions; sleep sessions; nutrition (including caffeine); hydration; blood pressure; blood glucose; oxygen saturation; respiratory rate; body temperature; and skin temperature. The app also asks for permission to read data older than 30 days, because imported ECGs are often older than that; it reads only the time window around each recording that you view or include in a report.

• The app only reads from Health Connect. It does not write, change or delete Health Connect data.
• Health Connect data is read on demand and shown on your device. It is not sent to LifeWave, Firebase, Adapty or any analytics service. It leaves your device in only two cases, both started by you: inside a PDF report that you create and choose to share, and, if you use optional AI Insights and agree on its consent screen, as a single "activity at onset" label for the selected recording (see 14.4).
• The "activity at onset" label (Resting, Light or Moderate/Vigorous) is worked out on your device from the step counts in the 5 minutes before the recording, unless you selected an activity yourself in the journal. The step counts themselves are never sent.
• You choose which categories to allow, and you can change or revoke access at any time in Health Connect (Settings → Apps → Health Connect, or the Health Connect app). Revoking access stops future reads; it does not delete data held by Health Connect or by the apps that wrote it.
• Health Connect does not provide ECGs, AFib history, heart-rhythm or heart-rate notifications, or your date of birth, so those iPhone features are not available on Android.

Google's Health Connect requirements. Our use of information received from Health Connect follows the Health Connect Permissions policy, including its Limited Use requirements. We use Health Connect data only to provide the features described here. We do not use it for advertising, do not sell it, do not use it to determine credit-worthiness or for lending, and do not let people read it except with your affirmative agreement (such as sharing a report), where needed for security, or to comply with law. We do not transfer it to data brokers or use it to train generalized AI models.

14.3 Device storage and backup. Android app data is stored in the app's private storage and is excluded from Android cloud backup and device-to-device transfer (the app turns backup off). As a result, uninstalling the app or moving to a new phone does not carry over your recordings and journal unless you export them yourself, for example as a PDF report. Profile → Your data → Delete all app data removes the app's local data and its anonymous Insights sign-in.

14.4 Optional AI Insights on Android. Section 4 applies. On Android the request is sent through Google Firebase (Cloud Functions in a United States region, Firebase Authentication with an anonymous account, and Firebase App Check using Google Play Integrity to confirm the request comes from the genuine app) to OpenAI. After you agree to the in-app Insights disclosure, a request contains: one image of the selected ECG page (for an imported photo, this is your image of the ECG, after the app blacks out text that looks like a name or identifier and any areas you cover in the preview), its date and time, the average heart rate and rhythm label you entered or confirmed from the report (if any), the activity at onset (see 14.2), the symptom and activity tags you selected, your questions and up to eight recent conversation turns, and your Adapty profile identifier so the server can confirm your subscription. It does not include any other Health Connect data (no heart-rate, step, sleep or other readings), your profile name or birth year, free-text journal notes or the original imported file. The app checks your messages and blocks sending text that appears to contain your profile name or contact details.

14.5 Optional analytics and crash reports on Android. Section 5 applies. Firebase Analytics and Crashlytics are switched off when the app is installed and are turned on only if you choose Allow Analytics (you can change this in Profile → Privacy at any time). The Android app does not use Firebase Performance Monitoring. The app removes the Android advertising-ID and Privacy Sandbox advertising permissions and sets Google's advertising consent signals to denied. Google ML Kit's on-device features may send Google limited diagnostic and usage information (such as API performance and device type) under Google's terms; this does not include your ECGs, journal or Health Connect data.

14.6 Google Play purchases. Subscriptions on Android are purchased and billed through Google Play. Google processes your payment and account information under its own privacy policy; we do not receive your payment-card number. To grant and restore Premium access, the app and Adapty receive information about the purchase from Google Play, such as the product, purchase token, order and subscription status, renewal and expiry dates, and technical device and profile identifiers. Adapty also receives real-time notifications from Google Play about subscription changes. Advertising-ID and IP-address collection options are disabled in our Adapty configuration. Manage or cancel your subscription in Google Play (Play Store → Profile → Payments & subscriptions). The app may ask Google Play to show a rating prompt; Google handles any rating or review you submit.

14.7 Android permissions. Besides Health Connect, the app uses internet access to support optional Insights, purchases and optional analytics. It uses the system photo picker, file picker and camera app to import ECGs, which give the app access only to the file or photo you choose. It does not request location, contacts, microphone or broad storage access.

14.8 How to delete your data (Android). This is the page Google Play links to for data deletion.

• In the app: delete a single ECG or journal entry from its screen, or delete everything in Profile → Your data → Delete all app data. This removes imported files, the journal, saved Insights chats, your profile and preferences from the device, and deletes the anonymous Insights account on our server too.
• Uninstalling the app also removes its data from the device (the app does not use Android backup).
• Data held by us or our providers: to ask us to delete information we or our providers hold (for example, information already submitted through Insights, subscription records, or opted-in analytics), email support@cardiobyte.app with "Privacy request" in the subject. Purchase records that Google Play or the law requires us to keep may be retained.
• The app has no user accounts, so there is no account to delete.

15. CHILDREN, CHANGES AND CONTACT

The service is intended for adults and is not directed to children under 13. We do not knowingly collect children’s personal information through our online services without legally required authorization. If you believe a child has submitted information, contact us so we can investigate and take appropriate action. An App Store or Google Play age rating is a content rating and is not a statement that the app is clinically appropriate for a child.

We may update this policy as features, providers or legal requirements change. We will update its date and provide additional notice or seek a new consent where required. A policy update does not retroactively authorize an incompatible use of previously collected health information.

Privacy contact: support@cardiobyte.app
LifeWave, LLC
2292 Faraday Ave
Carlsbad, CA 92008, USA