Effective date: May 20, 2026
Operator: MB Muzė LT
Address: Kaunas, Chemijos g. 27C-62, LT-51332, Lithuania
Email: info@muze.lt
Website: https://muze.lt
1. Introduction
This Privacy Policy explains how MB Muzė LT (“Nibbly,” “we,” “us,” or “our”) collects, uses, stores, shares, and protects information when you use Nibbly (the “App”) or contact us.
Nibbly is a baby food tracking app for parents and caregivers of babies starting solids.
This Privacy Policy applies to the Nibbly App and related website or support interactions.
2. Who We Are
The operator of Nibbly is:
MB Muzė LT
Kaunas, Chemijos g. 27C-62, LT-51332, Lithuania
Email: info@muze.lt
Website: https://muze.lt
3. Important Privacy Design: No Account and Local Baby Data
Nibbly does not require a user account.
Baby profiles, baby nickname or name, date of birth, allergy entries, introduced foods, food logs, reaction status, reaction notes, custom foods, custom meals, and similar personal app data are intended to be stored locally on your device.
We do not operate cloud sync for this data and do not maintain a server backup of this local baby and feeding data.
You may choose to use a nickname or fake name for a baby profile. You should avoid entering unnecessary sensitive medical details.
4. Information Stored Locally on Your Device
Depending on how you use Nibbly, the App may store the following information locally on your device:
- baby nickname or name you choose to enter;
- baby date of birth;
- allergy entries you choose to enter;
- introduced foods;
- reaction status;
- reaction notes;
- food and meal logs;
- custom foods or meals;
- local reminder settings;
- app preferences; and
- other information you choose to enter into the App.
This information is intended to stay on your device and is not synced to a Nibbly account.
Your device or Apple account settings may separately back up app data through Apple services, such as iCloud device backups. Those backups are controlled by Apple and your device settings, not by Nibbly.
5. Information We May Collect Automatically
Although baby and feeding data is stored locally, we may collect or receive limited technical, analytics, crash, purchase, attribution, and diagnostic information through third-party services.
This may include:
- device type and model;
- operating system version;
- app version;
- country or region;
- language settings;
- anonymous or pseudonymous app identifiers;
- general feature usage events;
- app open events;
- paywall and purchase-related events;
- subscription status information;
- crash reports;
- diagnostic logs;
- performance data;
- advertising attribution data; and
- information about whether App Tracking Transparency permission was granted.
We use this information to operate, improve, analyze, debug, secure, and market Nibbly.
6. Analytics
Nibbly may use Firebase Analytics and PostHog Cloud to understand general App usage and improve the product.
Analytics events are intended to be anonymous or pseudonymous and focused on general usage, such as app opens, feature usage, paywall views, subscription events, and similar product analytics.
Analytics events should not include baby names, date of birth, allergy text, reaction notes, parent notes, or detailed personal feeding records.
7. Crash Reporting and Diagnostics
Nibbly may use Firebase Crashlytics and Sentry to identify, diagnose, and fix crashes, bugs, and performance issues.
Crash and diagnostic data may include device information, operating system version, app version, crash traces, error logs, and technical information about the state of the App when an issue occurred.
We do not intentionally send baby names, reaction notes, or personal feeding notes to crash reporting services. However, you should avoid entering unnecessary sensitive information into fields that may appear in diagnostic contexts.
8. Purchases and Subscriptions
Nibbly may offer paid features, subscriptions, lifetime access, or free trials through Apple In-App Purchase. We may use RevenueCat to manage and validate purchase and subscription status.
RevenueCat and Apple may process information such as:
- anonymous or pseudonymous app user identifiers;
- purchase status;
- subscription status;
- product purchased;
- trial, renewal, cancellation, or expiration status;
- country or storefront information; and
- transaction-related information.
Nibbly does not provide RevenueCat with baby profile data, food logs, allergies, reaction notes, or local feeding history.
9. AI Meal Idea Features
Nibbly may provide AI-powered meal idea features through a backend proxy using OpenRouter and AI model providers selected through OpenRouter.
When you use AI meal idea features, Nibbly may send limited information to generate suggestions, such as:
- baby age;
- introduced foods;
- allergy entries; and
- reaction status.
Nibbly does not intentionally send the following information for AI meal idea generation:
- baby name or nickname;
- date of birth;
- reaction notes;
- parent notes;
- meal history;
- photos;
- account identifiers; or
- user account information.
AI-generated meal ideas may be inaccurate, incomplete, unsuitable, or outdated. They are not medical, nutrition, allergy, or feeding advice.
10. Firebase Cloud Functions and Backend Proxy
Nibbly may use Firebase Cloud Functions for backend logic, anonymous event handling, and proxying calls to AI providers.
Firebase Cloud Functions are not intended to store baby profiles, food logs, reaction notes, parent notes, or personal feeding records.
11. Apple Search Ads, IDFA, and Tracking
Nibbly may use Apple Search Ads attribution and other analytics or attribution tools to understand marketing performance.
Nibbly may request permission through Apple’s App Tracking Transparency prompt to access the Identifier for Advertisers (IDFA) or conduct tracking as defined by Apple.
If you grant permission, Nibbly and its service providers may use IDFA or related attribution information to measure advertising performance and understand how users discover the App.
If you deny permission, Nibbly will not access IDFA for tracking purposes. You can manage tracking permissions in your iOS device settings.
12. Voluntary Email Communications
Because Nibbly does not require an account, we do not require you to provide an email address to use the App.
You may voluntarily provide your email address in the App or through our website for support, feedback, updates, marketing, waitlist, or other communication purposes.
If you opt in to marketing emails, you may unsubscribe using the unsubscribe link or instructions provided in the email, or by contacting us at info@muze.lt.
Transactional, support, or service-related emails may still be sent where appropriate.
13. Local Reminders
Nibbly may allow you to schedule local reminders, such as meal plan reminders. These reminders are scheduled locally on your device.
Nibbly does not send your meal plan reminder data to our servers for cloud sync.
You can manage notifications through the App and your device settings.
14. Sharing Through the iOS Share Sheet
Nibbly may allow you to share meal cards or other content through the iOS share sheet.
Shared content may include information you choose to include, such as recipe text, notes, Nibbly branding, or the footer “Made by a parent using Nibbly.”
Shared content should not include baby names by default. You are responsible for reviewing any shared content before sending it through another app or service.
Once you share content outside Nibbly, that content is handled by the app, platform, or person you shared it with.
15. How We Use Information
We may use information for the following purposes:
- to operate and maintain Nibbly;
- to provide App features;
- to process purchases and subscription status;
- to provide AI meal idea features when used;
- to analyze anonymous or pseudonymous usage trends;
- to improve App design, features, reliability, and performance;
- to detect, diagnose, and fix crashes or bugs;
- to measure marketing and attribution performance;
- to respond to support requests or voluntary communications;
- to send marketing emails if you opt in;
- to comply with legal obligations; and
- to protect our rights, users, and services.
16. Legal Bases for Processing
If you are in the European Economic Area, United Kingdom, or another region with similar privacy laws, we rely on the following legal bases where applicable:
- performance of a contract, to provide the App and paid features;
- legitimate interests, to improve, secure, debug, and analyze Nibbly;
- consent, for marketing communications, App Tracking Transparency permission, and certain optional features where required;
- legal obligation, where processing is necessary to comply with law; and
- your explicit action or request, when you voluntarily provide information or use optional features.
17. When We Share Information
We may share limited information with service providers that help us operate Nibbly, including:
- Apple, for App Store distribution, In-App Purchases, subscriptions, refunds, and attribution;
- Firebase, for analytics, crash reporting, Cloud Functions, and related infrastructure;
- PostHog Cloud, for product analytics;
- RevenueCat, for purchase and subscription management;
- Sentry, for crash and error reporting;
- Cloudflare, for website, security, network, or infrastructure services;
- OpenRouter and AI model providers, for AI meal idea features when used;
- analytics and attribution providers, for marketing performance measurement; and
- email or support providers, if you voluntarily contact us or subscribe to communications.
We do not sell baby profiles, food logs, allergies, reaction notes, or local feeding history.
18. International Data Transfers
Some service providers may process data in countries outside your country or region, including outside the European Economic Area.
Where required by law, we rely on appropriate safeguards, such as contractual protections, data processing agreements, adequacy decisions, standard contractual clauses, or other legally recognized transfer mechanisms.
19. Data Retention
Local baby and feeding data is stored on your device until you delete it in the App, delete the App, reset your device, or otherwise remove it from your device.
Nibbly does not maintain a server backup of baby profiles, food logs, allergy entries, reaction notes, or local feeding history.
Analytics, diagnostic, purchase, attribution, support, and communication data may be retained by us or our service providers for as long as needed for the purposes described in this Privacy Policy, including product improvement, debugging, purchase validation, legal compliance, fraud prevention, and business records.
20. Deleting Your Data
Because Nibbly does not require an account and stores baby and feeding data locally, you can delete local app data by deleting entries in the App, deleting baby profiles where available, or deleting the App from your device.
Deleting the App removes local Nibbly app data from that device, subject to Apple device backups, iCloud backups, and your device settings.
If you have voluntarily contacted us by email or subscribed to marketing communications, you may contact us at info@muze.lt to request deletion or correction of information we hold about that communication.
21. Your Privacy Rights
Depending on where you live, you may have rights to:
- request access to personal data we hold about you;
- request correction of inaccurate personal data;
- request deletion of personal data;
- object to or restrict certain processing;
- withdraw consent where processing is based on consent;
- request portability of certain personal data; and
- lodge a complaint with a data protection authority.
To exercise privacy rights, contact us at info@muze.lt.
Because Nibbly does not require an account and stores baby and feeding data locally on your device, we may not be able to access, export, or delete local app data for you. You can manage local data directly on your device.
22. Children’s Privacy
Nibbly is intended for use by parents and caregivers, not by children. We do not knowingly collect personal data directly from children.
Parents and caregivers are responsible for deciding what information to enter into the App about a baby or child. You should avoid entering unnecessary sensitive information.
23. Security
We use reasonable technical and organizational measures designed to protect information processed through Nibbly and our service providers.
However, no app, device, network, or electronic service is completely secure. You are responsible for keeping your device secure, using device passcodes or biometric protection where appropriate, and managing your device backup settings.
24. Third-Party Links and Services
Nibbly may interact with third-party services such as Apple, Firebase, PostHog Cloud, RevenueCat, Sentry, Cloudflare, OpenRouter, AI model providers, analytics providers, attribution providers, email providers, and apps used through the iOS share sheet.
Those third-party services may have their own privacy policies and practices. We are not responsible for privacy practices of third-party services we do not control.
25. App Store Privacy Labels
Apple may require privacy information in App Store Connect. The App Store privacy labels are a summary and may not include every detail in this Privacy Policy.
If there is a conflict between an App Store summary and this Privacy Policy, this Privacy Policy provides the more detailed explanation of our practices.
26. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. If we make material changes, we may notify you through the App, website, App Store listing, or another reasonable method.
The updated Privacy Policy will be effective when posted or when otherwise stated.
27. Contact
If you have questions, requests, or concerns about this Privacy Policy, contact us at:
MB Muzė LT
Kaunas, Chemijos g. 27C-62, LT-51332, Lithuania
Email: info@muze.lt
Website: https://muze.lt