Privacy, plainly.

Vital Report (the “App”) is published by Neon Summit LLC (“we,” “us,” “our”), a Massachusetts limited liability company.

• Legal entity: Neon Summit LLC
• Mailing address: 1 Soares Farm Rd, West Bridgewater, MA 02379, United States
• Support email: support@neonsummit.co

Neon Summit LLC is the data controller for any personal information handled through the App.

This policy describes how the App handles information. It applies to the Vital Report iOS application, its widgets, its Siri/App Intents integration, Appointment Briefs, the limited product analytics described in §08 and §15, and any other features described in this policy. A handled-error diagnostics foundation exists in Vital Report source on GitHub; it is not in the currently shipping App Store binary and remains fully off (see §08).

It does not apply to third-party services you may independently use in connection with the App (such as Apple Health, iCloud, email, AirDrop, or another share destination), which are governed by their own privacy policies.

We want to be explicit about this because many health apps do the opposite. The App does not:

• Collect, upload, or transmit your Apple Health values, Appointment Brief context, or report contents to our servers. We operate no servers that receive that content.
• Use advertising identifiers (IDFA), the AppTrackingTransparency framework, SKAdNetwork, or any form of cross-app or cross-site tracking.
• Send Apple Health values, Appointment Brief context, report contents, export files, recipient information, or free-form notes to analytics providers. We use the limited product and subscription analytics described in §08 and §15 only to understand app flow, entitlement health, onboarding, and paywall performance.
• Build behavioral profiles about you.
• Sell, rent, or share your personal information for monetary or other valuable consideration.
• Use your health data or Appointment Brief content for advertising, marketing, or any purpose other than providing features you have asked for, as required by Apple’s HealthKit guidelines.

The App reads the following categories of information from your device with your explicit permission, and processes them locally on your device. Health values, Appointment Brief context, and report content are excluded from product analytics. They may leave your device through a share, print, save, or export destination you choose, including a destination you previously configured (see §07).

4.1  Apple Health & Fitness data

With your permission, the App reads categories you select, which may include: heart rate, resting heart rate, heart rate variability, blood oxygen, respiratory rate, body temperature, blood pressure, body mass and composition, steps, distance, active and resting energy, workouts, exercise minutes, stand hours, sleep analysis, menstrual and reproductive data, nutrition data, hydration, mindful minutes, and similar HealthKit categories supported by iOS.

The App reads this data to:

• Display dashboards, charts, trend lines, and your current-day values.
• Compute deterministic trends and notable changes for display in the App and in reports.
• Generate reports (PDF, CSV, JSON) that you review and choose where to send.
• Power Home Screen and Lock Screen widgets via a shared on-device container.
• Drive optional scheduled exports to destinations you configure.

4.2  Appointment Brief context

When you prepare an Appointment Brief, you may enter a visit reason, up to three questions for your clinician, and optional additional context. The App shows this content verbatim in a patient-authored section that is visibly separate from selected Apple Health observations.

4.3  Preferences and App state

The App stores settings on your device using iOS-provided mechanisms (UserDefaults, App Group containers, and the Keychain). This includes:

• Your chosen theme, default report format, selected metrics, dashboard preferences, and onboarding progress.
• Automation definitions (schedules you create for recurring exports).
• Subscription entitlement state reflected from Apple.
• A rate-limit counter for feedback submissions.
• Local aggregate product-usage counters used for privacy-safe reporting, such as onboarding completion, report/export events, and paywall views. These counters are stored on your device and are not automatically transmitted to us; they leave the device only if you choose an export path such as the test-build local analytics export described in §07.

Preferences, automation definitions, and cached health summaries stay on your device. Patient-authored Appointment Brief drafts are scoped to the report session and are not stored as reusable report metadata. The limited product analytics described in §08 and §15 may report that key app flows occurred, but do not include your stored settings, health values, Appointment Brief text, generated reports, or export contents.

When you use the in-app Send Feedback form (or the equivalent Siri/Shortcuts action), the App sends the contents of that form to a third-party email-relay service (“Web3Forms”) that delivers it to our support inbox at support@neonsummit.co. A feedback submission contains:

• A satisfaction rating and category you select.
• The free-text message you type.
• Your email address, if you choose to provide one (optional).
• App metadata useful for troubleshooting: App name, App version, iOS version, device model, and your subscription tier (e.g., Free or Pro).
• A timestamp.

If you email us directly at support@neonsummit.co, we receive the information you include in that email.

Vital Report Pro is sold through Apple’s In-App Purchase system and managed in the App with RevenueCat. When you buy a subscription or a lifetime unlock:

• Apple processes your payment. We do not receive your payment card, full name, billing address, or Apple ID.
• The App and RevenueCat receive App Store receipt and subscription lifecycle information that tells the App which product you own and whether it is still active.
• We use an app-specific, pseudonymous user ID for purchase validation, entitlement access, offerings, experiments, and subscription lifecycle analytics. We do not use your Apple ID, email address, or payment details for this ID.
• RevenueCat may forward subscription lifecycle events to PostHog so we can understand whether onboarding, paywall, trial, purchase, renewal, cancellation, refund, and entitlement flows are working. These events may include product, offering, entitlement, app version, platform, and app-specific user ID context, but not your health values, Appointment Brief context, report contents, export files, or payment card details.
• Apple provides aggregate commercial information through App Store Connect, such as total unit sales, refunds, and territories. This is Apple’s data, governed by Apple’s policies.

See Apple’s privacy policy at apple.com/legal/privacy for details. RevenueCat’s privacy policy is available at revenuecat.com/privacy.

The App includes features that let you move your data off-device to destinations you choose. A transfer happens because you tap a share, print, save, or export control, or because a previously configured scheduled automation runs.

• Files / iCloud Drive / AirDrop / Share Sheet / Email. The App hands a file you generated to iOS, which delivers it to the destination you pick. We do not see the contents.
• Appointment Brief review. The final one-page PDF is shown for review before share, print, or save controls become available.
• Widget data. Summaries used by the Home Screen and Lock Screen widgets are written to an on-device App Group container shared between the App and its widgets. The App does not transmit this widget data to Neon Summit or analytics providers.
• Scheduled automations. If you configure a recurring export, it runs on your device via iOS background task scheduling and delivers to the destination you previously configured, using the same mechanisms above.
• Local analytics export in test builds. In DEBUG and TestFlight builds, the App may let you share local aggregate analytics CSV/JSON files for reporting. These files contain coarse counts only, not health values, report contents, recipient information, identifiers, or free-form text, and leave the device only through the share destination you choose.

In all cases, you are the one choosing the destination, and your data leaves the device only along the path you selected or previously configured. Copies already shared, printed, or saved are controlled by the receiving destination and are not deleted when you remove the App.

To summarize, we use information only for the following purposes:

• Provide the App’s features you have requested (dashboards, Appointment Briefs, reports, widgets, exports, and automations).
• Process purchases and subscription entitlements through Apple.
• Respond to your support requests and improve the App based on your feedback.
• Evaluate privacy-safe product usage and subscription lifecycle events so we can understand whether onboarding, permissions, reports, exports, paywalls, offerings, trials, purchases, renewals, and entitlement flows are working.
• Protect the App against abuse (for example, rate-limiting feedback submissions).
• Comply with law, including Apple’s App Store Review Guidelines and applicable privacy laws.

We do not use your information for advertising, profiling, automated decision-making with legal effect, or any purpose not described in this policy.

8.1  Product analytics the App actually sends

Product analytics stay on by default. The Settings control is still labeled Share Anonymous Analytics. Turning it off stops app-sent PostHog product events. Onboarding discloses “Anonymous product analytics” as a privacy bullet; it does not include an analytics toggle. Continue does not change your analytics preference.

When sharing is on, the App sends named, allowlisted events through PostHog. Those events include onboarding step viewed or completed, HealthKit permission result, report and export actions, weekly rewind views, automation run results, paywall views, and offering or package context. App-side trial, purchase, and restore events are recorded locally only; subscription lifecycle events that reach PostHog come from RevenueCat as described in §06. Named events are tied to an app-specific, pseudonymous ID — not your Apple ID, email, or payment details.

Each named event also carries fields the App or the PostHog iOS SDK attach, and fields PostHog Cloud may add on receipt:

• App-stamped envelope: app_version and ios_version.
• PostHog SDK automatic context on those named events, including app name, version, and build; operating system name and version; device manufacturer, model, name, and type; screen size; locale; whether the device is on Wi‑Fi or cellular; and flags such as TestFlight, sideload, or simulator. The App does not send application-lifecycle autocapture events, screen-view events, or UI autocapture. Those SDK options are off in code.
• PostHog GeoIP enrichment. The App does not disable GeoIP. PostHog Cloud may derive approximate city, region, country, and timezone from the network address used to deliver the event. This is not GPS and is not Apple Health location data.

We do not use session replay, screen or UI autocapture, console or network capture, heatmaps, surveys, person profiles, advertising identifiers, native crash or exception autocapture, $exception events, captureException, dSYM upload, symbolicated stacks, or cross-app tracking.

8.2  Handled-error diagnostics foundation (not shipping)

While the foundation remains off, the App does not show a diagnostics consent screen, does not collect diagnostics consent, and does not emit handled-error diagnostic events. Vendor SDK opt-in follows product analytics only; diagnostics do not call optIn(). If a later approved release ever activates the foundation, events would be coded IDs only (not health values, error text, paths, or stacks), would stay off until a user-visible control appears, and would still require product analytics to be on. That activation has not happened.

Where the EU or UK General Data Protection Regulation applies, we rely on the following legal bases:

• Consent — for reading Apple Health data and for transfers to share or export destinations you choose. You may withdraw Health access at any time in iOS Settings → Privacy & Security → Health.
• Performance of a contract — to deliver the App, including subscription features you have purchased.
• Legitimate interests — to respond to support requests, evaluate privacy-safe product analytics and subscription lifecycle events, prevent abuse, and maintain the security and integrity of the App. Where we rely on legitimate interests, we have assessed that these interests are not overridden by your rights and freedoms.
• Compliance with legal obligations — where we must process information to meet a legal requirement.

• Apple Health data is stored by Apple on your device and in your iCloud (if you have iCloud Health sync enabled). The App reads it through the HealthKit API; the App does not maintain its own copy on any server.
• Preferences, automations, and cached summaries are stored locally on your device.
• Appointment Brief drafts are processed in the current report session. Generated reports you save remain in the App or destination you selected until you delete them there.
• Feedback submissions are transmitted over HTTPS to Web3Forms, which delivers them to our support inbox. Retention at Web3Forms is governed by their policy.
• Product analytics and subscription lifecycle events are transmitted over HTTPS to PostHog and RevenueCat. These services receive the named events, app-stamped envelope, SDK automatic context, and (for PostHog) GeoIP enrichment described in §08, plus the product, entitlement, and app-specific user ID context described in §06 — not health values, Appointment Brief context, report contents, export files, or payment card details. Handled-error diagnostics are not transmitted from the shipping App Store binary.
• Support emails are stored in our email provider’s systems for as long as needed to respond and maintain a reasonable support history.

We use HTTPS/TLS for the limited network traffic described in this policy and rely on iOS App Sandbox and device-protection mechanisms for local app data. No system is perfectly secure, and these protections do not control copies you choose to share, print, or save elsewhere.

• On-device App data generally persists for as long as the App is installed. Deleting the App removes its app-container data, but does not delete Apple Health data, App Store purchase history, or copies you previously shared, printed, or saved elsewhere.
• Apple Health data is governed by iOS and Apple Health’s own settings, not by us. Revoking HealthKit access or deleting health data is done in iOS Settings → Privacy & Security → Health, or in the Apple Health app.
• Feedback submissions and support correspondence are retained for as long as reasonably necessary to respond, maintain a support history, resolve an open issue, or comply with a legal obligation. We review and delete support records when they are no longer needed for those purposes.
• Product analytics and subscription lifecycle events are retained in PostHog and RevenueCat according to our account settings and those providers’ retention practices. These records are keyed to an app-specific, pseudonymous ID, not your Apple ID, payment card, health data, or report contents.

You have strong control over your data in the App:

• Revoke HealthKit access at any time: iOS Settings → Privacy & Security → Health → Vital Report.
• Delete the App to remove its app-container data, including stored preferences, automation definitions, cached widget data, and reports stored only in the App. This does not remove Apple Health data, purchase history, or copies you shared, printed, or saved elsewhere.
• Manage, cancel, or request a refund for your subscription: iOS Settings → [Your Name] → Subscriptions, or at apps.apple.com/account/subscriptions.
• Turn off optional product analytics with the Share Anonymous Analytics toggle in the App’s Privacy settings. Product analytics stay on until you turn that control off. This stops app-sent PostHog product events. It does not disable Apple or RevenueCat processing needed to complete purchases, determine eligibility, restore purchases, or manage entitlements. RevenueCat may continue forwarding subscription lifecycle events to PostHog using the app-specific pseudonymous ID described in this policy. The shipping App Store binary does not show a separate diagnostics toggle, and turning analytics off does not imply that diagnostics were ever on.
• Contact support at support@neonsummit.co for any other data request.

Depending on where you live, you may have additional rights under applicable law (see §13 and §14 below). To exercise any such right, email support@neonsummit.co. We will verify your request using the email address it was sent from, respond within the timeframes required by law, and will not discriminate against you for exercising any right.

If you are a California resident, the California Consumer Privacy Act, as amended by the California Privacy Rights Act, gives you the following rights:

• Right to know what personal information we have collected about you and how we use it.
• Right to delete personal information we have collected from you, subject to certain exceptions.
• Right to correct inaccurate personal information.
• Right to opt out of sale or sharing of personal information.
• Right to limit use of sensitive personal information.
• Right not to be discriminated against for exercising these rights.

The categories of personal information we may receive (as defined in the CCPA) are:

• Identifiers — the email address you voluntarily provide in feedback, and app-specific pseudonymous IDs used for analytics, purchase validation, and subscription entitlement access.
• Internet or other electronic network activity — limited product interaction events such as onboarding progress, permission flow, report/export actions, paywall views, app version, iOS version, PostHog SDK automatic app and device context, and subscription lifecycle events.
• Geolocation — approximate city, region, country, and timezone that PostHog may derive from the IP used to deliver product-analytics events. This is not GPS and is not Apple Health location data.
• Sensory or health information — only processed on your device, never received by us.
• Inferences — we do not derive inferences about you on our servers; on-device health insights are not transmitted.

To exercise your rights, email support@neonsummit.co. You may also authorize an agent to make a request on your behalf; we will require reasonable verification.

In addition to the rights described in §12, if you are located in the European Economic Area, the United Kingdom, or Switzerland, you have the right to:

• Access the personal information we hold about you.
• Rectify inaccurate or incomplete information.
• Erase your information (“right to be forgotten”), subject to legal retention requirements.
• Restrict or object to certain processing.
• Data portability — receive your information in a structured, machine-readable format.
• Withdraw consent at any time (without affecting processing done before withdrawal).
• Lodge a complaint with your local data protection authority. A list of EU authorities is available at edpb.europa.eu. UK users may contact the Information Commissioner’s Office.

To exercise these rights, email support@neonsummit.co.

The key third parties that may receive information in connection with the App, and what each one receives, are:

Destinations you choose through Apple’s share, print, save, or export interfaces may also receive the content you direct to them. Their handling is governed by their own terms and privacy policies.

Neon Summit LLC is based in the United States. If you are outside the United States, information described in this policy — including feedback or support email you send us, and product-analytics events delivered to PostHog and RevenueCat — will be transferred to and processed in the United States. For transfers from the EEA, UK, or Switzerland, we rely on appropriate safeguards where required, including Standard Contractual Clauses with our service providers where applicable.

Vital Report is not directed to children under the age of 13 (or the equivalent minimum age in your jurisdiction, such as 16 in parts of the EEA). We do not knowingly collect personal information from children. Apple Health itself imposes age-based limits on certain data categories. If you believe a child has provided us with personal information, please contact support@neonsummit.co and we will delete it.

We may update this Privacy Policy from time to time to reflect changes in the App, in our practices, or in applicable law. When we make a material change, we will update the “Last Updated” date at the top of this page, and — for significant changes that affect how we handle your information — we will provide notice within the App or through another reasonable means before the change takes effect. Your continued use of the App after a change becomes effective means you accept the updated policy.

Questions, requests, or concerns about this Privacy Policy or our data practices can be directed to:

Neon Summit LLC
Attn: Privacy
1 Soares Farm Rd
West Bridgewater, MA 02379
United States
Email: support@neonsummit.co