Hummy Privacy Policy

1. Information You Provide

Hummy stores information on your device to provide its kitchen assistant features, including:

• Ingredients and estimated quantities.
• Kitchen appliances, household size, and available cooking time.
• Cooking habits, dietary preferences, and ingredients you choose to exclude.
• Saved meals, personal recipes, favorites, meal plans, and cooking history.

You do not need to create an account to use Hummy. Your main kitchen records are stored locally rather than synchronized to a Hummy account.

However, some choices and actions—including onboarding answers, ingredient names, meal names, and dietary preferences—are also sent to our analytics provider as described below. Local storage does not mean that all information remains exclusively on your device.

Device backups may include local app information, depending on your operating system and backup settings.

2. Photos and AI Ingredient Recognition

When you scan ingredients, the photo you take or select is sent over HTTPS to our scanning service hosted on Cloudflare. This service forwards the image to Google Cloud Vertex AI, using Gemini models, to identify visible ingredients.

The request includes the image, its file type, and the language used for ingredient results. Our scanning request does not intentionally include your Hummy installation identifier, email address, or advertising identifier.

Image recognition takes place outside your device. Anything visible in the image is available for processing by the scanning and AI services.

Our scanning service does not maintain a photo library or application database of uploaded images. Infrastructure and AI providers may retain request content or technical records under their service terms, security procedures, abuse-monitoring requirements, and account settings. We do not promise immediate deletion or zero retention across all providers.

Ingredient names and information about scanning activity may be sent to Mixpanel. Our analytics integration does not send the uploaded image itself to Mixpanel or Meta.

Please avoid uploading faces, personal documents, addresses, or other unnecessary personal information. Manual ingredient entry is available if you prefer not to upload a photo.

3. Installation Identifiers

Hummy generates an installation-level identifier and uses it with Mixpanel and RevenueCat to associate analytics and subscription information with the same app installation.

This identifier does not contain your name or email address. However, information associated with a persistent identifier is pseudonymous, not necessarily anonymous.

Service providers may also process their own device or installation identifiers, together with technical information about your device and app.

4. Product Analytics — Mixpanel

We use Mixpanel to understand how Hummy is used, identify problems, and improve its features.

Information sent to Mixpanel includes:

• App sessions, screens viewed, and buttons selected.
• Onboarding progress and answers.
• Selected appliances, dietary preferences, and excluded ingredients.
• Ingredient names, saved meal names, and interactions with recipes and meal plans.
• Photo-scanning activity, result counts, and error categories.
• Subscription selections, purchase outcomes, trial conversions, prices, currencies, and product identifiers.
• Installation identifiers, app language, device region, and technical device and app information.

Mixpanel may derive approximate location, such as city, region, or country, from your IP address. This does not require precise GPS access.

We associate analytics events and profile properties with the Hummy installation identifier. We configure our integration to send data to Mixpanel's EU ingestion endpoint.

Session replay and automatic interface capture are not enabled in the current Hummy integration. We send explicitly defined app events.

Apple's tracking permission is separate from product analytics. Declining that permission does not turn off Mixpanel analytics.

5. Advertising Measurement — Meta

We use the Meta SDK to measure the effectiveness of Hummy advertising, understand installations and conversions, and support advertising optimization.

Meta may receive app activation and usage events, onboarding completion events, trial and subscription events, product identifiers, purchase values and currencies, SDK-generated identifiers, and technical device or network information.

These transmissions are separate from RevenueCat's subscription-management function. Subscription-related events are therefore used for advertising measurement as well as product analytics and premium-access management.

Our explicit Meta event integration does not send kitchen photos, ingredient lists, dietary preferences, personal recipes, names, or email addresses.

On iOS, Hummy requests permission through Apple's App Tracking Transparency framework. That permission governs access to the advertising identifier and tracking across other companies' apps and websites.

Declining permission does not necessarily stop all communication with Meta. The current integration can continue sending app and conversion events while applying advertising-identifier and tracking-permission controls. Event transmission should not be understood as a guarantee that the information is anonymous.

Where advertising identifiers and permission are available, Meta may use information to attribute and optimize Hummy advertising. Meta also processes information under its applicable terms and privacy policy.

You can review or change Hummy's tracking permission in iOS Settings → Privacy & Security → Tracking. Declining permission does not prevent you from using Hummy.

On Android, available advertising controls depend on your device and operating system settings. Apple's ATT permission does not apply to Android.

6. Subscriptions and Purchases

Apple or Google handles payment transactions through the applicable app store. Hummy does not receive your full payment-card details.

We use RevenueCat to manage subscriptions, validate purchases, restore access, and determine premium entitlements.

RevenueCat may process installation or app-user identifiers, product and transaction identifiers, receipts, subscription status, trial information, expiration dates, and technical information needed to provide these services.

As described above, purchase-related information is also sent to Mixpanel and selected conversion events are sent to Meta.

Deleting Hummy or resetting its local data does not automatically cancel a subscription. Manage or cancel subscriptions through your app-store account settings.

7. Support and Technical Information

If you contact us, we receive your email address and the information or attachments you provide. We use them to respond, troubleshoot issues, and handle privacy requests.

Hummy and its service providers may process IP addresses, timestamps, response codes, SDK diagnostics, and error information to deliver and secure their services.

Please do not send sensitive information that is unnecessary for your request.

8. Purposes and Service Providers

We process information to:

• Provide ingredient recognition and kitchen-management features.
• Suggest meals and support recipes, favorites, and meal planning.
• Manage purchases and premium access.
• Analyze usage and improve Hummy.
• Measure and optimize advertising.
• Respond to support and privacy requests.
• Maintain reliability, prevent abuse, and meet legal obligations.

Our providers include Cloudflare, Google Cloud Vertex AI, RevenueCat, Mixpanel, Meta, Apple, Google, and the email services used for support.

Providers process information under the agreements and policies applicable to their services. Some providers, particularly app stores and advertising platforms, also process information for their own purposes under their privacy policies.

We may disclose information when required by law or when reasonably necessary to protect users, investigate abuse, or protect legal rights.

Depending on applicable law and the processing involved, legal grounds may include providing requested services, legitimate interests in operating and improving Hummy, legal obligations, and consent where required. ATT permission is not a substitute for other consent required by law.

9. Retention and Deletion

Local kitchen information remains on your device until removed through available controls or deletion of app data. Offloading an app may preserve its data, and device backups may retain copies.

Our scanning service processes photos to return ingredient results without maintaining a persistent photo collection. Provider retention depends on applicable service terms and configurations.

Analytics and advertising information may remain with the relevant providers after you delete or reset Hummy. Resetting Hummy changes its installation identifier but does not automatically delete historical Mixpanel or RevenueCat records.

Purchase records may be retained to restore entitlements, resolve disputes, prevent abuse, and satisfy accounting or legal requirements.

Support correspondence is retained as reasonably necessary to handle requests and related obligations.

Contact info@kampbu.com to request access to or deletion of information associated with you. We may need information to locate relevant records and verify your request. We will handle requests subject to applicable legal requirements and retention exceptions. Records controlled independently by an app store or another provider may require a separate request to that provider.

10. Your Choices and Rights

You can use manual ingredient entry, manage camera and photo permissions, edit local information, manage subscriptions, and change available advertising permissions through your device settings.

Revoking a permission affects future access; it does not automatically delete information already processed.

Depending on your location, you may have rights to access, correct, delete, or obtain a copy of personal information; restrict or object to processing; withdraw consent; or opt out of certain advertising-related uses. You may also have the right to complain to a data protection authority.

Some jurisdictions may classify advertising-related disclosures as “sharing,” “targeted advertising,” or a “sale,” even without a monetary payment. Applicable requests can be sent to info@kampbu.com.

11. International Processing and Security

Our providers may process information outside your country of residence. Although our Mixpanel integration uses an EU ingestion endpoint, this does not mean that every provider or every processing activity is located exclusively in the EU.

International processing is subject to applicable provider agreements and legal requirements, including transfer safeguards where required.

We use HTTPS for scanning requests and rely on operating-system protections for local app information. No transmission or storage method is completely secure. Protecting your device and backups also helps protect your information.

12. Children's Privacy

Hummy is not specifically directed to children. If you believe a child has provided personal information without consent required by applicable law, contact info@kampbu.com so we can investigate and take appropriate action.

13. Changes and Contact

We may update this policy as Hummy or its data practices change. We will revise the date above and provide additional notice or request consent when required.

For privacy questions or requests:

Hummy Support

Email: info@kampbu.com

Additional provider information:

• Cloudflare Privacy Policy
• Google Cloud Privacy Notice
• RevenueCat Privacy Policy
• Mixpanel Privacy Policy
• Meta Privacy Policy