Effective date: April 10, 2026 · Last updated: September 9, 2026
RecallRadar ("we," "our," or "RecallRadar") is a product-recall decision-support service available through native mobile apps, a mobile web checker, and a Chrome browser extension. RecallRadar is developed and maintained by RecallRadar (contact: recallradarapp@gmail.com). Our website is recallradarapp.com.
Core recall checking does not require an account. When you use the native mobile app or mobile web checker, RecallRadar may process:
If you purchase, restore, or activate RecallRadar Pro, we may also process:
RecallRadar does not collect browsing history, keystrokes, mouse movements, precise or coarse location, contacts, advertising identifiers, health or fitness information, or full payment-card details. The native mobile app does not collect a user name or email for its core flow. We do not sell personal data, track users across other companies' apps or websites, or use this data for advertising profiles. Network services may process an IP address as technically necessary to deliver and protect requests.
The public RecallRadar website uses Google Analytics 4 to measure aggregate page visits and clicks on install, pricing, scanner, and campaign links. We disable Google Signals and advertising personalization. We do not send names, email addresses, product queries, payment details, activation tokens, or extension identifiers to analytics, and we do not join website visitors to Chrome Web Store or Stripe identities. Google may process technical request information, including an IP address, to provide the service under its own privacy terms.
RecallRadar can accept a product name, brand, UPC or barcode, and supported retailer information. Barcode scanning requests camera access only after you choose Scan barcode. Camera frames are processed on the device for real-time barcode recognition and are not uploaded, captured, or retained by RecallRadar. RecallRadar does not request microphone access or record audio.
The native app stores saved products and the latest 50 checks locally on the device. The mobile web checker stores recent checks, saved products, and a short-lived result cache in the browser. You can remove local app data by deleting saved items and history where those controls are available, clearing browser site data, or uninstalling the app. Using the operating-system share sheet sends only the share text and links you choose to the destination you select; RecallRadar does not receive your contacts.
Product queries are sent to the RecallRadar API, which searches RecallRadar's current official-source recall records. Barcode identifiers may also be sent to Open Food Facts to identify a product. Product queries are not sent to Google Analytics. Core mobile checking does not require an account, and mobile product activity is not joined to a Pro email address or Stripe subscription.
When you visit a supported retailer page (Amazon, Walmart, Target, etc.), RecallRadar reads the product title, brand, and model number visible on that page. This information is used only to form a query to an official government recall database (FDA, USDA FSIS, or CPSC). Recall matching and product checking are separate from Pro entitlement records. Product queries are sent to the applicable recall-data service and are not joined to your Pro email or Stripe subscription by RecallRadar.
The native mobile app stores saved products, the latest 50 checks, a random installation identifier, and a session identifier locally on your device using platform-provided app storage. This information is not synchronized to an account. Uninstalling the app removes its local app storage, subject to the device platform's backup and restoration behavior.
The Chrome extension stores the following data locally in your browser using chrome.storage.local:
Tracked products, recent history, and recall-result caches remain local. The activation credential is sent
only to RecallRadar's production API to verify Pro status. A legacy local premiumEnabled value
is not authoritative and cannot grant Pro. You can clear local data by removing the extension or clearing
extension storage in your browser settings.
RecallRadar obtains recall information from the following official government data sources:
RecallRadar's production API searches a canonical recall ledger populated from these official sources. Source ingestion and official-link access are governed by each agency's privacy practices. For barcode identification, the app may submit the barcode to Open Food Facts.
Apple — distributes the iOS app and may process App Store download, purchase, device, diagnostic, or account information under Apple's own privacy policy. RecallRadar does not receive your Apple ID or full payment information from the core app flow.
Stripe — Pro plan payments are processed by Stripe, Inc. RecallRadar never sees or stores your payment card details. Stripe's privacy policy is available at stripe.com/privacy.
RecallRadar API — verifies signed Pro entitlement and activation requests. It stores the normalized email and limited subscription authority records needed to provide Pro, but does not receive full card details.
Brevo — sends transactional Pro activation and restore email as RecallRadar's email service provider. Brevo receives the destination email address and message content needed for that delivery.
Saved products and the latest 50 checks remain on the native device until removed through available app controls or the app is uninstalled. Browser-stored data remains until cleared through RecallRadar or browser controls. Anonymous session credentials are short-lived and expire automatically.
Pseudonymous product-check, activity, security, and diagnostic records are retained only for as long as reasonably necessary to operate, secure, troubleshoot, measure, and improve RecallRadar, meet legal obligations, and resolve disputes. Because the core mobile flow has no account, these records are associated with random identifiers rather than a name or email.
Pro entitlement records are retained while needed to provide restoration, subscription status, security, dispute handling, and applicable legal or accounting obligations. One-time activation tokens expire after 15 minutes; the server stores only a token hash. Security and webhook audit records may be retained to prevent replay and investigate delivery or billing problems. To request deletion of eligible information, contact recallradarapp@gmail.com. Include enough information for us to locate the applicable record; never send payment-card details. Some transaction records may need to be retained by RecallRadar, Apple, or Stripe where legally required.
RecallRadar does not load or execute any remotely hosted code. All extension logic is bundled within the extension package distributed through the Chrome Web Store. API calls retrieve data (JSON) only — no scripts are fetched or executed from external sources.
RecallRadar is not directed to children under the age of 13 and does not knowingly collect any personal information from children. Optional Pro purchase and activation are intended for adults or use with the involvement of a parent or guardian.
If we make material changes to this privacy policy, we will update the effective date at the top of this page and, where appropriate, notify users through the website or applicable app-store listing. Continued use of RecallRadar after changes constitutes acceptance of the updated policy.
Questions about this policy? Email us at recallradarapp@gmail.com.