Privacy Policy

Who is responsible for the app

The developer and publisher identified on the app's store page is responsible for the app (the “Developer”). This Policy covers data handled by the Baby Journal application itself (the “App”).

Data you may save

You decide what to add. It may include personal and sensitive information about a child and their care:

• the child's profile, including name, sex, date of birth, and birth measurements;
• entries about feeding, sleep, diapers, temperature, growth, medicines, vaccinations, allergies, illnesses, and notes;
• photos you select or take and voice notes you record;
• local reminder settings, including dates and times.

How data is used

The App uses this data only for features you choose: storing and displaying the journal, calculating durations and statistics, attaching media, and showing local reminders.

• The App does not create an account, has no app backend, and does not synchronize the journal between devices.
• The journal is not sent for analytics or synchronized. Advertising identifiers are not used. Technical analytics and diagnostics are described below.
• The camera, system photo picker, microphone, and notifications are used only after your action and permission. Selected media is copied into the App's storage; local-notification settings are passed to the operating system for display on the device.

Firebase and AppMetrica

We use Yandex AppMetrica and Google Analytics for Firebase to understand usage and improve the App, and Firebase Crashlytics to diagnose native and JavaScript failures. The Developer can access events and technical reports in the services’ consoles.

Events include the first observed launch of an installation, app launches, visits to the three onboarding screens, onboarding completion, and opening Today, Journal, Statistics, and More. Parameters contain only fixed screen and step names, not entered values. The first observed launch is not the exact download date. SDKs may also collect service events and session information.

Services may process installation and app-instance identifiers, event times, device model, OS and app versions, language, sessions, and technical crash details. Network communication uses an IP address that may indicate an approximate country or region. This data is not fully anonymous.

App events and manual reports do not include the child’s name or birth date, health measurements, medicines, notes, photos, audio, or journal-entry identifiers. Advertising identifiers, ad personalization, precise location, and deep-link capture are disabled. JavaScript reports are sanitized to fixed codes and code coordinates; native reports may contain technical exception messages and stack traces. This is not a cloud backup of the journal.

Technical data is sent to Google and Yandex servers and may be processed outside your country. The providers describe their processing in the documents linked below. Opening external pages requires internet access.

Collection currently starts automatically when the App starts, before Continue is tapped; there is no separate analytics switch in the interface. Camera, microphone, and notification permissions do not control analytics. The journal works offline; SDKs may buffer technical data and send it when connectivity returns.

Technical-data retention depends on the service, project settings, and provider rules; the 24-hour local-media deletion rule does not apply. Deleting entries or uninstalling the App does not delete reports already sent. Contact the Developer about technical data and applicable rights; fulfilling a request depends on the law and service capabilities. Do not attach the child’s health data or media.

• Google Privacy Policy
• Firebase privacy and data processing
• Yandex Privacy Policy
• AppMetrica data processing

Storage and security

Entries are stored in the App's local database, while photos and audio are stored in its local files on your device. The App works offline and does not provide built-in cloud sync, backup, export, or import.

Your operating system, app store, or device settings may separately create system backups, transfer data, or collect technical diagnostics under the relevant platform's rules. The Developer does not receive that data through the App and does not control those system features.

The App relies on device security and operating-system app isolation. It does not add a separate PIN or additionally encrypt its database or media. Protect your device with a passcode and do not share it with anyone who should not see the journal.

Retention and deletion

Journal entries remain on the device until you edit or delete them or uninstall the App. Manage entries in the App and system permissions in device settings. Technical data already transmitted is retained separately under the analytics providers’ rules.

After you delete linked media, its local file may remain for up to 24 hours solely to support Undo and safe cleanup. Uninstalling the App normally removes its local data, but copies in a system backup or previously exported by operating-system features are governed by your platform settings and policies.

Children's data

The App is intended for parents and other adults caring for a child, not for independent use by children. The adult user is responsible for having the right to enter information about the child and for controlling access to the device.

Your control

The Developer has no remote access to your journal and cannot correct or delete it on your device. You control entries and system permissions yourself. Contact the Developer about transmitted technical data. Depending on applicable law, you may have rights of access, correction, deletion, restriction, objection, and complaint to a supervisory authority.

Changes to this Policy

This Policy may be updated when features or legal requirements change. The revised version will be available in the App with a new effective date. This Policy describes data processing and does not replace separate consent where required by law.

Contact

For questions about these documents or the app, contact the developer using the contact details on the app-store page from which you installed it.