Nevada privacy
Nevada Consumer Health Data Privacy Policy
Effective July 16, 2026 · Last updated July 20, 2026
This policy describes how Loommi, Inc. handles consumer health data under Nevada law through Loommi services made available to Nevada consumers.
Some described accessibility, safety, memory, recognition, cloud, and support features are planned and may not be available. Describing them is not a statement that Loommi currently collects the related information and is not consent. A feature remains off until Loommi provides the applicable notice and obtains affirmative consent, unless processing is necessary to provide the product or service the consumer requested as permitted by Nevada law.
1. Contact
Loommi, Inc. 14 Tews Ct Newport, RI 02840, USA Telephone: (781) 718-2161 support@loommi.ai — subject “Privacy request”
2. Consumer health data categories and purposes
Depending on a feature the consumer or parent enables, Loommi may process:
| Category | Purpose |
|---|---|
| Optional accessibility information and related health or disability inference | Apply a user-selected communication, sensory, hearing, speech, mobility, learning, or other accessibility setting. |
| Health-related conversation content or saved memory | Provide the activated response or memory the user requested and make it accessible and deletable. |
| Suicide, self-harm, eating-disorder, abuse, violence, crisis, or other safety classification | Select a protective response, present crisis resources, interrupt harmful output, and measure the safety system. |
| Voice recording, face image, voiceprint, face geometry, or recognition result associated with health or identity | Provide optional recognition after a separate person-specific biometric permission. |
| Consent, withdrawal, deletion, device, and security records | Apply choices, authenticate the household, protect the information, and demonstrate compliance. |
Loommi does not use consumer health data for targeted advertising, sale, data brokering, general-purpose AI-model training, diagnosis, or a credit, insurance, employment, housing, education, health-care, or other legal or similarly significant decision.
3. Sources
Sources may include the consumer; the consumer's parent or legal guardian; an activated microphone or camera interaction; on-device safety or recognition processing; the paired device or application; and a processor acting under Loommi's instructions. Loommi does not buy consumer health data from data brokers.
For recognition kept only on one household robot, the owner may record another adult household member's choice only after that adult receives the notice, agrees, and asks the owner to record it. This local choice does not permit online health-data or biometric processing. Another competent adult must complete an online adult flow themself. A household owner cannot act for a child whose parent or legal guardian is someone else.
4. Collection, use, and manner of processing
Loommi collects only the category identified in the feature notice and uses it only for the stated purpose. Optional accessibility information is not required for an unrelated core function. Optional memory, recognition, backup, cloud, and support upload remain off until enabled.
Depending on the enabled feature, Loommi processes consumer health data on the robot, in the companion application, in Loommi's restricted cloud systems, or through a processor identified in the feature notice. On-device processing is the planned default for ordinary recognition and conversation. An optional cloud path remains off until the applicable notice and consent are presented. Loommi does not silently move information from a local mode to a cloud mode.
Before consent-based collection, Loommi clearly states the categories, purposes, uses, recipient categories, and withdrawal method. The consumer takes an unambiguous affirmative action. A material new category or purpose requires a new consent before processing.
5. Sharing and processors
Loommi does not currently share consumer health data with a third party or affiliate for an independent purpose. It has no affiliate with access to consumer health data.
Depending on the enabled feature, processors may include Cloudflare for restricted API and security services and Supabase for restricted account, consent, profile, and optional cloud storage. Loommi will identify another cloud, support, or verification processor before consumer health data is sent to it. A processor acts under a binding contract, follows Loommi's instructions, uses reasonable security, assists with rights requests, and may not use the data for advertising or its own model training.
Before a disclosure that requires sharing consent, Loommi will identify the category and recipient and obtain a consent separate from collection consent.
Loommi does not permit a third party to collect consumer health data over time and across different Internet websites or online services when a consumer uses Loommi's website, Store, application, device, or online service.
6. Sale
Loommi does not sell consumer health data or offer it for sale. It does not condition a product or service on an authorization to sell. A general policy acceptance does not authorize a future sale.
7. Rights and request process
A Nevada consumer may ask Loommi to:
- confirm whether Loommi collects, uses, shares, or sells their consumer health data;
- access that data;
- review the data and request correction of inaccurate information;
- obtain a list of third parties with whom it was shared or sold;
- withdraw consent for future collection or sharing; and
- delete the data.
Use the application's Privacy Center when available or email support@loommi.ai with the subject “Privacy request.” Use the same process to review data or request a change, and identify the information you believe is inaccurate. You do not need to create a new account. Loommi may authenticate the consumer or the authority of a parent, guardian, or authorized representative.
Loommi ordinarily responds within 45 days after authentication and may take one additional 45-day period when reasonably necessary after providing notice and the reason. If Loommi declines a request, it explains why and how to appeal. Appeal through the same channel with the subject “Privacy appeal.” Loommi decides the appeal within 45 days and identifies the Nevada authority that can receive a complaint if the appeal is denied.
Loommi does not unlawfully discriminate because a consumer exercises a right. Withdrawing an optional permission may stop the feature that requires the information but does not disable unrelated features.
8. Deletion and retention
Not later than 30 days after authenticating a deletion request, Loommi deletes the covered consumer health data from its active records and network and notifies each affiliate, processor, contractor, and other third party with which Loommi shared the data. Each notified recipient must delete the covered data from its active records and network not later than 30 days after receiving the notice. Loommi completes deletion sooner where an immediate feature control exists.
Loommi's isolated recovery copies are overwritten within 90 days and are not restored to active use. If an affiliate, processor, contractor, or other third party holds the data in an archived or backup system, deletion may be delayed only as necessary to restore that system and no later than Nevada's outside limit of two years after the request was authenticated.
An offline device completes a queued command when it reconnects; the consumer may use local deletion or factory reset immediately. A broken device that cannot be reset enters restricted service intake for erasure or destruction of accessible information.
The Loommi Privacy Notice provides the category schedule. Consumer health data is not retained indefinitely merely because it could improve a product.
9. Security
Loommi limits access to people and processors who need it for the requested purpose and uses safeguards appropriate to the sensitivity of the data, including minimization, role-based access, adult authentication, encryption in transit, encryption at rest where cloud data is stored, device credentials, logging, processor restrictions, deletion controls, testing, and incident response. No system is completely secure.
10. Changes and how Loommi gives notice
Before collecting a new category, using consumer health data for a new purpose, or adding a recipient that requires consent, Loommi will update this policy, provide an in-context notice, and obtain the applicable affirmative consent. Loommi notifies affected consumers of a material policy change before it takes effect through a direct account email, a conspicuous in-application notice, or both, using the contact and service channels available for the affected feature. A policy update is not retroactive consent.