Product Recall Alerts — Privacy Policy
Last updated: 29 October 2026 · Package:
com.ibrahimtxy.productrecall · Developer: bulbildir
1. What the app does
Product Recall Alerts checks US product recalls and UK food alerts on the CPSC recall web service and the FSA food alerts service at an interval you choose, and sends a notification to your phone when a recall or food alert matching your watch is published. An example watch: crib, cot or play yard.
The app never buys, reserves or holds anything. It points you at the official notice on cpsc.gov or food.gov.uk; you act there yourself.
2. Data we collect
The developer collects none. We run no server and receive nothing from your device — not your watches, not your device identifier, not your usage, not crash reports.
The one exception is advertising, and the developer does not process that either: in the free tier Google serves the ads and may use your device's advertising ID (AAID) and IP address. See §5.
3. What is stored on your device
The watches you create (source, search term, which field or which kinds of alert, a category, remedy, Canada or UK-nation filter, and for an allergy profile its allergens and the name you give it), your interval setting, the records already seen (their IDs with status and price, up to 500 per watch) so the app does not repeat itself, the recent finds (up to 20 per watch: title, second line, status or price and its previous value, link and the time found), shown under the watch as Recent finds and deleted with the watch, and the measured data usage. All of it lives in the app's private storage and is deleted when you uninstall the app.
4. Servers the app talks to
The app connects ONLY to the CPSC's open recall service and the FSA's own food alerts services. There is no account and no sign-in. For US products, what you type is sent to the CPSC as a search term, exactly as if you typed it on their website; a category check and My products read the CPSC's public list whole and match on your phone, and Recall history sends only the brand you tap. For UK food, the word you type and your allergy profiles (allergens and name) are NEVER SENT anywhere — matching happens on your phone. Your product list (name, brand, model) and the recalls you viewed are kept only on your phone. The addresses:
www.saferproducts.govwww.cpsc.govdata.food.gov.ukalerts.food.gov.ukwww.food.gov.uk
These requests are ordinary public web requests over HTTPS, the same ones your browser makes on the public CPSC recall list and FSA food alerts list. They carry no identifier of you.
5. Advertising
This section applies to version 0.1.0 and later. Earlier versions show no ads, contain no advertising library and read no advertising ID.
The free tier shows ads. They are served by Google AdMob; the developer does not choose what is shown and has no direct relationship with advertisers. The formats used are:
- Banner — at the bottom of the screen; it never covers your content.
- Rewarded — only when you tap the offer yourself; it grants temporary extra watch slots.
- Native — a card inside your watch list, always marked with an “Ad” label.
Interstitial, rewarded interstitial and app open ads are no longer used; versions of the app released before 28 October 2026 also showed these formats.
- Paid members see no ads and no ad request is made — nothing leaves the device for AdMob, and no consent form is shown.
- To select, serve and measure ads, Google may use your device's advertising ID (AAID) and IP address. The developer never reads or stores that identifier; Google is the party that processes it.
- You can reset or delete the advertising ID in Settings › Google › Ads. The app keeps working if you do.
- In the European Economic Area, Switzerland and the United Kingdom, Google's certified consent form is shown before the first ad loads. You can change your choice later from the Privacy options link inside the app.
- How Google processes this data: policies.google.com/technologies/partner-sites
There is no analytics (Firebase Analytics and the like), no crash reporting (Crashlytics and the like) and no marketing tracker. How you use the app is never reported to the developer.
6. Permissions
| Permission | Why |
|---|---|
ACCESS_NETWORK_STATE | To avoid pointless attempts while offline, and to tell mobile data from Wi-Fi. |
INTERNET | To reach the public CPSC recall list and FSA food alerts list. |
POST_NOTIFICATIONS | To tell you a recall or food alert matching your watch was published. That is the whole app. |
READ_BASIC_PHONE_STATE | So the ads library can tell Wi-Fi from mobile data. It grants no access to your phone number, IMEI or call log; the app does not declare it, the ads library adds it. |
RECEIVE_BOOT_COMPLETED | So your watches resume after the phone restarts. |
VIBRATE | To vibrate when a notification arrives. |
WAKE_LOCK | So the phone does not fall asleep in the middle of a check. The app does not ask for this itself; the background work library (Android Jetpack WorkManager) adds it. |
BILLING | So you can buy a paid membership through Google Play. The app does not declare this permission itself; the Google Play Billing library adds it. Your payment details (card, address, invoice) never reach the app and are never seen or stored by it — Google Play takes the payment. All the app learns is whether your membership is active. |
AD_ID | Ads in the free tier are served by Google AdMob, which may read the device advertising ID (AAID). The app does not declare this permission itself; the ads library adds it. Paid members make no ad request at all. You can reset or delete the ID in Settings › Google › Ads. |
7. Payment and membership
If you buy a paid membership, the payment is handled by Google Play. Your card details are never entered into the app and are never seen by the developer.
Monthly and yearly memberships renew automatically; Google Play charges your account at the start of each period. The lifetime membership is a one-off purchase and does not renew. You can cancel a subscription at any time in Google Play Store › Menu › Subscriptions; cancelling takes effect at the end of the period you have already paid for. Refunds are also handled by Google Play — the developer has no access to the payment.
The app has no server of its own. Whether your membership is active is read again every time the app asks Google Play (when you open the app and when you view the membership screen). That is why a cancellation or refund closes the membership the next time you open the app. If you changed device, Restore purchases on the membership screen brings back a purchase made with the same Google account.
8. Children
The app is not directed to children. The developer collects no data from anyone; the advertising data described in §5 is processed by Google.
9. Keeping and deleting your data
Everything the app stores stays on your device; there is no account and no server copy. Deleting a watch removes it immediately. Clearing the app’s storage, or uninstalling the app, deletes everything it has ever kept — nothing survives elsewhere, so there is no separate deletion request to make. A paid membership is held by Google Play, not by the app: it survives reinstalling and can be brought back with Restore purchases.
10. Changes
If this policy changes, the date at the top changes with it.