Privacy
Privacy policy
What this app collects, why it collects it, and what you can ask us to delete.
AI Baby Cry Analyzer, published by Gowalk, helps adult caregivers record care and request optional observations about cry recordings. This policy describes the rebuilt app and its online services. It is not a medical service, and children should not use it independently.
Your care journal
Names or nicknames, dates of birth, feeding and sleep records, diaper changes, growth measurements, medicines, milestones and notes are saved in the app's local database. Use a nickname and record only information you need. These records are not uploaded to our shared-care service unless you choose family sharing. Device and operating-system storage settings also apply to information held on your device.
Reminders are scheduled on your device. Settling sounds are included in the app. Microphone recording begins only after your action and permission; it is not continuous monitoring. Temporary recordings stay on the device until discarded, replaced, cleared by the operating system or removed by the app's account-deletion process.
Optional AI observations
Before an analysis, the app asks permission to send up to 12 seconds of audio and the care context shown in the consent dialog. Context can include age in months, time since feeding, time awake and care checks already tried. We do not send the child's name, full birth date or free-text journal notes in the analysis request. Please avoid recording other people's speech.
The request passes through our backend to OpenRouter and Google's Vertex AI service. Our backend processes audio in memory and does not store the recording. We restrict model routing to providers offering zero data retention for request content. Technical processing and security information may still be handled under the providers' policies. We do not use your recordings to train our own models.
We retain the resulting sound observation, submitted care context, request identity and processing status in your online account so the app can recover interrupted requests and enforce usage limits. Results are uncertain observations, not diagnoses or identified causes of crying. A content report records the result identity and your selected reason for review.
Optional voice and text care drafts
Quick log can turn a short voice note or up to 1,200 characters of text into at most three feeding, pumping, sleep or diaper drafts. Only after your consent do we send that note and its reference time through our backend to OpenRouter and Google Vertex. Names, dates of birth and journal history are not automatically attached; do not include details you do not want processed. The same restricted routing and request-content retention policy applies.
Our backend does not retain the source text or audio. While a request is pending, a copy stays in this device's care database so interrupted requests can recover. It is removed when the resulting drafts are received or when you discard the pending request. Voice recording files are discarded after the pending copy is saved, or when you leave the recording screen. Unsent typed notes are discarded when you leave that screen.
Structured proposals, their reference time and processing status remain in your online account for recovery, export and usage limits until account deletion. Completed proposals also remain on this device until dismissed or account data is deleted. Drafts do not enter the journal or family sharing automatically. Each requires your review and explicit save; the saved journal entry contains your confirmed corrections. Quick log shares the existing AI allowance and provides no medical advice.
Shared care and exports
Family sharing uploads the profiles, care entries and timers you choose to move into a shared journal. Authorized caregivers can read and edit those records. Invitation codes expire after 24 hours. Share codes only with people you trust; the journal owner can remove a caregiver. Removing access cannot erase a copy someone already exported or recorded.
Journal exports and account exports are created only when requested. When you use the system share sheet, the destination you select receives the file under its own practices. Export files may remain in the app's temporary storage until cleared. We cannot delete copies you have sent to another app or person.
Accounts, purchases and security
Firebase Authentication creates an anonymous account for online features. The app also uses an installation identifier and device-held signing material to authenticate requests. Firebase App Check, Apple's App Attest and Google's Play Integrity help verify legitimate app access. These services process technical device, connection and attestation information. Our hosting and network providers, including Cloudflare, process requests to deliver and protect the service.
Apple or Google processes payments. We do not receive payment-card details. The app and backend handle store transaction references, product identifiers, entitlement status and expiry information to verify purchases, restore access and apply the correct allowance. Sensitive purchase references are encrypted in server storage. Deleting app data does not cancel a store subscription; cancel it in the store's subscription settings.
Optional analytics and crash reports
Usage analytics and crash reporting are separate choices in Care → Settings → Preferences. Both default off. If enabled, Firebase Analytics receives fixed events such as screen visits, feature use, onboarding steps and purchase outcomes. Firebase Crashlytics receives technical crash traces and app/device information. We do not attach names, care notes, audio, birth dates or purchase credentials to these diagnostic events, and advertising identifiers and ad personalization are disabled.
Turn either choice off at any time. The app stops new collection for that choice and requests removal of unsent crash reports when crash reporting is disabled. Previously transmitted diagnostics remain subject to the provider's retention and deletion procedures. Firebase's privacy information describes these services, including the removal process for Crashlytics data after its retention period.
Retention and deletion
Local care records stay until you remove them or delete app data. Shared records and online analysis results and structured care proposals stay until the applicable account or owned shared journal is deleted. Individual shared-entry deletions retain synchronization records so other caregivers can receive the deletion; they are removed with the owned journal. Short-term purchase-allowance records expire after 24 hours and are removed by periodic maintenance.
Care → Settings → Privacy and data lets you export online data or request account deletion. Deletion removes your analyses, care proposals, reports, shared journals you own and their members' access; it also removes this device's care database, recordings, reminders and unsent exports and requests deletion of the Firebase account. The app remains in recovery until those steps finish. Shared journals owned by someone else remain with that owner.
We retain limited retired-account and request-security records to prevent deleted credentials from becoming active again and to protect usage limits. Store records and diagnostics may have separate provider retention obligations. We do not promise that deleting this account removes records held independently by Apple, Google or recipients of an export.
If you no longer have the app, submit an account or data deletion request through the support form. Describe the account or shared journal concerned so we can establish ownership before acting. Do not include passwords, payment-card details or recordings. Support requests include the contact details and message you provide and are retained to handle your request and its follow-up.
Your choices and questions
You can decline recording or analysis, keep journals local, disable diagnostics, remove sharing access and export or delete your account data. Processing by service providers may take place outside your country. No system can guarantee absolute security, so use your device's security controls and share sensitive care information thoughtfully.
Use the support form for access, correction, deletion or privacy questions. We may ask for information needed to verify a request. We update this page when the app's practices change.