Skip to content

Recalls Watch

Privacy Policy

Last updated:

This policy explains how Recalls Watch (recalls.watch), operated by Anderson Gomes Ferreira, handles personal data. It is written to meet the GDPR, UK GDPR and Brazil's LGPD.

1. What you type stays on your device

The tools on this site run in your browser. Values you enter are not sent to or stored on our servers. When the site remembers preferences or drafts it uses your browser's local storage, which you can clear at any time.

2. Consent (Google Consent Mode v2)

Until you choose, all measurement and advertising signals are denied by default (ad_storage, ad_user_data, ad_personalization, analytics_storage). Your choice is stored locally and can be changed anytime in (also in the footer). This site currently uses nothing that requires consent, so no cookie notice is shown.

3. Audience measurement

If we enable audience measurement, we will use Cloudflare Web Analytics, which measures visits in aggregate, without cookies and without identifying you.

4. Advertising

This site takes part in Google AdSense and may show Google ads. Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this and other sites. Personalized ads and these cookies are only used if you consent in ; without consent the site does not load the ad code.

You can opt out of personalized advertising in Google Ads Settings or, for other vendors, at aboutads.info. Learn more at How Google uses cookies in advertising and How Google uses information from sites that use its services.

5. Hosting and technical logs

The site is served by Cloudflare, which processes technical connection data (IP address, browser, time) to deliver pages and prevent abuse. We do not use it to identify you.

6. Your rights

You may request access, correction or deletion of personal data and withdraw consent at any time. Since we do not store what you type, clearing your browser storage removes it. Contact: contato@recalls.watch.

7. Site-specific information

"My products" is a list kept only in this browser (localStorage, key "recalls:my-products"). If you turn on the browser alert, the browser keeps two more keys there: "recalls:my-products-alerts" and "recalls:my-products-seen" (the notices already told). None of it is sent to us, there is no account, and clearing the site data of the browser erases it.

The vehicle lookup sends the make, model and year you choose straight from your browser to api.nhtsa.gov. The VIN lookup sends the VIN you type straight from your browser to vpic.nhtsa.dot.gov, the VIN decoder of NHTSA, and then asks api.nhtsa.gov for the campaigns of the decoded model. NHTSA receives your IP address like any website you visit. We do not receive or store the VIN.

The recall lookup by number sends the number you type from your browser to the agency that issued it (saferproducts.gov for CPSC, api.fda.gov for FDA, api.nhtsa.gov for NHTSA).

Product photos on CPSC notices are loaded by your browser from cpsc.gov, which therefore sees the request.

The check box and the search run in your browser over files of this site (/data/check/ and /data/recalls.json). What you type is not sent: the browser only asks for the index files it needs, named by a short number computed from each word or code and shared by many others. What you type is not written to the page address either; only the button "Copy link to this result" makes a link that carries it. The vehicle lookup keeps the make, model and year in the address, so the page can be shared.