Food Companion
Privacy Policy

Draft — reviewed against implementation October 12, 2026

Punky Food Companion is operated by Punky Bee, LLC.

Draft — not approved legal text. AI-provider retention and use, operational logs, backups, manual request handling and production advertising/payment arrangements remain to be verified.

Information collected and stored

• Account details. Lovable Cloud authentication handles your email, password credentials and sign-in session. Punky stores a display name, account identifier, waiver acceptance and account timestamps in its database, not your plaintext password.
• Dietary profile. Diets and allergens you select or type are stored in Lovable Cloud and used to analyze food. These can reveal sensitive health-related information.
• Scans and favorites. Product names, barcodes, ingredients, source information, extracted or inferred food information, restrictions reflected in results, warnings, explanations, analysis and timestamps are stored in scan history. Favorites store copies of scan results. Daily usage, scan reservations and reward counts are also stored.
• Submitted photos. Photos are processed and transmitted for analysis. Punky Bee does not save submitted photo files in its database or file storage. Extracted text, inferred ingredients and analysis can remain in scan history. Product-image links from food databases are different from your submitted photo files.
• Tester feedback. Lovable Cloud stores your rating, selected topics, comment, app version, scan count, submission time and, when signed in, account identifier. Feedback is used for product improvement. Please avoid personal or sensitive information in comments.

AI analysis — photos and restrictions

Submitted photos are sent through the Lovable AI service to Google's Gemini model for image recognition and text extraction. When AI interpretation or alternative suggestions are used, requests can also include your dietary/allergy restrictions, product and ingredient information, and detected conflicts. Not every scan needs AI. The analysis requests do not deliberately add your account email, but a photo or text you submit may itself contain personal information. Provider retention, logging and any secondary use or training terms still need verification; this draft makes no promise about those providers' use of the data.

Food-database requests are different

Open Food Facts, USDA FoodData Central and FatSecret receive product lookup information such as a barcode, product name, brand or food search term. These lookups do not deliberately send your account email, saved dietary/allergy profile or submitted photo file. Food names or search text can come from a photo analysis. The providers can receive normal request metadata; their retention practices are not established by Punky's code. Food lookups and USDA/FSIS recall requests may pass through Punky's proxy hosted on Fly.io. Lovable Cloud hosts account data and backend processing. Hosting and proxy logging/retention also need verification.

Authorized AI-assistant connection

If you authorize a compatible AI assistant to connect to Punky, it can read your dietary and allergy profile, retrieve recent scan names, times, verdicts, flagged allergens and explanations, and check supplied ingredients against your restrictions. This is separate from the scan AI service. The tools require authentication and are scoped to your account. Information returned to the assistant is handled under that assistant provider's terms and may remain in its conversation history; deleting Punky's account does not delete those conversations.

Stripe and payment status

Stripe checkout and subscription-management code is installed, but checkout payments are unconfigured in the reviewed website build. Production billing is not represented as active. When configured and used, Stripe receives payment information directly, and billing requests can include your account email and account identifier. Punky stores Stripe customer, subscription, price and product identifiers, status, billing periods, cancellation settings, environment and tier in Lovable Cloud, not full card details. Stripe-held customer and financial records are not removed by Punky's account deletion.

AdMob — current testing and planned production

The Android app includes the Google AdMob SDK and Google's official test rewarded-ad IDs. There are no live ad IDs configured. The website does not display native AdMob ads; a separate development-only simulated ad screen exists for testing. The temporary backend test-reward allowance is off. Production ads are planned, not enabled.

When an Android test ad is requested, Google receives an account identifier and an ad transaction identifier for reward verification, alongside information collected by its SDK. The exact SDK/device-data behavior and provider retention remain to be verified, even for test ads. Punky stores reward transaction IDs, provider, date, scans granted and account identifier; signed Google confirmations additionally store ad unit, Google transaction ID, reward amount, verification key ID and timestamps. These prevent duplicate rewards and enforce usage limits. Consent prompts are not implemented. There is no iPhone project or implemented iPhone ad support. Any production advertising requires a separate privacy/consent review and configuration.

Access, logs and retention

Account-facing database access is restricted to the signed-in user's records. Authorized assistant tools and privileged backend operations have the access needed for their purpose. The current code does not set a general automatic expiry for account data, scan history, feedback, usage or reward records. Daily counter resets do not delete historical usage rows. Shared product-identity cache entries are rechecked for freshness, not automatically erased on account deletion.

Operational error and performance logging is implemented, and browser errors can be reported to Lovable. Development ad-event logging also exists. The content, access, retention and deletion of hosting/provider logs and backups still need verification. Do not assume that not saving submitted photo files means providers, logs or backups retain no copies.

Deleting your account and data

Use Profile → Delete Account in the app, or our deletion-request page to email a request. Manual requests require identity verification. Never email your password.

Account deletion removes your sign-in account, profile and waiver flag, dietary and allergy selections, scan history and stored analysis, favorites, local subscription records, scan usage and reservations, feedback-prompt state, ad reward grants, and Google AdMob server-confirmation records associated with your account.

Tester feedback is retained for product research with its account identifier set to empty. Ratings, selected feedback topics, comments, app version, scan count and submission time remain. This is not guaranteed to make a comment anonymous: personal information you wrote in it may remain. Tell us in your deletion request if a comment contains personal information so we can review it. Shared product-identity cache entries remain because they contain product facts, not your account identifier or personal dietary verdict.

Punky attempts to cancel an active Stripe subscription before removing local records. Cancellation errors are logged and do not stop account deletion, so cancellation is not guaranteed. Stripe customer, payment and financial records are not deleted by this process. If you have an active subscription, confirm cancellation or contact support to avoid further charges.

Deletion is performed in successive steps, not one all-or-nothing operation. If a step fails, some records may already be removed; you can retry or contact privacy@punkybee.com. The process does not erase provider-held copies, assistant conversations, operational logs or backups. Their retention and deletion arrangements still need verification; we cannot promise complete deletion from those systems or a verified retention period yet.

Age and launch review

No age-verification step is implemented. Intended age eligibility and any child-specific requirements remain subject to owner and legal review before launch.

Contact Punky Bee, LLC

Privacy and deletion requests: privacy@punkybee.com. General support: support@punkybee.com.