Ore Washington Consumer Health Data Privacy Policy

Effective date: October 11, 2026

This separate Consumer Health Data Privacy Policy describes how 0xdesigner LLC, doing business as Ore ("Ore"), processes consumer health data subject to the Washington My Health My Data Act. Ore's general Privacy Policy describes its other personal-information practices.

Categories of consumer health data collected

Ore may collect the following categories of consumer health data:

• Meal and dietary information: meal descriptions, voice recordings (sent for transcription and not stored), voice transcripts, selected meal photos, foods, portions, eating times, saved or usual foods, calories, macronutrients, corrections, and dietary patterns.
• Body and plan inputs: sex, age, height, weight, activity level, training frequency, goals, and time zone, plus optional body-fat estimates or target weights retained from earlier app versions if the consumer previously provided them.
• Derived or inferred information: nutrition estimates, energy needs, calorie and macronutrient targets, plans, trends, and inferences about dietary habits or physical-health goals.
• Optional Apple Health information: when the consumer chooses to connect HealthKit, Ore reads available body mass, steps, Active Energy, daily Activity Summary information, and workouts on the consumer's device to suggest confirmable onboarding answers, show steps, and calculate a bounded positive Calorie credit (internally called Activity Fuel). If comparable full-day energy history is not available, Ore may use steps and the consumer's confirmed program weight to make a conservative walking-energy estimate. Raw HealthKit samples, individual workout and Active Energy records, Activity Summary information, and source details remain on the device. If a Health weight seeds the editable weight question, Ore stores it only after the consumer confirms it as a program answer. Ore also stores the derived daily step total for each synced day, plus the local date, derived Calorie credit amount and carbohydrate grams, calculation version, and timing of the Calorie credit. For program creation with Apple Health connected, Ore also collects derived summaries of typical steps, recorded workout days, weight-measurement availability, and typical active calories with the count of qualified observed days. If the consumer separately turns on Export data to Apple Health, Ore writes the calories, protein, carbohydrates and fat of meals logged afterwards to HealthKit on the device and, while the switch stays on, updates or removes them when the meal is edited or deleted. Entries already written stay in Apple Health after the switch is turned off or the Ore account is deleted, until the consumer deletes them in the Health app. This happens on the device and sends nothing new to Ore's servers.
• Health-feature activity: pending drafts and technical or usage records linked to the use, performance, security, or reliability of Ore's meal and nutrition features.
• Identifiers associated with health data: internal account and request identifiers, Apple account identifier and email or relay address, IP address, and device, app, operating-system, and technical information linked to the consumer's use of Ore's health features.
• Support information: consumer health data that a consumer voluntarily includes in a support request or attachment.

Purposes for collection and use

Ore collects and uses these categories to provide the meal logging, nutrition estimation, diary, saved-food, trend, and nutrition-plan services requested by the consumer; personalize and maintain those services; authenticate and secure the account; process and troubleshoot requested features; provide support; prevent fraud or abuse; comply with law; and establish, exercise, or defend legal claims.

Ore does not sell consumer health data.

Categories of sources

Ore obtains consumer health data:

• Directly from the consumer through text, speech, selected photos, corrections, plan answers, settings, and support communications.
• From the consumer's device when the consumer chooses to use camera, photo, or speech features.
• From Apple Health on the consumer's device when the consumer affirmatively connects HealthKit. Each available data type is used independently, and the consumer can change access in Apple's Health or Settings app.
• From Sign in with Apple for the account identifier and any name or email the consumer chooses to share.
• Automatically from the app, device, and Ore's servers when the consumer uses a meal, nutrition, plan, security, or support feature.
• By deriving estimates, targets, plans, trends, or other outputs from consumer submissions.
• From service providers that return requested AI analysis, speech transcripts, or nutrition information.

Categories of consumer health data disclosed

As needed to provide requested services, operate Ore, or comply with law, Ore may disclose:

• Meal text, voice transcripts, selected meal photos, and prior draft or logged-meal items when the consumer requests a revision to AI routing and inference providers. For a morning Insight, Ore also discloses the consumer's nutrition goal and daily calorie, protein, carbohydrate, fat, and fiber targets; up to the last 28 days of confirmed meals, including titles, confirmed ingredients and portions, and calories, protein, carbohydrates, fat, and fiber per meal; dietary restrictions entered in onboarding; and the headlines and suggested actions from Ore's recent Insights. When Apple Health is connected, Ore also discloses the daily step total and derived Activity Fuel calorie credit for each of those days. Ore does not disclose raw HealthKit samples, workouts, Active Energy, Activity Summary details, source details, the consumer's name or email, Apple identifiers, sex, age, height, weight, or payment information for Insights. Direct target adjustments use software calculations. The model returns a headline, a short paragraph, and one "Try this" suggestion. Ore checks the text against fixed rules for medical claims, diagnoses, medication guidance, dietary restrictions, and data or system language, and does not show it if a check fails.
• For optional Health-informed program creation, separate expanded permission allows structured profile answers and compact summaries from up to 28 completed days to be sent to Google Gemini through OpenRouter. Summaries cover weight and weight-measurement availability, steps, active calories and recording coverage, and workout types, durations and counts. Gemini generates one provisional maintenance estimate, calorie target, macro targets and short explanations. Software validates the returned structure, arithmetic and supported storage limits before presentation. There is no separate AI writer call. Raw HealthKit samples, source identifiers, account identifiers, body-fat estimates and time zone are excluded. Declining uses a standard non-AI estimate, which may have different targets. Existing programs change only after review and acceptance.
• If the consumer enables helpful notifications and separately permits background AI decisions, computed logging and app-activity aggregates are sent directly to TypeSafe Jev to choose a first-log, routine, return, or no notification. This request excludes meal text, photos, Apple Health data and account identifiers. Fixed notification copy is delivered through Apple Push Notification service; the consumer can turn off each notification category in Ore Settings.
• Food-search terms to nutrition-information providers.
• When a meal request names a brand or restaurant without nutrition evidence, only the public brand and product name, or restaurant and dish name, to Exa through OpenRouter for a bounded search of public nutrition information. The query does not include account information, the nutrition plan, diary history, Apple Health data, or saved-food contents.
• Account-linked meal, plan, draft, derived, and health-feature activity data to hosting, database, security, and technical-service providers.
• Ordinary web-request identifiers and technical information to the public-website host when a consumer visits oreapp.fit or a policy page.
• Voice recordings, when the consumer records a meal by voice and has granted Ore's AI permission, through OpenRouter to AI speech-to-text models, currently OpenAI and Mistral transcription models, to turn the recording into text. These requests are limited to inference endpoints that do not use the content for training and do not retain it, and Ore does not store the recording.
• Audio to Apple's speech-recognition service when speech recognition is not performed entirely on the device.
• Consumer health data included in support correspondence to the support-email provider and personnel handling the request.
• Consumer health data relevant to a request, dispute, security incident, legal obligation, or qualifying corporate transaction to professional advisers, transaction counterparties subject to appropriate protections, and authorities when reasonably necessary and permitted by law.

Categories of third parties and specific affiliates

Ore may disclose consumer health data to these categories of recipients:

• Hosting and database processors: Railway Corp.
• Public website hosting: Vercel Inc. may process ordinary web-request information, such as an IP address and browser or device information, when a consumer visits oreapp.fit or a policy page.
• AI routing and inference providers: OpenRouter, Inc. and AI inference providers selected through its routing, or a directly configured inference provider. Configured model families are listed at oreapp.fit/subprocessors, but a model-family name does not necessarily identify the recipient of a dynamically routed request.
• Nutrition-information providers: USDA FoodData Central and FatSecret when configured.
• Web-search provider: Exa through OpenRouter when configured, for the bounded public product or menu search described above.
• Device and speech provider: Apple Inc.
• Support-email provider: Google LLC through Google Workspace.
• Professional advisers, transaction counterparties, and authorities: these recipients may receive consumer health data when reasonably necessary to obtain advice, complete a corporate transaction subject to appropriate protections, comply with law, enforce Ore's terms, or protect rights, safety, and security.

Ore has no affiliates with which it shares consumer health data as of the effective date above.

Consumer health data rights

Subject to applicable law, a consumer may:

• Confirm whether Ore collects, shares, or sells consumer health data concerning the consumer and access that data, including a list of recipients and an active email address or other online contact mechanism for each recipient.
• Withdraw consent to future collection or sharing of consumer health data.
• Request deletion of consumer health data from Ore's network, including required deletion from archived or backup systems, and require Ore to notify applicable processors and other recipients of the deletion request.
• Appeal Ore's refusal to act on a request.

Ore will not unlawfully discriminate against a consumer for exercising these rights. Ore does not require a consumer to create a new account to submit a request, although Ore may require use of an existing account or additional information when reasonably necessary to authenticate the request.

How to exercise rights or appeal

Consumers may use Settings → Delete Account for an authenticated account- deletion request or email support@oreapp.fit with the subject Consumer Health Data Request. An appeal may be submitted to the same address with the subject Consumer Health Data Appeal.

Ore will respond without undue delay and within 45 days after receiving a request, subject to one additional 45-day extension when reasonably necessary and permitted by law. If Ore denies an appeal, the response will explain the decision and provide a method to contact the Washington Attorney General.

For program estimation, a qualified typical-step summary includes its observed-day count. Ore may use sufficiently covered walking history to raise the starting activity estimate; it does not add wearable calories to that estimate or treat missing or low step counts as proof of inactivity. Existing saved targets are not automatically rewritten.

Health-informed program summaries and retention

For optional program creation, Ore receives derived summaries from up to 28 completed days: available weight measurements, daily steps, active calories and recording coverage, and deduplicated workouts by type, duration and count. Raw HealthKit samples and source identifiers remain on-device. Expanded, explicit AI permission is required before compact summaries and profile answers are sent to Google Gemini through OpenRouter. Declining uses a standard non-AI estimate. When a program is accepted, its inputs, derived Health evidence and decision metadata are stored with the account-linked program and document history. They are covered by the account-deletion process in the general Privacy Policy. Existing targets change only after review and acceptance.