FerroLady privacy policy

Effective 31 October 2026

The short version

  • What you log in FerroLady is health information, and we treat it that way.
  • It is used to run the app for you — nothing else. We do not sell it, share it with advertisers or insurers, or use it for advertising.
  • There is no advertising in the app. Google Firebase helps us see how it is used, and our own servers deliver your reminders and collect crash reports. They learn that something happened, such as that you logged a dose, and never what you entered: no results, symptoms, cycle days, notes, or whether you took it.
  • Your data goes to a doctor only if you choose to send them a report yourself.
  • You can export everything, and delete your account and all of it, from Settings at any time.

Who we are

FerroLady is operated by Royal Nation LLC (“we”, “us”). We are responsible for the personal information described here. For any privacy question or request, email admin@royalnationllc.com. Please do not include passwords, sign-in codes or health records in your first message.

What we collect

Account. Your email address and a sign-in identifier. If you choose to sign in with Apple or Google, we receive the email address (and, if you allow it, the name) that provider shares with us.

Profile and settings. Your region, time zone, preferred lab units, an optional note about the supplement you take, reminder times, and a record of which version of our consent you accepted and when.

Health information you enter. Blood-test results with their dates and units, whether you took your supplement and any side effects you note, symptom check-ins, period and bleeding records, your recovery-journey stage, appointments and what happened at them, and any notes. We collect only what you type in — FerroLady does not read data from Apple Health, Google Health Connect, wearables or any other app or device.

Reports. When you make a report for your doctor, we store the PDF and a copy of the entries it was made from, so it can be opened again later exactly as it was.

Notifications. If you allow reminders on iPhone or Android, our own push server receives your sign-in identifier, your device’s push token, a random identifier for this installation of the app, the app and operating system version, language and time zone, and the text of each reminder, so it can deliver them to your device. It records whether each reminder arrived and was opened. It uses your IP address only to limit the rate of requests and does not store it. This traffic passes through Cloudflare. Reminders on the web use your browser’s push subscription instead.

Purchases. If you buy the Recovery Pass, a transaction identifier, the store, product, date, and whether it was a test purchase. Apple or Google takes the payment; we never see or store your card details.

Usage events. The names and times of actions such as completing a check-in or making a report, linked to your account. These records have no field for health content: they never contain your notes, symptom scores or lab values.

Analytics and crash reports (Google Firebase). On iPhone and Android, we choose to send Google two things: that a dose was logged — never whether it was taken or skipped — and that the Recovery Pass screen was opened. Firebase also records, automatically, that the app was opened and for how long, when it was first opened, the app version, your device model, operating system and language, an approximate location worked out from your IP address, and a random identifier for this installation of the app. If you buy the Recovery Pass, it records that a purchase of that product was made, and its price. If the app crashes, Firebase Crashlytics receives the technical details of the crash along with your device and operating system information and which of the two actions above came just before it. Crash and error reports also go to our own error server, with the technical details of the error, your device and operating system, the app version and the random installation identifier used for notifications; they do not include your name, email, sign-in identifier or what you tapped. We do not give Google your account identifier, name or email, and we switch off the advertising identifier and screen-by-screen tracking, so this is tied to an installation of the app, not to you.

Technical data. Our hosting and infrastructure providers process routine technical information, such as IP addresses and request logs, to deliver and secure the service.

How we use it

Only to provide FerroLady to you:

  • signing you in and keeping your records in sync across your devices;
  • showing your records back to you, and making the reports you ask for;
  • sending the reminders you choose, at the times you choose;
  • verifying Recovery Pass purchases;
  • answering your support requests; and
  • understanding, in aggregate, which parts of the app are used, and finding and fixing crashes, so we can improve it.

FerroLady does not interpret your results, diagnose anything or give medical advice, and nothing you log is used to decide what the app shows you beyond your own records. We do not use your information for advertising, profiling or automated decisions about you, and we do not sell or rent it.

Our legal basis

Where laws such as the EU and UK GDPR apply, we handle your health information on the basis of your explicit consent, which you give during sign-up. Your other information is handled because it is necessary to provide the service you asked for. You can withdraw consent at any time by deleting your account; withdrawal does not affect processing that happened before it.

Who else handles it

We use a small number of service providers, each only for its part of running the app, and each bound to process your information on our behalf:

  • Clerk — sign-in and account management.
  • Convex — stores your records and runs the app’s back end.
  • Vercel — hosts this website and makes report PDFs.
  • RevenueCat — verifies in-app purchases, linked to your sign-in identifier.
  • Google Firebase — usage analytics and crash reports from the iPhone and Android apps, described above.
  • Cloudflare — carries traffic to our own push and error servers, which deliver reminders to iPhone and Android and collect crash reports.
  • Apple and Google — app stores, payments, and the push services (Apple Push Notification service and Firebase Cloud Messaging) that our push server uses to reach your phone. Web reminders go through your browser’s push service.

Beyond these providers, we share your information only if you ask us to, or if the law requires it. A report you export or share leaves FerroLady under your control; we cannot recall or delete copies you have sent elsewhere.

Where it is processed

Our providers are based in, and process information in, the United States, among other places. If you live elsewhere, your information is transferred there. Where the law requires it, we rely on recognised safeguards for these transfers, such as the European Commission’s standard contractual clauses included in our providers’ data processing terms.

How long we keep it

Your records stay in your account until you delete them or delete the account. The 90-day history view on the free plan only changes what is displayed — nothing is deleted because of it, and everything is always included in your export.

When you delete your account, we immediately delete your profile, every record and every stored report from our active database, remove your sign-in account, delete your record from our push server and ask RevenueCat to delete its record of you. Providers keep backups and technical logs for limited periods under their own retention schedules, after which they are overwritten; we do not restore deleted accounts from them. Apple and Google keep their own records of your purchases, which we cannot delete. Analytics and crash reports are tied to an installation of the app rather than to your account, so deleting your account does not remove them; it does remove the link between that installation and you on our push server. Google keeps event-level analytics data for 2 months and user-level data for up to 14 months, then deletes it.

Your rights and choices

  • Export — Settings → Export gives you all of your records as a file.
  • Delete — Settings → Delete your account removes everything, or see the account deletion page if you no longer have the app.
  • Correct — you can edit or remove any entry in the app.
  • Reminders — turn them off in Settings, or in your device’s notification settings.

Depending on where you live, you may also have rights to access, correct, restrict or object to processing, and to complain to a data-protection authority. Email admin@royalnationllc.com to exercise any of them. We may need to confirm the request comes from the account owner, and we respond within the time the law requires.

Consumer health data (United States)

Some US state laws, including Washington’s My Health My Data Act, give specific rights over consumer health data. Everything you log in FerroLady is consumer health data. We collect the categories listed under “What we collect”, directly from you, for the purposes listed under “How we use it”. We share it only with the providers listed above, to run the service and to understand how the app is used. We do not sell consumer health data. You can access, delete or withdraw consent for it as described above; to appeal a decision we make about a request, reply to our response at admin@royalnationllc.com and ask for it to be reviewed.

Security

Information is encrypted in transit, and access to the app’s data is checked on every request so that one account can never read another’s. No system is perfectly secure; if a breach affected your information, we would tell you and the relevant authorities as the law requires.

Children

FerroLady is intended for adults aged 18 and over. We do not knowingly collect information from children. If you believe a child has created an account, email admin@royalnationllc.com and we will delete it.

Changes to this policy

If we change how we handle your information, we will update this page and its effective date, and tell you in the app before any significant change takes effect.

Back to FerroLady