Effective date: September 30, 2026
This Privacy Policy ("we," "us," "our") applies to the following mobile applications:
BiteBot (nutrition and meal-tracking app)
Blipcode – QR & Barcode Scanner ("Blipcode")
and any other app that links to this policy (each, an "App").
Sections below are written per feature. If a section says "If you use [App Name]," it only applies to that App. Not every clause applies to every App, since the Apps do different things.
We do not sell your personal information.
1.1 Data stored locally on your device
If you use BiteBot: meal logs, water intake, and profile data are stored locally on your device, not on our servers.
If you use Blipcode: your scan history and the codes you create are stored locally on your device, not on our servers. Blipcode has no accounts and does not require you to sign in.
We do not have access to this locally stored data unless you choose to export or share it (for example, via the share sheet).
1.2 Camera
If you use Blipcode: the App uses your camera to scan QR codes and barcodes, and to photograph text you want to turn into a code ("Snap to Create"). Camera frames and photos are processed on your device and are never sent anywhere. Photos taken for Snap to Create are not saved to your photo library.
If you use BiteBot: the App uses your camera to capture photos of meals for analysis (see 1.4 below).
1.3 Photo library
Both Apps may let you pick an existing image (for example, a photo containing a QR code, or a meal photo) using your device's photo picker. We only access the specific image you select. Blipcode can also save a code you create to your photo library, only when you tap Save.
1.4 Third-party processing (BiteBot only)
When you use BiteBot's photo-analysis feature, the photo and related text are sent to the following third-party services solely to provide that feature:
Hugging Face: analyzes meal photos
Spoonacular: provides nutrition and recipe data
These providers process this data under their own privacy policies. We do not control how long they retain it; if you want data deleted from their systems, you'll need to contact them directly.
1.5 Contacts (Blipcode only)
If you choose to fill in a code from one of your contacts, Blipcode asks for permission to read the contact you pick. If you save a scanned contact card, Blipcode opens your device's own contact editor so you can review it first. Contact details stay on your device.
1.6 Calendar (Blipcode only)
If you choose to add an event from a scanned code to your calendar, Blipcode asks for calendar access to create that single event. Calendar data stays on your device.
1.7 Advertising and analytics
If you use BiteBot: the App may display ads served by Google AdMob. If you grant App Tracking Transparency (ATT) permission on iOS, ads may be personalized based on your activity across other companies' apps and websites; if you deny it, you'll still see ads, but not personalized ones. You can change this anytime in your device's Settings.
If you use Blipcode: the current version shows no ads, does not track you, and does not use your device's advertising identifier. If a future version adds ads, this policy will be updated first.
1.8 Product and book lookups (Blipcode only)
When you scan a product barcode, Blipcode sends only the barcode number to Open Food Facts to show the product's name, photo, and details. When you scan a book's ISBN, it sends only the ISBN to Google Books to show the title, authors, and cover. No account, name, contact details, or scan history is sent with these requests. As with any internet request, these services can see your device's IP address.
1.9 Link check (Blipcode only)
If you tap "Check where this link goes" on a scanned link, Blipcode contacts that link's own website to follow its redirects and show you the final address, the same way opening the link in a browser would. Nothing is sent to us. If you tap "Check with Google Safe Browsing," your browser opens Google's Safe Browsing status page for that site's domain only, never the full link.
1.10 Diagnostics from on-device scanning (Blipcode on Android only)
On Android, Blipcode uses Google ML Kit to read barcodes and text on your device. Your camera images and scanned content stay on your device, but ML Kit sends Google anonymous diagnostics (device and app information, performance and error data, and an identifier used for these statistics) to measure and improve the service. This data is not used for advertising. On iOS, scanning uses Apple's on-device frameworks and sends nothing.
1.11 Subscriptions and purchases
If you use BiteBot: subscriptions are managed by Apple (App Store) or Google (Play Billing). We do not collect or store your payment details; the platform handles billing directly.
If you use Blipcode: the current version does not include any subscriptions or in-app purchases.
Google AdMob: advertising. BiteBot only (Blipcode shows no ads in the current version).
Apple App Tracking Transparency: ad personalization consent. BiteBot only.
Hugging Face: meal photo analysis. BiteBot only.
Spoonacular: nutrition and recipe data. BiteBot only.
Apple App Store / Google Play Billing: subscription management. BiteBot only.
Open Food Facts: product details for scanned barcodes. Blipcode only.
Google Books: book details for scanned ISBNs. Blipcode only.
Google ML Kit: on-device barcode and text reading, with anonymous diagnostics sent to Google. Blipcode on Android only.
Each provider processes data under its own privacy policy, which we encourage you to review.
You can, at any time:
Delete individual entries (meal logs, scan history, saved codes) within the App
Disable notifications in your device Settings
Deny or revoke camera, contacts, calendar, or photo-library permissions in your device Settings
Deny or revoke App Tracking Transparency in your device Settings
Manage or cancel subscriptions through your App Store or Google Play account settings (BiteBot)
Because some data is only stored locally on your device, uninstalling the App deletes that data. We cannot delete data already sent to a third-party provider (see sections 1.4, 1.8, and 1.10) on your behalf; please contact that provider directly.
Our Apps are not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, contact us and we will take appropriate steps to delete it.
We take reasonable measures to protect data processed by our Apps. However, no method of electronic storage or transmission is 100% secure, and we cannot guarantee absolute security.
We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated effective date.
For privacy questions or data-deletion requests, contact us at: support.azee@gmail.com