1. Data controller
- The controller of personal data processed in the BabySOS Service is LifeNexa (the “Controller”).
- For anything concerning personal data, write to: kontakt@lifenexa.pl. We have not appointed a data protection officer; the address above handles all enquiries.
2. What data we process
- Parent account: e-mail address, password (we store only a cryptographic hash, never the password itself), and optionally name, phone number and country (used to pick the right emergency number).
- Child profile: name, date of birth and – only if you enter it – blood type, allergies, medication, chronic conditions and other important health notes, an optional photo and instructions for caregivers. Health data is a special category of data (Art. 9 GDPR).
- Daily schedule and events: planned and recorded activities (feeding, sleep, nappies, bath, etc.), times, amounts and notes – entered by the parent, or by a caregiver within the access granted to them.
- Emergency contacts: label, name and phone number of people named by the parent (third-party data – the parent declares they may provide it).
- Caregiver access: the caregiver's name and relationship given by the parent, scope of permissions, validity period, last-used time, and a hash of the access token and code – the token and code themselves are shown to the parent only once and are not stored by us in plain form.
- Notifications (mobile app): a device token for push notifications, if you enable notifications.
- Technical and security data: IP address, browser and request time in server logs, and an account security event log (e.g. sign-in, creating or revoking access, password-reset request).
3. Purposes and legal bases
- Providing the Service – creating and running the account, daily schedule, sharing information with caregivers, SOS mode and emergency card, exporting and deleting data (Art. 6(1)(b) GDPR – performance of a contract).
- Children's health data – we process it solely on the basis of your explicit consent, given by voluntarily entering that data (Art. 9(2)(a) GDPR). You can withdraw consent at any time by deleting the data or the whole child profile; this does not affect lawfulness of processing before withdrawal. A caregiver sees it only if you separately allow it.
- Security and abuse prevention – server logs, login attempt limits, protection against attacks (Art. 6(1)(f) GDPR – the Controller's legitimate interest).
- Handling enquiries and defending claims – correspondence with you, defence against claims (Art. 6(1)(f) GDPR).
- Push notifications – sent only after you consent in your phone's system settings (Art. 6(1)(a) GDPR); you can withdraw consent in the phone settings.
- Legal obligations – where the law requires it (Art. 6(1)(c) GDPR).
Providing the data marked as required (e-mail, password, child's name and date of birth) is voluntary but necessary to create an account. All other data is optional.
4. Children's data
The Service is intended for adults: parents and legal guardians. We do not create accounts for children. A child's data is entered by a parent or legal guardian, who is responsible for its accuracy and scope. Access by other people to a child's data requires a deliberate action by the parent and is limited by them and revocable at any time.
5. Recipients
Data is not sold or shared for advertising. We use the following categories of recipients (processors):
- server infrastructure provider – OVHcloud (server located in Poland; hosting of the application, database and backups);
- e-mail server – sending system messages (e.g. password reset);
- Expo Push Notification Service (Expo Technologies, Inc.) together with the Google and Apple system notification services – only if you enable notifications in the mobile app; the device token and the notification content (child's name, caregiver's name and type of recorded activity) are transmitted;
- public authorities and entitled entities – only where required by law.
We use no analytics, advertising or third-party tracking tools. Fonts and site resources are served from our own server.
6. Transfers outside the EEA
We store data in Poland. The data needed to deliver push notifications (Expo and the Google and Apple system services) may reach a third country (the United States), and only if you enable notifications in the mobile app. This is done under GDPR-compliant mechanisms (including standard contractual clauses or an adequacy decision).
7. How long we keep data
- Account and children's data – until you delete the account (or, respectively, the child's profile). Deleting the account permanently removes child profiles, schedules, events, contacts, instructions and caregiver access grants from the production system.
- Backups – data removed from the production system may remain in automatic backups for up to 30 days and is then overwritten; backups are used only to restore the system after a failure.
- Password-reset token – valid for 1 hour and single-use.
- Caregiver access – until it expires or is revoked, after which it stops working; the entry stays visible to the parent until the account is deleted.
- Server logs – for as long as needed for security and diagnostics, after which they are automatically rotated and deleted.
- Correspondence and data needed to defend against claims – until the claims become time-barred.
8. Your rights
You have the right to access your data, rectify it, erase it, restrict processing, data portability, object to processing based on legitimate interest, and withdraw consent at any time.
You can exercise most of these rights yourself: edit data in the app or panel, download a full copy in JSON format (“Account” tab), delete individual data, a child profile or the whole account. For anything else write to kontakt@lifenexa.pl – we will reply within one month.
You also have the right to lodge a complaint with the supervisory authority: the President of the Personal Data Protection Office (UODO), ul. Stawki 2, 00-193 Warsaw, Poland (uodo.gov.pl).
9. Automated decision-making
We do not take decisions about you by solely automated means and we do not profile users.
10. Data security
We apply measures appropriate to the risk, including: an encrypted connection (HTTPS/TLS), passwords stored only as hashes, caregiver access tokens stored only as hashes, sessions in an HttpOnly cookie, login attempt limits, separate permissions for health data (invisible to caregivers by default), a security event log and regular backups.
11. Cookies and similar technologies
The site uses a strictly necessary session cookie (babysos_session), set after sign-in to keep you signed in (HttpOnly, Secure, SameSite=Lax, valid for up to 30 days or until sign-out). We use no analytics, marketing or advertising cookies, so no consent banner is shown. The mobile app keeps the session token in the system's secure storage. After you choose a language, we store the lifenexa_locale cookie (Secure, SameSite=Lax, up to 12 months). It remembers your explicit choice from 15 languages and is shared across lifenexa.pl subdomains. We do not choose a language based on your location.
12. Changes to this policy
We will announce material changes to this policy in the app, in the panel or by e-mail. The current version is always available on this page; its effective date is shown at the top of the document.
13. Care assistant and optional OpenAI
Record and schedule analysis runs on the BabySOS server without an external model. Optional OpenAI chat is disabled by default pending administrator configuration and package limits. Sending a question requires explicit consent on the chat screen.
When enabled, OpenAI receives the question, up to six recent messages, types/times/amounts of up to 60 records and up to 30 schedule titles for the selected child. Database identifiers, the child’s name and birth date, photos, notes, contacts and medical card are excluded. Questions and schedule titles can still contain private details entered by the user.
BabySOS does not store chat content in its database; it remains in screen memory until leaving or clearing the conversation. The database stores the package and request/token-budget counters without conversation text. Disabling response storage in the API does not guarantee zero provider retention. Processing and any transfer outside the EEA depend on the provider account configuration; the administrator must establish these terms and complete the information before enabling the service.
The assistant helps organise care. It does not make medical decisions or automatically save changes. OpenAI answers can be incorrect; check facts against the records and schedule.
14. Photos and optional voice recordings
A profile photo is optional. Metadata is removed and the image is resized before storage. Only authorised parents can access it after signing in. It is included in data exports and removed with the child's profile.
Recording starts only on your action and with system permission, lasts up to 30 seconds, and stops in the background. You can play or delete it. Leaving the screen removes the recording; interrupted recordings in cache are cleared on the next launch.
Sending audio to OpenAI requires separate consent for that recording, an enabled service and package allowance. Audio can include other people's voices. BabySOS does not store audio on its server. Provider processing and retention depend on the provider account terms; lack of BabySOS storage does not imply zero provider retention. The database stores seconds, requests and budget counters. Other features work without uploading audio.
Review the transcription before sending a question. Sound descriptions cannot establish the cause of crying or assess a child's health. Care suggestions depend on parent observations. Saved history notes contain text only.
15. AI cry detection and contact
A short clip is sent only after explicit consent for that recording. Local YAMNet detects sound categories on the BabySOS server; audio is not sent to an external provider or retained on the server. Results can be wrong. The model does not determine the cause of crying, illness or pain. Care suggestions use selected observations and a checklist based on the child’s records. We store the text result, request identifier, account and child linkage, and monthly counter. Results are included in data export and removed with the account or child profile. Limits are shared across children and devices on an account and reset at the start of each UTC month. Failed analyses do not consume quota. The phone recording is removed on leaving the screen. Analysis requires internet access. The contact form stores your name, email, app, topic and message in an administrator inbox to answer your enquiry, based on consent in the form, until the enquiry is resolved and for the justified period needed to handle it. Withdraw consent by contacting kontakt@lifenexa.pl. Do not include passwords or child health details.
16. Payments and invoices
When you buy a paid plan we process: the plan and period, amount, date, the chosen payment operator, transaction and subscription identifiers assigned by the operator, payment and refund status, the moment you requested the service to start, and the invoice details entered in the customer panel (name or company name, tax ID, address). We neither receive nor store payment card data.
Legal bases: performance of the contract (Art. 6(1)(b) GDPR) and tax and accounting obligations (Art. 6(1)(c) GDPR). Invoices and billing records are kept for the period required by tax law (as a rule 5 years from the end of the year in which the tax payment deadline passed) – also after the Account is deleted.
Recipients: the payment operator you choose (Stripe, Przelewy24 or PayPal – each also processes payment data as a separate controller under its own terms), the invoicing system provider (Fakturownia) and – where invoices are issued in KSeF – the Polish Ministry of Finance as operator of the National e-Invoicing System. Payment operators may transfer data outside the EEA under mechanisms provided for in the GDPR.
17. LifeNexa AI assistant, voice and feedback
The optional LifeNexa assistant is separate from the record analysis in section 13. It receives your question, conversation identifier and application screen name. The backend uses your account identifier to check permissions and limits. Records, photos, surnames, health information and the child profile are not attached automatically. Avoid entering personal details about children or other people when they are not needed.
The assistant may use a local model or a cloud provider configured by the administrator. A notice before the conversation discloses possible cloud use, and each answer identifies the provider reported by the service. Model failures do not prevent diary or schedule use. Answers can be wrong; the assistant does not diagnose or contact emergency services. Opening a proposed form requires your confirmation, and saving requires separate confirmation in that form.
Speech transcription requires consent to send that particular recording to the LifeNexa AI service. Recordings can include nearby voices; record only what you wish to share. Review and edit the transcript before sending a question. The mobile app uses the phone's voice to read answers only after you enable it. The browser panel uses the LifeNexa AI service for speech synthesis.
Answer ratings are aggregated as application counters without conversation text or an account association. Reporting a problem is optional and requires a separate, initially unchecked consent for that answer. The owner then receives that question and answer, the problem category and optional comment. The service stores the encrypted report for up to 90 days without a user identifier. Personal information you type into the question or comment may still appear in the report. Without this consent, text is not submitted as a problem report.
18. Trials, releases and contact requests
- Before activating the trial, we require your full name, phone number and email verification. The email code is single-use, valid for 15 minutes and limited to 8 attempts. We do not store the code in plain text. We store the installation identifier in browser storage or the phone’s secure storage solely to protect the trial against abuse.
- To compare repeated trial requests, we store HMAC hashes of the email address, phone number and installation identifier. These are pseudonymised data, not anonymous data. Preventing abuse is based on the controller’s legitimate interest (Article 6(1)(f) GDPR); providing the Account and trial is based on performance of a contract (Article 6(1)(b)). We keep the hashes for up to 24 months, including after Account deletion. We do not use them for advertising or tracking outside BabySOS. You may object and request an individual review.
- The contact form stores the name, email address, selected application, topic, message and handling status you provide. Do not include unnecessary information about your child. Enquiries are used to respond and provide support; they are not published. Access is restricted to authorised support staff.
- Only the administrator uploads installers. They contain no accounts, API keys or children’s data. Downloads may create a standard request entry in hosting logs. iOS links may redirect to the App Store or TestFlight, where Apple’s terms apply. Cry recordings are not retained after processing; the result and allowance usage remain on your Account. Sound recognition does not determine the medical cause of crying.
We also record the language selected when you submit an enquiry, so our support team can take it into account when replying.
19. Care library, reviews and preferences
We store checklist progress separately for each signed-in user and child profile to provide the chosen care feature. The data are private, available in data exports and deleted when the account or child profile is deleted. Guide content remains available without AI.
Submitting a review is voluntary. Following separate consent and moderation, we publicly display the alias, rating, review text, language and date, and any support reply. Do not post children's information or contact details. You can withdraw your consent in the Your review tab using the Withdraw and delete review button; the review and reply will be deleted. Withdrawal does not restrict other app features. A security log records the operation without the review text. You can also email kontakt@lifenexa.pl.
We store your selected interface language in the necessary bsos_app_locale cookie and your time zone in bsos_tz, for up to one year. On your phone, the language preference is stored locally. These settings are not used for advertising or tracking.