Hara Privacy Policy

Last updated: October 22, 2026

This policy explains how Opusflame Limited (Hara, we, us) handles personal information through the Hara app, website, AI assistant, and Hara Care portal. Contact: info@harahealth.app. Website: https://harahealth.app.

Health records, conversations, and inferences can be sensitive personal information. AI processing, optional Care sharing, and device permissions are separate choices. This policy explains our practices; reading it, accepting the Terms, or continuing to use Hara does not itself give consent where an affirmative permission is required.

1. Our role and scope

Hara is the operator and controller of personal information used to provide our consumer service. A professional or organization you connect with may be independently responsible for its own use of your records and professional communications. Where Hara processes information on an organization's behalf under a separate agreement, that agreement and the organization's privacy notice also apply to that processing.

Whether HIPAA or another health-sector law applies depends on the actual relationship and use, not the name of the app. This policy is not a HIPAA Notice of Privacy Practices, business associate agreement, or certification of compliance. It does not replace any agreement required for a professional's use of Hara.

2. Information we collect and its sources

These data come from you, your device and use of Hara, connected sign-in or payment providers, the professionals you choose to connect with, and the analyses Hara generates. We do not need precise or background location for the current food, assistant, or Care features. An IP address may indicate an approximate region.

3. Why we use information

We use account and device information to authenticate you, maintain sessions and history, restore access, and operate the Service. We use food, health, conversation, and preference information to provide the tracking, analysis, personalization, summaries, recipes, and memory features you request. Records and their corrections also update related calculations and later summaries.

We use Care information to establish and manage authorized connections, show shared records, generate requested summaries where AI processing is permitted, send professional messages, deliver notifications, and record access and sharing activity. We use purchase information to manage paid access, trials, restoration, and subscription measurement.

We use service activity to understand reliability and feature usage, investigate errors, provide support, protect accounts, prevent abuse, and comply with legal obligations. Authorized personnel may access records or processing traces when needed for support, troubleshooting, security, or service operation. Where advertising measurement is enabled, the limited events and recipients are described in section 7.

4. AI providers, data sent, and memory

Hara integrates Google Gemini API (Google) and OpenAI API (OpenAI). The provider used depends on the feature and service configuration. A workflow can use more than one provider, for example image recognition followed by analysis of the extracted information. The AI notice identifies these recipients before you grant AI processing permission.

Depending on the feature, a request can include your current message or food/menu image; relevant prior messages; diagnosis and dietary preferences; recent or requested-period food scans, meals, reactions, bowel records, and check-ins; derived trigger or trend information; and saved health or preference memory. We also send instructions and technical context needed to produce the requested result. Some context contains record references or timestamps. These requests are not anonymous simply because a name is omitted.

Hara does not need to send your password, sign-in token, payment card information, or advertising identifier as AI prompt content. Personal details that you include in text or images may nevertheless reach the AI provider. Do not include unrelated identity documents, contact information, or another person's records.

AI-enabled features may summarize conversations and update memory in background processing while permission is active. Saved memory can influence later replies across conversations. Closing a conversation does not erase memory. To request access, correction, or deletion of stored memory or related summaries, contact info@harahealth.app; removing one message or record may not remove every derived item.

For requests covered by Google's Gemini Paid Services terms, Google states that prompts and responses are not used to improve its products; limited safety and legal logs may still be retained. OpenAI states that API content is not used for model training by default unless the customer opts in, and standard abuse-monitoring logs may be retained for up to 30 days, with exceptions described in its documentation. These are not promises of zero retention. See https://ai.google.dev/gemini-api/terms and https://developers.openai.com/api/docs/guides/your-data.

Hara's recipe feature uses an internal library first and may use Google Search grounding for web-based results. The search provider may receive the search request and relevant prompt context. Google's grounding terms provide for 30-day retention of prompts, context, and output for grounding, debugging, and testing. Opening a source link also sends normal browser request information to that website, under its privacy policy.

You can decline AI processing and withdraw permission in account settings. Withdrawal stops new AI processing under that permission; it does not undo completed processing or erase information already sent, stored, or present in provider logs. A request already in progress may already have been transmitted. Existing records and deletion rights are addressed below. A new recipient or materially different purpose requiring consent needs a new notice and permission; this policy does not grant open-ended permission for undisclosed AI providers.

5. Hara Care sharing, messages, and exports

Hara Care is currently a limited internal beta. Its availability is restricted to invited testers, and synthetic or appropriately de-identified test records should be used. A beta label does not remove privacy protections: if personal information is processed during testing, the applicable parts of this policy and law still apply. Real patient use requires the separately authorized arrangement described in the Terms.

Connecting to a professional is optional and separate from AI permission. Verify the professional and organization shown before connecting. The connection notice describes access to food logs and reactions, health profile and check-ins, associated summaries, exports, and care messages. A connection can expose records already stored and new records added while sharing remains enabled; it is not limited to records created after the invitation.

Current connection flows enable food sharing, health sharing, data export, and care messages when you connect. You can change Food logs & reactions, Health profile & check-ins, Allow data export, and Care messages for each connection, or disconnect, in the Care team controls. Your name and account contact details may be visible to the connected professional so they can identify you. Related findings can reveal health information even when derived from food logs.

AI summaries available in Care can contain sensitive inferences and source-record references. Where an authorized professional requests a new AI summary, relevant records may be processed by the AI providers described above under your AI permission and sharing settings. The professional's request is not a substitute for your permission.

We store professional messages, their sender and recipient, timestamps, and read or delivery status. Remote care-message alerts use a generic notification rather than the full message body; opening Hara displays the message to the authenticated recipient. Device preview and notification settings remain under your control. Other notifications may still reveal that you use Hara.

Changing permissions or disconnecting stops subsequent access through the connection, but it cannot recall information already viewed or downloaded. A professional may have separate legal recordkeeping obligations. You may contact that professional about their copies, and Hara will handle or forward deletion requests to recipients where required by law. Disconnection does not by itself delete Hara's stored messages, summaries, or access records.

When you export or share a report, food record, image, or conversation yourself, the destination you choose receives that content. Files may include sensitive health information and remain on your device or with the recipient after deletion from Hara. Check the contents and recipient before sharing.

6. Other service providers and disclosures

Service providers process information for the services they supply, subject to applicable agreements and law. We may also disclose information when legally required or necessary to protect legal rights or safety, limited to what is appropriate. In a merger, acquisition, or transfer of the Service, information may be transferred subject to applicable law, appropriate protections, and required notice or consent. This is not permission to sell consumer health data contrary to law.

7. Analytics, advertising measurement, and tracking choices

Firebase Analytics receives app activity and technical metadata, such as page or feature names, event times, app instance identifiers, device/app versions, and purchase-funnel information. Its SDK may also collect standard events such as first opening or starting a session. These events can reveal that you use a health-related app even without the contents of your records.

Hara does not include diagnosis answers, symptom details, food/photo content, free-text health responses, conversations, Care messages, or inferred trigger findings in its custom analytics event payloads. Health-feature page views, clicks, and detailed onboarding steps are not sent to advertising measurement integrations. Limited install, registration-completion, checkout, and subscription events may be used for measurement when those integrations are enabled.

Meta provides app-event advertising measurement; AppsFlyer and Adjust provide attribution; RevenueCat observes subscription transactions and lifecycle events and may forward subscription measurement to AppsFlyer and its configured advertising integrations. Relevant data may include app/account identifiers, AppsFlyer ID, IDFV, IP address, product/transaction IDs, price, currency, and subscription event times. These services do not receive full payment card details from Hara. Availability depends on configuration; a service being listed does not mean it is enabled for every user or build.

We do not sell your food records, health records, conversations, or Care messages or use their contents to target advertising. Disclosure of identifiers and conversion events to advertising partners may still constitute sale or sharing under some privacy laws even without payment. Consent to AI processing or Care sharing is not consent to advertising tracking.

On iOS, you can manage tracking permission under Settings > Privacy & Security > Tracking. IDFA access and tracking require the applicable permission. Refusing tracking does not prevent you from using paid features. ATT is not a universal analytics opt-out, and the absence of IDFA does not by itself make other processing anonymous or exempt from privacy law. To exercise applicable opt-out or consent-withdrawal rights, contact info@harahealth.app with the subject Privacy opt-out. We do not treat an operating-system permission as a substitute for any additional consent the law requires.

8. Device permissions and your controls

Camera and photo permissions support selecting food/menu images and saving exported visuals. Microphone and speech-recognition permissions support optional voice dictation. Notification permissions support reminders and remote messages. Hara uses local storage for sessions, settings, and cached content. Websites or portals may use session storage to keep you signed in, and externally loaded assets can send normal request metadata to their hosts.

You can change device permissions in system settings, withdraw AI processing in Hara's account settings, adjust individual Care connections, correct supported records in the app, or contact us about health-data processing and deletion. Declining an optional permission affects the feature that needs it. Withdrawing consent does not make earlier lawful processing unlawful and does not automatically cancel subscriptions.

9. Retention and account deletion

We retain account information, uploaded images, food and health records, conversations, summaries, and memory to provide account history and the features you use, until they are deleted or no longer needed. Retention depends on the purpose, sensitivity, legal requirements, and whether an item is needed for security, resolving disputes, or documenting permissions. Derived summaries and memory may be stored separately from their source records.

You can request account deletion in Hara's account settings or email info@harahealth.app from the address associated with your account. The in-app request initially disables the account and marks it for deletion; an account-recovery period may apply. This first step is not an assurance that all databases, images, backups, exports, and vendors' copies are instantly erased.

We handle verified deletion requests within the time required by applicable law, explain any permitted extension or exception, and arrange recipient deletion where required. Information retained for a lawful exception must remain limited to that purpose. Backups, security records, financial records, and provider logs may have different deletion schedules. A statutory deletion right takes priority over a routine retention schedule; ask us for details about your request.

We may retain genuinely de-identified information only where permitted by law. Removing a name or replacing it with an ID does not by itself de-identify health information. Independently retained professional records and your own exported copies are addressed in section 5. Deleting an account does not cancel an Apple subscription; cancel separately in Apple account settings.

10. Security and international processing

We use safeguards such as HTTPS for transmission, secure device storage for session tokens, authentication, and access controls. No system can guarantee complete security. If an incident triggers a notification obligation, we will notify affected people and authorities as required by the applicable law. A health-data incident can include an unauthorized disclosure, not only an external intrusion.

Hara and its providers may process information outside your country, including in the United States and other countries where they operate. Local laws and access rights may differ. Where a transfer requires a specific legal safeguard, that safeguard must be in place; your acceptance of the Terms is not a general waiver of transfer protections. Contact us for information about destinations and safeguards relevant to your data.

11. Legal bases and regional rights

Where GDPR or UK GDPR applies, ordinary personal data is processed as necessary to perform the service contract, on consent where required, for legal obligations, or for legitimate interests such as account security and service reliability after considering your rights. Optional advertising processing is subject to the consent or opt-out rules that apply to it.

Health data, including sensitive health inferences, needs an additional lawful condition. For the consumer health-tracking and AI personalization features, explicit consent is the relevant condition under Article 9(2)(a) where GDPR or UK GDPR applies, alongside an Article 6 basis. A general Terms acceptance does not provide this explicit health-data consent. Professional use may require a different documented basis and agreement; a professional's involvement does not automatically supply one.

Depending on your location and the law's applicability, you may request access, a portable copy, correction, deletion, restriction, objection to processing, withdrawal of consent, a list of relevant recipients, or an opt-out of sale, sharing, or targeted advertising. California residents may also have rights concerning use of sensitive personal information and authorized agents. Hong Kong residents may have access and correction rights under the Personal Data (Privacy) Ordinance. You may complain to your competent privacy authority, including the ICO in the UK or the PCPD in Hong Kong, where applicable.

These examples are not an exhaustive list of countries or rights. Mandatory local privacy and consumer-health protections continue to apply in every market where Hara is available. Access to particular AI features may be limited by the provider's supported regions and applicable law, even if the app can be downloaded from your app store.

Send requests to info@harahealth.app. We may ask for information reasonably necessary to verify your identity or an authorized agent's authority, without requesting unnecessary health details. We respond within applicable legal deadlines, explain any lawful refusal or extension, and do not retaliate for exercising rights. Where a right to appeal applies, reply with Privacy appeal; we will explain the outcome and available regulator complaint route. Legally applicable browser opt-out signals must be given effect for covered online processing; email remains available for account-related requests.

Hara's automated insights support personal understanding. They are not intended to make decisions about access to healthcare, insurance, employment, or other legal or similarly significant outcomes. You can question an inference, correct underlying information, or ask for help from a person through the contact address above.

12. Consumer health data privacy notice

This section summarizes our consumer health data practices, including for people whose information is covered by Washington's My Health My Data Act or similar state laws. It supplements the details above and does not limit protections those laws provide.

Categories and sources: we collect the health and food records, symptoms, bowel records, check-ins (including menstrual/cycle information if provided), conversations containing health details, preferences, and health inferences described in section 2. Sources are you, your use of the Service, professionals you choose to connect with, and Hara's generated inferences. Information linking you to use of a health service can itself be consumer health data.

Purposes: we use these categories for requested tracking, AI analysis, memory and personalization, summaries, recipes, authorized Care sharing and messages, support, and security. Where law requires consent for collection or sharing, it must be obtained for that purpose; exceptions for a requested service apply only to the extent the law permits. New purposes or categories require the legally required notice and consent before processing.

Recipients and shared categories: cloud/storage and operational processors receive the records needed to provide the Service; Google and OpenAI receive relevant content and health context for authorized AI features; selected professionals receive the records, summaries, identity details, and messages permitted by the Care connection; and your selected export recipients receive what you share. Device speech services process optional dictation. Analytics and measurement providers described in sections 6 and 7 receive limited activity or conversion information, which may itself disclose use of Hara, rather than the contents of your health records. These categories must still be assessed under consumer health-data rules. No affiliate is separately designated as a recipient of health records by this notice.

Rights and requests: contact info@harahealth.app to confirm processing, access consumer health data and the applicable list of third parties and their contact details, withdraw collection or sharing consent, or request deletion. You can also change Care and AI permissions in the app. Where Washington law applies, verified requests are generally answered within 45 days, with a permitted extension if necessary and explained. Required deletion extends to recipients and backups as provided by law; any permitted backup delay must not exceed six months from authentication. If a request is denied, email Privacy appeal; Washington appeals receive a written response within 45 days, and you may complain to the Washington Attorney General at https://www.atg.wa.gov/file-complaint.

Hara does not sell consumer health records or use geofencing around health facilities to identify people seeking care or target them with messages. An AI permission or Care connection is not authorization to sell consumer health data. The broader legal treatment of measurement disclosures is explained in section 7.

13. Adults and policy changes

Hara is intended for people aged 18 or older. It is not intended to collect children's health information. If you believe a child has supplied information, contact us so we can investigate, restrict further processing, and arrange deletion where required.

We may update this policy and its last-updated date as the Service or legal requirements change. Material changes receive additional notice where required. A revised policy or continued use does not replace any fresh consent required for a new purpose, recipient, or category of sensitive information.

14. Contact

For privacy questions, access or deletion requests, consent withdrawal, or complaints, contact Opusflame Limited at info@harahealth.app. Website: https://harahealth.app. Please do not send more health information than is needed to describe your request.