RecallFlag Privacy Policy

No account

RecallFlag does not require an account or login. MW Interactive does not maintain its own RecallFlag user profile for app users.

Product codes

Entered or scanned GTIN, EAN and UPC identifiers are used to search the local RecallFlag database. The audited app code does not send scan history to an MW Interactive backend, and MW Interactive does not operate a server that stores users' checked-product history.

The app can connect to supported official sources to download public alert data and update its local cache. When connecting to an external official service, that service may technically receive standard network information such as an IP address.

Camera

The Android camera permission is used only for barcode scanning through the on-device scanner. RecallFlag does not use the camera to record the user, store photos, or send camera images to an MW Interactive server.

Local data

RecallFlag stores data locally on the device, including the cached official alert database and product-code index, app settings, selected language and market, FREE daily usage counters, cached PRO entitlement, translated-text cache, source retry deadlines, update timestamps, notification opt-in and notification watermark.

Local app data can be removed by clearing app data in Android settings or uninstalling the app. Purchases are handled by Google Play and may remain available through the Google account according to Google Play rules.

Background updates and local notifications

Android WorkManager may periodically connect to the existing official sources to update the local database. Android controls when background work runs and may delay or stop it. When RecallFlag is opened, it can perform a catch-up update if the saved data is stale.

New-alert notifications are disabled by default and generated locally on the device after an update. RecallFlag requests Android's POST_NOTIFICATIONS permission only when the user enables this option. It does not use Firebase Cloud Messaging, an MW Interactive notification server or a device notification token, and it does not upload scan history for this feature.

Official sources

RecallFlag downloads public product safety and recall information from external official sources. The current code includes providers for UOKiK in Poland, NKFH in Hungary, Vaarallisettuotteet.fi / Tukes in Finland, GOV.SI in Slovenia, TTJA in Estonia and EU Safety Gate public reports. Availability and coverage can vary by source.

MW Interactive does not control the privacy practices of those external institutions. Review their websites for their own notices: UOKiK, NKFH, NKFH API, Tukes / Vaarallisettuotteet.fi, Vaarallisettuotteet.fi configuration, GOV.SI, TTJA, EU Safety Gate weekly XML.

Google Mobile Ads

The app contains Google Mobile Ads / AdMob integration. In configured FREE releases it can show banner ads, an interstitial after the defined usage threshold, and a user-initiated rewarded ad before FREE PDF export. Google User Messaging Platform is used where consent or privacy options are required. PRO does not request ads. A release explicitly built with ads disabled does not initialize or request AdMob ads.

Google and its partners may process data under their own policies, such as device or advertising identifiers, technical data and approximate information needed to provide ads, depending on configuration and user choices. MW Interactive does not control data collected by Google's SDK. See Google Privacy Policy and Google advertising policies.

Google Play Billing

RecallFlag PRO is processed through Google Play Billing as a lifetime non-consumable product. MW Interactive does not receive the user's full payment card details. The app receives purchase information needed to determine the PRO entitlement according to Google Play Billing.

ML Kit translation

RecallFlag uses Google ML Kit Translation for optional free-text descriptions only. Language models may be downloaded from Google services. Translation runs on-device, the original official text remains available, and translated text is not used for exact matching or safety decisions. Google documents technical diagnostics, installation identifiers, model-download events and language configuration processed by its ML Kit infrastructure.

PDF reports

PDF reports are generated locally on the device. After generation, the user can save, share or pass the PDF to another Android app. From the moment the user shares the file, further processing also depends on the selected app or destination service.

Analytics and telemetry

The audited app code does not include Firebase Analytics, Firebase Crashlytics, Sentry, App Center or a first-party MW Interactive telemetry system that records search history. This does not mean that Google Mobile Ads or Google Play Billing perform no technical measurement under their own policies.

Children

RecallFlag is not presented as an app directed to children. It is a utility for checking product safety and recall alerts.

Retention and deletion

MW Interactive does not maintain a central RecallFlag account or backend profile to delete. Local app data can be removed through Android clear app data or by uninstalling the app. Data processed by Google is subject to Google's policies.

Security

RecallFlag uses HTTPS when communicating with supported official sources where those sources provide HTTPS. No online system can be promised to be perfectly secure.

Changes

This policy may be updated when the app, external services or legal requirements change. The latest version will show its update date at the top of the page.

Contact

For privacy questions: support@mwinteractive.com.