Privacy Policy

Who operates Bebble

Bebble is a parenting and baby-care tracking app operated by Wyzer Labs LLC. References to “we” and “us” in this policy mean Wyzer Labs LLC.

This policy covers Bebble account information, information you add about your baby and their care, and information received when you choose Continue with Google.

Information you provide

When you use Bebble, you may provide information such as:

Account information

• Email address and sign-in information, including a password if you choose email-and-password sign-in
• Account identifier and authentication session information
• Display name and basic Google identity information if you choose Google Sign-In, as described below

Baby profile information

• Baby’s name
• Date of birth
• Profile photo
• Due date and birth measurements, if you choose to add them

Tracking information

This may include records you choose to log, such as:

• Feeding
• Pumping
• Sleep
• Diapers
• Growth
• Activities
• Medications
• Health entries, including vaccinations and temperatures you log
• Milestones and development check-ins
• Custom logs
• Notes

Memories

You may choose to save memories, notes, and photos, along with titles, dates, tags, people, and favorite status. Baby profile photos and memory photos are uploaded to private Supabase Storage buckets to make them available to authorized members of that baby’s Care Circle.

Planner and reminder information

You may create reminders, medication schedules, appointments, and other baby-related tasks.

Preferences and Care Circle information

Bebble stores preferences such as units, appearance, time format, Quick Log choices, and reminder settings. Care Circle records include membership, a relationship you choose to add, and invitation details such as the recipient’s email address and invitation status.

Imported information

If you use Bebble’s import feature, you select an export file from a supported app. Bebble reads a cached copy on your device to identify records that can be added to your selected baby profile. Supported records are sent to Supabase only after you confirm the import.

Optional voice entry

If you use voice entry, Bebble requests microphone and speech-recognition permission and uses your device’s speech-recognition service to turn speech into text. That service may process speech on the device or through its provider, depending on your device and settings. Bebble parses the resulting text on your device and saves the care records you confirm.

Support information

If you contact us at hello@bebble.app, the information you choose to send may include your message, reply email address, and screenshots. The current in-app Contact us form prepares this information on your device but does not deliver it to the Bebble team.

Google Sign-In

Continue with Google is an optional way to create or sign into your Bebble account through Supabase Auth. When you choose it, Google provides basic account identity information:

• Your name
• Your email address
• A reference to your profile picture, if Google supplies one

Supabase also records the Google account identifier and email-verification information needed to associate that identity with your Bebble account. This is basic identity access, not access to the content of your Google services. Bebble does not receive your Google password.

Bebble does not request access to Gmail, Google Drive, Google Calendar, Google Contacts, Google Photos, or other Google service content. Google Sign-In does not give Bebble access to your messages, files, calendar events, contacts, or Google Photos library.

How Google user data is used

Bebble uses Google identity information to authenticate you, create or sign into your Bebble account, and identify the account associated with your baby profiles and records.

Your Google name can initialize your Bebble display name. That name identifies you to people who share a baby profile with you, appears in Care Circle and memory attribution, and identifies you in Care Circle invitations you send. Your email address is also used to check whether an invitation was addressed to your account.

The Google profile picture reference is retained in authentication metadata. The current app uses your display name for Care Circle identification; it does not display your Google profile picture there.

These are the current uses of Google identity information. Google Sign-In is not used to import baby-care records or to read other Google service content.

Information collected automatically

Signing in and using Bebble sends authentication requests and the data needed for the features you use to Supabase. Supabase Auth maintains account and sign-in information, including account identifiers and sign-in timestamps.

Bebble records some feature activity to provide the app’s functionality, including saved activities, lesson-read status, development check-ins, and planner completion. These records are associated with the relevant account or baby profile.

The configured Expo app-update service receives app project, platform, and runtime-version information to check for compatible updates. These update requests do not include Google identity information.

The current app does not integrate an advertising SDK or a third-party usage-analytics or crash-reporting SDK. Its in-app Contact us form can prepare optional problem-report diagnostics on your device, including:

• App version
• Device type
• Operating system
• Current app screen and timestamp

These diagnostics do not automatically include your baby’s tracking history, memories, photos, or other baby data. The current form does not send the prepared report to a server.

How we use your information

We may use your information to:

• Provide Bebble’s tracking and logging features
• Keep your records available across supported devices
• Provide reminders and planner features
• Show age-relevant Activities, Quick Learn, and Development content
• Generate Bebble insights when you allow tracking data to be used for this purpose
• Create reports and exports requested by you
• Process imported records
• Respond to support requests
• Maintain security and prevent misuse
• Diagnose bugs and improve app reliability
• Improve Bebble’s features and user experience

Age-based content

Some Bebble features are primarily based on your baby’s age or developmental stage.

This includes features such as:

• Activities
• Quick Learn
• Age-relevant Development content

These features do not require Bebble to analyze your feeding, sleep, diaper, or other tracking history.

Bebble insights

Bebble may use the tracking information you log to provide personalized observations, summaries, and trend interpretations.

You can control this from:

Profile → Privacy & data controls → Use tracking data for Bebble insights

Turning this setting off does not delete your tracking records.

It also does not disable age-based features such as Activities or Quick Learn.

Bebble insights are intended to help organize and explain information you have recorded. They are not a medical diagnosis and should not replace advice from a qualified healthcare professional.

Photos and memories

Photos and memories you add are used to provide Bebble’s memory features.

We do not create a memory or represent a photo as belonging to your baby unless it was actually provided or saved through your account.

Reminders and notifications

If you enable reminders, Bebble may use information such as:

• Your configured reminder schedule
• The time of your most recently logged feed or pumping session
• Medication schedules you create
• Planner items
• Your notification preferences
• Reminder and notification hours you set

You control the reminder schedules. Bebble does not independently determine when your baby should be fed, pumped for, or given medication.

Importing data

Bebble may allow you to import information from supported baby-tracking services.

When you select an import file, Bebble may process it to:

• Identify supported records
• Map records into Bebble categories
• Identify possible duplicate records
• Show you a preview before import

Bebble should not add records until you confirm the import.

This file-based import is separate from Google Sign-In and does not request access to Google Drive or any other Google account content.

Exporting your data

You may use Bebble’s Export Data feature to create a copy of supported information associated with your baby profile.

Available export formats may include formats such as CSV or PDF.

Exported files can contain personal information. You are responsible for how you store or share files after they leave Bebble.

Other users on a baby profile

Bebble may allow more than one user to access the same baby profile.

Active members of a baby’s Care Circle can access the shared baby profile, care records, and memories. Members can see one another’s Bebble display names. The baby’s owner can invite and remove members; those membership-management actions are restricted to owners.

Only add people you trust.

Service providers

Bebble uses the following service providers for its current features:

• Supabase provides authentication, the app database, private photo storage, and backend functions. It processes Google identity information to establish and maintain your Bebble account, and stores the baby-care information you save.
• Resend delivers Care Circle invitation emails. When you send an invitation, it receives the recipient’s email address, your Bebble display name, the baby’s name, and the invitation link and message. Your display name may have originated from Google Sign-In.
• Expo provides the configured app-update service and receives the app project, platform, and runtime-version information needed to deliver compatible updates. These requests do not include Google identity information.

These providers may process information on our behalf only as needed to provide their services.

Sharing and transfers of Google user data

Google identity information is processed by Supabase as Bebble’s authentication and backend provider. Your Bebble display name, which may come from Google, is shared with other members of your baby’s Care Circle and is included in invitations you send through Resend to your chosen recipients.

Bebble’s current Google sign-in and Care Circle features do not sell Google user data or transfer it for advertising, retargeting, data brokerage, credit assessment, or lending. These features use and transfer Google identity information for account access and the account-identification and sharing functions described in this policy.

Advertising and analytics

The current app has no integrated advertising, third-party usage-analytics, or crash-reporting SDK. Care-history trends and feature-progress records are used to provide Bebble’s own features. If new analytics or advertising services are introduced, this policy must describe their data handling before that handling begins.

Where information is stored

Google identity information becomes part of your Supabase Auth user and identity records. Your Google name may also be copied into the Bebble profile’s display name. The application profile does not duplicate your authentication email or password, and its creation flow does not copy your Google profile picture into a separate profile-photo field.

Baby profiles, care records, memories, planner information, and supported account preferences are stored in the Supabase database. Uploaded baby profile photos and memory photos are stored in private Supabase Storage buckets.

Bebble also stores information on your device, including the authentication session and user information returned by sign-in, local preferences, and cached or exported files. Signing out removes the saved authentication session from app storage; it does not delete the account or the information stored in Supabase.

Data retention

We keep information for as long as reasonably necessary to provide Bebble, maintain your account, comply with applicable obligations, resolve disputes, and protect the service.

Google identity information and account-profile information remain associated with your Bebble account while the account exists. The current app does not automatically delete an account after a period of inactivity or provide a working self-service account-deletion flow.

Removing a Supabase Auth account removes its linked application profile, account preferences, and Care Circle memberships through database relationships. It does not automatically delete shared baby profiles or their care records: those belong to the baby profile, and records can remain with the author reference removed. An account that is the only owner of a baby profile cannot be removed until that ownership is transferred or the baby profile is removed. Stored photos also need separate handling.

Supabase does not allow an Auth account to be deleted while it owns stored files. Those files must be deleted or their ownership reassigned before account removal. Account removal is not a substitute for deleting the baby’s stored photos or shared records.

Some information may need to remain temporarily in backups or where retention is legally required.

Your choices and controls

Depending on the feature, Bebble may allow you to:

• Turn off tracking-data-based Bebble insights
• Manage notification and reminder preferences
• Set reminder and notification hours
• Export your data

These controls do not currently provide a working backend deletion flow for an account or bulk deletion of baby-care data. See the account-deletion section below.

Turning off a feature does not necessarily delete information that was already stored.

Google connection and account deletion

You can choose email-and-password sign-in instead of Continue with Google. You can also remove Bebble’s connection in your Google Account’s third-party connections settings. Removing that connection prevents continued Google authorization; it does not erase identity information already stored with your Bebble account or delete baby-care records.

The current app shows a Delete account action under Privacy & data controls, but that action does not delete your Supabase account. The current in-app Contact us form also does not deliver deletion requests. Signing out, removing the Google connection, or uninstalling Bebble does not delete your account or cloud records.

Account removal and removal of shared baby data are separate actions, as explained under Data retention. Photos, shared records, and account ownership must be considered when handling a deletion request.

To request account deletion or make a personal data request, contact Wyzer Labs LLC at hello@bebble.app.

Security

We use reasonable technical and organizational measures designed to protect information handled by Bebble.

Bebble uses Supabase authentication for account access and a PKCE code-exchange flow for Google sign-in. Its Google sign-in callback and configured hosted Supabase connections use HTTPS, which protects information in transit.

Supabase row-level security restricts account and baby-data access based on the signed-in user and active Care Circle membership. Membership-management actions check baby ownership. Baby photos and memory photos use private storage buckets with membership checks and time-limited signed links for display.

Signed photo links can be used by anyone who has the link until it expires, so take care when sharing links or exported files.

However, no internet-connected service or storage system can guarantee absolute security.

Google API Services User Data Policy

Bebble’s use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements.

This statement applies to the basic identity information received through Google Sign-In and the uses and transfers disclosed above. It does not mean that Bebble accesses Gmail, Drive, Calendar, Contacts, Google Photos, or other Google service content.

Children’s information

Bebble is designed for parents and caregivers to manage information about babies and children.

Bebble is not intended to be used independently by children to create accounts or submit their own personal information.

Parents and caregivers are responsible for the information they choose to add about a child.

Changes to this Privacy Policy

We may update this Privacy Policy as Bebble changes.

When we make material changes, we may provide notice through the app or by another appropriate method.

The last-updated date at the top of this policy shows when it was revised. Before requesting additional Google permissions or using Google user data for a new purpose, we will update these disclosures and request any required consent.

Contact us

You can contact Wyzer Labs LLC at hello@bebble.app for privacy questions, account deletion requests, personal data requests, Google Sign-In privacy questions, and general privacy concerns.

The current in-app Contact us form does not deliver messages or privacy requests to the Bebble team.