Android app privacy
HalalFoodScan Android privacy policy
This policy applies to the Android app with package ID com.akhandaf.halalfoodscan.
Who provides the app
HalalFoodScan is provided by Marwan Akhandaf (AIPGEN). This notice explains how the Android app uses information. For privacy questions or requests, contact akhandafm17@gmail.com.
The short version
You do not need to create a HalalFoodScan account. Ingredient recognition, halal analysis and supported AI explanations run on your device. Online product searches, prayer times, purchases and complimentary Premium-code redemption use the services described below.
The Google Play Data safety disclosure, checked on 1 October 2026, says that data is encrypted in transit, users can request deletion, and no user data is shared with other companies or organisations under Google Play’s Data safety definition. Service providers still process limited data on our behalf when they are needed to deliver a feature; those providers and data flows are named in this policy.
Data the Android app may collect
| Category | Data | Declared purpose |
|---|---|---|
| Financial information | Purchase history | App functionality and analytics |
| Location | Approximate and precise location (optional) | App functionality |
| Device or other identifiers | Device or other IDs | Analytics |
| App activity | App interactions | App functionality and analytics |
| App activity | In-app search history (optional) | App functionality |
| App information and performance | Diagnostics | Analytics |
| Personal information | User IDs | App functionality and analytics |
| Personal information | Political or religious beliefs (optional) | App functionality |
Scans, photos and ingredient text
The camera is used when you choose to scan a barcode or ingredient label. Photos you select or capture, ingredient text, halal analysis and supported AI prompts are processed on your device. The app does not upload those images or AI prompts to our server or to an AI-generation service. Temporary capture files may remain in app storage until Android clears them or you clear the app’s storage.
When you look up a barcode or search for a product, the barcode or search query is sent to Open Food Facts or Open Beauty Facts. Loading product images also contacts their image service. These providers receive normal connection information, including your IP address and app request metadata. Watched products can be checked again in the background when you enable that feature.
Information stored on your device
Scan history, saved and watched products, shopping lists, allergy and dietary preferences, prayer settings and completion records, language choices, and downloaded offline catalogues are stored in the app’s local storage. They are used to provide the features you select. Optional dietary and religious preferences are provided deliberately through app settings, remain on your device and are not sent to RevenueCat as customer attributes. You can remove them in the app or by clearing app storage.
Android’s backup or device-transfer service may include app data, depending on your device and backup settings. You can manage those copies through Android or your Google account. Clearing app storage removes the current local copy; it does not necessarily remove a previous system backup.
Optional prayer location and notifications
Google Play lists approximate and precise location as optional. If you choose current-location prayer times, Android may provide the location accuracy that you allow. You can enter coordinates instead. The selected coordinates, date, calculation method and prayer settings are sent to Aladhan to retrieve prayer times. The app caches the schedule locally for reminders and its widget, and does not continuously track your location in the background.
Prayer and product-watch notifications are scheduled on your device. You can turn off notifications or revoke camera and location permissions in Android settings. Features that depend on a permission will then be limited.
Google Play purchases and RevenueCat
Optional Premium subscriptions and the lifetime purchase are processed by Google Play and managed through RevenueCat. RevenueCat receives an anonymous app user identifier, purchase tokens and transaction history, product and subscription status, purchase country or currency where supplied by the store, and app/device metadata needed to validate purchases, restore access, prevent fraud and analyse subscription performance.
We do not receive your full payment-card details. Purchase information is associated with the store account and the app’s RevenueCat identifier. There is no advertising SDK in the app, and we do not sell personal information. Android billing uses RevenueCat; it does not use Superwall.
Optional Premium access codes
If you redeem a complimentary Premium access code, the app sends the code and your anonymous RevenueCat identifier to our Cloudflare-hosted redemption service. We store a hash of the code, your anonymous identifier, the redemption time and access expiry, and processing status. This lets us validate the code, prevent repeated or excessive use, recover interrupted requests and ask RevenueCat to activate your access. We do not store the original code in the redemption database or app preferences.
Cloudflare processes connection information, including your IP address, to deliver and protect this service. The app does not send an email address, payment details, scan history, dietary preferences or AI prompts with a redemption. Redemption records remain while needed to provide access and prevent code abuse. You can request deletion using the method below; deleting an active redemption record may also remove its complimentary access. A complimentary code does not cancel an existing paid subscription.
On-device recognition and AI
The app uses Google’s ML Kit tools for barcode and text recognition and, on supported devices, Gemini Nano through Android AICore for optional AI explanations. Required recognition or AI models may be downloaded by Google services. AI availability depends on your device, language and installed system components.
Although inference happens on your device, Google’s SDKs can collect app and device identifiers, device and operating-system information, configured languages, feature-use events, model-download events, errors and performance diagnostics. This supports service operation, troubleshooting and improvement. The app does not enable an advertising-ID integration.
Service providers and security
“No data shared” in Google Play’s Data safety section uses Google’s defined term. It does not mean that no external service ever processes data: the service providers below process limited information on our behalf only when needed for the feature you choose. Network requests use HTTPS, and providers may process data in countries other than your own.
- RevenueCat manages purchase validation, entitlement status, restoration and subscription analytics.
- Google processes Play purchases, Android backup and system-service data; see also the ML Kit data disclosure.
- Open Food Facts, including the Open Facts ecosystem, receives product identifiers or searches needed for product lookups.
- Aladhan receives the prayer-time request details described above.
- Cloudflare hosts the access-code service and this website, processing ordinary connection information to deliver and protect them.
This website sets no advertising or tracking cookies and uses no third-party analytics script. A click on an App Store or Google Play button sends the destination store, page path, article slug and button location to a first-party Cloudflare endpoint. Only daily aggregate counts are retained in an EU-hosted database; the counter stores no visitor or device identifier, IP address, referrer or individual click record.
Access, retention and deletion
Local records remain until you remove them in the app or clear app storage in Android settings. Downloaded offline data can be removed in the app. System backups are managed separately as described above. Purchase and redemption records remain while needed to provide access, restore purchases, prevent fraud or code abuse, answer support requests and meet legal or accounting obligations.
To request access to or deletion of information handled by us or by RevenueCat on our behalf, use Request data deletion in the app’s settings, or email akhandafm17@gmail.com with the subject “HalalFoodScan Android privacy request.” The in-app email draft includes your anonymous RevenueCat identifier so we can locate the relevant record. You review and send the email yourself. Do not send card numbers or passwords.
Some transaction records may need to be retained for legal or accounting reasons; any applicable limitation will be explained when we respond. Google controls its store records, account data and system backups under its own policy. A deletion request or uninstalling the app does not cancel a subscription. Cancel recurring billing through Google Play subscriptions.
Depending on your location, you may have rights to access, correct, erase, restrict or object to processing, request portability, and complain to your data-protection authority.
Children
HalalFoodScan is intended for people making their own shopping and dietary choices, and is not directed at children under 13. If you believe a child has provided personal information to us, contact us so we can investigate and respond.
Website and iPhone/iPad privacy
This page covers the Android app. The separate iPhone, iPad and website privacy policy describes those services.
Changes and contact
We keep this policy and the Google Play Data safety declaration aligned when the app or its services change. Material changes will be published here with a new updated date. If you notice a discrepancy or have a privacy question, email akhandafm17@gmail.com.