Privacy Policy
Last updated: 12 November 2026
1. Data Collection
Nilu collects health data necessary for period tracking. This includes cycle dates, symptoms, mood logs, and physical signs. If you choose, you can also log pregnancy test results and — once you turn it on in Privacy settings — sexual activity. Your data is primarily stored on your device. If you use pregnancy mode, this also includes your pregnancy record (last period and due date; how the pregnancy ended — saying so is optional), your appointments and notes, whether you are trying to conceive, and the blood pressure and weight readings you enter. If you use the pregnancy tools, this also includes what you record in the contraction timer and your answers about your baby's movements, your birth plan and your hospital bag list. These records are stored encrypted on your device and never leave it unless you export them or turn on cloud sync (section 4). For your account we also process your email address, your name if provided and an account ID; if you enter your date of birth in Profile → Personal Info, your date of birth (encrypted on the device, and in the cloud copy if cloud sync is on); in the free version, technical information such as your IP address when ads are shown (section 7); and, if you subscribe or make an in-app purchase (such as an outfit for Nilu), your purchase information. Data is collected electronically when you enter it in the app, import it from a health app (section 8) and from your sign-in provider.
2. How data is used
Your data is used to provide cycle predictions, health suggestions and the partner features. Your health data is not used for ad targeting and is not sent to ad networks. The services we rely on to run the app (section 6) receive only what their own function requires. Legal bases: running your account, verifying your subscription and setting up partner pairing are necessary to perform our contract with you; showing non-personalised ads in the free version and keeping the service secure rely on our legitimate interest; storing health and sexual-life data in the cloud copy and sharing it with your partner happen only with your explicit consent (for Türkiye: KVKK Art. 5(2)(c), 5(2)(f) and 6). Records that stay on your device never reach us.
3. Partner Sharing
The partner feature is optional and requires signing in with Apple, Google or email; pairing uses your account’s identifier. No phone number is requested. You approve the pairing request, and only one partner can be connected at a time. Turning sharing on also requires your explicit consent, because the closeness status (desire level and affection needs) concerns your sex life and is a special category of personal data. Only this status reaches your partner; your cycle dates, symptoms, pain records, notes and your pregnancy and postnatal records are not sent. When you turn sharing off or remove your partner’s access, your last status is deleted from the server. Your partner can also disconnect from their side. A pairing code or invite link connects only one person: when you approve someone, remove your partner’s access or your partner leaves, your codes are revoked and any other pending requests are deleted. Your partner’s app opens in the theme you choose; for this, the name of your active theme (for example “Ocean”) is also kept in the same record. The theme name is not health information and is written even while closeness sharing is off.
4. Account and Cloud Sync
An account is optional: you can use the app without one; to use cloud backup, move to a new device or use the partner feature you sign in with Apple, Google or email. When you sign in, Firebase Authentication receives an identifier for your account, your email address (Apple's relay address if you chose to hide your email) and your name if provided. If you sign up with email, Firebase stores your password only in irreversible (hashed) form; we can’t see it. Signing in alone sends no health data. Cloud sync is turned on only if you separately give your explicit consent: your period and daily logs (including sexual activity and pregnancy tests), pregnancy and postpartum records, measurements, cycle settings and profile details are then stored in Google Cloud Firestore, linked to your account, and synced between the devices where you sign in with the same account. Only you can access this copy; it is not sent to your partner. It is encrypted in transit and at rest but is not end-to-end encrypted. The servers may be outside your country; because health data is a special category of personal data, this processing relies on your explicit consent, and the consent screen states clearly that the data is stored on servers abroad. You can withdraw consent at any time on the app's "Account & cloud backup" screen: turning sync off deletes the cloud copy. You can delete your account on the same screen.
5. Data Security
Health data on your device is stored encrypted. Data you send to your partner and — if you turn it on — your cloud copy are encrypted in transit and stored encrypted on the server. This is not end-to-end encryption: because the keys are held by the service provider, the provider can technically access that data. Server rules allow only your own account to read your cloud copy. Data that never leaves your device is unaffected.
6. Third-party services
The app uses: Firebase (Google) — if you use the partner feature, for the pairing code, the closeness status you choose to share and your theme name; for signing in with Apple, Google or email (Firebase Authentication); if you turn on cloud sync, for the copy of your records (Cloud Firestore); if you allow notifications, for announcements and offers (Firebase Cloud Messaging); RevenueCat, Apple and Google Play for verifying subscriptions and in-app purchases; Google AdMob for ads in the free version. Each service receives only the data its own function requires. Unless you turn on cloud sync, your cycle records, symptoms, pain records, notes, pregnancy and postnatal records and blood pressure and weight readings are not sent to any of them; if you do, they go only to Firebase — never to the ad or subscription services. Server locations: the cloud copy and partner data are on Cloud Firestore servers in Europe (eur3: Belgium and the Netherlands); Firebase Authentication, Google Sign-In and Google AdMob run on Google’s global servers, mainly in the US; RevenueCat operates in the US and receives your account ID and purchase information for subscriptions and in-app purchases; Apple (Sign in with Apple, App Store payments) and Google Play (payments) use their own servers; on iOS the app also asks the App Store whether a newer version is available (no personal data is sent). Our website is hosted on GitHub Pages (US): when you visit it, GitHub receives your IP address; the site uses no cookies or analytics.
7. Advertising
The free version shows ads: banners at the end of content screens (library, articles, yoga, recipes) and a single card labelled “Ad” among the articles in the library list; a full-screen ad at most once a day before an exercise session (or, if it doesn’t load in time, when you close the finished session) — never in your first session or on sensitive days, such as a day you logged severe pain; and — only if you choose — rewarded video ads that unlock Premium for 2 days (once per device) or lend you one shop piece from the wardrobe for 24 hours (at most once a day). Whether this trial has been used (only a "used" flag) is kept on your device — on iOS in the keychain — so it remains if you delete the app; it is never sent anywhere. Which piece you borrowed and when the loan ends are also kept only on your device. Ads are not personalised: the app sends no health data, cycle information or profile data to the ad network. To serve an ad, the network receives technical information about your device and connection (such as your IP address). Premium removes ads.
8. Device permissions, Apple Health and Health Connect
The camera is used only to scan a partner QR code; no image is stored or sent anywhere. Face ID, your fingerprint or your device passcode is used only for the app lock, and verification happens on your device. If you allow notifications, reminders are prepared on your device and their contents are not sent anywhere; Nilu may also send announcements and — only if you turn them on — offers as push notifications: for this, your device’s notification token is registered with Google’s Firebase Cloud Messaging and subscribed to topics by language and the notification types you choose. The token is not linked to your account and we do not store it; you can turn both types off in Notification settings. If you allow Apple Health or Health Connect access, the app reads only your menstrual flow. If you turn on “Write my period days to Health”, it also writes the period days you record to Apple Health or Health Connect. You can withdraw any of these permissions at any time in your device settings. If you turn on discreet notifications, the lock screen does not show what a reminder is about.
9. Retention and deletion
Your health records stay on your device until you delete them. Apart from your account, server-side data exists in only two cases. Partner feature: the pairing code, the partner connection, the closeness status you share and your theme name; turning sharing off deletes your status; when you remove your partner’s access or your partner leaves, the connection, the status and the theme name are deleted, and your pairing code and any open invite link are revoked. A new code is created only when you want to pair again. Account and cloud sync: your account is kept until you delete it, and your cloud copy for as long as sync stays on; turning sync off deletes the copy (only a “sync turned off” marker remains so your other devices stop too), and deleting your account deletes the copy and the account entirely. If you signed in with Apple, the app’s link to your Apple ID is revoked as well. “Delete all my data” removes everything: your account and cloud copy, the pairing code, the closeness record and the identifier are deleted, and on-device data is wiped. This cannot be undone.
10. Your rights
You can export, correct, restore from a backup or completely delete your data in the app at any time. You have the right to learn whether your personal data is processed and to request information about it; to learn the purpose of processing and whether it is used for that purpose; to know the third parties in Türkiye or abroad to whom it is transferred; to have incomplete or inaccurate data corrected; to have it erased or destroyed; to have such corrections and erasures notified to those third parties; to object to an outcome against you arising solely from automated analysis; to object to processing and to data portability where applicable; and to claim compensation for damage caused by unlawful processing (KVKK Art. 11 for Türkiye; equivalent rights under other applicable laws). Write to niluapp@proton.me; requests are answered within 30 days at the latest, as a rule free of charge. If your request is rejected, you find the answer insufficient or no answer is given in time, you can complain to Türkiye’s Personal Data Protection Board (KVKK Art. 14) or to the data protection authority where you live. Data controller: Hürkan Çelebi, Bağcılar/İstanbul, Türkiye.
11. Changes
When this policy changes, the “last updated” date above is revised. You can always read the current text inside the app.