Last updated: October 11, 2026
This Privacy Policy describes how 0xdesigner LLC, doing business as Ore ("Ore," "we," "us," or "our"), collects, uses, discloses, and retains personal information through the Ore mobile application, the oreapp.fit website, and Ore support. It is a notice of our data practices and does not create contractual rights or replace the Ore Terms of Use. Ore is operated from the United States and this Policy applies wherever Ore is offered.
Ore is a meal-logging and general-wellness app. We do not sell personal information, use it for targeted advertising, or permit third-party advertising trackers in the app.
For disclosures and rights concerning consumer health data, see the separate Washington Consumer Health Data Privacy Policy and Nevada Consumer Health Data Privacy Policy.
Ore uses Sign in with Apple. Depending on the choices you make with Apple, we receive an Apple account identifier, your name, and an email address or Apple private-relay address. We use this information to create, authenticate, secure, and support your account and to associate your Ore content with it. Ore does not receive your Apple password.
We collect information you submit or create through Ore, including:
If you choose to connect Apple Health, Ore may read body mass, step count, Active Energy, daily Activity Summary information, and workouts from HealthKit. Ore uses available body mass and activity evidence to suggest onboarding answers that you still confirm, show steps in your diary, and calculate a small positive Calorie credit (internally called Activity Fuel) on unusually active days. When comparable full-day energy history is not available, Ore may use steps and your confirmed program weight to make a conservative walking-energy estimate.
If you separately turn on Export data to Apple Health, Ore writes the calories, protein, carbohydrates and fat of meals you log afterwards to HealthKit on your device and, while the switch stays on, updates or removes them when you edit or delete the meal. Turning it off stops new writes. Entries already in Apple Health stay there after you turn it off or delete your Ore account, until you delete them in the Health app. This happens on your device and sends nothing new to Ore's servers.
Raw HealthKit samples, individual workout and Active Energy records, Activity Summary details, and Apple Health source details remain on your device. If an available Health weight seeds the editable weight question, the weight you confirm becomes an ordinary saved program answer. Ore also sends its server the local date, derived daily step total, derived Calorie credit amount and carbohydrate grams, the calculation version, and calculation/finalization times. The confirmed program answer and derived daily totals are linked to your Ore account so the same program and daily nutrition budget can be shown across your devices. If Apple Health is connected and you have granted AI permission, the daily step total and derived Calorie credit for recent days are included in the Insight context sent to the AI provider. Raw HealthKit samples, workouts, Active Energy, Activity Summary details, and source details are not sent. Like a manually entered weight, a weight you confirm may shape saved plan targets. Ore does not send that weight to generate Insights.
For program creation with Apple Health connected, Ore sends its server and stores available derived summaries from up to 28 completed days: weight measurements, steps, active calories and recording coverage, and deduplicated workouts by type, duration and count. Missing records remain unknown. These are not raw HealthKit samples, source identifiers or measured metabolism.
Where Health-informed AI programs are available, an explicit permission page asks before sending profile answers and compact Health summaries to Google Gemini through OpenRouter. 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 explanation call. Declining gives a standard, non-AI estimate, which may differ from the AI-selected estimate. Existing programs change only after you review and accept new targets. This does not enable automatic daily adjustment.
You may skip Apple Health and use Ore's manual onboarding answers without losing the core plan or diary. You can change Health access in Apple's Health or Settings app. Because Apple protects read-permission privacy, Ore cannot reliably distinguish a denied Health data type from a type that simply has no available samples.
We use this information to provide the diary, estimates, drafts, saved foods, trends, and planning features you request; personalize those features; maintain your history; prevent abuse; troubleshoot the service; and comply with law.
If you use voice logging, Ore accesses the microphone only while it is recording. When you stop or send, the app sends the voice recording to Ore's server. If you have granted Ore's AI permission, the server sends it through OpenRouter to AI speech-to-text models, currently OpenAI and Mistral transcription models, to turn it into text. Those requests are limited to inference endpoints that do not use the content for training and do not retain it. Ore does not store the voice recording; it is discarded once the request finishes. If cloud transcription is not available, speech recognition may occur on your device or through Apple's speech-recognition service, depending on the device, operating system, language, availability, and Apple's service behavior. The resulting transcript may be processed and retained like other meal text, including in a pending draft and account document history.
You can change microphone and speech-recognition permissions in iOS Settings.
If you use photo logging, Ore processes only the photo or photos you take or select for that submission. The app resizes them before transmission. Ore uses the images to identify foods and estimate nutrition. Photos you attach are staged with the pending meal draft and, when you confirm it, stored with the meal entry so Ore can display them in your diary. Ore deletes those stored photos when you delete the meal or your account. Service providers may also temporarily process or retain request data under their applicable API terms, security practices, and legal obligations.
You can change camera and photo-library permissions in iOS Settings.
Ore uses commercial AI APIs and nutrition-information services for meal analysis and morning Insights, and optional personalized program creation. For a personalized program, AI generates a provisional maintenance estimate, calorie target, macro targets and short explanations from the disclosed profile and Health summaries. Software validates the returned structure, arithmetic and supported storage limits. Direct target adjustments and programs created without AI personalization use software calculations. Current routing services, configured model families, and service categories are described at oreapp.fit/subprocessors. Providers may change as we change models, routing, infrastructure, or features.
If you have granted Ore's AI permission and enable helpful notifications, Ore sends TypeSafe Jev computed logging and app-activity aggregates at periodic checks. There is no additional AI permission for notifications. These include local clock time, counts and timing of known logs, recent app activity and notification history, and your enabled reminder categories. Jev chooses whether to invite a first log, remind you near an observed logging time, welcome you back after a pause, or send nothing. This request excludes meal text, photos, Apple Health data and account identifiers. Ore stores the choice and limited decision diagnostics with your account and sends only fixed notification copy through Apple Push Notification service. You can turn off Meal reminders or Check ins in Ore Settings or revoke notification permission in iOS Settings.
Depending on the feature, Ore may send meal text, a voice recording for transcription, a voice transcript, selected photos, and prior draft or logged-meal items when you request a revision. To recognize saved foods in text or voice logs, Ore sends that text plus saved-food names, aliases, and ingredient names to TypeSafe Jev through OpenRouter. That decision request does not include saved nutrition totals, diary history, account identifiers, or Health information. The app asks you to confirm a suggested saved food before attaching it. For meal revisions, Jev receives the requested change, current meal item names and portions, and any targeted clarification context to distinguish additions, corrections and whole-meal changes; it does not receive account identifiers or Health information. For a morning Insight, Ore sends the AI provider your 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, the context also includes the daily step total and derived Activity Fuel calorie credit for each of those days. It does not include raw HealthKit samples, workouts, Active Energy, Activity Summary details, or source details.
The model returns a headline, a short paragraph, and one "Try this" suggestion. Before showing an Insight, Ore checks the text against fixed rules that prohibit medical claims, diagnoses, medication guidance, data or system language, and suggestions that conflict with dietary restrictions. Ore does not show the Insight when those checks fail. For Insights, Ore does not send your name, email, Apple identifiers, sex, age, height, weight, or payment information. 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. Accepting a program saves its targets and explanation without rerunning the model. Content that you choose to type, speak, or photograph may itself contain personal information, and that content will be processed as part of the request.
When a meal request names a brand or restaurant without providing nutrition evidence, Ore may send only the public brand and product name, or restaurant and dish name, through OpenRouter to its configured web-search provider, currently Exa, to find public nutrition information. That search query does not include your account information, nutrition plan, diary history, Apple Health data, or saved-food contents.
Ore applies OpenRouter's data_collection: deny routing control to requests made through OpenRouter. OpenRouter describes that setting as excluding inference providers that collect user data. Ore does not use personal information to train a general-purpose AI model of its own. Commercial API terms and provider-side security, abuse-prevention, legal-compliance, or transient technical retention may still apply. A configured model-family name does not necessarily identify the inference provider that receives a dynamically routed request.
Before Ore sends meal or diary information for third-party AI processing, the app asks for permission. If you do not grant permission, you can still create and access an Ore account, complete the deterministic onboarding calculation, and view or adjust your plan targets; AI-powered meal estimates and daily insights remain unavailable until permission is granted. To withdraw permission after granting it, use Settings → Delete Account. Successful account deletion revokes access to Ore and deletes associated account records from Ore's active production database, subject to the limited retention exceptions described under Retention and deletion. Stopping use of Ore prevents new activity but, by itself, does not withdraw permission or delete information already stored in your account.
We collect information needed to secure, operate, and improve Ore, including IP address and request timing for rate limiting; request and account identifiers in server logs; app and OS version; feature or model path; model and token usage; processing time; and success, failure, or repair status. If you enable Insight notifications, we store an Apple Push Notification service device token and your preference to route those alerts to this installation. We also store the device timezone, the scheduled check-in time, and content-free delivery and interaction receipts to avoid overlapping alerts, retry temporary failures, and understand whether notifications help. These records do not contain meal text or nutrition values. We do not use the device token for advertising or tracking.
Apple's MetricKit may provide crash, hang, CPU, or disk-write diagnostics. Ore forwards the diagnostic payload supplied by Apple to our server and does not intentionally add meal text or photos to it. MetricKit payloads may contain technical device, operating-system, application, and stack-trace information.
Structured model-usage records do not include the meal text, transcript, or photo itself. We use technical information for authentication, security, rate limiting, debugging, reliability, capacity planning, cost management, and first-party product analytics—not advertising.
Ore does not require a subscription or purchase for app access. During the transition from an earlier paid version, Ore may continue receiving verified StoreKit lifecycle information for historical subscriptions, such as product and original transaction identifiers, status, expiration or renewal information, environment, and an account-linking token. We use those records only for support, fraud prevention, legal compliance, and winding down prior subscriptions—not to determine access. Apple processes payment details; Ore does not receive your full card number or billing address.
If you contact support, we collect your sender address, message, attachments, and any information you choose to include. Support correspondence is processed through Google Workspace and used to respond, investigate issues, maintain appropriate business records, protect the service, and comply with law. Do not send information that is unnecessary for us to address your request.
We may disclose personal information as reasonably necessary for the purposes described above:
These providers may process information in the United States or other locations. We do not sell personal information or disclose it for targeted advertising.
We generally retain account, meal, nutrition, plan, draft, derived Activity Fuel, telemetry, and diagnostic information while your account remains active and as reasonably needed to provide, secure, and support Ore. Raw HealthKit samples and source identifiers remain on-device. For program creation, Ore receives derived summaries covering up to 28 completed days. When you accept a program, its profile answers and derived Health evidence are stored with the program and its account-linked history so the calculation can be explained and reproduced. This includes available weight measurements, daily steps and active-calorie summaries, recording coverage, and deduplicated workout type, duration and count. Account deletion removes this account-linked program history under the deletion process below.
You may request account deletion inside Ore under Settings → Delete Account. Ore authenticates deletion requests, and the in-app process also attempts required Apple credential revocation. When in-app deletion succeeds, Ore deletes the account and associated records from its active production database, including account-linked document history, telemetry, and diagnostics. If the in-app process cannot complete, email support@oreapp.fit with the subject Privacy Request; a failed Apple credential-revocation attempt does not waive a deletion right available under applicable law.
Some information may remain temporarily in restricted backups, security logs, or service-provider systems until overwritten or deleted under applicable retention schedules. We may retain limited information when reasonably necessary to comply with law, resolve disputes, enforce agreements, prevent fraud or abuse, or establish or defend legal claims. Where applicable law requires broader or faster deletion, including deletion instructions to processors or deletion from backups, we follow those requirements. Apple retains its own purchase history independently.
Support correspondence is retained only as reasonably necessary to respond, investigate issues, maintain appropriate business records, prevent abuse, and comply with law.
If you started an Ore subscription in an earlier app version, deleting the Ore app or your Ore account does not cancel it. Manage any remaining subscription through Apple while it winds down.
We use reasonable administrative, technical, and organizational safeguards designed to protect personal information, including encrypted network connections. No safeguard, system, transmission, or storage method can guarantee absolute security.
Ore is not directed to children under 13, or the higher minimum age that applies in your country, and we do not knowingly collect personal information from a child under that age. If you believe a child has provided information to Ore, contact us so we can review and address the request.
You can:
We may need to authenticate a request. Applicable law may permit or require us to retain certain information or decline a request in limited circumstances. We will not unlawfully discriminate against you for exercising a privacy right.
Washington consumers and people whose consumer health data is collected in Washington should review the separate Washington Consumer Health Data Privacy Policy. Nevada consumers should review the separate Nevada Consumer Health Data Privacy Policy. These notices provide additional disclosures, request methods, and appeal rights.
Connecticut consumers may, subject to applicable law, ask to confirm processing; access, correct, delete, or obtain a portable copy of personal information; and opt out of covered sales, targeted advertising, or profiling. Ore does not sell personal information or use it for targeted advertising. Submit a request by emailing support@oreapp.fit with the subject Privacy Request. To appeal a refusal to act, use the subject Connecticut Privacy Appeal. Ore will respond to an appeal within 60 days and, if an appeal is denied, provide a method to contact the Connecticut Attorney General.
Ore is operated from the United States, and the information described in this Policy is processed and stored in the United States and in the other locations where our service providers operate. Data-protection laws in the United States may differ from those of your country. By creating an Ore account, you understand that your information, including meal, dietary, and body information, will be transferred to and processed in the United States as described in this Policy. Ore separately asks for in-app permission before sending covered meal or diary information to third-party AI providers.
Where laws such as the EU or UK General Data Protection Regulation or Canada's federal and provincial privacy laws apply, Ore relies on the following legal bases:
You may withdraw AI-processing consent at any time through Settings → Delete Account as described under AI and nutrition processing; this deletes the account and ends access to the service. You may decline AI-processing consent without losing access to your account, but AI-powered meal estimates and daily insights remain unavailable. Subject to applicable law, you may also request access to, correction of, deletion of, or a portable copy of your personal information, request restriction of or object to certain processing, and decline to consent without discrimination. Submit requests by emailing support@oreapp.fit with the subject Privacy Request. You also have the right to lodge a complaint with your local data-protection or privacy authority.
We may update this Policy as our service, providers, or legal obligations change. We will update the date above and provide additional notice when required by law.
The entity responsible for this Policy is 0xdesigner LLC, doing business as Ore. For privacy questions or requests, email support@oreapp.fit.
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.