Futurion LLC, doing business as Alova
Last updated: October 13, 2026
This Privacy Policy explains how Futurion LLC, doing business as Alova ("Alova," "we," "us"), handles personal information in the Alova iOS app, the alova.dev website, and our related support services (the "Service"). Our app is offered to adults in the United States.
Every companion is an AI character, not a human chat partner. Some opening messages and system or safety responses use text prepared by Alova rather than a live AI-generated response. Limited human access to information for support, safety, security, and legal purposes is described below; it is not a human companion-chat service.
For privacy questions or requests, email privacy@alova.dev. You can also write to Futurion LLC, 522 W Riverside Ave, Ste N, Spokane, WA 99201, United States. Our separate Consumer Health Data Privacy Policy gives additional information about health-related content and Safety Signals. Where it provides more specific protection for consumer health data, that protection applies.
Account and eligibility information. Your email address, account identifiers, sign-in information, the name you choose, and your age-eligibility confirmation and its date. We do not ask for your date of birth or an identity document in the ordinary registration flow. An eligibility or security review may require additional information; we explain what is needed when we ask.
Profile and preferences. The preferences you provide, including who you would like to meet, what you are looking for, interests, and app settings. A preference about a companion's gender may reveal sensitive information, including information that could suggest sexual orientation. We use the preference to personalize the companions shown to you, not for advertising.
Conversation and relationship information. Messages you send and receive; derived memory such as summaries, saved facts, and significant conversational events; and information needed to retrieve relevant memories and maintain continuity. We also keep relationship state, companion choices, conversation activity, virtual gifts, and other in-app interactions. Memory is generated automatically and can be incomplete or wrong.
Health-related information and Safety Signals. Messages or support requests may contain information about physical or mental health. Automated processing can identify possible distress, suicide, self-harm, disordered eating, or other safety concerns. These are not diagnoses. Certain operational safety records include the event category, time, associated account or conversation identifiers, and the response provided. For specified crisis, age-claim, or output-moderation events, a record can also include a limited excerpt of the user's message or generated reply, capped at 200 characters. Not every signal includes an excerpt. The Health Data Policy explains these records and your rights.
Consent and privacy records. The document versions presented or accepted, permissions granted or withdrawn, relevant dates, and information needed to process privacy requests and restrictions.
Purchases. Subscription and entitlement status, Sparks balances and transactions, virtual-item purchases, and purchase, renewal, expiration, cancellation, and refund information received from Apple and RevenueCat. Apple handles payment details. Alova does not receive your full payment-card number or Apple Account password.
Device, notification, and usage information. A random installation identifier; notification permission and registration information, including your push token when registered; time zone; app and operating-system information; and limited activity information such as whether a particular conversation is open, when it was read, and delivery status. Optional product analytics can include screens, feature use, and purchase-flow events associated with an account or analytics identifier. Message text, memory text, and Safety Signals are not included in product analytics.
Technical and support information. IP addresses and request metadata received by our hosting services, app and device information, errors and security records, and what you voluntarily send to support, including attachments and our replies.
Information you choose to include. We do not request access to your contacts, precise device location, or photo library for the current text-chat service. This does not mean we cannot receive that information: a message or support attachment can contain your birthday, gender, location, photograph, or other personal details. Please do not send passwords, payment-card details, identity documents, or another person's private information unless specifically necessary for an identified support process.
We use information to operate accounts and authentication; provide conversations, memory, relationship continuity, and requested virtual experiences; manage subscriptions and Sparks; deliver notifications; enforce age, content, and security rules; answer support and privacy requests; resolve transaction problems; and meet legal obligations.
With the required permissions, recent context and memory may also be processed when you have not just sent a message. This includes updating memory and generating a companion-initiated message. Turning off phone notifications is not the same as turning off in-app companion initiative or withdrawing AI-processing permission.
Safety processing can change how the service responds, display crisis resources, restrict inappropriate output, or suppress unsuitable relationship progression, purchase suggestions, or proactive contact during a sensitive interaction. We do not use health-related information to target purchases or advertising.
We use optional product analytics to understand feature use and improve the app. Essential transaction, consent, abuse-prevention, and security records are separate from optional product analytics.
We do not sell personal information, share it for cross-context behavioral advertising, or use private conversations or Safety Signals for advertising. Alova does not operate an advertising business within the Service. We do not use consumer health data for credit, employment, insurance, housing, or similar eligibility decisions.
We distinguish accepting our Terms from the permissions that govern conversation processing: one permission covering conversation storage, memory, and health-related processing, and a separate permission for third-party AI processing. Merely reading a policy or closing a screen does not give those permissions.
Conversation storage, memory, and health-related processing. A single permission covers storing your conversations and derived memory together with the health-related content, safety processing, and Safety Signals described in the Health Data Policy. It is the health-data consent presented during onboarding; conversation storage is not a separate permission you can grant or withdraw on its own. The current companion-chat service includes required safety processing that cannot be disabled independently. Without this permission, companion chat and dependent AI processing are unavailable; eligible browsing, account management, and privacy requests remain available. Withdrawing this permission disables dependent chat features, stops new processing that depends on it, and starts deletion of the covered conversation, memory, and recoverable archive data, while leaving the account in place. The completion process and limited exceptions are explained in Section 6. This is a limitation of the service we provide, not a claim that every AI chat service is legally required to use the same design.
Third-party AI processing. This is a separate permission. Before sending personal conversation data to Anthropic, we ask for your permission and explain the data and purposes. Withdrawal stops new transmissions that depend on that permission, including replies, memory work, companion-initiated messages, and applicable AI-generated virtual-experience responses. It does not, by itself, erase every record already held by Alova or a provider. You may separately request deletion.
Use Profile → Account → Privacy to manage available permissions or email privacy@alova.dev. An in-app change must reach our servers and be confirmed to take effect there. If the app reports an error or remains offline, contact us. Once withdrawal is effective, already-started work must not be used to restart the withdrawn processing or recreate erased conversation data. Information already transmitted remains subject to the applicable retention and deletion process.
You can grant a permission again later. Doing so does not restore data that has been permanently deleted. Withdrawal does not cancel an Apple subscription; see Section 7.
We disclose information necessary for the following services. Calling a recipient a provider does not mean it receives all account data or that every activity it performs is under Alova's control.
AI training, retention, and human review are different issues. Anthropic's commercial API terms state that inputs and outputs are not used for model training by default. Alova does not opt private user conversations into provider training or submit them as training feedback. Providers may nevertheless use authorized personnel and retain limited information for safety enforcement, security, or legal obligations. Our permitted processing does not mean zero retention or a guarantee that no authorized person at a provider can ever see data.
We may disclose limited information in response to valid legal requirements, to investigate fraud or security incidents, or to protect rights or safety where the law permits. Consumer health data receives the additional restrictions in the Health Data Policy. General legal, safety, or business-transfer language is not permission to disregard those restrictions.
A merger, acquisition, or transfer of the business may involve a successor receiving information subject to applicable law and the privacy obligations that continue to apply. A transfer does not independently authorize new uses of consumer health data.
Limited access at Alova. Conversations are not watched by a live response team. Authorized people may review information needed for a support request, a reported response, a safety or age-eligibility review, a security incident, or a legal obligation. This is not real-time crisis monitoring.
The installation identifier is created by the app. It is not Apple's advertising identifier. It helps distinguish notification registrations and device-specific activity, including whether a conversation is currently open. These identifiers are not used to track you across other companies' apps or websites for advertising.
Notification appearance depends on the privacy option in Profile → Account → Notifications and iOS settings. Available options can limit a notification to the app name, a companion name, or an eligible message preview. We restrict previews to avoid exposing health or other highly sensitive conversation details. Enabling previews does not authorize sending sensitive health information through push notifications. People with access to your lock screen may still see the information that is displayed.
You can turn Alova notifications off for a device in iOS Settings, or use the account-level notification control in the app. Phone notification permission is not required for chat. Turning it off does not necessarily stop a permitted companion-initiated message from appearing inside Alova.
On sign-out, the app asks the server to stop notifications for that account on the device. An offline or failed request may not reach the server, even if local sign-out completes. Notifications may continue until deregistration, another valid registration change, or account deletion takes effect. For immediate device-level protection, turn Alova notifications off in iOS Settings. A notification already passed to Expo or Apple may still arrive and cannot be recalled by Alova.
Signing out or disabling notifications does not automatically erase the stored registration. The account-deletion process removes account-linked registrations that we hold. It does not erase Apple's independent purchase records or other information that a provider has a separate lawful obligation to retain. We remain responsible for forwarding applicable deletion requests to our processors.
The app keeps local information needed for its operation, including cached state and preferences. Other devices that are offline may not receive an account or privacy update until they reconnect. You can remove the app and clear its notifications on a device you control; copies you deliberately exported, screenshots, and backups outside Alova's control are separate from the copies our deletion process handles.
Account and conversation data. We generally retain account information while the account is open and conversation history, memory, and recoverable archives while needed to provide the continuing relationship service, unless you delete them or a relevant withdrawal requires erasure. Premium ending does not, by itself, delete a relationship's history or memory.
Remove is not Delete. Removing a conversation can hide it and retain a recoverable archive. Starting fresh changes the relationship state; it is not a general privacy-erasure request. Use the privacy controls or contact us to request deletion. Permanently erased data is not recoverable through paid Restore.
Safety records. Linked operational records are kept only for the safety, incident-review, and compliance purposes described here, with retention determined by the relevant event, account status, and any unresolved review or lawful preservation requirement. Their content is separate from ordinary chat history. A permitted excerpt can exist before deletion; the promise is not that all safety records are anonymous from the start.
Other limited records. Purchase records may be retained for refunds, accounting, tax, and legitimate dispute handling. Limited consent, privacy-request, and security evidence may be retained where needed and legally permitted. We do not retain private chat text merely because an accounting record is needed. Support retention depends on resolving the request, necessary follow-up, and any applicable legal requirement.
What deletion covers. You can initiate account deletion inside the app at Profile → Account → Privacy. The process covers associated active account, conversation, memory, recoverable archive, device-registration, and other personal data held by Alova, subject only to applicable legal exceptions. We send required deletion instructions to relevant processors and recipients. Submission is not a promise that every distributed copy disappears instantly; we distinguish initiation, active-system cleanup, and later processor or backup completion.
Backups are not used as a source of ordinary conversation after deletion. Consumer health data in archives or backups is handled within the applicable legal deadline; under Washington's My Health My Data Act, the permitted delay cannot exceed six months after authentication of the request. A shorter applicable deadline controls. Restoring a backup must not make erased information available for ordinary processing again.
Provider retention. Anthropic's published commercial policy generally provides a 30-day deletion period for standard API inputs and outputs, subject to service/model-specific terms and exceptions. Its policy also describes longer retention for flagged usage-policy content and related classifications, and for legal obligations. See Anthropic's retention information (privacy.claude.com/en/articles/7996866-how-long-do-you-store-my-organization-s-data). These schedules do not waive your statutory rights or excuse Alova from handling an applicable deletion request. We do not promise an unverified zero-data-retention arrangement.
De-identified statistics. After erasure of linked safety records, we may retain safety statistics only if they meet the applicable legal standard for de-identification. Removing names or reducing dates alone is not enough. We remove identifying links and content, take reasonable measures against re-identification, do not attempt to re-identify the data, and impose required restrictions on recipients. Records that remain reasonably linkable to a person continue to be treated as personal information, not as an exception to deletion.
Where a specific law permits or requires limited preservation, it is restricted to that purpose and duration. There is no blanket exception allowing us to keep all conversations for an undefined investigation. We explain a refusal or limitation on a request and the available appeal route, except where disclosure is legally prohibited.
We offer U.S. users the ability to ask whether we process their information, obtain a copy, request correction or deletion, and appeal a refusal. Certain rights are required by state law; our voluntary offer does not limit any stronger legal right. A request can also ask about recipients or restrictions on processing to which you are legally entitled. The Health Data Policy describes additional rights for consumer health data.
Email privacy@alova.dev, or use the available in-app privacy controls. Describe the request and the account email, if you have one. You do not need to create an account to submit a request. We may authenticate ownership using existing information or request only additional information reasonably necessary. We do not ask for your password or one-time sign-in code. An authorized agent may act where allowed by law.
We handle requests without undue delay and normally within 45 days after receipt. A single extension of up to 45 days is used only when legally permitted and reasonably necessary, with timely notice and an explanation. A shorter applicable deadline takes priority, including Nevada's specific consumer-health-data deletion deadlines. Authentication is handled promptly and does not extend a deadline that runs from receipt. Requests are free except for a fee expressly permitted by applicable law; we explain any lawful fee before charging it.
To appeal, reply to our decision or email privacy@alova.dev and explain that you are appealing. No exact phrase or subject line is required. We provide a written decision and reasons within 45 days, or sooner if required. If an appeal is denied, we provide the appropriate state Attorney General complaint route. You may contact a regulator without completing our internal appeal first.
No unlawful discrimination. We do not penalize you for exercising privacy rights. A feature that depends on processing you decline or withdraw may become unavailable; that necessary functional consequence is explained before you choose. It does not authorize an unrelated fee or a penalty on other eligible features.
Analytics. Turn off Allow analytics in Profile to stop optional account-linked product analytics from the app and server after the choice is saved. This does not delete past events by itself or stop necessary security and transaction records; you may separately request deletion of applicable past personal information.
Browser signals. We do not sell information or use cross-context behavioral advertising. Global Privacy Control therefore has no sale or advertising-sharing activity to opt you out of under our current practices; it is not treated as a withdrawal of conversation consent. Do Not Track is a different browser signal. We do not track you across other companies' sites for advertising, but essential website request information is still processed. These statements do not limit any obligation to honor a legally recognized opt-out signal.
Subscriptions. Deleting an account or withdrawing permission does not cancel an Apple subscription. Manage it separately in iOS Settings → your name → Subscriptions → Alova. You do not have to wait until the paid period ends to request deletion.
Alova is for people 18 and older. Companion chatbots may not be suitable for some minors, and Alova does not offer companion chat to minors. We do not knowingly offer the Service to, or intentionally collect information from, children. If we learn an account belongs to someone under 18, we restrict access and handle associated information as required by law. Report suspected underage use to support@alova.dev.
We use access restrictions, encryption in transit, and other technical and organizational safeguards appropriate to the information. No system is completely secure. Conversations must be accessible to authorized processing systems to generate replies; we do not represent them as end-to-end encrypted against Alova and its AI processors.
U.S. availability is not a promise of U.S.-only processing. Alova and its service providers may process information in the United States and other countries where authorized infrastructure or personnel operate. Anthropic's commercial infrastructure, for example, supports international processing. Applicable contracts and legal safeguards govern transfers; we do not claim that the laws of every destination are identical to those in your state.
We post a revised policy with a new date when our practices change. Before a material change applies, we provide appropriate notice and obtain new permission when required. We do not use a policy update to retroactively authorize a new use of previously collected consumer health data without the required consent.
Privacy: privacy@alova.dev
Support: support@alova.dev
Futurion LLC (dba Alova), 522 W Riverside Ave, Ste N, Spokane, WA 99201, United States.