Privacy Policy
This policy covers the Ruva apps and this website, myruva.co. The apps run on iPhone, iPad, Mac (the iPad app, on Macs with Apple silicon), Apple Watch, Android phones and tablets, and Wear OS watches. The policy explains what information they handle: what it is, why, where it goes, how long it’s kept, and the choices and rights you have. We’ve tried to write it so it can be read, not just agreed to.
In this policy, “your phone” means the phone, tablet or Mac where you use Ruva. Watches are covered in Watch apps.
The short version
- What you log stays on your phone. Your periods, symptoms, notes, medicines and settings are stored in a database on your device. You don’t need an account, and we can’t see that data. If you use Ruva on a watch, your phone sends it a short summary of today, directly and not through us.
- Cloud features are optional. What you log leaves your phone only if you turn on sync between your devices, make a cloud backup, share with a partner or use the community. Each one sends only what it needs.
- No ads, and no advertising ID. Ruva has no advertising, and this website uses no cookies or analytics. The app uses Google Analytics for Firebase, with its advertising features switched off, to see which screens and features are used, and counts screens that could reveal health matters itself, anonymously, so they never go to Google. Google never receives what you log or your health data. Both are on by default for everyone, and you can switch them off in Settings › Privacy settings. We don’t sell personal information, and we don’t share it for advertising.
- Nudges carry no words. If you haven’t used Ruva for 3 days, we can send your phone or browser a signal with no text in it, and Ruva writes the nudge on your device. To send it we keep only a notification token, your time zone, your check-in hour and the day you last used Ruva. You can switch nudges off.
- Payments add no features. Optional support payments go through the App Store or Google Play. We never see your card details.
- You stay in control. You can download everything you’ve logged and delete everything, from inside the app.
Who we are
Ruva is operated by Zuro Ansa Tech LLP, a limited liability partnership registered in India (“Ruva”, “we”, “us”).
For the personal information described in this policy, we’re the controller under data protection laws such as the GDPR, the “regulated entity” under US consumer health data laws, and the “data fiduciary” under India’s Digital Personal Data Protection Act.
For anything about your privacy, contact us at hello@myruva.co. The same address reaches our grievance officer for India and our data protection contact (encarregado) for Brazil. If we’re required to appoint a representative in the European Union or the United Kingdom, we’ll name them here.
What stays on your phone
Everything you log in Ruva is stored in a private database on your device. That includes:
- period days and flow, symptoms, moods, energy, sleep, discharge, sex, test results, basal temperature, weight, water and notes
- the profile details you choose to enter, such as a name, birth year, height, weight, your goal and cycle settings
- contraception and pill setup, pregnancy and birth dates, contraction timings, medicines and supplements, reminders, health-check answers, course progress, saved guides and where you stopped reading
- after a birth, your baby’s feeds, nappies and sleep, and any tags you create
- your care region and any care contacts you type in
We don’t receive this information, and it isn’t sent anywhere unless you use one of the features described below. Because it lives on your phone, keeping your phone secure (a screen lock, software updates) protects it too.
App lock. You can lock Ruva with your device’s screen lock, such as your fingerprint, face, passcode or, on a Mac, Touch ID or your password. Your device’s operating system checks it, and Ruva never receives biometric data. While the lock is on, Ruva also hides its content from the recent-apps screen and screenshots on Android. The app lock doesn’t apply on a watch.
Your phone’s own backups. On Android phones, tablets and Wear OS watches, Ruva switches off Android’s automatic app backup, so your Ruva data isn’t copied to Google Drive. On iPhone and iPad, if you use iCloud Backup or back up to a computer, that backup can include Ruva’s data, as it does for other apps. On a Mac, a Time Machine or other backup can include it too. Those backups are controlled by you and Apple.
App usage analytics
The app uses Google Analytics for Firebase, a Google service, to see which main screens and features are used, so we know what to improve.
What Google receives: an app-instance ID that the Firebase SDK creates for the app on your device; your device model, operating system and app version; the app’s language; your approximate location, as precise as the city, which Google works out from your connection without storing your IP address; when sessions start and how long they last; which screens you open, such as Today, the calendar, Patterns, the Library, Community and Settings, except the health screens listed below; general feature events, such as making a backup, turning on sync or posting in the Community; and, if you choose to support Ruva, that a support purchase happened, with the product and amount (never your name or payment details). Google also learns whether the app is signed in to an account, and when you create an account or sign in to it on another device, with the sign-in method (Google, Apple or email).
What it never receives: anything you log, your health data, your cycle or pregnancy details, the topics of the articles you read or of Community posts, your name, email address or account ID, or your device’s advertising ID. Ruva never sets a user ID in Google Analytics.
Health screen counts: screens whose names could reveal something about your health never go to Google. Instead, the app keeps its own anonymous counts of how many devices opened the pregnancy, after-a-birth, pregnancy-loss, health-check, medicines, daily check-in, logging, contraction-timer, birth-preferences, Moving gently, pelvic-floor and cycle recap screens on a day, and the setup step that asks how long your period lasts. In Moving gently, they also count how many devices started a routine, finished one, ended one early, finished a pelvic floor set or turned on an exercise reminder on a day, never which routine or what you logged. They also count how many devices reached each setup step, logged for the first time, came back 1, 2 to 7, 8 to 30 or more than 30 days after first opening Ruva, could show notifications or not, and were shown or opened a reminder or a nudge, tapped a mood on a nudge, or switched a reminder or nudges off on a day, never which reminder or what it said. They also include how many accounts were created each day with each sign-in method, and our server counts how many nudges it sent each day. They’re kept as daily totals in Ruva’s own Firebase project (Cloud Firestore), never sent to Google Analytics or any other analytics or advertising company, and contain no identifier, no health values and no time finer than the day. Sending them needs an anonymous ID (see Optional cloud features below), which Ruva creates the first time they’re sent and never stores with the counts. The same Share app usage switch turns them off. Separately, we keep totals of accounts by sign-in method and of Community members. These are totals only, and only Ruva’s administrators can read them.
How it’s handled: Google processes this data for us, as our processor, under its data processing terms. Google doesn’t use it for advertising: the advertising ID isn’t collected, and Google’s advertising and data-sharing features are switched off for Ruva. Google keeps the data for 2 months; after that, only reports showing totals remain.
Switching it off: app usage analytics is on by default for everyone, in every country and at every age. Anyone can switch it off in Settings › Privacy settings › Share app usage, and the app then stops sending it.
In the web app at app.myveya.co, Google Analytics uses cookies, and only while app usage analytics is switched on. This website, myruva.co, uses no cookies or analytics.
Optional cloud features
Four features use our cloud service: sync between your devices, cloud backup, partner sharing and the community. They’re off until you use them.
The first time you use one, or the first time health screen counts are sent, Ruva creates an anonymous ID for your phone through Firebase Authentication, a Google service. It’s a random identifier with no name, email address or phone number attached. The cloud data is stored in Google Cloud Firestore in Mumbai, India. It’s encrypted while it travels and while it’s stored, but it isn’t end-to-end encrypted. Security rules limit who can read each record, as described below. We access it only to run and protect the service, to act on your requests, or when the law requires it.
Sync between your devices
Who can use it: people who have linked a Google, Apple or email account, as described below. An email account needs a verified address.
What’s sent: a copy of your Ruva record. That means your profile, period days, every logged entry and note, your reminders and your personal settings, such as contraception and pill setup, due and birth dates, care region, medicines and the people you’ve blocked in the community. Care contacts are included only if you choose to back them up. Each item also carries when it was last changed and a random ID for the device that changed it, so your devices can tell which change is newest. When you delete an entry, a small marker with its date and type stays in the synced copy, so your other devices delete it too.
What stays on each device: your theme, app lock, language and discreet widget setting; your Health Connect and Apple Health settings, and the note of which days came from them; how reminders are scheduled; partner sharing codes; what you’ve hidden or liked in the community; which articles you’ve read; an unsaved contraction-timer session; the times you agreed to the cloud features; and the import undo note.
When: only after you agree. Ruva asks when you link an account, or once when you open the app if you linked one before. The same agreement covers cloud backup, so if you’ve already agreed to cloud backup, Ruva doesn’t ask again. While Ruva is open on a signed-in device, it sends what you change and brings in changes from your other devices, usually within seconds. Nothing syncs while Ruva is closed. A device catches up the next time you open it.
Who can read it: only your account. Nobody else using Ruva can read or list it.
Turning it off: in Settings › Your data & devices. Turning sync off deletes the synced copy from our cloud, and each device keeps what’s stored on it. Deleting your account deletes the synced copy too. Signing out stops syncing on that device, and leaves your data on the device and in the synced copy until you turn sync off or delete your account.
If you made a cloud backup before using sync, it’s deleted once sync has uploaded everything, because the synced copy takes its place.
Cloud backup
What’s sent: a copy of your Ruva record. That means your profile, period days, every logged entry and note, your reminders and your personal settings: contraception and pill setup, due and birth dates, care region and medicines. Care contacts are included only if you choose to back them up.
When: only when you tap Back up now. Each backup replaces the previous one. Cloud backup is for people who haven’t linked an account. With a linked account, sync takes its place.
Who can read it: only your anonymous ID (or your linked account, below). Nobody else using Ruva can read or list it.
You can restore the backup on the same phone, or on a new phone after linking the same account. You can delete just the backup in Your data & devices, and deleting your account deletes it too.
Linking a Google, Apple or email account
You can link a Google account (Android), use Sign in with Apple (iPhone, iPad and Mac), or create an account with your email address (on every platform). Linking is needed for three things: syncing your devices, using the community, and moving to another phone, where it lets you restore your backup. Everything else in Ruva works without it.
With Google or Apple, Ruva uses only your email address, to recognise the account. With Apple, you can choose to hide your email, and Apple then gives us a private relay address. Firebase Authentication also stores the basic details your sign-in provider includes when you sign in (for Google, that’s usually your name and a link to your profile picture). Ruva doesn’t read or use them.
Google and Apple learn that you signed in to Ruva. They don’t receive your cycle data from us. Signing out of the linked account in Ruva leaves your data on the phone and, if you use sync, in the synced copy. The account record stays in Firebase Authentication until you delete your account in the app or ask us to delete it (see Account and data deletion). On Apple devices, deleting your account also revokes Ruva’s access to Sign in with Apple.
Email accounts. Instead of Google or Apple, you can create a Ruva account with your name, your email address and a password of at least 8 characters. You can do this when you first set up Ruva, in Your data & devices, or when you join the community. Firebase Authentication runs these accounts for us, as it does for Google and Apple sign-in. The app sends your password straight to Firebase and doesn’t keep it. Firebase stores only a protected (hashed) form, and we never receive your password. Your name is stored with the account in Firebase Authentication. It’s used only to greet you in the emails about your account, and it’s never shown in the community.
We use your email address to recognise your account when you sign in on another phone or device, where your data can sync or you can restore your backup. We also use it to send you a link to verify the address and, when you ask, a link to choose a new password. Firebase sends these emails for Ruva, in the app’s language. To use sync or join the community with an email account, you need to verify the address first. You can sign out at any time, as with Google or Apple. Settings › Delete my account asks for your password, then deletes the account, including your name, email address and password, along with everything else that deleting your account removes.
Partner sharing
What’s sent: the name you’ve entered (up to 40 characters) and up to six short lines that you choose in the app, such as your cycle day, the approximate start of your next period, or whether you’re in your fertile window. In pregnancy, it’s the week and due date instead, only if you turn that on. The shared summary holds nothing else: no logs, notes or other dates.
Who can read it: anyone using Ruva who enters your 8-character code. Codes can’t be listed or searched, so only people you give the code to can find the summary. Only share it with people you trust. To show that the summary is yours, your anonymous ID is stored in a separate record that only you can read. Someone with your code sees the name and the lines, not your ID, so they can’t use it to link the summary to your Community posts.
The summary updates while sharing is on. When you stop sharing, the copy on our server is deleted.
Community
Who can join: people who have linked a Google, Apple or email account, as described above. An email account needs a verified address. Other members see your display name, never your email address or account details.
What’s sent: the posts and replies you write, the topic you choose, your display name, your account ID, the time, and the numbers of likes and replies.
Who can read it: everyone using the community in Ruva. Posts aren’t linked to your cycle data. A display name doesn’t make what you write anonymous, though: a name, a workplace or a detailed story can identify you. Please don’t post anything you wouldn’t want strangers to read.
You can delete your own posts and replies at any time, and deleting a post also deletes the replies under it. Deleting your account deletes all your posts with the replies under them, your replies on other posts, and your reports. If you report a post or reply, we store the reason, what you reported, your anonymous ID and the time. Only we can read reports. Posts that several people report are hidden automatically until we review them, and we remove content that breaks the Community guidelines. If a device keeps breaking them, we can stop its anonymous ID from posting.
If you block someone, the list of people you’ve blocked is stored on your phone (and in the synced copy or your cloud backup, if you use them). They aren’t told. You can unblock them in Settings › Privacy settings.
Health Connect on Android
Health Connect is Android’s on-device store for health records. Ruva uses it only for the features you turn on, and each one asks for its own permission.
- Sync. Ruva writes your period days and flow, period dates, weight and basal body temperature to Health Connect. It reads weight and basal temperature that other apps have saved there, for days you haven’t logged them in Ruva. It also reads the period records it wrote, so it can keep them in step with your Ruva log.
- Import period history. Ruva reads the period days and flow that other apps have saved in Health Connect, shows you a preview, and saves what you confirm. Where Health Connect allows it, Ruva asks for access to past data, so it can bring in records older than 30 days. Days brought in this way aren’t written back to Health Connect.
- Sleep from Health Connect. Ruva reads your sleep sessions and saves the minutes asleep for each night, to show your sleep by cycle phase. It never replaces a value you typed yourself.
Health Connect data stays on your device. Values that Ruva imports become part of your Ruva record, so they’re included in sync and in a cloud backup if you use them. Ruva doesn’t use Health Connect data for advertising, doesn’t sell it and doesn’t use it for anything other than the features you see in the app. Ruva’s use of information received from Health Connect follows the Health Connect permissions policy, including its Limited Use requirements. You can turn access off at any time in Health Connect’s settings.
Apple Health on iPhone and iPad. If you turn it on, Ruva writes your period days and flow to Apple Health, reads the period days and flow that other apps have saved there so you can import your history, and, if you turn on sleep, reads your sleep and saves the minutes asleep for each night. Days brought in from Apple Health aren’t written back, and weight and temperature aren’t shared with Apple Health. Apple Health asks for your permission, and you can change it at any time in the Health app. The same rules apply as for Health Connect: the data stays on your device, values Ruva imports become part of your Ruva record, and Ruva doesn’t use it for advertising, sell it or use it for anything other than these features. You can also bring in history from an Apple Health export file, as described below.
Importing your history
You can bring in your period history from a file: an Apple Health export, an export from Clue, Flo, Natural Cycles, drip. or Mensinator, a CSV file, or a Ruva file you saved earlier. You can also import it from Health Connect or Apple Health, as described above. Ruva reads the file on your phone and shows you a preview before saving. The file isn’t uploaded, and nothing in it is sent to us or anyone else. Ruva takes only period days and flow, and entries such as symptoms, moods, spotting, test results, temperatures and notes that match what you can log in Ruva. Everything else in the file is left out. What you import becomes part of your Ruva record.
So that you can undo an import, Ruva keeps a note of what the last import added or changed, on your phone only. It isn’t included in your downloads, sync or cloud backup, and it’s deleted when you delete your data.
Reminders, notifications and widgets
Reminders you set up are scheduled by your phone’s operating system, so their content never passes through us. That covers every reminder, including the weekly pregnancy update and the daily check-in, which your phone skips on days you’ve already logged. If you use sync, your reminders sync too, and each signed-in device schedules them itself, so they can appear on each one. On a locked screen, notifications use neutral wording, and a medicine reminder can show a name you choose instead of the medicine. If your phone passes notifications to a watch, Ruva’s reminders appear there with the same wording. If you turn on the daily logging reminder, it offers mood buttons. A mood you tap there is saved on your phone like any other log.
Ruva’s widgets show your cycle day and next period estimate, or your pregnancy week, to anyone who can see your screen. That includes the home-screen widgets on Android, iPhone and iPad, and the Lock Screen widgets on iPhone and iPad, which hide words such as “period” while the device is locked. The shortcuts on the app icon can show actions such as “Period started”, and the Quick Settings tile on Android shows the day or week in neutral wording, because it can be seen on a locked phone. Discreet mode removes period and ovulation wording from widgets and shortcuts. The widgets read a short summary that Ruva saves for them on your device. They don’t connect to the internet, and nothing is sent to us.
Nudges when you’ve been away
If you haven’t opened Ruva or tapped a check-in for 3 days, Ruva can nudge you on the 3rd, 4th, 5th, 6th and 7th day, then on the 10th, 14th, 21st and 30th. You get at most one a day, at your check-in time and never at night. After that it stays quiet until you use Ruva again. Nudges pause for the same weeks as the daily check-in after a pregnancy loss.
To send them, your phone or browser gives Ruva a notification token from Firebase Cloud Messaging, and Ruva keeps a small record in our cloud database under your anonymous ID. The record holds the token for each of your devices (up to five), your time zone, your check-in hour, the day you last used Ruva, a date until which Ruva should stay quiet (never the reason), when the next nudge is due and how many have been sent. It holds nothing you log and no health information.
When a nudge is due, our server asks Firebase Cloud Messaging to deliver a signal that contains only a number from 1 to 9. Google delivers it to Android phones; for the web app, your browser’s push service delivers it (Google for Chrome, Apple for Safari, Mozilla for Firefox, Microsoft for Edge). They can see that Ruva sent something and when, but not what it says, because the signal contains no words. Ruva then writes the nudge on your device, in your language, from what’s stored there: for example a mood check-in, how many days until your next period estimate, or a guide to read. On a locked screen it uses the same neutral wording as other reminders, and with discreet mode on it’s always a plain check-in.
The switch is in Settings › Reminders › Nudge me when I’ve been away. It’s on by default, except for anyone under 18, where it starts off. Nudges only appear if you allow notifications. Turning nudges off, deleting all data or deleting your account deletes the record and the token. A token that stops working, for example after you uninstall Ruva, is deleted the next time a nudge is due.
Watch apps
Ruva has companion apps for Apple Watch and Wear OS watches. The watch shows a summary of today and lets you log a few things. Your full record stays on your phone. Apple Watch works with the iPhone app, not with iPad or Mac.
What your phone sends to the watch: one short summary, updated when something changes. It contains:
- your mode (tracking your cycle, trying to conceive, pregnancy, after a birth or paused), the app’s language and whether discreet mode is on
- today’s cycle day and phase (or the dates they’re worked out from: the start of your current cycle and your last logged period day), the estimated next-period window and how confident it is, and the fertile-window estimate when Ruva shows one
- in pregnancy, the due date and how far along you are; after a birth, the weeks since the birth
- today’s pill and medicine doses, and whether you’ve taken them
- what you’ve logged today (period, flow, symptoms and moods), and the symptoms and moods offered for quick logging
Never sent to the watch: your past cycles or any other history, notes, weight, temperature, sex, test results, partner sharing, Community content and account details.
What the watch sends back: only what you log on it: a period starting or ending, flow, a symptom or mood, a pill or dose taken, and a contraction-timer session. Your phone saves these in your Ruva record like any other log.
How it travels: directly between your phone and your paired watch, through Apple’s WatchConnectivity on Apple Watch and Google’s Wearable Data Layer (part of Google Play services) on Wear OS. It doesn’t go through Ruva’s servers, and nothing is sent unless a watch with Ruva is paired. When your phone and watch aren’t connected by Bluetooth, Apple or Google may carry it over Wi-Fi or a mobile network. On Wear OS, Google may relay it through its own servers. Ruva can’t switch that off, which is one reason the summary is kept short.
What the watch stores: the latest summary, any logs not yet received by your phone, and a contraction-timer session until it’s saved. They’re kept in Ruva’s private storage on the watch. Removing Ruva from your watch deletes them. If you delete your data in Ruva on your phone, the watch’s summary is cleared the next time they connect.
Watch faces and tiles. Ruva’s complications and its Wear OS tile can show your cycle day or pregnancy week, the days until your next window, or whether you’ve taken your pill. People near you may see your watch face. Discreet mode, which you turn on in Ruva on your phone, removes words such as “period”, “ovulation” and “pregnancy” there and on the watch app, and shows a medicine’s discreet name instead of the real one. Ruva’s app lock doesn’t apply on the watch, so your watch’s own screen lock protects it.
Exports and the doctor summary
The JSON and CSV exports and the doctor summary PDF are created on your phone. So are the calendar file (.ics) with your predicted periods and the cycle recap image you can choose to share. We don’t receive any of them. You choose where to save or send them. Once you send a file by email, a messaging app or a cloud drive, that service’s terms and privacy policy apply to the copy. If you add the calendar file to a calendar that syncs online, such as Google, Apple or Microsoft calendars, that provider stores the events. With neutral titles on, each event is just called “Ruva”.
Support payments
Supporting Ruva is optional and adds no features. Payments go through the App Store or Google Play, which process them under their own terms and privacy policies. We don’t receive your card details, name or billing address.
The stores give us transaction reports (such as product, price, date, country and an order number), which we use for accounting, tax, refunds and fraud prevention. The app asks the store, on your phone, whether you have an active monthly contribution, so it can show it.
Rating and support requests
After you’ve used Ruva for a month, it may ask you once to rate it. It uses the App Store’s or Google Play’s own rating window, and the store decides whether the window appears. Ruva never learns whether you rated it, or how. On Android and in the web app, Settings › Rate Ruva opens Ruva’s page on Google Play, where Google’s own terms and privacy policy apply.
If you’ve never supported Ruva (with a monthly contribution or a one-time payment), it asks whether you’d like to, after three months of use and then every three months. You can close the request, and nothing changes if you don’t support.
Neither request appears in the weeks after a pregnancy loss. Your phone works out when to show them, and no data is sent to us for either.
Settings › Send feedback opens a new email to us in your email app. We receive only what you choose to send, with your email address, and keep it as described in How long we keep information.
The website
Browsing myruva.co
The website is hosted on Firebase Hosting, a Google service. Like any web server, it processes your IP address and basic browser information to deliver pages and protect against abuse. We don’t use that information to identify you or to build a profile.
The website uses no cookies, analytics, advertising pixels, social media plugins or third-party fonts. The interactive demo uses sample data that stays in the page’s memory and is cleared when you reload it.
When the waitlist form was open, it kept the times of your recent attempts (not your email address) in your browser’s local storage, to stop repeated submissions. The form is closed now. You can clear what’s left in your browser settings at any time.
The waitlist
The waitlist is closed. Ruva is live in your browser, and we no longer collect addresses. This section describes the addresses already on the list.
What we collected: your email address, the platform you were interested in, the language of the page, the page you signed up from, the time, and a record that you agreed to be emailed.
Why: to email you once about Ruva’s launch. That’s the only message we’ll send.
How it’s stored: in Google Cloud Firestore in Mumbai, India. Each entry is filed under a one-way code made from your email address, so signing up twice didn’t create a second entry. Nobody can read the list from the website.
How long: we delete the list within 90 days after that launch email has been sent. You can ask us to remove your address sooner, and every email we send includes an unsubscribe link. If we use an email delivery service to send that message, it will act on our behalf, and we’ll name it in the service provider table below before we use it.
Why we use information, and our legal bases
If you’re in the European Economic Area, the United Kingdom or Switzerland, data protection law requires a legal basis for each use of personal information. Information about your periods, sexual activity, pregnancy and health is “special category” data. We only process it in our cloud with your explicit consent, which you give when you choose to use a cloud feature after reading what it sends.
| Purpose | Information | Legal basis |
|---|---|---|
| Sync between your devices | Your synced copy, including health information, with the change times and device IDs that keep it in step | Explicit consent; the sync service you ask for |
| Cloud backup and restore | Your backup, including health information | Explicit consent; the backup service you ask for |
| Linking an account | Email address, sign-in provider ID, and for an email account, your name and the protected (hashed) form of your password | Providing the service you ask for |
| Partner sharing | Name and the summary lines you choose | Explicit consent |
| Community | Posts, replies, display name, account ID | Consent, and explicit consent for any health information you include |
| Moderating the community and handling reports | Posts, reports, anonymous IDs | Legitimate interests in keeping the community safe; legal obligations |
| Health Connect sync, history import and sleep (on your phone) | Period, flow, weight, temperature and sleep records | Explicit consent |
| Watch apps (between your phone and watch) | Today’s summary and the logs you make on the watch | Explicit consent; providing the feature you ask for |
| Support payments | Store transaction reports | Legal obligations (tax and accounting); providing the purchase |
| Waitlist | Email, platform, language, page, time | Consent |
| Running and securing the website and cloud service | IP address, technical request data | Legitimate interests in a secure, working service |
| App usage analytics and health screen counts | App-instance ID, device and app details, approximate location, session times, screens, feature events, whether the app is signed in, and account sign-ups and sign-ins with their method; daily counts of health screens, Moving gently use and new accounts, the anonymous ID used to send them, and totals of accounts and Community members | Legitimate interests in understanding how the app is used so we can improve it, with an easy way to switch them off |
| Nudges when you’ve been away | Notification tokens, time zone, check-in hour, the day you last used Ruva, nudge timing | Legitimate interests in reminding you about an app you installed, with a switch to turn it off and your device’s own notification permission |
| Responding to requests and legal claims | What’s needed for the request | Legal obligations; legitimate interests; establishing or defending legal claims |
You can withdraw consent at any time by turning the feature off or deleting the data. That doesn’t affect what happened before you withdrew it.
Who we share information with
We don’t sell or rent personal information. We don’t share it for targeted or cross-context behavioural advertising, and we don’t give it to data brokers.
Information is shared only:
- With our service providers, who process it on our instructions (see the table below).
- With the app stores and sign-in providers, which act independently under their own privacy policies when you buy something or sign in.
- With the people you choose: someone you give your partner code to, and the readers of anything you post in the community.
- Between your own devices. If you use a watch app, Apple’s or Google’s watch services carry the summary and your watch logs between your phone and watch, as described in Watch apps.
- When the law requires it. Most of what you log never reaches us, so we can’t hand it over. For what we do hold, we only respond to valid legal orders, we challenge requests we believe are unlawful or too broad, and we tell you before disclosing unless the law forbids it. We won’t voluntarily give information about your periods, pregnancy or reproductive health to law enforcement.
- If Ruva changes hands. If Ruva is merged, acquired or transferred to another organisation, this policy will continue to protect your information, and we’ll tell you before any change to how it’s used.
Service providers
| Provider | Service | What it handles | Where |
|---|---|---|---|
| Google (Firebase) | Authentication, Cloud Firestore, Cloud Functions, Firebase Hosting, Firebase Cloud Messaging (nudges), Google Analytics for Firebase (app usage) | Anonymous IDs, linked emails, the names and hashed passwords of email accounts, the verification and password emails it sends for us, synced copies, backups, partner summaries, community posts, reports, the waitlist, website requests, app usage analytics, health screen counts, nudge records and the content-free nudge signals | Firestore data in Mumbai, India; authentication, hosting and analytics run on Google’s global infrastructure, including the United States |
| Google (Google Play) | App distribution, payments | Purchases and downloads on Android | Global |
| Your browser’s push service (Google, Apple, Mozilla or Microsoft) | Delivering nudges to the web app | Your browser’s notification token and the content-free nudge signal | Their global infrastructure |
| Apple (App Store, Sign in with Apple) | App distribution, payments, sign-in | Purchases and downloads on iPhone; sign-in | Global |
International transfers
Cloud data is stored in India, and Google may process it in other countries where it operates, including the United States. When personal information from the EEA, the UK or Switzerland is transferred to countries without an adequacy decision, we rely on the Standard Contractual Clauses (and the UK addendum) in Google’s data processing terms, and on the EU-US Data Privacy Framework where it applies. If you use the cloud features from a country that requires consent for transfers abroad, turning a feature on is how you give it, and you can withdraw it by turning the feature off.
How long we keep information
| Information | How long |
|---|---|
| What you log, on your phone | Until you delete it or uninstall Ruva |
| Summary and logs on a watch | Until they’re replaced, received by your phone, or you remove Ruva from the watch |
| Synced copy | Until you turn sync off or delete your account. Signing out doesn’t delete it |
| Cloud backup | Until you replace it with a new backup or delete it, or until sync has uploaded everything |
| Partner summary | Until you stop sharing or delete your account |
| Community posts and replies | Until you delete them or your account, or we remove them |
| Reports you make | Until you delete your account, and no longer than 12 months after we’ve reviewed them, unless we need them longer for safety or a legal claim |
| Anonymous IDs stopped from posting | Until we lift the restriction |
| Anonymous ID and linked account | Until you delete your account in the app or ask us to delete them |
| App usage analytics | 2 months in Google Analytics; after that, only reports showing totals remain |
| Health screen counts | As daily totals, which contain nothing personal, for as long as Ruva exists. The anonymous ID used to send them is kept as described for anonymous IDs above |
| Nudge record (notification tokens, time zone, check-in hour, the day you last used Ruva) | Until you turn nudges off, delete all data or delete your account. A token that stops working is deleted the next time a nudge is due |
| Waitlist | Up to 90 days after the launch email |
| Store transaction reports | As long as tax and accounting law requires, usually 6 to 10 years |
| Emails you send us | Up to 2 years after the conversation ends |
When we delete cloud data, it’s removed from the live database straight away. Copies in Google’s internal backup systems are overwritten on Google’s schedule, usually within a few months.
Your controls in the app
- Download everything: Settings › Your data & devices › Download (JSON or CSV).
- Delete your account: Settings › Delete my account (also in Privacy settings and Your data & devices). This deletes your data on the phone, the synced copy, your cloud backup, your partner summary, your community posts and replies, your reports and your sign-in account. Your other devices keep what’s stored on them.
- Turn sync off: Settings › Your data & devices. This deletes the synced copy from our cloud, and each device keeps what’s stored on it.
- Delete only the cloud backup: Settings › Your data & devices › Delete cloud backup.
- Stop sharing, delete posts, sign out: in Partner sharing, the community and Your data & devices.
- Unblock someone: Settings › Privacy settings.
- Switch app usage analytics off: Settings › Privacy settings › Share app usage.
- Switch nudges off: Settings › Reminders › Nudge me when I’ve been away.
Step-by-step instructions, including how to ask us if you no longer have the app, are on Account and data deletion.
Your rights
Wherever you live, you can ask us to:
- tell you whether we hold information about you, and give you a copy
- correct or complete it
- delete it
- give it to you in a portable format
- stop or limit a use of it, or object to it
- withdraw any consent you’ve given
Most of this you can do yourself in the app. For anything else, email hello@myruva.co. You don’t need an account to use Ruva, so we may ask for details that let us find your data, such as your linked email address or partner code. We’ll only ask for what’s needed and won’t use it for anything else. We’ll answer within one month, or sooner where the law requires, and we won’t treat you differently for using your rights. You can use an authorised agent where the law allows.
European Economic Area, United Kingdom and Switzerland
You have the rights listed above under the GDPR, the UK GDPR and the Swiss Federal Act on Data Protection. You can also complain to your local data protection authority, for example the Information Commissioner’s Office in the UK. We’d appreciate the chance to sort things out first.
United States
State privacy laws (including California). In the past 12 months we’ve collected these categories of personal information, only through the features, app usage analytics and health screen counts described above: identifiers (an anonymous ID, an app-instance ID for app usage analytics, a random ID for each device that syncs, an email address if you linked an account or joined the waitlist, and your name if you created an email account); sensitive personal information (health information in a synced copy, cloud backup or partner summary, anything you post in the community, and account log-in credentials: the email address and password of an email account, with the password stored by Firebase only in a protected, hashed form); commercial information (store transaction reports); and internet activity (technical request data processed by our hosting provider, app usage analytics, and anonymous health screen counts that aren’t linked to you). We collect it from you, from your device and from the app stores, for the purposes in this policy, and disclose it only to the service providers listed above.
We don’t sell or share personal information as California law defines those terms, and we don’t use sensitive personal information to infer characteristics about you or for any purpose that would give you a right to limit it. You have the right to know, access, correct and delete your information, and not to be discriminated against for using these rights. If we decline a request, you can appeal by replying to our decision; if you’re unhappy with the outcome, you can contact your state attorney general.
Consumer health data. Washington’s My Health My Data Act and similar laws in Nevada, Connecticut and other states give additional rights over health information. Our Consumer Health Data Privacy Policy explains how they apply to Ruva.
India
Under the Digital Personal Data Protection Act, 2023, you can access a summary of your personal data and how it’s processed, correct, complete, update or erase it, withdraw consent, nominate someone to act for you, and have your grievances addressed. Contact our grievance officer at hello@myruva.co. If you’re not satisfied with our response, you can complain to the Data Protection Board of India.
Brazil
Under the LGPD, you can confirm whether we process your data, and access, correct, anonymise, block, delete or port it. You can also ask who we’ve shared it with, learn what happens if you don’t consent, and revoke consent. Contact our encarregado at hello@myruva.co. You can also complain to the Autoridade Nacional de Proteção de Dados (ANPD).
Saudi Arabia, the United Arab Emirates and other Arabic-speaking countries
Data protection laws such as Saudi Arabia’s Personal Data Protection Law, the UAE’s Federal Decree-Law No. 45 of 2021 and Egypt’s Law No. 151 of 2020 give you the right to be informed, to access, correct and delete your data, and to withdraw consent. Health data is treated as sensitive, and we only process it in our cloud with your explicit consent. Turning on a cloud feature sends that data outside your country, to India and possibly other countries. You can complain to your national data protection authority.
China
Under the Personal Information Protection Law, health information is sensitive personal information, and storing it in our cloud means transferring it outside mainland China. We only do that with your separate consent, which you give by turning on a cloud feature after reading what it sends. You have the rights to know and decide, restrict or refuse processing, access, copy, transfer, correct and delete your information, and to ask us to explain these rules. Google services that the cloud features rely on may not be available in mainland China. Everything on your phone still works without them.
Other countries
Wherever you are, we give you the rights described in this section and handle requests the same way.
Children and teenagers
Ruva is for people aged 13 and over. It isn’t directed at children under 13, and we don’t knowingly collect their personal information. Many people start their periods in their early teens, and Ruva can be useful then. Teenagers aged 13 and over can use everything that stays on the phone. App usage analytics and health screen counts also apply to teenagers who use the app, with the same switch to turn them off (see App usage analytics). Nudges when you’ve been away start switched off for anyone under 18.
The cloud features need more care. If you’re younger than the age at which you can consent to online services where you live (between 13 and 16 in European countries and the UK, and 18 in India), you need a parent’s or guardian’s permission before using sync, cloud backup or partner sharing. Using the community needs a linked account, and you need to be 16 or over to post or reply.
If we learn that we’ve collected personal information from a child without the consent the law requires, we’ll delete it. Parents and guardians can contact us at hello@myruva.co.
Security
We protect information by collecting as little as possible and keeping most of it on your phone. On top of that:
- all connections to our cloud service and website use HTTPS encryption
- Google encrypts stored data
- security rules limit each record to its owner: the synced copy to your account, backups to your ID, partner summaries to holders of the code, reports and the waitlist to us
- the waitlist can’t be read from the website, and entries are filed under a one-way code instead of your email address
- access to the cloud console is limited to the people who run Ruva
No system is perfectly secure. If a breach affects your personal information, we’ll tell you and the authorities as the law requires.
App permissions
| Permission | Platform | Why Ruva asks | If you say no |
|---|---|---|---|
| Notifications | iPhone, iPad, Mac, Android, web app | To show the reminders you set up and, if you leave them on, nudges when you’ve been away | Ruva works, without reminders or nudges |
| Run at startup | Android, Wear OS | To set your reminders again after the phone restarts, and to refresh the watch’s tile and complications | Reminders may stop after a restart until you open Ruva |
| Health Connect: menstruation, weight, basal body temperature (read and write) | Android | To sync those records with Health Connect, only if you turn it on | Ruva works without syncing |
| Health Connect: past data (read) | Android | To import period history older than 30 days, only if you import it | Only the last 30 days can be imported |
| Health Connect: sleep (read) | Android | To show sleep by cycle phase, only if you turn it on | Ruva works without sleep data |
| Apple Health: period days and flow (read and write), sleep (read) | iPhone, iPad | To sync your periods with Apple Health, import period history and show sleep by cycle phase, only if you turn them on | Ruva works without Apple Health |
| Screen lock (fingerprint, face, passcode or password) | iPhone, iPad, Mac, Android | For the optional app lock. Your device checks it, and Ruva never receives biometric data | App lock isn’t available |
| Vibration | Wear OS | A short tap to confirm a log on the watch | Not asked separately |
| Internet and network status | iPhone, iPad, Mac, Android | For the optional cloud features, sign-in, store purchases and app usage analytics | Everything on the phone keeps working offline |
| In-app purchases | iPhone, iPad, Mac, Android | For optional support payments | Nothing changes; support is optional |
Google Play services libraries used for sign-in and Firebase also declare a permission to read Google services configuration. Ruva doesn’t use it for anything else. Ruva doesn’t ask for your location, contacts, camera, microphone, photos or advertising ID.
Links to other websites
Ruva’s guides link to sources such as the NHS and the CDC. Those sites have their own privacy policies, which we don’t control.
Changes to this policy
We’ll update this policy when Ruva or the law changes. The version and the date at the top of the page show when it last changed. If a change affects how we use information you’ve already given us, we’ll tell you in the app or on this website before it takes effect and, where the law requires, ask for your consent again. Earlier versions are available on request.
What changed in version 1.10: Veya is now called Ruva. The operator (Zuro Ansa Tech LLP), the data we hold and your rights are unchanged.
What changed in version 1.9: nudges when you’ve been away now start on for adults in the European Economic Area, the United Kingdom and Switzerland too, as they already did everywhere else. If you haven’t changed the switch yourself, it’s now on. Nudges still start off for anyone under 18 and only appear if you allow notifications. You can switch them off in Settings › Reminders › Nudge me when I’ve been away.
What changed in version 1.8: Veya can now nudge you when you haven’t used it for 3 days. The new section Nudges when you’ve been away explains the content-free signal sent through Firebase Cloud Messaging, the small record we keep to send it, who delivers it and how to switch it off. Reminders you set up still never pass through us. Our own daily counts now also cover setup steps, first logs, returns, whether notifications can show, and reminders and nudges shown, opened and switched off.
What changed in version 1.7: if you link an account, Veya can now keep your devices in sync. The new section Sync between your devices explains what it sends, what stays on each device, and what turning it off, signing out and deleting your account do. Once sync has uploaded everything, an earlier cloud backup is deleted. App usage analytics now also notes when sync is turned on, and our own daily counts now include the Moving gently screens and exercises. The policy also corrects the list of counted screens, says that Google’s approximate location can be as precise as the city, and covers Apple Health on iPhone and iPad, the weekly pregnancy and daily check-in reminders, Rate Veya and Send feedback.
What changed in version 1.6: you can now create a Veya account with your name, email address and a password, instead of using Google or Apple. The section on linking an account explains how Firebase Authentication handles it, what we use your name and email address for, and how to delete the account. App usage analytics now also records whether the app is signed in, and when an account is created or signed in on another device, with the sign-in method. Our own daily counts now include new accounts by sign-in method, and we keep totals of accounts and Community members.
What changed in version 1.5: the app now uses Google Analytics for Firebase, with its advertising features switched off, to see which screens and features are used, never with what you log or your health data, and keeps its own anonymous daily counts of health screens, which never go to Google. The new App usage analytics section explains what Google receives, how long it’s kept and how to switch it off; both are on by default for everyone. This website still uses no cookies or analytics.
What changed in version 1.4: the community now needs a linked Google or Apple account, and other members see only your display name. Partner sharing now keeps your anonymous ID in a separate record that only you can read, and shares your pregnancy week only if you turn that on. The policy also covers the new import sources (Apple Health export, Natural Cycles, drip. and Mensinator), the import undo note, widgets on iPhone and iPad, shortcuts, the Quick Settings tile, the mood buttons on the daily reminder, the calendar file and the cycle recap image. None of these send new information to us.
What changed in version 1.3: from 20 October 2026, Veya is operated by Zuro Ansa Tech LLP, a limited liability partnership registered in India, instead of an individual. Our terms of use are now governed by the laws of India. Nothing else about how we handle your information changes.
What changed in version 1.2: the policy now covers Veya on iPad, Mac, Apple Watch, Android tablets and Wear OS watches. It adds sections on the watch apps, importing your history, and rating and support requests, and it describes Health Connect’s history and sleep reads.
Contact
Zuro Ansa Tech LLP
Email: hello@myruva.co
Language of this policy
This policy is published in English, Spanish, French, German, Brazilian Portuguese, Arabic, Simplified Chinese and Hindi. The translations are provided for your convenience. If a translation differs from the English version, the English version prevails, unless the law where you live requires otherwise.