Effective date: November 1, 2026
This Privacy Policy ("we," "us," "our") applies to the following mobile applications:
* BiteBot (nutrition and meal-tracking app)
* Blipcode – QR & Barcode Scanner ("Blipcode")
* Bublingo (Translator app)
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 for money. Where an App shows ads, the advertising partners described in section 1.7 may use certain data as described there, and you can limit this through the choices in section 3.
1. Data We Collect
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.
* If you use Bublingo: your translation history, saved translations, conversations and settings are stored locally on your device, not on our servers. If you choose to keep the photos you scan, they are stored on your device too. Bublingo 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).
* If you use Bublingo: the App uses your camera to capture text you want to translate, such as signs, menus and pages. Camera frames and photos are processed on your device. Only the text recognized in them is sent for translation (see 1.13 below).
1.3 Photo library
The Apps may let you pick an existing image (for example, a photo containing a QR code, a meal photo, or a photo containing text to translate) 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: Blipcode shows ads served by Google AdMob to people who have not bought Premium. To show and measure ads, AdMob may collect your device's advertising identifier (if you allow it), device and app information, IP address and approximate location, how you interact with ads, and diagnostics. On iOS, ads are personalized and your advertising identifier is used only if you tap Allow in Apple's App Tracking Transparency prompt; if you tap "Ask App Not to Track" you still see ads, but not personalized ones. Where the law requires it (for example the EEA, the UK and some US states), Google's consent message asks for your choice before any ad is requested, and you can change that choice later in Settings > Personalized Ads Privacy. On Android you can reset or delete your advertising ID in your device's Settings. Premium removes ads.
* Settings fetched from Firebase (Blipcode): Blipcode uses Firebase Remote Config (Google) to read app settings, such as which offers to show. Firebase creates an installation identifier for the app and, like any internet request, receives your IP address and basic device and app information. We do not use it to identify you, and it is not used for advertising. Blipcode does not use Firebase Analytics or any other analytics service.
* If you use Bublingo: the current version shows no ads, has no analytics service of its own, does not track you, and does not use your device's advertising identifier. The only analytics-type data is the anonymous diagnostics that Google ML Kit sends to Google (see 1.10). If a future version adds ads or analytics, 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 and opening scanned content (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.
Some actions open another app or website and hand it the scanned content, but only when you tap them. "Search the web" opens Google Search with the scanned text or code number. Address results open your device's maps app (Apple Maps on iPhone). Links open in your browser. Those services receive that content and handle it under their own privacy policies.
1.10 Diagnostics and models from on-device processing (Blipcode on Android; Bublingo on Android and iOS)
On Android, Blipcode uses Google ML Kit to read barcodes and text on your device and to find details such as addresses, dates and phone numbers in scanned text. 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. ML Kit also downloads language and recognition models from Google when they are first needed. On iOS, Blipcode's scanning uses Apple's on-device frameworks and sends nothing.
Bublingo uses Google ML Kit on both Android and iOS to read text from photos, to detect the language of scanned text and, as a backup when the online translation service is unavailable, to translate on your device. The same anonymous diagnostics may be sent to Google on both platforms, and ML Kit downloads language models from Google when they are first needed.
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: Blipcode Premium is an optional auto-renewing subscription (weekly, monthly or every 3 months) that removes ads. Purchases are handled by Apple (App Store) or Google (Play Billing); we do not collect or store your payment details. To know that Premium is active, Blipcode keeps only the date your subscription runs to, on your device.
* If you use Bublingo: the current version does not include any subscriptions or in-app purchases.
1.12 Microphone and speech recognition (Bublingo only)
When you dictate or use Talk, Bublingo asks for microphone and speech-recognition permission and uses your device's speech recognition to turn your voice into text. Depending on your device and language, your audio may be sent to Apple (iOS) or Google (Android) to be transcribed, under their own privacy policies. We do not receive or store your audio. The resulting text is translated as described in 1.13. Bublingo can read translations aloud using your device's built-in voices.
1.13 Translation and dictionary lookups (Bublingo only)
To translate, Bublingo sends the text you type, paste, speak or scan, together with the languages you selected, to Google's online translation service and shows you the result. No account, name or contact details are sent with these requests. As with any internet request, the service can see your device's IP address. If the online service is unavailable, Bublingo may translate on your device instead (see 1.10). When you look up an English word, Bublingo sends that word to Datamuse (api.datamuse.com) to show look-up results and suggestions. Please do not enter sensitive information that you would not want processed by these services.
1.14 Wi-Fi networks (Blipcode only)
If you scan a Wi-Fi code and tap Connect, Blipcode passes the network name and password from the code to your device's own Wi-Fi system so it can join the network (on iPhone this uses Apple's Hotspot Configuration feature). Blipcode does not send them to us or to anyone else, and it does not read your other Wi-Fi networks. A Wi-Fi code you scan or create is stored on your device in your history like any other code.
2. Third Parties We Use
* Google AdMob: advertising (BiteBot and Blipcode).
* Google User Messaging Platform: the consent message shown where the law requires it (BiteBot and Blipcode).
* Apple App Tracking Transparency: ad personalization consent on iOS (BiteBot and Blipcode).
* Firebase Remote Config (Google): app settings (Blipcode).
* Hugging Face: meal photo analysis. BiteBot only.
* Spoonacular: nutrition and recipe data. BiteBot only.
* Apple App Store / Google Play Billing: subscription management (BiteBot and Blipcode).
* Open Food Facts: product details for scanned barcodes. Blipcode only.
* Google Books: book details for scanned ISBNs. Blipcode only.
* Google Safe Browsing, Google Search and Apple Maps: opened only when you tap the matching action on a scan result (Blipcode only).
* Google ML Kit: on-device barcode and text reading, detection of addresses, dates and phone numbers (Android), language detection and backup translation, with anonymous diagnostics sent to Google. Blipcode on Android; Bublingo on Android and iOS.
* Google online translation service: translation of text you type, speak or scan. Bublingo only.
* Datamuse: English word look-ups and suggestions. Bublingo only.
* Apple / Google speech recognition: turning your voice into text. Bublingo only.
Each provider processes data under its own privacy policy, which we encourage you to review.
3. Your Choices and Controls
You can, at any time:
* Delete individual entries (meal logs, scan history, saved codes, saved translations) within the App
* Disable notifications in your device Settings
* Deny or revoke camera, microphone, speech-recognition, contacts, calendar, or photo-library permissions in your device Settings
* Deny or revoke App Tracking Transparency in your device Settings
* Change your ad consent choice in Blipcode's Settings (where it is offered), and reset or delete your advertising ID in your device Settings
* Manage or cancel subscriptions through your App Store or Google Play account settings (BiteBot and Blipcode)
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.7, 1.8, 1.9, 1.10, 1.12, and 1.13) on your behalf; please contact that provider directly.
4. Your Privacy Rights
Depending on where you live (for example the EEA, the UK, California and other US states), you may have the right to know what personal information is processed about you, to have it deleted or corrected, to object to or opt out of personalized advertising, and to withdraw consent you have given. We do not run accounts or servers that hold your scans, codes, history or purchases; that data stays on your device, where you can view and delete it yourself (section 3). Data processed by advertising and other third-party providers is held by them, and you can use their tools and the consent and tracking choices in section 3 to limit it. If you want to make a request, or have a question about your data, contact us at the address in section 8 and we will respond within the time the law requires. We will not treat you differently for using these rights.
Where the law requires your consent for ads, we rely on your choice in Google's consent message and Apple's tracking prompt, and you can withdraw it at any time as described in section 3.
5. Children's Privacy
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.
6. Data Security
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.
7. Changes to This Policy
We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated effective date.
8. Contact Us
For privacy questions, rights requests or data-deletion requests, contact us at: support.azee@gmail.com