Privacy Policy

Who is responsible for the app

Diana Kaida is the operator responsible for the Baby Journal application (the “App”). For privacy questions and requests, contact [email protected]. This Policy covers data handled by 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.
• Your journal is not synchronized or sent for analytics or advertising. Technical analytics, crash diagnostics, and separately permitted marketing processing 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.

Analytics, attribution, and advertising

We use Google Analytics for Firebase and Yandex AppMetrica to understand how the App is used and improve its operation. Ordinary technical usage analytics starts automatically when the App starts. The Developer can view usage events and technical reports in the providers’ consoles.

Usage events include the first observed launch of an installation, app launches, onboarding steps and completion, and opening Today, Journal, Statistics, and More. Event parameters contain fixed screen and step names, not values entered in the journal. SDKs may also collect service events and session information. The first observed launch is not necessarily the download date.

Technical data may include installation and app-instance identifiers, event times, device model, operating-system and App versions, language, and sessions. Network communication uses an IP address that may indicate an approximate country or region. This data is not fully anonymous.

With your separate permission, Google Analytics for Firebase and AppMetrica may also be used to determine the installation source, measure advertising campaigns, create advertising audiences, and personalize advertisements for our App outside the App. This processing may use advertising identifiers, including IDFA on iOS, and may involve matching technical or advertising data with data from other apps and websites. There are no advertisements inside the App.

The child’s name and date of birth, health information and measurements, medicines, journal notes, photos, and audio are not sent for analytics or advertising and are not used to create advertising audiences. Journal-entry identifiers are not included in App events or manual diagnostic reports. Analytics and marketing services do not provide a cloud backup of the journal.

Marketing processing is enabled only after you give separate permission in the App and, on iOS, grant permission through App Tracking Transparency (ATT). Accepting the Terms, continuing onboarding, or granting camera, microphone, photo, or notification permissions does not give marketing permission. Refusing marketing permission does not restrict the journal.

You can withdraw marketing permission in More → Advertising and privacy. You can also change ATT permission in iOS Settings. Withdrawal stops further advertising processing by the App. It does not automatically delete previously transmitted data or existing audiences held by the providers. Contact the operator about deletion of previously transmitted data and other privacy requests.

The journal works offline. Analytics SDKs may buffer technical data and transmit it when connectivity returns. Technical analytics runs automatically and is separate from marketing permission. System permissions for camera, photos, microphone, and notifications do not control technical analytics.

Technical and, when separately permitted, advertising data is sent to Google and Yandex servers and may be processed outside your country. Their processing is described in the linked policies. Opening those external pages requires internet access.

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

Crash diagnostics

Firebase Crashlytics is used separately to diagnose native and JavaScript failures. Reports may contain technical exception information, stack traces, device and operating-system details, and App version information. The Developer can access diagnostic reports in Firebase.

JavaScript reports are sanitized to fixed codes and code coordinates; native reports may contain technical exception messages and stack traces. The child’s name and date of birth, health measurements, medicines, journal notes, photos, and audio are not included in App events or manual reports. Crash diagnostics does not back up your journal.

Firebase Crashlytics retains crash stack traces, extracted minidump data, and associated installation identifiers for 90 days before starting removal from live and backup systems. Raw NDK minidump files are held temporarily for crash processing and then discarded.

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.

Withdrawing marketing permission stops further advertising processing by the App but does not automatically erase technical data, previously transmitted advertising data, or audiences already created by the providers. Deleting a journal entry or uninstalling the App does not automatically delete data already sent to those providers.

To request deletion of transmitted technical or advertising data, email [email protected]. Diana Kaida handles these requests using the providers’ available procedures and applicable requirements. Additional information needed to identify the relevant technical records may be requested. Do not send the child’s health information, journal entries, photos, or audio. Withdrawal of permission is separate from a deletion request.

Google Analytics for Firebase retains user-level and event-level data according to the Analytics property’s retention settings. Standard properties support periods of 2 or 14 months. The configured period may restart for user identifiers when new activity is recorded. Standard aggregated reports are not subject to that same retention setting. These options do not mean that every category of data is deleted after the same period.

AppMetrica retention depends on the applicable service terms, data category, and project settings. This Policy does not promise a fixed maximum retention period or an automatic deletion date for all AppMetrica data. Provider-held reports and advertising audiences may remain after you stop using the App or withdraw marketing permission, subject to the provider’s rules and applicable requirements.

The linked Google, Firebase, Yandex, and AppMetrica documents explain their processing. You may use the providers’ privacy channels for questions about their processing. You may also contact Diana Kaida at [email protected] about the App’s processing and deletion requests; referring to a provider does not remove the operator’s responsibilities.

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.

Marketing permission can be withdrawn in More → Advertising and privacy; ATT permission can be changed in iOS Settings. The journal remains available when you refuse or withdraw marketing permission.

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

The operator of Baby Journal is Diana Kaida. For privacy requests, including questions about technical or advertising data and requests for deletion, email [email protected]. Do not include the child’s health information, journal entries, photos, or audio in your request.