Privacy Policy

Welcome to Bunbee ("we," "our," or "us"). This policy describes the personal information involved when you use our website and app, who receives it, and the choices available to you.

This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you visit our website or use the Bunbee application. Some features require an account; you can choose whether to provide additional information for features involving a child profile or pregnancy stage.

We collect information in three ways: information you provide directly, information collected automatically through your use of the Service, and information from third parties.

INFORMATION YOU PROVIDE

• Account and authentication data: name, email address, a hashed password, a database user ID and session records. Bunbee manages its own authentication and uses a secure HTTP only session cookie containing a signed token.
• Caregiver and onboarding data: caregiver role, guidance preferences, areas of interest, optional location and life stage, which may include pregnancy stage.
• Child profile and allergen tracker data: name or nickname, date of birth, feeding and texture stages, dietary preferences, allergens, sensitivities, medical considerations, allergen introduction status and any reaction or professional guidance notes you enter. We treat the child health information as special category data; Section 5 explains its separate consent.
• Scan, search and saved content: scanned barcodes and images, product search terms recorded in scan history, saved products and recipes, and meal plans or ideas.
• Bee and support content: messages, optional images attached to chats, conversation summaries, and the name, email address and message submitted through the contact form.
• Subscription data: Stripe processes web payments; we store Stripe customer and subscription identifiers and subscription status. For iOS purchases, RevenueCat processes subscription lifecycle and entitlement information. We associate it with the account using a custom RevenueCat user ID in the form bunbee_user_<database user ID>. Payment card details are handled by the payment provider, not stored in our account database.

INFORMATION COLLECTED AUTOMATICALLY

• Device and operational data: browser or device information needed to deliver the service, and request, error and security diagnostics. Backend operational logs can contain account user IDs and other identifiers associated with a request.
• Feature records: scan history, saved items and chat usage counts support app features and service operations. The separate published app visitor tracker is described in Section 7A.
• Cookies and Similar Technologies: see Section 7A (Cookies) below.

INFORMATION FROM THIRD PARTIES

• Product data services: external product lookup sources, including a separate Supabase product data service, help us retrieve product information. This Supabase service is not our account database or authentication provider.
• Subscription providers: Stripe reports web payment and subscription outcomes; RevenueCat reports iOS purchases and entitlements associated with the custom user ID.

Under UK GDPR Article 6 (and Article 9 for special category data such as allergy information), we process your personal data on the following legal bases:

You can withdraw a consent or request deletion through the available account controls or by contacting us. Withdrawal does not affect processing that took place before it. Disabling a general preference does not itself grant or renew consent for pregnancy or child health data.

We send information to AI services to provide specific features, as described in Section 7. This policy does not make an unverified promise about every provider's model training practices.

Account and app data is stored in Floot managed Postgres. Bunbee manages authentication using hashed passwords and signed session tokens delivered in secure HTTP only cookies. Cloudinary stores media used by the app. The external Supabase product lookup service is separate from account storage and authentication.

We use security controls to protect data, but no transmission or storage system can be guaranteed completely secure. Contact us if you have a question about how your information is handled.

You can control how we use your data via Settings → Privacy & Data:

• PERSONALISATION
  When enabled, Bee may use relevant saved information to tailor guidance. This setting does not replace the separate affirmative consent required before pregnancy or child health information can be processed for that purpose.
• CHAT HISTORY
  When on, your conversations with Bee are saved so you can refer back to them and get more relevant follow-up answers.
  Turning this off deletes saved conversation history through the consent settings flow.
• CHILD PROFILES
  This setting controls whether child profiles are saved. Separately, we ask for affirmative, versioned consent to process the full child health information set, including allergens, feeding and texture stages, sensitivities and medical considerations.

We also request distinct, affirmative and versioned consent when you provide pregnancy stage. The server records the time and version of each pregnancy or child health consent. A child profile created before the current consent process remains stored and available for export or deletion, but cannot be used for child dependent features until you renew consent. You can continue using generic features without giving that consent. You can withdraw consent or delete a child profile separately; historical chats may still contain information you previously entered unless you also delete chat history.

When you create an account, we record the date you accepted these Terms and our Privacy Policy. If we update either document significantly, we will notify you.

Under UK GDPR (Articles 15–22), you have the right to access, correct, export, delete, restrict, object to, and port your personal data. You also have the right to withdraw consent for processing that relies on consent (without affecting the lawfulness of processing before withdrawal) and the right to lodge a complaint with a supervisory authority (see Section 10).

ACCESS & EXPORT

Settings → Privacy & Data → Export JSON provides account details, consent settings, onboarding preferences, child profiles, chat conversations and messages, and your user summary. This export does not currently include scan history, saved Library items or meal plans. Contact us to request access to other personal information.

CORRECTION

Update your personal information directly in Settings.

DELETION

Settings → Privacy & Data → Delete Account.

When you delete your account, we erase from our active systems:

• Your account, login credentials, and contact details
• Your onboarding preferences and saved settings
• All child profiles and their associated data (DOB, allergies, preferences)
• Your scan history and saved Library items
• Your chat conversations with Bee
• Your meal guides

The in app account deletion process removes the account and associated app records from active systems. Some third party records, operational logs, transaction records or backups may remain where retention or legal requirements apply. Contact us about those records or an erasure request.

WHAT WE MAY RETAIN (and why)

• Payment and tax records: Payment providers and records subject to accounting obligations may follow separate retention requirements.
• Backups and operational logs: Copies and diagnostics may persist for a period after deletion.
• Legal requirements: Relevant records may be retained when a legal obligation or claim requires it.

CHILD PROFILE DELETION (without deleting your account)

Settings → Child Profiles → [profile] → Delete. This permanently removes the profile and associated guidance context. Note that historical chat conversations that referenced this child will retain those references unless you also delete your chat history.

OTHER RIGHTS

You can also:

• Restrict processing: ask us to stop using your data for particular purposes while keeping it stored.
• Object to processing: where we rely on legitimate interests, including some service operations.
• Data portability: request applicable data in a structured, commonly used format. The in app JSON export covers the categories listed above, not every record.

To exercise any of these rights, use Settings or contact hello@bunbee.app. We will respond within one month.

We work with the following providers to deliver the Service. We share only the data necessary for each provider to perform its function.

INFRASTRUCTURE

• Floot managed Postgres stores account and app records. Bunbee manages account authentication; Supabase is not used for account authentication or account data storage.
• Cloudinary stores app media, including uploaded images.
• Resend delivers account and other emails, including the welcome email, which currently contains upgrade promotion content. It receives recipient details and email content.

AI SERVICES AND STAFF CONTENT CREATION

• Anthropic supports Bee responses, food guidance, meal generation and conversation summaries. Depending on the feature, it receives chat text, optional chat images, relevant caregiver context, saved food or recipe information, and child information only when the required current consent allows that use.
• Google Cloud Vertex AI and Gemini support semantic embeddings and retrieval, follow up suggestion generation, and barcode, package, ingredient and nutrition label image analysis.
• Public evidence search services may receive factual search terms derived from a question when external evidence lookup is needed.
• OpenAI and Ideogram receive prompts staff submit for Content Studio image creation. Runway receives staff video prompts and, when provided, reference images for Content Studio video creation. These staff content tools are separate from Bee.

PRODUCT DATA PROVIDERS

• Open Food Facts, the external Supabase product data service and other product sources help retrieve ingredient and nutrition information. Product queries can be sent to these external providers; the Supabase service does not hold Bunbee account records.
• Nominatim and OpenStreetMap provide optional reverse geocoding. If you choose to use device location, coordinates are rounded to two decimal places before transmission or storage; the service returns locality and country information.

PAYMENT PROCESSING

• Stripe processes web payments and supplies customer, subscription and payment status information.
• RevenueCat manages iOS purchase and entitlement information. Bunbee links it to the account using bunbee_user_<database user ID>.

Bunbee uses an essential session cookie to keep you signed in. App storage may also support operational features and saved preferences. We do not offer an analytics cookie preference control in Settings.

ESSENTIAL COOKIES

The signed authentication session cookie is used to maintain your account session. Service operations also create the records and diagnostics described above:

• Authentication session records and the session cookie
• Operational request, error and security logs, which may include user IDs

VISITOR ANALYTICS

Bunbee does not install a separate external analytics SDK. Floot visitor tracking is disabled for this published version. Previously published builds may have collected page paths, referrers, browser user agents and languages, country inferred from time zone, and a random session ID. Those visitor events did not include the URL query string or IP address. Previous visitor records may remain with Floot and its analytics processor Tinybird for Floot's documented 12 month retention period.

Disabling visitor tracking does not stop operational request, error and security logs, scan history, or other feature records from being collected for service operation and app features.

Some providers may process information outside the UK and EEA. The destination can depend on the provider and the feature:

• Anthropic, Google, Stripe, RevenueCat, Resend and OpenAI may process relevant information internationally.
• Cloudinary, Floot and other service providers may also process information in other regions.

If you have questions about where a particular provider processes your information or the arrangements for an international transfer, contact hello@bunbee.app. We do not describe any provider region or transfer agreement here as verified for every processing activity.

Bunbee is intended for adults, including parents, guardians and caregivers.

CHILD PROFILES YOU CREATE

Adults can create profiles for children in their care. A child's name and date of birth are personal data. We treat the full child health information set — including allergens, feeding and texture stages, dietary preferences, sensitivities, medical considerations and allergen tracker notes — as special category data under UK GDPR Article 9, not only allergy or medical information.

Processing child health information for child dependent features requires a separate, affirmative and versioned consent action. You can use generic features without giving that consent, and can withdraw consent or delete a profile (see Sections 5 and 6).

DIRECT USE BY CHILDREN

The Service is not designed for direct use by children under 18. We do not knowingly collect data directly from children. If you become aware that a child has created an account, please contact us at hello@bunbee.app and we will delete it.

We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last Updated" date at the top of this policy.

You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page.

CONTROLLER IDENTITY

The data controller for personal data processed through the Service is:

Emaloua Limited
128 City Road, London, EC1V 2NX
Company number: 17118671
Registered in England and Wales

CONTACT

For questions about this Privacy Policy or to exercise any of your rights, contact:

• General privacy queries: hello@bunbee.app
• Billing-specific privacy queries: billing@bunbee.app

We do not currently appoint a Data Protection Officer because we are not required to under UK GDPR Article 37. If this changes, we will update this Policy.

RIGHT TO COMPLAIN

If you are unhappy with how we have handled your personal data, you have the right to lodge a complaint with the UK Information Commissioner's Office (ICO):

• Web: ico.org.uk
• Phone: 0303 123 1113
• Post: Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF