Lua Care

Privacy Policy

Last updated: October 23, 2026

1. Introduction

Lua Care uses personal and health data to provide support, records, and AI features. This policy covers the app and its related web surfaces. Reviewed October 23, 2026.

Your health data remains sensitive even when we use internal identifiers or remove names and emails from a workflow. We do not claim your conversations, files, or history are anonymous. Messages, notes, and attachments may contain information that identifies you.

We limit context to the feature. In workflows separating identity from context, we do not automatically attach your account’s contact details; content you submit and a profile you choose to share may include a name or other identifiers. Avoid providing other people’s data without authorization.

Accepting terms does not replace specific AI, health, or connection permissions. Each feature retains its controls. This update does not activate conversation exports for learning or a training program.

2. Information we collect

We collect the following information, which you provide to us voluntarily:

Profile data:

  • Name or nickname (may be anonymous).
  • Year of birth.
  • Hormonal stage (menstrual cycle, perimenopause, menopause).
  • Contraceptive method (if applicable).

Health data, conversations, and documents:

  • Physical and emotional symptoms you log.
  • Menstrual cycle dates and data.
  • Daily menstrual flow level and any free-text notes you choose to log.
  • Sleep information (hours, quality).
  • Weight and height (if you choose to provide them; they are optional).
  • Information about PCOS (if you choose to provide it).
  • Food and physical activity logs.
  • History and studies you provide, laboratory results and reference ranges, supplements, doses, and reported intake.
  • Questions, responses, plans, preferences, corrections, notes, images, and documents you submit; text and data extracted for analysis. Audio and transcripts when you use voice.

Data from devices and services you connect:

  • Depending on permissions and source: sleep and its stages, activity and workouts, steps, heart rate, heart-rate variability, recovery, temperature, oxygen saturation, weight, and available cycle data. Not every device or connection provides every category.
  • We use them to show your records, trends, context, and personal follow-up; they enter AI features only when your permissions and the source’s terms allow it. They are not used for advertising or brought into model training by this notice.
  • When you authorize an account connection, we may process account identifiers, tokens or sessions, and sync status. If Lua’s flow asks for a username, password, or verification code, Lua receives them to complete access: they are sent encrypted to the connection service, not to the bot. Persistent tokens or sessions are protected with encryption; reauthentication may be required.

Optional intimate health module:

  • You may optionally enable the intimate health module to log libido level, sexual activity, and comfort during intercourse. This information is entirely optional, stored privately under your privacy controls, and used only to detect patterns related to genitourinary syndrome of menopause (GSM) and your hormonal well-being. You can disable the module at any time; previous data is retained only if you choose to keep it.

Technical data:

  • Internal account and session identifiers; app, bot, model, configuration, and tool versions when recorded.
  • Dates, times, time zone for routines, duration, usage, retries, errors, and operation status; technical security and support records.
  • Permissions and consents, their versions and dates when collected. Technical records may remain linked to your account through internal identifiers.

Pregnancy pause mode:

  • The Lua Care application is NOT functional for pregnancy follow-up. We do not collect information relevant to that state. When you activate pregnancy mode, the app stops calculating cycle phases and performing usual hormonal tracking functions. Although you can continue logging food, sleep or other data, these are not processed for gestational follow-up. We recommend consulting a doctor or gynecologist and using a specific application designed for pregnancy tracking.

3. How we use your information

We process data needed for the features you use:

  • Maintain your account, records, and history and handle support requests.
  • Relate cycle, symptom, food, sleep, activity, study, and supplement signals with their dates and provenance.
  • Answer questions, analyze attachments, and prepare plans, records, reminders, and follow-up under each feature’s permissions.
  • Allow Lua and the specialists to review relevant context and prepare cloud-based follow-up even while the app is closed. Notifications depend on your settings and permissions.
  • Measure operation, usage, and failures through technical metadata and diagnose problems. This does not mean every error is detected or every conversation is reviewed by a person.

We do not sell your health data or use it for personalized advertising. We do not use your conversations or health files to train AI models. The technical quality archive may retain error, version, and usage metadata; export of real questions and answers to an external longitudinal review is not active. Any future learning or research program requiring a new purpose must explain it and obtain the specific authorization required before it begins.

Technical quality review may use external analysis services with access limited to failure metadata, versions, and pseudonymized references. This workflow does not provide chat content, attachments, audio, or credentials. References allow incident investigation through authorized internal access; they do not make records anonymous or give the reviewer general access to your account. Review does not itself execute training or automatically publish changes.

4. Processing with artificial intelligence

With the applicable AI authorization, we use providers according to the enabled feature. Automatic or proactive functions retain the same permissions as use from chat; opening a message does not activate new permissions. Context may include relevant history, messages, notes, studies, and attachments, and does not become anonymous merely by removing direct identifiers.

  • Data that is sent: depending on the feature, health context, messages, notes, images and documents you select, extracted text, plans, and tool results; audio and transcripts if you use voice. Content may contain identifiers you included. Do not send passwords, access codes, or other people’s documents without authorization.
  • Amazon Web Services (Amazon Bedrock) and Anthropic (Claude): process the context, messages, and attachments needed for insights, chats, specialists, analysis, and follow-up, according to the enabled model and feature.
  • ElevenLabs: may process audio or transcripts in voice features that enable it; it does not receive every conversation.
  • Fish Audio: processes audio and transcripts when you choose voice conversation and this provider is enabled.
  • OpenRouter and OpenAI: process the description needed for educational or food images when that feature uses them; this does not give them your complete profile.
  • These providers are subject to confidentiality and data-protection obligations requiring the same or an equivalent level of protection.
  • The data is not used to train third-party AI models.
  • Processing takes place on secure servers with encryption in transit.
  • When you share your profile with a doctor, the medical copilot also processes the structured summary with artificial intelligence in a read-only manner. To contextualize the profile, that processing may include your name, so it is pseudonymized, not anonymous.

AI responses may draw on scientific information and other sources; not every statement is individually verified. See Sources and methodology section.

5. Storage and security

Your data is protected by:

  • Encryption in transit (TLS/SSL) and at rest.
  • Secure authentication with PKCE (Proof Key for Code Exchange).
  • Account-based access controls and Row Level Security on tables that require them; authorized services process data to operate features.
  • Restricted internal access to personal data. The Lua team does not use your name or email to analyze your hormonal profile; operational flows use internal identifiers whenever possible.
  • Cloud infrastructure and connection services with restricted access. No system can guarantee absolute security.
  • Request rate limiting to prevent abuse.
  • Security headers (CSP, HSTS, X-Frame-Options) to protect the application.

6. Data sharing

We only share data in the following limited circumstances:

  • Service providers: Supabase for data, storage, and authentication; Vercel and Amazon Web Services for hosting and execution; Cloudflare for the technical quality archive and infrastructure functions; Cursor (Anysphere) for technical review of failure metadata, without conversation content in that workflow; Amazon Bedrock and Anthropic for AI; Fish Audio and, when enabled, ElevenLabs for voice; OpenRouter/OpenAI for images that use them. Connections may use a Lua-operated gateway on Hetzner servers and your device provider for authentication and sync. They do not all receive all your information; access depends on the feature and configuration.
  • Legal obligation: If required by law, court order, or valid legal process.
  • Protection: To protect the rights, property, or safety of Lua Care, our users, or others.

Sharing your hormonal profile with healthcare professionals:

  • Consent when sharing. Lua Care lets you generate a link to share a structured summary of your hormonal profile (stage, observed evidence, patterns, and history summary) with the healthcare professional you choose. Each time you generate a link, you give your express, specific consent for that act of sharing; we log the date of that consent.
  • You control the link. It is your responsibility to generate the link and decide whom you give it to. Lua Care does not control and is not responsible for the use, storage, or disclosure the healthcare professional makes of the information once shared. The professional acts as an independent data controller, not as Lua Care's processor.
  • Read-only. The professional's access is read-only; they cannot modify your original data in Lua Care.
  • AI-assisted summary. To build the summary and assist its reading, an AI copilot operated through Amazon Bedrock and Anthropic Claude queries your historical data on a read-only basis. To contextualize the profile, this copilot may process data that includes your name; therefore this flow is pseudonymized, not anonymous. Processing is subject to data-protection agreements and is not used to train their models.
  • Educational nature. The summary is guidance-oriented and educational, generated automatically from data you logged (self-reported, not validated clinical measurements), and may contain inaccuracies. It does not constitute a diagnosis and must not be the sole basis for a clinical decision; assessment is the healthcare professional's responsibility.
  • Data accuracy. You are responsible for the accuracy of the information you log; the summary reflects that data.
  • Revocation. You can revoke access at any time from the app. Revocation prevents future access but cannot retrieve or delete information the professional has already seen, downloaded, or retained.
  • Limited scope. Shared data is limited to the structured summary; it does not include free-text notes or the detail of individual logs outside that summary.

7. Data retention

We retain your data for as long as your account remains active. If you request the deletion of your account, we will delete your personal data within a maximum of 30 days, unless the law requires it to be kept for a longer period.

Data of guest (anonymous) users is kept for as long as the session remains active on the device.

Disconnecting a source stops new reads through that connection once revocation completes. Session connections have their Lua authorization revoked; you can also withdraw permissions through the provider. This does not by itself delete previously imported data, derived records, or copies you shared. You may request deletion through available controls or support.

Authentication attempts expire and their encrypted credentials are processed temporarily. Sessions or tokens needed for sync remain protected until revocation or expiration. Technical records, backups, and data required for security or legal purposes may follow a different lifecycle; we do not promise instant deletion. Compacting a report does not automatically delete its originals.

8. Your rights

As a Lua Care user, you have the right to:

  • Access: Request a copy of the personal data we hold about you.
  • Rectification: Correct inaccurate or incomplete data.
  • Deletion: Request the deletion of your account and all your data.
  • Portability: Request your data in a structured, commonly used format.
  • Withdrawal: Withdraw your consent at any time.

To exercise any of these rights, contact us at soporte@lua.care. We will handle your request within a maximum of 15 business days.

9. Adults only

Lua Care is an application exclusively for people over 18 years of age. Use by minors is not permitted. We do not knowingly collect data from anyone under 18.

If we discover that we have collected data from a person under 18, we will delete it immediately.

10. Cookies and similar technologies

The app uses protected device storage for sessions, preferences, and content needed to operate. Web surfaces may use cookies and browser storage for authentication, language, security, and preferences. Technical access records are not therefore anonymous. We do not use your health data for advertising tracking.

11. International transfers

Your data may be processed on servers located outside your country of residence. In those cases, we make sure that adequate protection measures are in place in accordance with applicable law.

12. Changes to this policy

We may update this Privacy Policy from time to time. We will notify you of significant changes through the App. The "last updated" date at the top of this document indicates when the most recent revision was made.

If a change requires new authorization, continued use of the app or an update to this page alone will not be treated as that authorization.

13. Legal framework

We apply the privacy and consumer-protection obligations relevant to the service and your circumstances. This policy does not certify universal compliance with every law or waive mandatory rights. Pseudonymized data may still be personal and health data; removing direct identifiers does not automatically remove those obligations.

14. Contact

If you have questions, comments, or requests regarding this Privacy Policy or the handling of your personal data, contact us at:

soporte@lua.care