This Privacy Policy explains how Feeding Littles Labs, LLC ("we," "our," "us") collects, uses, and shares information when you use the Feeding Littles app for iPhone and Android and hosted pages shown in‑app (the "Service"). If you are located in the European Union (EU), European Economic Area (EEA), United Kingdom (UK), or Switzerland (together, "Europe"), Section 8 describes additional rights that apply to you.
1) Scope
This Policy applies to the Service as defined above and not to third‑party websites or services that may be linked.
2) Information we collect
Account & profile. Firebase user ID, the email you sign up with (required to create an account; Sign in with Apple may share a private relay address), and an optional first name. We do not collect the advertising ID (IDFA on iPhone, AAID on Android).
User Content. Recipes, collections, meal plans, grocery lists (including item photos), journal notes and photos, files you import such as PDFs, and related details you add or import (for example, ingredients and instructions we structure for you, text read from your photos on your device, and AI parse results for recipes).
Subscription/entitlement metadata. Limited purchase/entitlement status via RevenueCat (e.g., product ID, purchase state, expiration). We do not receive card numbers. RevenueCat also receives your account email, which is removed when you delete your account.
Analytics & diagnostics. Event‑level, aggregated analytics (Firebase Analytics) and crash reports (Crashlytics), including device model, OS, app version, and crash traces. We associate these events and reports with your Firebase user ID and pseudonymous app‑level identifiers generated by these tools to help diagnose issues, and we design event parameters not to include obvious PII. Some events include grocery item names and store names you enter, to improve those features. We do not use advertising identifiers.
Support. Messages you send to support.
Automatic technical data. Automatic connection data processed by our providers (for example, IP address used to infer approximate region, device type, and app version).
No ads; no sale/share for targeted advertising. We do not use advertising SDKs or sell/share personal information for cross‑context behavioral advertising.
Categories of personal information (CPRA‑style):
- Identifiers (UID, email, IP, and non‑advertising app‑level identifiers created by our analytics and crash reporting tools)
- Commercial information (subscription/entitlement metadata)
- Internet/Network activity (in‑app events, crash logs)
- User content (recipes, collections, meal plans, grocery lists, journal notes, images)
- Geolocation (approximate) (region inferred from IP; we do not collect precise location data)
- Support communications
Sensitive personal information: we do not knowingly collect or use SPI for additional purposes (e.g., precise geolocation, health diagnoses, or child data).
3) How we use information
- Operate, maintain, and improve the Service (including sync, search, and parsing of imports).
- Provide Community, where users can discover recipes imported from public web links.
- Use AI services (Google Gemini models via Firebase AI / Vertex AI) to turn recipe text, photos and files you provide into structured recipes, and to sort grocery text you paste into list items.
- Provide and manage subscriptions and entitlements (via RevenueCat and the App Store or Google Play).
- Diagnose performance and resolve crashes (Firebase/Crashlytics).
- Security & abuse prevention (e.g., rate‑limiting, fraud detection).
- Prevent abuse and enforce policies (e.g., DMCA and repeat‑infringer policy).
- Provide support and respond to requests.
- Compliance & legal (e.g., DMCA processing, lawful requests).
- No ads; no cross‑context behavioral advertising.
4) Sharing and processing
We share information only as needed to run the Service:
- Processors: Firebase/Google (for authentication, database, storage, analytics, crash reporting, and AI models used in recipe extraction), Apple and Google (payments and subscriptions through the App Store and Google Play; we do not receive your full card number), RevenueCat (subscriptions; we share your account ID, email, and an app analytics ID), Brevo (email communications; we share your email, first name, account ID, subscription status, and whether you’ve imported a recipe, to send service-related messages and other emails you can unsubscribe from), Dub.co (short links for shared recipes, meal plans and household invites; we send the link and its preview, which can include your first name, the recipe name and photo, or the meal plan dates).
- Household members: People in your Household can see your first name, your recipes (including their notes and photos) and your collections. Meal plans and grocery lists in a Household are shared, and every member can edit them. Your journal notes and photos and your email stay private.
- Shared links: When you share a recipe or meal plan by link, anyone signed in to Feeding Littles who has the link can see it and your first name. The link stays up to date with your changes until it is removed.
- Community: Recipes you import from public web links may be listed in Community for other users to discover and save, with a link back to the original source. We never include your edits, photos, or notes, and never show who imported a recipe. Recipes you add any other way (from a photo, pasted text, a file on your device, or from scratch) are never included.
- Internal ops only: Slack, for internal alerts (for example, import problems and Community reports). When you report an import problem, the alert includes your account ID, your report and any attachments, and your name and email if you ask us to tell you when it’s fixed.
- Legal/DMCA: Minimal account data may be disclosed to rights‑holders to process notices/counter‑notices or as required by law.
- Business transfers: In a merger, acquisition, or financing, subject to this Policy.
We do not sell personal information or share it for cross‑context behavioral advertising.
5) Your choices
- Shared links. To remove a shared recipe or meal plan link, email app+privacy@feedinglittles.com with the link. Copies saved elsewhere may stay.
- Account deletion. Use the in‑app Delete Account control, or follow the steps on our account deletion page. We will delete your account and related data subject to the retention schedule below.
- Email preferences. You can unsubscribe from non‑essential emails via the link in those emails; service and transactional emails may still be sent as needed.
6) U.S. state privacy rights (CPRA/CPA/VCDPA/CTDPA/UTDPA)
Right to know/access, delete, and correct. You may request access to, deletion of, or correction of personal information we maintain about you.
Right to opt‑out of sale/share for targeted advertising. We do not sell or share personal information for cross‑context behavioral advertising.
Right to limit use of sensitive personal information. We do not use sensitive personal information for additional purposes.
How to exercise rights. Email app+privacy@feedinglittles.com or use in‑app controls (when available).
Verification & authorized agents. We verify requests via account login or email confirmation. Authorized agents must provide written authorization, and we may require you to verify your identity directly.
Appeals (where applicable). If we deny your request, you may appeal by replying to our decision email. If you remain unsatisfied, you may contact your state attorney general.
Non‑discrimination. We will not discriminate against you for exercising these rights.
Global Privacy Control (GPC). Our web pages and the App don’t use advertising or cross‑site tracking, so a GPC signal has nothing to turn off. We treat it as a request to opt out of sale and sharing, which we never do.
7) Children and family use (COPPA)
The adult account holder is the user of record. The Service is not directed to children under 13, and we do not knowingly collect personal information from children under 13 without verifiable parental consent. Minors may use the App only under the adult account holder’s supervision. If you believe we collected a child’s information in error, contact app+privacy@feedinglittles.com and we will delete it.
8) European users; international data transfers
Controller. Feeding Littles Labs, LLC is the controller of personal information processed under this Policy. Contact: app+privacy@feedinglittles.com.
Legal bases (GDPR / UK GDPR). Where European data protection law applies, we process personal information on these legal bases:
- Contract (Art. 6(1)(b)): creating and securing your account, storing and syncing your User Content, recipe imports (including AI parsing of content you choose to import), subscriptions and entitlements, and support.
- Legitimate interests (Art. 6(1)(f)): product analytics and crash reporting to keep the Service reliable and improve features, and security and abuse prevention. We use pseudonymous app‑level identifiers, do not use advertising identifiers, and do not sell personal information.
- Consent (Art. 6(1)(a)): non‑essential marketing emails. You can withdraw consent at any time via the unsubscribe link in those emails.
- Legal obligation (Art. 6(1)(c)): responding to lawful requests and meeting record‑keeping obligations.
Your rights. You may request access to, correction of, deletion of, or a portable copy of your personal information; object to or ask us to restrict processing based on legitimate interests; and withdraw consent at any time (this does not affect processing that happened before withdrawal). To exercise these rights, email app+privacy@feedinglittles.com or use the in‑app controls (account deletion is available in the App). You also have the right to lodge a complaint with your local data protection authority (in the UK, the ICO; in Switzerland, the FDPIC).
No automated decision‑making. We do not make decisions that produce legal or similarly significant effects about you based solely on automated processing. AI features only structure recipe and grocery content you choose to add.
Data location and transfers. Our systems are hosted primarily in the United States, and your information may be processed in the United States and in other countries where our service providers operate. Where European law requires safeguards for these transfers, we rely on mechanisms such as the EU‑U.S. Data Privacy Framework (including its UK Extension and the Swiss‑U.S. Data Privacy Framework) for certified providers, and/or Standard Contractual Clauses.
9) Security
We use reasonable administrative, technical, and organizational safeguards appropriate to the data we handle (e.g., encryption in transit, role‑based access controls, least‑privilege). No system is perfectly secure.
10) Data retention schedule
- Account (UID, email), basic profile: while account is active; delete within 30 days of confirmed deletion request; limited backups up to 90 days.
- User Content (recipes, collections, meal plans, grocery lists, journal notes, images): while account is active; delete within 30 days of account deletion; backups up to 90 days after deletion; images already cached on a device can last up to a year.
- Community recipes: These come from public web pages and never show who imported them. When you delete your account, we remove your account’s link to them, but the recipes may stay in Community.
- Household content: meal plans and grocery lists you add to a shared Household stay with that Household for its other members after you delete your account.
- Shared recipe and meal plan links: kept while the link is active; deleted when you ask us to remove the link or when you delete your account; server logs about 30 days.
- Import problem reports (your report, diagnostics, and any photos, PDFs or text attached): kept while your account is active and deleted when you delete your account. Slack alerts follow our Slack workspace retention settings (currently around 90 days).
- Support communications: up to 24 months, then aggregate or delete.
- Analytics and crash reports (Firebase Analytics, Crashlytics, and the copies we export for analysis): up to 14 months; aggregate thereafter.
- Server logs/Cloud Functions logs: about 30 days.
- Subscription/entitlement metadata (RevenueCat): while subscription is active and up to 7 years thereafter for tax/audit/chargeback defense (minimal data—no card numbers).
- Brevo contacts (email, first name, account ID, subscription status, and whether you’ve imported a recipe): deleted when you delete your account. If you joined our email list before creating your account, email us and we will delete that contact.
- Legal holds & safety: we may preserve specific data when required by law, to comply with lawful requests, or to establish, exercise, or defend legal claims.
11) Changes to this Policy
We may update this Policy. If changes materially affect your rights, we’ll notify you in‑app or by email.
Contact
Privacy: app+privacy@feedinglittles.com
Support: app+support@feedinglittles.com
DMCA: app+dmca@feedinglittles.com (see our DMCA Policy for mailing address and phone)