Skip to content
← HormonaIQ home

Privacy Policy

Effective

This policy covers the HormonaIQ app for iOS and Android, the website hormonaiq.com and its waitlist. The short version:

  • Your health data is yours. We do not sell it and we do not use it for ads.
  • The app has no advertising or analytics SDKs.
  • Ora, the AI companion, stays off until you turn it on.
  • You can export everything, and deleting your account is immediate and permanent.

Who we are

HormonaIQ is developed and run by Riazul Islam, an individual developer, who is responsible for your data under this policy (the data controller). In this policy, “we” and “us” mean Riazul Islam as the developer of HormonaIQ.

Contact: contact@hormonaiq.com

What we collect

Your account

Your email address and password, handled by Supabase Auth. We never see or store your password ourselves. If you sign in with Apple or Google instead, we receive your email address (or Apple’s private relay address) and, if you allow it, your name; no password is created. During setup we also store your year of birth, your time zone and the conditions you choose to track.

Health and cycle data

What you log: period and bleeding dates, cycle settings and predictions, daily symptoms, mood, energy, sleep, notes and condition-specific entries such as blood pressure or bone-density results. This is the core of the app, and it is saved to your account so it syncs and is backed up.

Questionnaires

Your answers to screening questionnaires such as PHQ-9, DRSP and ASRS, including questions about mood and about thoughts of self-harm. If an answer suggests you may be at risk, the app shows crisis resources. We do not contact anyone on your behalf.

Lab documents

If you upload a PDF to the lab vault, our server extracts its text and then discards the original file. We keep the extracted text, encrypted, in short passages together with search vectors made from them, so Ora can find what is in your documents.

Ora conversations

If you turn Ora on, your messages and Ora’s replies are saved encrypted on your phone. To write each reply, your message, the recent conversation and the logs Ora needs are sent to our server and to the AI providers listed below. Our server does not keep a copy of the conversation. If you also turn on Ora’s memory, Ora keeps a small number of short facts from your messages so it can remember context between conversations.

Reminders and settings

Whether daily reminders are on and the time you chose, plus your app preferences and privacy consents. Reminders are scheduled on your phone as local notifications. The app does not register for push notifications, so no push token is created or sent to us or to Expo.

Technical data

When the app talks to our server, our hosting and monitoring services record technical details such as the time, the part of the service that was called, response times and any server error. Your IP address is processed by our hosting providers to deliver the service and appears in their short-lived logs. The app contains no analytics or advertising SDK. If the app crashes, it sends a crash report to Sentry: the error, the app version, your device model and OS, and a random account ID. Crash reports contain no health data, email address, name or screen recording.

What we do not collect

We do not collect your location, contacts, photos, advertising ID or payment details (the app is free). Voice features are switched off in this version, so the app does not record or send audio. We will update this policy before that changes.

How we use it

We use your data only to run HormonaIQ for you:

  • to keep your account, sign you in and let you reset your password;
  • to save, sync and back up your logs, and show your calendar, cycle predictions and insights;
  • to score questionnaires and build the clinician report you choose to share;
  • to write Ora’s replies and search your lab documents, if you use those features;
  • to show crisis resources when your answers suggest you may be at risk;
  • to send account emails and the reminders you switched on;
  • to keep the service secure, and to find and fix errors.

We do not use your health data for marketing, and we do not build advertising profiles.

Ora and AI processing

Ora is an AI companion. It is off by default and only processes your data after you turn it on. You can turn it off at any time in the app; your logs keep working either way.

When Ora is on, your message, the recent conversation and the logs it needs are sent from our server to OpenRouter, our AI service, which routes it to a model provider such as Groq. The model and provider can change over time. These providers process requests under their own terms, and we have configured every request so that it is not used to train AI models.

Ora may also run a general web search through Tavily. Ora is instructed to keep these search queries free of personal details. Lab-vault documents are processed by AI embedding models via OpenRouter, under the same no-training setting, to make them searchable, whether or not Ora is on.

Ora’s memory is a separate, optional consent. When it is on, Ora keeps at most 30 short facts, stored encrypted. Facts about crisis or self-harm are filtered out. Facts older than 180 days are never recalled and are deleted by a nightly clean-up.

Ora can be wrong. It is not a doctor and does not diagnose or treat anything.

Who processes your data

These companies process data for us, as our service providers, only to run the features described here. We do not share your data with anyone else, except where the law requires it.

Supabase

Your sign-in email and password (stored by Supabase Auth as a hash), and the database that holds your account, logs and settings. Waitlist entries are stored in a Supabase database too.

Why: Sign-in, password reset codes and data storage.

Apple and Google (only if you use their sign-in)

A sign-in request from the app. They confirm who you are and return your email address (Apple can hide it behind a relay address) and, if you allow it, your name. No health data is sent to them.

Why: Sign in with Apple and Sign in with Google.

Railway

Runs our server and its short-lived cache in Southeast Asia, so every request from the app passes through it.

Why: Hosting.

OpenRouter, and the model providers it routes to

Only if Ora is on: your message, the recent conversation and the logs Ora needs for that reply. For the lab vault: the text extracted from a document you upload, split into short passages. OpenRouter routes requests to model providers such as Groq, and lab documents are processed by AI embedding models. Requests are configured not to be used for training.

Why: Writing Ora’s replies and making your lab documents searchable for you.

Tavily

Only if Ora is on and decides to look something up: a short, general search query. Ora is instructed to keep it free of personal details. Your logs and identity are not sent.

Why: General background web search for Ora.

Neo4j Aura

Holds our clinical reference library, which contains no personal data. When Ora looks something up there, the condition or topic name is sent.

Why: Clinical reference look-ups for Ora.

Resend

Your email address and the content of a transactional email we send you.

Why: Account emails, such as account recovery messages.

Sentry and Logfire (Pydantic)

Server error reports and request traces: timings, error details and a random request ID. Request bodies, cookies and sign-in tokens are removed from error reports, and fields that match health terms are scrubbed from traces. App crash reports (Sentry only): the error, app version, device model and OS, and a random account ID, with no health data, email or name.

Why: Finding and fixing server errors and app crashes.

Vercel

Hosts this website and counts page views with Vercel Web Analytics, which sets no cookies.

Why: Website hosting and anonymous visit counts.

Web3Forms

A copy of a waitlist signup, emailed to us.

Why: Waitlist notifications.

What we never do

  • We never sell or rent your personal data, and never trade it with anyone.
  • We never use your health data for advertising or marketing, and never share it with ad networks or data brokers.
  • We never use your data for data mining or to build behavioural profiles.
  • We never retroactively change how we use data you have already given us.

Security

All traffic between the app and our server uses encrypted HTTPS (TLS) connections. The copy of your data on your phone is stored encrypted on the device.

On our server, daily-log notes and self-harm answers, Ora memory facts and lab-document text are additionally encrypted field by field (AES-256-GCM) before they are stored. Database access is limited per user with row-level security, so one account cannot read another account’s rows. Supabase also encrypts the whole database at rest.

No system is perfectly secure. If a breach affects your data, we will tell you and the relevant authorities as the law requires.

How long we keep data

  • Your account and everything in it is kept until you delete it. Deleting your account removes it immediately and permanently (see Delete your account).
  • A self-harm answer in a daily logis erased from our server 72 hours after you save it. The rest of that day’s log is kept.
  • Ora memory facts are never recalled after 180 days and are cleared by a nightly clean-up. You can clear them yourself at any time.
  • Data exports you request are deleted from our server after their 7-day download window.
  • Deletion record. When you delete your account we keep one permanent record: the random sign-in ID of the deleted account and the time it was deleted. It holds no email address and no health data. It exists so that a sign-in token issued before the deletion cannot quietly re-create the account.
  • Server error reports, app crash reports and traces in Sentry and Logfire are kept for up to 30 days. Personal details and health terms are scrubbed before they are sent.
  • Database backups are kept for up to 7 days, so deleted data can remain in a backup until it expires.

Your rights and choices

Wherever you live, you can:

  • Export your datain the app: You → Privacy & data → Export my data. You get a JSON file of everything in your account.
  • Delete your account and all datain the app: You → Privacy & data → Delete account and all data. It is immediate and permanent. Without the app, request deletion by email; we complete email requests within 30 days.
  • Correct your data by editing or deleting any log in the app.
  • Withdraw consentat any time: turn Ora or Ora’s memory off, delete Ora’s chat history, or remove a lab document.
  • Ask us for access to your data, or object to or restrict how we use it, by writing to contact@hormonaiq.com. We respond within 30 days.
  • Complain to the data protection authority where you live.

Age requirement

HormonaIQ is for adults aged 18 and over. We do not knowingly collect data from anyone under 18. If you believe someone under 18 has an account, contact us and we will delete it.

Not medical advice

HormonaIQ is not a medical device and does not diagnose, treat, cure or prevent any condition. Scores, predictions, insights and Ora’s replies are information to help you talk with a clinician, not medical advice. Always consult a qualified healthcare professional. If you are in crisis, see our crisis resources.

Website and waitlist

This part covers the waitlist on hormonaiq.com. It is separate from your app account: deleting your app account does not remove a waitlist entry, so ask us if you want both removed.

What we collect

When you join the waitlist, we collect the information you choose to submit: your email address, the condition or experience that brought you here, symptoms you track, tools you currently use, what would make the product useful to you, and whether you are open to a feedback call.

Your answers about conditions and symptoms are health-related, so we treat them with the same care as the rest of your data. Every one of them is optional.

We also store the page that referred you and your browser type (user agent), so we can tell which channels bring people here and spot spam signups.

If you opt into a feedback call, we may also record notes from that conversation with your explicit consent. You can withdraw this consent at any time.

How we use it

Your information helps us understand who we are building for. We use it to:

  • Send early-access invitations and product updates. Only meaningful updates about the product and your access: no spam, no daily digests.
  • Shape product decisions. Aggregated responses (never individual data) inform what we build first. Quotes from the waitlist appear in marketing materials only with your explicit permission.
  • Reach out for optional research conversations, if you opted in.

Where it lives

Waitlist submissions are stored in a Supabase database that only our server can read or write. A copy of each signup is also emailed to the founding team through Web3Forms. Data is encrypted in transit (TLS) and at rest, and access is limited to the founding team.

If you join a feedback call, notes are stored separately from your waitlist profile and associated only with the email you provided.

Your choices

You can decline to answer any question on the signup form without losing your place. Every field except email is optional. You can unsubscribe from any email using the link at the bottom of every message we send, and you can ask us to delete your waitlist entry at any time.

Cookies

This site does not set cookies. We count page views and referral sources with Vercel Web Analytics, which works without cookies and does not identify you across sites. No tracking cookies, no behavioural profiling, no third-party ad networks.

Where data is processed

Our database is hosted by Supabase in Singapore, and our server runs on Railway in Southeast Asia. Some of our service providers, including the AI providers, process data in the United States and other countries. Where the law requires it, we rely on those providers’ contractual safeguards for international transfers.

Changes to this policy

If we change this policy in a way that affects how we handle your data, we will tell you in the app or by email before the change takes effect, and update the date at the top of this page. This version is effective from 21 October 2026.

Contact

Questions, concerns or requests: contact@hormonaiq.com. For help with the app, see Support.