Privacy Policy

Last updated: July 18, 2026

Liberator: Food Scanner ("we", "our", or "us") is a food scanner operated by Lucky Happy Fish LLC. Libby is the in-app guide/mascot. This policy explains the information Liberator handles when you use the app, create an optional account, scan a product, or send us a photo.

1. You Can Use Libby Without an Account

Libby creates a random device identifier on first use and stores it on your device. Our server uses that identifier to issue a device token, apply rate limits, retrieve your device-linked profile, and associate scans with your device. The identifier is pseudonymous, but it can become linked to an account if you sign in or create one.

Optional account methods include email and password, Sign in with Apple, and Google sign-in. Account syncing is separate from anonymous device access.

2. Information We Handle

• Device and security data — random device ID, signed device token, platform, app version, first- and last-seen timestamps, and security or abuse status.
• Optional account data — email address, password hash, display name, and the account identifiers returned by Apple or Google. We do not store your plain-text password.
• Optional profile data — age range, sex selection, diet preferences, allergies, goals, health-related preferences, and ingredients you want Libby to flag or prefer. Your optional first name and some app preferences are stored locally; selected profile fields are also synced to our server under your device ID.
• Scan and product data — scanned barcode or product identity, scan type, timestamp, duration, score, image type, processing provider, and the resulting product or ingredient analysis. This means our scan logs can identify which barcode was scanned.
• Photos and extracted text — label photos, package photos, grocery-haul photos, and text extracted on your device may be uploaded for processing. In the release configuration, ordinary scan uploads and raw OCR or prompt text are processed transiently and are not written to Libby's storage after the response. A photo you separately choose to contribute as a product image may be retained as shared catalog imagery and displayed to other Libby users.
• Local app data — recent scans, cached scan results, basket items, profile choices, notification settings, and entitlement state are stored on your device.
• Notifications and referrals — if you grant notification permission, Libby may store your Apple Push Notification service token with your device ID. If you use a referral link, we store the referral code and completion state needed to provide the referral feature.
• Purchase status — if an in-app purchase is available and completed, Apple processes payment. Libby may receive product, transaction, expiration, and entitlement information needed to verify access. We do not receive your card number.

3. Camera and Photo Processing

Barcode scanning can run through the camera without uploading a continuous camera feed; the detected barcode is sent for product lookup when an online result is needed. Photo and Grocery Haul features upload the selected image or images.

Depending on availability and scan type, uploaded photos or extracted label text may be processed locally or sent to service providers such as Google Gemini, Groq, OpenRouter and models available through it, or our self-hosted Kiro gateway. Extracted label text may also be processed through DuckDuckGo AI Chat. These providers receive the image or text, the processing prompt, and technical request data needed to return a result. Do not include faces, addresses, receipts, prescription information, or other personal material in a food photo.

Ordinary single-product and Grocery Haul uploads are not automatically added to the product-photo catalog. The original analysis image and raw OCR or prompt text are not retained by Libby after the response in the release configuration. Derived product facts, such as a detected product name or ingredient list, may improve shared catalog data. A separate product-photo contribution is retained only when you intentionally submit it through that flow.

4. How We Use Information

• Provide barcode, ingredient-label, product-photo, and grocery-haul results
• Personalize flags and explanations using your saved preferences
• Keep scan history, enforce usage limits, and restore device-linked access
• Verify purchases and maintain subscription or other entitlement state
• Prevent abuse, diagnose failures, audit scan quality, and improve product coverage
• Send notifications you have enabled and operate referral features you use

We do not sell your personal information or use it for third-party behavioral advertising.

5. Service Providers and Data Sources

Libby relies on service providers and public data sources to operate. Depending on the feature, these may include:

• Supabase for database and image storage
• Apple for Sign in with Apple, StoreKit, and push notifications
• Google for Google sign-in and Gemini processing
• Groq, OpenRouter, DuckDuckGo AI Chat, and our Kiro gateway for text or image processing when those routes are available
• Open Food Facts, USDA FoodData Central, and product-identity lookup services for product names, ingredients, nutrition, barcodes, and images
• Semantic Scholar and OpenAlex for scientific-literature discovery

We share only the information reasonably needed for the requested feature, but each provider processes information under its own terms and privacy policy. See Data Sources & Attribution for product-data licensing details.

6. Retention

• Server records: device, account, profile, subscription, referral, and scan-log records are retained while needed to provide and secure the service or until they are deleted. The current backend does not enforce a universal 90-day automatic deletion rule for scan logs.
• Analysis uploads: the release configuration does not retain ordinary single-product or Grocery Haul images, raw on-device OCR text, or raw model prompts in Libby's storage after returning the result. Processing providers may keep technical records under their own policies.
• Product-photo contributions: a photo you explicitly submit to the shared product catalog may be retained in image storage until it is removed or no longer needed. Contact support to request review or removal.
• Derived data: product-level ingredient data, model responses, hashed cache keys, and de-identified catalog improvements may be cached to avoid repeated processing and improve future results. Libby's model cache does not store the raw prompt.
• On your device: recent history is capped at 50 entries. Barcode result cache entries expire after about 30 days and are capped at 300 entries. Other local preferences remain until you clear them, delete your account data, or remove the app.

7. Your Controls and Deletion

You can clear recent history from the Profile screen; that clears the recent-history list on that device and does not by itself erase server scan logs. The in-app Delete account action requests deletion of the current device's server profile, scan-log, subscription, and device records, then clears Libby-owned local profile, history, scan cache, basket, sign-in token, and entitlement state.

That automated device deletion does not currently guarantee removal of a product photo you separately contributed to the shared catalog, a provider's own processing logs, or de-identified product-level improvements. To request review or removal of those records, or to request deletion of an optional signed-in account that may span devices, email support@nueralhook.app from the address associated with the account when possible.

You can also control camera, photo-library, and notification access in iOS Settings.

8. Security

We use signed access tokens, password hashing, request limits, and access controls intended to protect the service. No storage or transmission system is guaranteed to be completely secure.

9. Children's Privacy

Libby is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child submitted information, contact us so we can review and delete it.

10. Changes to This Policy

We may update this policy as Libby changes. We will revise the date above and provide additional notice when required.

11. Contact

Questions? Email us at support@nueralhook.app.

Lucky Happy Fish LLC
New York, NY, USA