For the Newborn Rhythms mobile application. Last updated: November 1, 2026.
This Privacy Policy explains how RageWorks Development LLC (“we,” “us,” or “our”) collects,
uses, stores, and shares information in connection with the Newborn Rhythms
mobile application (the “App”). The App helps you track postpartum health
information for a mother and a newborn. Because the App handles health
information, we treat the data you enter as sensitive and confidential.
By creating an account and using the App, you agree to the practices described
in this policy. If you do not agree, please do not use the App.
1. Information We Collect
We collect only what is needed to provide the App:
Account and authentication information. When you sign in with
Google or with Apple, we receive a unique account identifier and basic profile
details such as your email address and display name. We use Firebase
Authentication (a Google service) to manage sign-in.
Health and personal information you provide (sensitive). This
is information you choose to enter about a mother's postpartum health and a
newborn's health and care (for example, feeding and related tracking entries).
You decide what to record.
Sharing information. If you invite another person to share
data, or accept an invitation, we process the information needed to link those
accounts and apply the access role you choose.
Limited technical information. Our infrastructure provider
(Google Firebase) processes basic technical data, such as connection metadata,
that is necessary to operate and secure the service. The App checks your
device's network connectivity to support offline use.
Crash diagnostics. The App uses Firebase Crashlytics (a
Google service) to detect and diagnose crashes. When the App crashes or
runs into an unexpected error, it collects a report containing the stack
trace and basic device and app state (such as device model, operating
system version, and app version) to help us find and fix problems. So that
we can see how many installations a problem affects and how stable the App
is overall, the crash-reporting service also generates identifiers for this
installation of the App — they identify the installation, not you,
and the App does not link them to your account — and Firebase
collects basic information about the App and your phone's operating system
(such as the App's package name, the operating system and Firebase SDK
versions, and the type of network connection). These reports never include
the health entries you record. Crash reporting is turned off in development
(debug) builds.
Voice input (optional). Some quick-log buttons can be held
down so you can say what happened instead of filling in a form. While you
hold the button, your phone's speech recognition converts what you say into
text. Where that happens depends on your phone:
On iPhone and iPad, speech is recognised
on your device only. If your device cannot do that, voice
input does not work there and the button simply opens the form as
usual. The audio does not leave your device.
On Android, speech is recognised by your phone's
speech service, which is provided by Google. The App asks it to work
on your phone, but depending on your Android version and on whether
an offline speech pack is installed for your language, that service
may send the audio to Google to recognise it. The App cannot tell
which of the two happened, so it tells you this in the App before
the first time you use voice input on a device. Audio handled this
way is processed by Google under the
Google Privacy Policy.
On both, we never receive the audio ourselves, and the App does not record
it or write an audio file to your device. The recognised text is used to
pre-fill the entry form; nothing is saved until you check the form and press
Save. See section 4 for the case in which the recognised text leaves your
device.
Barcode scanning (optional). When you add or edit a food, you can
scan the barcode on its package instead of typing its name. The camera is
used only while the scanner is open, the barcode is read on your device,
and no photo, video or camera frame is saved or sent anywhere. On
Android, Google's ML Kit does the reading and sends Google the technical
information described below. The App
then sends the barcode number to our servers to look the product up in
our own copy of the United States Department of Agriculture's public
Branded Foods data, and shows you the name and the ingredient list on
file, one ingredient per line (the list is split into lines on your
device); nothing is saved until you press Save. We keep no record of
which products you look up: our servers do not log these lookups, and
the number is held only for the moment it takes to answer. If you save
the food, the barcode number is stored with it in your records, as the
food's name is. You can tap ingredients on the list to add them to the
food: when you save, each one you tapped is added to the food, using an
ingredient of the same name you already have or, if there is none, a
new one named as the label prints it, stored in your records like any
ingredient you add yourself. The App never checks the list against your
list of avoided foods and never says whether a product contains, or is
free of, anything.
Reading an ingredient list from a photo (optional). When
a food has no ingredient list on file, you can photograph the ingredient
list printed on its package instead of typing it. The camera is used
only while that screen is open, the words in the photo are read on your
device, and the photo is deleted as soon as it has been read: it is
never kept, never added to your photos and never sent anywhere, so we
never receive it. As with barcode scanning, no photo, video or camera
frame is saved or sent anywhere. Google's ML Kit does the reading and
sends Google the technical information described below. The text that
was read is shown to
you in the form as a draft, for you to check against the package and
correct; it stays in the form only until you press Save or leave it,
and is not stored. Only the ingredients you tap are saved, exactly as
with a list from the barcode catalog above. The App never checks the
text against your list of avoided foods and never says whether a
product contains, or is free of, anything.
Google ML Kit (barcode and photo reading). Barcode
scanning on Android, and reading an ingredient list from a photo on
Android and on iPhone and iPad, use Google's ML Kit, which reads on your
device. ML Kit never sends Google the camera image or what it read from
it, but it does send Google technical information about how it ran: your
phone's manufacturer, model, operating-system version and build, and the
machine-learning hardware it has; the App's package name and version; an
identifier for this installation of the App (it identifies the
installation, not you, and the App does not link it to your account);
how long a read took; the image format and size; which version of the
ML Kit feature ran, what it did (for example, starting up or reading an
image) and the size of what it read and returned; and error codes.
Google uses this to measure, debug, maintain and improve ML Kit and to
detect misuse or abuse, under the
Google Privacy Policy.
On iPhone and iPad, barcode scanning uses Apple's own on-device reader,
not ML Kit.
Feedback you send us. If you use the in-app “Send
feedback” feature, we collect the message you write, the category you
select, and basic app and device context (app version and build, platform,
and operating system version) so we can understand and follow up on your
feedback. Feedback is associated with your account while your account
exists. Please don't include health details in feedback; it is handled as
general support information, not as a health entry.
Purchase-screen and locked-feature activity. If you open
the Supporter screen, we record which step you reached: that you viewed
it, that you started a purchase, and whether the purchase completed or,
if it did not, a coarse reason (for example, cancelled or a network
problem). If you reach a feature that is locked, we record which one.
Each record holds the app version and build number, the platform, and
the time, and is associated with your account. We record this ourselves
in our own cloud database, not through an analytics company or SDK, and
these records contain no health entries.
The App includes Firebase Crashlytics for crash diagnostics and Google's ML Kit
for on-device barcode and text reading; both send Google the technical
information described above. We do not include third-party advertising or
analytics SDKs, we do not use your data for advertising, and we do not sell
your personal information.
2. How We Use Your Information
To provide the App's core features and store your entries.
To authenticate you and keep your account secure.
To synchronize your data across your devices and, where you choose, with people you share with.
To operate, maintain, troubleshoot, and improve the reliability and security of the App.
To review, respond to, and act on feedback you choose to send us.
To understand whether the Supporter screen and locked features work, using the activity records described in section 1.
To comply with legal obligations.
3. How Your Information Is Stored
The App is offline-first. Your entries are stored locally on your device and,
when you are connected, synchronized to Google Firebase (Cloud Firestore) so your
data is backed up and available across your devices. Data is encrypted in transit
using TLS and encrypted at rest by Google's cloud infrastructure.
Reminders. Reminders for scheduled medicines and supplements,
feeding times, and pumping times are scheduled by your phone's own notification
system. Nothing is sent from a server to deliver them. By default, a reminder says
only that a reminder is due. If you turn off “Hide details in notifications” in
the App's reminder settings, a reminder shows the person's name and, for a dose,
the name of the medicine or supplement. Depending on your phone's lock-screen
settings, this may be visible without unlocking the phone.
4. How We Share Information
With people you authorize. The App includes a sharing feature.
When you invite someone (for example, a partner or caregiver), the data you
share becomes visible to that person according to the role you assign. You
control who you invite and can manage or revoke access.
With service providers that process data on our behalf. We use
Google Firebase services (Authentication, Cloud Firestore, Cloud Functions,
and Crashlytics), Google Cloud infrastructure including Gemini Enterprise
Agent Platform (formerly Vertex AI), to operate the App, and Apple's
“Sign in with Apple” for authentication. These providers process data
subject to their own terms and privacy policies:
To interpret voice input. When you use the optional voice
input described in section 1, the App first tries to interpret the recognised
text entirely on your device. If it cannot do so confidently and you are
online, it sends that text and the kind of record you are logging (for
example, a diaper change or a feeding) to Google's Agent Platform (Gemini)
through our Cloud Function, which returns the fields to pre-fill the form.
The App does not send audio in this request. We do not store the text. Our
server does keep a log entry for each request, recording your account
identifier, the kind of record, and the length of the text — but
not the text itself. Google is already the infrastructure provider named
above, so this is an additional purpose rather than an additional company.
If you are offline, nothing is sent and the form simply opens for you to
fill in. (Speech recognition itself, which on Android may involve Google's
speech service, is described in section 1.)
Records you export. You can export records from the App as
spreadsheet (CSV) files, for example to give to a clinician. The App builds
these files on your device, and exporting sends neither the files nor their
contents to us: nothing is uploaded, and no copy is kept in our cloud
storage. Your phone's share sheet then opens and you choose the app that
receives the files (for example, email, a messaging app, or your phone's
file storage). Along with the files, that app receives a short message
naming the people in the export, the date range, and the number of records,
and the file names can include those people's names. From then on, the
files are handled under that app's own terms and privacy policy, not ours.
The App keeps a copy of your most recent export in its temporary storage on
your device until your next export replaces it, you sign out, or you delete
your account; your phone may also clear it sooner. Copies you save or send
elsewhere through the share sheet are yours, and deleting your account does
not remove them. People you share with can also export the records they can
see, and revoking their access does not recall files they have already
exported.
For legal reasons. We may disclose information if required by
law or to protect the rights, safety, and security of users or the public.
We do not sell your personal information and we do not share it for advertising.
5. Data Retention and Deletion
We keep your information for as long as your account is active. You can delete
your account from within the App. Deleting your account removes your data from
your device and from our cloud storage. Five exceptions:
Feedback you submit through the in-app “Send
feedback” feature is retained in de-identified form — we remove
the link to your account, but may keep the message and basic app context to
help us improve the App.
Purchase-screen and locked-feature records (section 1) are
retained in de-identified form — we remove the link to your account,
but keep the step or feature reached, the app version and build number, the platform,
and the time so that our counts stay accurate.
Voice-input request logs, described in section 4, never
contain the text and are not removed when you delete your account. They
expire on their own after about 30 days.
Crash reports, described in section 1, are not linked to
your account, so they are not removed when you delete it. Firebase keeps
them, and the installation identifiers that go with them, for 90 days and
then begins deleting them.
ML Kit's technical information, described in section 1,
is not linked to your account, so it is not removed when you delete it.
Google has not published how long it keeps it.
Some information may remain in routine backups for a limited period before
being overwritten, and we may retain limited records where required by law.
6. Your Rights and Choices
You can access and edit your entries directly in the App, and you can delete your
account at any time. Depending on where you live (for example, the EEA, the UK, or
California), you may have additional rights, such as the right to access, correct,
delete, or export your personal information, or to object to or restrict certain
processing. To make a request, contact us using the details below.
7. Children's Privacy
The App is intended for use by adults (such as a parent or caregiver). It is not
directed to children, and we do not knowingly allow children to create accounts.
Information about an infant is entered by the adult account holder. If you believe
a child has created an account, please contact us and we will take appropriate
action.
8. Security
We use reasonable technical and organizational measures to protect your
information, including encrypted transmission (TLS), encryption at rest provided
by our cloud infrastructure, and authenticated access controls. No method of
transmission or storage is completely secure, and we cannot guarantee absolute
security.
9. International Data Transfers
Our service providers may store and process your information on servers located in
countries other than your own. Where required, we rely on appropriate safeguards
for such transfers.
10. Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we will revise the
“Last updated” date above. Significant changes may be communicated within the App.
11. Contact Us
If you have questions or requests regarding this Privacy Policy or your
information, contact us at:
support@newborn-rhythms.com.