Privacy Policy

01Privacy summary

Summary

• Care records live in the app’s local storage on this iPhone.
• There is no developer-run record server and no account system.
• Family Sharing is off by default. After the family owner enables Daybub Family, records sync through a CloudKit shared zone in the owner’s iCloud and can be read and written by up to six members. This is not Apple Family Sharing.
• We use Firebase Analytics for anonymous usage events, and you can turn it off in Settings. It measures actions such as feature use. It does not include baby nicknames, note text, or photos; it does not collect the advertising identifier (IDFA), include an ad SDK, perform cross-app tracking, or build user profiles.
• Photos come from the system picker or camera and only selected or captured images are handled, up to 6 per record.
• CSV export is triggered by you and handled through the system share sheet.

02Processing principles

Processing principles

Daybub processes only information necessary for product features. The data path is designed as local first, minimal collection, and deletable: information is created on device, stored on device, and kept under your control for export or deletion.

03System permissions

System permissions

The current version does not request Contacts, location, microphone, HealthKit, Bluetooth, or background-location permission. Family Sharing uses Apple’s iCloud account system and iOS handles sign-in. We never receive your Apple ID or password.

04Data categories and location

Data categories and location

05Photos and reminders

Photos and reminders

Photos

Photo capture and selection happen in iOS system interfaces. When picking from the library, iOS presents the permission prompt and you may grant only Selected Photos. Daybub copies only the selected or captured image, up to 6 per record, into private app storage for record detail and memory grids. It does not scan your photo library or upload photos to our services.

Reminders

Reminders calculate reference intervals locally from record times you enter. The current version supports feeding intervals and to-dos. Medicine and temperature are never automatically reminded because that could replace medical judgment.

06Retention, export, and deletion

Retention, export, and deletion

Information remains in this iPhone’s app storage until you delete records, clear data, or delete the app. Personal mode mirrors to your own private iCloud database; Family mode stores records in the owner’s iCloud CloudKit shared zone. The app currently exports records.csv; complete backup for baby profiles, photos, and documents is still being improved.

07Family Sharing and iCloud

Family Sharing and iCloud

Family Sharing is off by default. Only after you actively create a family or join with an invitation code does the app sync data through Apple CloudKit. Before then, all data stays on this iPhone.

Where data is stored and whose storage it uses

Personal mode uses each user’s private iCloud database. Daybub Family uses a CloudKit shared zone created by the family owner: shared baby profiles, records, to-dos, photos, member information, and the Family entitlement primarily count against the owner’s iCloud storage. Invited members keep local data/cache and can read and write the shared zone.

• Capacity: up to 6 members — 1 owner plus 5 invitees.
• Family members must be signed in to their own available iCloud account, but do not need to belong to the owner’s Apple Family Sharing group or share Apple iCloud+ storage.
• The developer cannot access record content, member names, or photos in the shared zone; the app has no operational backend or account system and never receives your Apple ID.
• Precise exception: Apple CloudKit public database contains a minimized invitation directory that maps the six-character code to a CKShare link. The current version writes only the code and link, no family name; the upgrade maintenance flow clears the family-name field written by older versions. The directory contains no member names, care records, or photos.
• Sync limitations: sharing/sync may pause if a member is not signed in to iCloud, the network fails, or the owner’s iCloud storage is insufficient. Records already saved on device are not deleted.
• Subscription expiry: when Family Annual expires, family collaboration and member-derived Plus pause; existing records remain and collaboration resumes after renewal.
• Only family members you invite and who successfully join can see shared information. People without a valid invitation cannot access it. Active timer state is not synced.

How to stop sharing

You can also manage this app’s iCloud access in the iOS Settings iCloud section. After sharing stops, the app returns to local-only mode.

08Third-party SDKs and cross-border transfer

Third-party SDKs and cross-border transfer

The app currently integrates one third-party SDK to understand feature usage and improve the product. It is not an advertising SDK and does not participate in cross-app tracking.

What it collects

• Feature-use events and parameters, such as “created a record” or “opened a screen.” They describe behavior types and do not include baby nicknames, note text, photos, invitation codes, email addresses, or exact birth dates.
• Device and app information: model, system version, language, and app version.
• Country/city-level coarse region, which Google may derive from network information. The app does not access GPS, Wi-Fi positioning, or precise coordinates.
• Firebase SDK technical diagnostics, such as installation or technical state information. They do not include care records, photos, notes, or family member information.
• An app-instance identifier and vendor identifier (IDFV). IDFV is shared only among apps by the same developer and cannot track you across developers.

What it does not collect

• It does not collect the advertising identifier (IDFA). Therefore the app does not show the system “Allow Tracking” request and does not perform ad attribution.
• It does not collect Contacts, precise location, Health data, microphone audio, or browsing content.
• Data is not sold, used to build user profiles, or shared with advertising platforms.

Cross-border transfer

Firebase Analytics data is processed by Google’s global infrastructure. For users in mainland China, analytics data may be stored or accessed outside mainland China. If you do not want this processing, turn off anonymous usage statistics in Settings; after that the app sends no analytics events.

Retention follows the Firebase project configuration; the standard retention period is no longer than 14 months. If another third-party SDK is added later, we will first disclose its name, purpose, data types, and how to turn it off in this policy and in the app.

09Children and family use

Children and family use

The app is intended for parents, caregivers, and family members. The baby is the subject of the records, not an account holder. Adults should install, configure, and use the app, and show records to other caregivers only when necessary.

10Security limitations

Security limitations

• Local storage benefits from the iOS app sandbox and data protection, but the app cannot replace a device passcode, backup, or careful safekeeping.
• After ZIP, CSV, or shared content is exported, security depends on the destination app, cloud service, or recipient you choose.
• Do not keep sensitive records on a shared device unless you understand and accept its sign-out, lock, and backup policies.
• Debugging, analytics, and operations must not use real-user family records, member names, or photos; engineering validation uses only test accounts and test families. Invitation codes and links in the public directory are minimized sensitive data and are not written to logs.

11Your rights

Your rights

You can view, correct, export, and delete information in the app. Depending on your region, you may have legal rights to access, correct, delete, restrict processing, port data, and complain. Because there is no developer server or account system, most requests can be completed directly on the device.

Anonymous usage analytics: you can turn them off anytime in Settings. The app immediately stops sending analytics events; you can turn them back on later. Turning analytics off does not affect other features.

For help, contact us through the published contact information on the support page. We will handle requests according to applicable law and actual technical capability.

12Policy changes

Changes

We update this policy as product capabilities change and explain important changes in App Store release notes or on the support page. New processing purposes, permissions, or sync capabilities will be disclosed before the feature is enabled.

13Contact and effectiveness

Contact and effectiveness

This policy became version 1.1 on 2026-10-13. Compared with version 1.0, this revision:

• Corrected iCloud status: Family Sharing through CloudKit is available only after you enable it, with sync scope, storage provider, and stop method explained.
• Added the third-party SDK list, Firebase Analytics cross-border explanation, and opt-out method.
• Corrected permission descriptions: added camera, photo-library write, and Calendar; clarified photo-library reading.
• Corrected “the developer does not collect data”: local data is not uploaded to our server, but the two data-off-device situations above exist.

This policy is version 1.4, effective 2026-11-07. Compared with version 1.3, it discloses Other Diagnostic Data and country/city-level coarse location that Firebase SDKs may generate, and clarifies that both are used only for anonymous analytics, not tracking, and never include baby or family content.

Version 1.3, also effective 2026-11-07, clarified that the family shared zone counts against the owner’s iCloud storage; documented the six-member capacity, iCloud/network/storage limitations, and data retention after subscription expiry; corrected the visibility boundary of the public invitation directory; and explained that newer versions do not store the family name there and clear the legacy field after upgrade.

The previous policy was version 1.2, effective 2026-10-15. Developer name, legal entity, support email, and region information are below.