Legal Information

Last Updated: November 1, 2026

Welcome to Tummy Scanner! These Terms of Service ("Terms") govern your use of the Tummy Scanner mobile application ("App") provided by Lucas Barnes Content ("we," "us," or "our"). By downloading, accessing, or using our App, you agree to be bound by these Terms. If you do not agree to these Terms, please do not use the App.

1. App Usage and Purpose

Tummy Scanner is a pretend game for families. You type a food name or take or choose a photo of a meal, the App plays a pretend "tummy scan" animation, and then it shows AI-generated jokes, fun food facts, simple nutrition information and a playful bite suggestion. The App does not scan, measure or examine the body in any way. It is not a medical, nutritional or diagnostic tool, and its content is for entertainment and general knowledge only. It should not be treated as professional medical or dietary advice. If you have concerns about your child's eating, growth or health, please talk to a qualified health professional.

Bite suggestions are playful prompts, not targets. Your child decides whether and how much to eat. Please don't use the App to pressure a child to finish a meal or to eat more than they want.

Parental supervision is required for children using the App. AI-generated content can sometimes be inaccurate or unexpected, so please review it with your child.

2. User Conduct

You agree not to:

• Misuse the App or its content in any way.
• Attempt to interfere with the App's operation or security.
• Reverse-engineer, decompile, disassemble, or otherwise attempt to extract source code from the App.
• Exploit APIs or other services provided by the App for unauthorized purposes.
• Upload or input inappropriate, offensive, or unlawful content (e.g., in the food name field or in photos).
• Submit photos of people or photos that show personal information. Photos should show food only.
• Use the App for any purpose other than its intended personal, non-commercial use.

3. Intellectual Property

The App and its original content (excluding user-provided food inputs but including generated jokes, facts, nutritional info snippets, design, code, branding, etc.) are the property of Tummy Scanner and are protected by copyright and other intellectual property laws. You are granted a limited, non-exclusive, non-transferable license to use the App according to these Terms.

4. Disclaimers and Limitation of Liability

THE APP IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED. WE DO NOT WARRANT THAT THE APP WILL BE UNINTERRUPTED OR ERROR-FREE.

TO THE FULLEST EXTENT PERMITTED BY LAW:

• WE SHALL NOT BE LIABLE FOR INDIRECT DAMAGES OR LOSSES ARISING FROM YOUR USE OF THE APP; AND
• YOU ASSUME FULL RESPONSIBILITY FOR YOUR USE OF THE APP AND ITS CONTENT.

5. Jurisdiction

These Terms shall be governed by the laws of Ontario, Canada. If you access the App from outside Canada, you agree that any disputes will be subject to Ontario law without regard to conflict-of-law principles.

Last Updated: November 9, 2026

This Privacy Policy describes the Tummy Scanner mobile app ("App") and this website. Lucas Barnes Content ("we," "us," or "our") operates the App. The App has no accounts or sign-in. It does not ask you to create a profile or to enter your name, email address, or other contact information to use its core features.

Who the App is for

Tummy Scanner is intended for parents and caregivers who use the App together with a child during mealtimes as a playful pretend scanner—not for children to download, sign up, or use on their own without adult supervision. A child may tap along or read results with you, but you should stay involved, review AI-generated content, and decide what is appropriate.

What we collect

We collect limited information to run the App, understand reliability, and process scans. We do not sell personal information.

Information you choose to provide

• Food names you type when you start a scan (optional if you use a photo instead).
• Food photos only when you choose to take or pick a photo for a scan.
• Written feedback when your App version includes Feedback in Settings (see below). The form does not ask for your name, email, or photos.

Information collected automatically

• Firebase Analytics: The Firebase SDK runs when the App starts. It uses installation and app-instance identifiers and logs usage such as automatic screen views, session activity, and events we configure (for example, store review prompts). Data can include app version, device model, operating system version, general engagement metrics, and approximate location such as country or city derived from a masked IP address. Analytics does not use the App's device-location permission; Google says it does not log or store IP addresses. When enabled in an App version, scan events record scan mode and coarse failure or return-time categories for scan starts, successful and failed scans, first successful scans, and returns home. They do not include food names, photos, feedback text, generated results, or raw errors. Enabling these optional events does not turn off automatic Analytics screen collection or Firebase Crashlytics.
• Firebase Crashlytics: If the App crashes or logs certain errors, Crashlytics can send crash reports that may include stack traces, error messages, app version, device model, and operating system version to help us fix problems. Crashlytics collection is not affected by whether optional scan events are enabled.
• Firebase App Check: The App can obtain device attestation tokens from Google and send them with cloud requests. Which requests require a valid token depends on the backend configuration for your App version (feedback endpoints are designed to require App Check in production; scan endpoints may not).
• App and platform metadata sent with cloud requests (for example app version and platform) so we can operate and secure the service.

Stored on your device

App preferences (such as dark mode, Custom Bites Mode, onboarding status, and when a rating prompt was last shown) are stored locally on your device. If you start but do not submit feedback, the draft is also stored on your device and is not sent to us. It is cleared when you next open Feedback after it is more than 7 days old; you can clear it sooner.

How food names and photos are processed

When you type a food name, it is encoded and sent over HTTPS to our Firebase Cloud Functions (Google Cloud, us-central1) and processed by Google's Gemini models via Vertex AI to check that it is a food and to generate the joke, fun fact, nutrition information, and bite suggestion.

The App uses the camera or photo library only when you choose to take or pick a photo. The photo is reduced to at most 1024 × 1024 pixels on your device, encoded, and sent the same way so Gemini can identify the food; the detected food name is then used as described above.

Our App code does not write photos or food names into an in-App history or a Firestore database for you to retrieve later. Inputs are used to produce your scan result. Google Cloud and Firebase may still process, log, or retain request content or technical metadata in platform or vendor systems according to their settings. We use operational logging for troubleshooting and abuse investigation, not to build advertising profiles.

When Custom Bites Mode is on, the bite count you choose stays on your device and the App does not request an AI bite suggestion.

Feedback (App versions with this Settings option)

If Settings includes "Feedback," parents and caregivers may optionally send written feedback. If you do not see that option, feedback is not part of your installed App version.

While feedback is unsent, its text stays in the App's local draft and is not sent to Firebase. If feedback submission is disabled in your App version, the draft remains on your device until you clear it or open Feedback after it is more than 7 days old.

The form does not ask for your name, email address, or photos. You choose a category and may enter free text; please avoid typing personal information about yourself or your child, because that text can be stored and read by us. Each submission is stored in our private backend (Firebase Firestore) with the text, category, app version, platform, and a unique receipt identifier. Submissions are protected with Firebase App Check in production, transactional server logic, idempotency keys, and rate limits. To reduce abuse, the server may also use derived technical identifiers (for example a hash of the App ID and client network address) within hourly windows—this is not the same as having no identifiers.

After a successful submit, the App shows the full receipt identifier (a UUID). Keep it if you want to delete that submission in the App: deletion requires the complete receipt identifier, not a partial or guessed value. You can also email tummyscanner@gmail.com with the full receipt and we can help locate and delete that feedback record. We review feedback privately to fix issues and improve the App.

Coordinated App releases are designed to run a daily job that deletes stored feedback older than 90 days. The job processes a bounded batch each day and reports when older records remain for a later run, so records are removed on a rolling basis, not necessarily the instant they reach 90 days. The job and related deletion automation must be deployed and operating in production for that schedule to apply; until then, stored feedback may remain until you delete it with your receipt or contact us. Separate rate-limit records used for abuse prevention expire after 48 hours and are removed by the same daily job. Backups, logs, and vendor systems may retain copies we do not control or immediately purge.

Service providers

We use service providers that process data on our behalf to run the App and website, including:

• Google Firebase (Analytics, Crashlytics, App Check, and Cloud Functions)
• Google Vertex AI / Gemini (food-name and photo processing)

The App may show Apple's or Google's standard store rating prompt. Ratings and reviews are handled by the App Store or Google Play, not by us.

How we use information

• Provide scan results and App functionality
• Secure backend requests and reduce abuse
• Measure usage and improve reliability (Analytics)
• Diagnose and fix crashes and errors (Crashlytics)
• Review optional feedback when that feature is enabled

Retention

On-device preferences remain until you change or remove them or uninstall the App. Scan inputs are not kept in an in-App history; retention elsewhere depends on cloud logging and vendor settings. Firebase Analytics and Crashlytics data already collected remains subject to our Firebase and Google settings and vendor retention tools (Crashlytics supports configurable retention in the Firebase console; we do not state a specific period here). Stored feedback and rate-limit records follow the feedback section above when that feature is enabled. We do not promise that every copy in logs, backups, or third-party systems is deleted on a particular timeline.

Sharing and sale

We do not sell your information. We share information only with the service providers listed above so they can process it to operate the App and website, and when required by law.

Website

This website uses Vercel Web Analytics, which is cookieless, to count page views, and Google Analytics 4 to understand how visitors use the site. The website does not use advertising trackers.

Children's privacy

The App is designed for supervised family use led by a parent or caregiver. It has no accounts and shows no third-party advertising in the App. We do not ask children for their name, email address, or other contact information in the App interface. Please photograph food only, not people. Settings options such as Rate are behind a simple parent check. When a child is present, you should supervise what is typed, photographed, and shared.

Your choices and privacy requests

You can deny camera and photo library access in device settings and still use the App by typing food names. Uninstalling the App removes on-device preferences. Uninstalling does not by itself delete information already sent to Firebase Analytics, Crashlytics, or our cloud backends; those records are handled as described in the retention section and through support requests where applicable.

To ask questions, exercise privacy rights, or request help deleting stored feedback, email tummyscanner@gmail.com. Include the full feedback receipt UUID when you have one. We aim to respond within 48 business hours.

Contact

Privacy questions about this policy: tummyscanner@gmail.com.

If you have questions about these Terms or Privacy Policy—or wish to exercise privacy rights—please contact us at tummyscanner@gmail.com. We aim to respond within 48 business hours.