Futurion LLC, doing business as Alova
Effective date: October 13, 2026
This separate policy explains how Alova handles consumer health data under Washington's My Health My Data Act, Nevada's consumer-health-data law, and other applicable protections. It supplements our Privacy Policy. It does not mean Alova provides medical care, therapy, diagnosis, or emergency response.
Contact privacy@alova.dev, or write to Futurion LLC, 522 W Riverside Ave, Ste N, Spokane, WA 99201, United States. Requests sent to support@alova.dev are also accepted. You do not need an account to read this policy or create a new account to submit a privacy request.
Health-related information is not limited to a medical diagnosis or to messages that trigger a safety response. Depending on what you choose to share, we receive and process:
Health-related conversation content. Messages about physical or mental health, mood, sleep, stress, symptoms, conditions, disability, medications, treatment, substance use, or reproductive or sexual health. This includes references to seeking or receiving health services that you voluntarily include in a conversation. We do not require you to supply a medical history to use Alova.
Derived conversation information. Health-related information reflected in a generated reply, summary, saved fact, or other memory derived from a conversation. Such information can be inaccurate. It is treated as health-related information when it meets the applicable legal definition, not as harmless data merely because a model generated it.
Safety Signals and associated records. Automated indications of possible distress, suicidal thinking, self-harm, disordered eating, or other relevant safety concerns; the time and category of a safety event; the associated account or conversation; and information about the system response or resource presentation. Certain crisis, age-claim, and output-moderation records may include a relevant message or generated-output excerpt of up to 200 characters. An age-claim excerpt can incidentally contain health information. Ambiguous distress records and eating-disorder output records do not receive excerpts under the corresponding excerpt rules.
Support and rights communications. Health or safety information you choose to send to support, report to us, or include in a privacy request, together with necessary case-handling information.
We do not connect the current text-chat service to HealthKit, medical-provider records, biometric sensors, or a device's precise location for health-data collection. Information you voluntarily type or attach can nevertheless reveal health or location information. Please provide only what is needed for your conversation or request.
The sources are you, information generated from your interactions with Alova, and service events needed to associate data with the correct account, conversation, or request. We do not buy health profiles from data brokers.
Processing includes storing submitted text, using relevant context to generate AI responses, creating and retrieving memory, applying automated text-based safety checks, and limited authorized human review for support, safety, security, or legal matters. A Safety Signal is a system inference, not a clinical finding. No one is continuously monitoring conversations for emergencies.
With the required permission, we use relevant health-related information to provide the companion conversations and continuity you request, including replies and memory. Background memory updates and eligible companion-initiated messages can process recent conversation context even when you have not just sent a message; that context may contain health-related information.
Safety processing is used to recognize possible crisis or self-harm, provide appropriate resources, prevent harmful generated content, apply relevant age and safety restrictions, and avoid inappropriate romantic, commercial, or proactive behavior during sensitive interactions. It is also used to investigate a specific reported problem and evaluate the safety response through appropriately protected records or de-identified statistics.
We use information in support and rights communications to respond to your request. We process limited information for security incidents, legal requirements, or legal claims only to the extent an applicable legal basis permits it.
We do not sell consumer health data, use it for targeted advertising, or use it to target purchases based on vulnerability. We do not use it for credit, employment, insurance, housing, or similar eligibility decisions, or operate geofences around health-care facilities to identify or target people. Permission for chat is not authorization for an unrelated health-research or model-training program.
Before consent-based health collection or safety inference begins, we request separate affirmative permission describing the categories, purposes, recipient categories, and withdrawal method. Accepting general Terms, reading this policy, or closing a notice is not health consent.
The current companion-chat service includes essential safety processing that cannot be disabled independently. You may decline. Companion chat and dependent AI features will then remain unavailable; eligible browsing, account management, and privacy requests remain available. We do not close an otherwise eligible account solely because you decline this permission.
Withdraw in Profile → Account → Privacy, or email privacy@alova.dev. Once withdrawal is effective, we stop future collection and processing that depends on it, including dependent background processing. An in-app request must reach the server and be confirmed; an offline or failed change is not a completed server withdrawal. Contact us if it cannot be completed in the app.
Withdrawal does not reverse processing already completed lawfully. It is also different from a request to delete all previously collected health data. You may request both at the same time. A withdrawal flow may erase or de-identify associated records as part of enforcing your choice; do not rely on withdrawal as a way to preserve existing history. It does not authorize us to retain data that the law requires us to delete.
Recipients receive only the information appropriate to the stated purpose:
No health-data affiliate recipient is designated in the current service. Before adding an affiliate recipient, we will identify it and obtain any required permission. We do not make health information available for independent advertising or unrelated third-party profiling.
PostHog product analytics, RevenueCat subscription management, and Apple's payment processing do not receive private health-related messages or Safety Signals for those purposes. Push notifications through Expo and Apple are a separate delivery service, not a means for transmitting Safety Signals or sensitive health details. A user asking an external crisis service for help communicates directly with that service; Alova does not automatically forward the conversation to it.
Processor access under restricted instructions is different from an independent third-party use. Where the law requires separate consent for a disclosure, we obtain it before disclosure; collection consent is not treated as a blanket sharing authorization. A sale would require any legally prescribed separate authorization, but Alova does not sell consumer health data and this policy requests no sale authorization.
We do not permit third parties to use our app or legal pages to collect consumer health data over time across unrelated sites or services for their own profiling. External websites you independently visit operate under their own policies.
We use Anthropic's commercial AI service. Its default no-training policy is distinct from its retention, abuse-prevention, and authorized human-review practices. We do not opt private conversations into provider training. Providers may retain information or allow limited personnel review where their applicable terms and the law permit; statutory deletion rights still apply.
Information may be processed in the United States and other countries where authorized providers or personnel operate. U.S.-only app availability is not a guarantee that every processing step takes place in the United States. The Privacy Policy provides additional provider and retention information.
You may ask us to confirm collection, sharing, or sale; access your consumer health data; provide the legally required list of recipients, including relevant third parties or affiliates and contact mechanisms; withdraw applicable permission; delete your consumer health data; and appeal a refusal. You may also request correction of inaccurate health-related information through privacy@alova.dev; we offer this correction process even where the applicable health statute does not separately require it.
Use Profile → Account → Privacy for the available privacy controls, or email us. To request health-data deletion without deleting the whole account, email privacy@alova.dev and describe the request. You are not required to manually locate every memory, archive, or safety record. We explain any necessary effect on chat history or continuity rather than requiring you to keep unwanted health data as the price of retaining your account.
We authenticate requests using reasonable information, do not require creation of a new account, and do not ask for passwords or sign-in codes. An authorized agent may act where applicable law allows. Requests are handled without undue delay, normally within 45 days after receipt. A legally permitted extension is explained within the initial period. A shorter applicable deadline controls.
For Nevada requests governed by NRS 603A.515, we delete the covered data from our records and network and notify the relevant recipients within 30 days after authentication, subject to the statute's specific backup exception. Recipients have their own statutory deletion deadline. For Washington requests, the deadline that runs from receipt is not extended by authentication. These different rules are not interchangeable.
Requests are free except for a fee expressly permitted by law. We explain a lawful fee before charging it. We do not unlawfully discriminate for exercising rights; a feature that necessarily depends on withdrawn processing may become unavailable, as explained in Section 4.
Appeal: Reply to the refusal or email privacy@alova.dev, explaining that you are appealing. No special wording is required. Within 45 days, or a shorter required period, we provide a written decision with reasons. A denied appeal includes the appropriate Attorney General complaint route, including the Washington Attorney General (atg.wa.gov/file-complaint) or Nevada Attorney General (ag.nv.gov/Complaints/File_Complaint), as applicable. You may contact a regulator directly.
Health-related information in conversations and memory is retained for the continuing service described here unless deletion or a relevant withdrawal requires earlier erasure. Operational safety and support records are retained only as reasonably necessary for the associated safety, case-handling, or legal purpose. We do not retain all health data indefinitely merely because a legal claim might someday occur.
A valid deletion request covers the relevant messages, derived memory, safety records and excerpts, recoverable archives, and other copies within our controlled systems. We notify the processors and other recipients that must also act. Account deletion initiates this process for associated account data. A completed processor or backup step can occur later than active-system cleanup, within the legally applicable limit.
Remove conversation and Start fresh are not general health-data deletion requests. A recoverable archive may remain. Use privacy controls or the request route above. Once data is permanently erased, neither a purchase nor renewed consent restores it.
Applicable backup exceptions are limited, not a right to continue ordinary use. Washington permits a delay of no more than six months from authentication for the specified archive or backup deletion; a stricter applicable requirement controls. Backup restoration must not reintroduce erased information into active use. Processor policies do not override statutory deletion obligations.
We retain de-identified safety statistics only where the applicable legal de-identification standard is met. Identity links, message excerpts, and identifying details are removed; we take reasonable measures against re-identification, publicly commit not to re-identify, and impose required recipient restrictions. Simply removing a name or reducing a timestamp to a calendar quarter does not by itself establish that every legal standard has been met. Information that remains linkable is still treated as consumer health data.
Any specific legal preservation exception is limited to its lawful scope and duration. We explain a refusal or limitation and the appeal route unless the law prohibits that explanation.
We use access restrictions, encryption in transit, and technical and organizational safeguards appropriate to the information. These measures reduce risk but do not eliminate it. Our service is not a substitute for confidential care from a qualified health professional.
We publish a revised policy and provide appropriate notice of material changes. Additional categories, purposes, or recipients requiring permission are disclosed and consented to before the new processing begins. This policy's general terms do not pre-authorize an undisclosed expansion.
Contact: privacy@alova.dev
Futurion LLC (dba Alova), 522 W Riverside Ave, Ste N, Spokane, WA 99201, United States.