Privacy and personal data notice

1. Using local trackers without an account

Installing the app does not by itself create a server account. You can use language preferences, a local profile, tracking focus, journal notes and tracker records on your device without an account. Downloading a published guide or audio catalogue, account actions and email links use the network.

The Android local health database uses SQLCipher encryption, with its key held in secure device storage. This does not encrypt your audio files, PDF/JSON exports or copies shared with external apps. Local storage in a browser development preview does not provide the same protection as the Android database.

2. Optional account information

If you choose to create an account, the server processes a name or nickname, random account ID, email when supplied, app/platform version, active tracking module and account/activity times. An email-free guest server account is also created only after your choice. This information supports account management, login security and service operation; creating an account does not automatically upload health records.

In the email/password flow, a password is transferred over HTTPS and stored as a scrypt hash with a separate salt. Server session and one-use action keys are stored as hashes. Phone sessions use secure device storage; browser accounts stay in the page's memory. Do not send your password to support.

3. Separate consent for a health copy

With a verified member account and a separate sync choice, pregnancy weeks/dates/measurements, baby names/birth dates/sex/measurements and supported notes and records from those two modules may be copied to your account. This optional health copy exists to keep the selected records with your account. Creating an account and consenting to health sync are distinct actions.

Enabling sync during an open app session may send subsequent changes; the choice is made again when reopening the app. This does not guarantee automatic restoration of all records on another device. Free-text health or identifying details are not automatically removed; enter only what is needed.

The server health copy uses AES-256-GCM encryption. Authorised service administrators can read it through protected user details, but cannot edit health records from the panel. This is not end-to-end encryption preventing operator access. Detailed period records, contraction sessions, microphone files and JSON backups are excluded. Active-module metadata may still indicate use of cycle or contraction tracking.

4. Microphone, audio and local reminders

The microphone is used with permission when you start recording. Your recordings, up to three minutes each, stay in the private app file area, are not uploaded by account sync and are outside the encrypted health database. Delete them individually or through local cleanup. A playing audio title may appear in system media controls or on the lock screen.

App reminders are scheduled locally by the operating system according to your permission and preferences; they are not daily server push messages. Notification display without permission or identical delivery times on every device are not guaranteed.

5. PDF, JSON and sharing you choose

A PDF report or JSON tracker backup may include selected personal or health information. These are unencrypted outputs; a JSON backup does not archive audio files. The PDF cache holds at most ten copies, and owned copies older than seven days are removed during a relevant generation/cleanup action. There is no separate exact-day-seven cleanup job; the operating system may clear cache earlier.

Share or email transfers the file to the app you select. It does not automatically upload the file to your account or send mail on your behalf. Check the recipient and attachment. Manage deletion of downloaded, sent or externally copied files at their destination.

6. Website, panel and connection information

The yuvilya.com introduction and blog pages do not request an account or health records. No advertising, behavioural tracking or visitor analytics script has been added to this site. If you choose to save language or cookie preferences, limited preference information may remain in your browser; see the Cookie Policy.

panel.yuvilya.com is for authorised administrators. Administrator login uses a session cookie and access-security checks. Hosting, DNS/CDN and security services carrying internet requests may process IP addresses, request paths, timestamps and technical connection information for delivery and security. No first-party analytics script does not mean infrastructure providers process no technical information.

7. Service providers and the Google option

Hosting services help provide the app account and published catalogue. When you request verification or a reset, the SMTP email provider processes your address and one-use account link for delivery; no health record is attached. Opening the link alone does not change your account; explicit confirmation is required.

Google sign-in uses basic account identity, name/email and authentication information only if configured and selected. Your Google password is not given to Yuvilya, and the full Google identity token is not stored as an account profile. This notice does not mean Google sign-in is available in every release.

The current Android preparation package disables Firebase Messaging automatic initialization and the Analytics collection startup default. These settings do not establish the absence of every identifier flow in every SDK or network provider. Google, Cloudflare and external apps you choose may process information under their own privacy terms. Internet services or providers may process information in different countries; contact support for provider and transfer details.

8. Purposes and your choices

Account and technical information is used to provide the account service you request, manage login and recovery, prevent abuse and operate securely. Local records power on-device features. The optional health copy uses a separate explicit choice/consent, which you can withdraw.

Depending on the processing and applicable law, bases include providing the requested service, legitimate interests in service security, necessary legal obligations and explicit consent for the optional health copy. Reading a privacy notice is not itself consent to health sync. Withdrawing sync consent does not prevent local tracking.

9. Retention and actual limits

The server account and current consented health copy remain while the account exists or until the relevant deletion/withdrawal action. No automatic expiry for inactive accounts is defined. User sessions last at most 30 days, administrator sessions 12 hours, verification links 24 hours and password-reset links 30 minutes. Used action links cannot be reused. Expiry does not mean every row is physically erased at the same instant.

Your audio recordings can remain until individual deletion or local cleanup. External sharing copies follow the chosen service's retention. A universal maximum retention period or automatic deletion propagation across technical backups, infrastructure logs and provider copies is not currently defined. Contact support about access or deletion requests for those copies; we do not promise immediate or forensic erasure of every copy.

10. Distinct deletion actions

Revoking sync consent removes the current server health copy and keeps your account and local records. Deleting the server account removes the current account, associated session/action records and consented server copy while keeping on-device trackers. Clearing local data separately cleans local records and owned audio/PDF copies, without deleting the server account or copy. Incomplete local cleanup gives a retry message.

Delete a server account through in-app account management or the functional form at https://yuvilya.com/app/account-delete. For an email-free guest account, use the in-app deletion path. Contact support if you cannot access it; do not email your password or detailed health records. Uninstalling the app is not a server-account deletion request.

11. Rights and safe support

Use the app controls or [email protected] for applicable rights of access, correction, deletion, processing information, withdrawal and other data rights. Your connection to an account may need secure verification; unnecessary identity documents or health details should not be requested.

Your support email, request text and replies are processed to handle the request. Redact personal/health fields in screenshots. If you suspect an account problem, do not share a password; use recovery. Any applicable right to contact the relevant data-protection authority remains available.

12. Content, child information and updates

Yuvilya is intended for adult parents and caregivers; it does not require a baby to create an account. Anyone entering a child's information should consider their authority to share it and the child's privacy. Blog content is not an individual medical assessment.

This notice is updated for material data-flow changes, with required new choices presented before the relevant feature. Check the last-updated date. Contact: RAVNHEIM / Yuvilya, [email protected].