Privacy Policy
Last updated: November 16, 2026
Recall Relay collects as little as it can to run the service. We don't sell your information, we don't show ads, and we don't use tracking or analytics cookies.
What we collect, and why
- Your email address
- When you create a key or subscribe. We use it to send your sign-up link and sign-in links for the account page, to give each person one free key, and to contact you about your key or plan: a welcome email when your key is new, a reminder when your key has used most or all of its plan's requests, and the alert emails you set up. We also store a "normalized" form of it (lower case, without "+tags" and, for Gmail, without dots) so the same mailbox can't collect several free keys.
- Your API key
- We keep only a fingerprint (a one-way hash) of your key and its first few characters, so we can recognize it. We can't see or recover the key itself.
- Usage counts
- How many API requests each key made each day, to apply your plan's limits and show your usage.
- Alert settings
- For each alert you create: its name, the words, brands, barcodes or other filters you chose, how it's delivered (to a web address, with a signing secret, or by email to your key's address), plus a record of which recalls were sent to it and whether delivery worked.
- The weekly roundup
- If you subscribe to our weekly recall email: your email address (and its normalized form), when you confirmed it, and for each roundup we send you a fingerprint (a one-way hash) of that email's personal unsubscribe link, so the link works. We send you nothing else.
- Payment details
- If you subscribe, Stripe handles the payment. We receive and keep your Stripe customer id, subscription id and checkout id, your plan and your email. We never see or store your card number.
- IP addresses, for rate limits
- To stop abuse we count sign-ups, sign-in emails and weekly-roundup confirmation emails per network per day, keyed by IP address (for IPv6, the network's /64 block). These daily counters are deleted after 30 days. Searches and car checks on this website and in the app (per network, like the daily counters), the app's My products checks, sign-up attempts and sign-in attempts are also counted per IP address, in memory only: these counts are never saved to the database, and they're forgotten roughly an hour after your last attempt (searches much sooner), or whenever the server restarts.
- Emails we send
- A log of each email the site sends (its type, the normalized recipient address, the time and whether it was delivered), so we can stay within our daily sending limit and spot problems.
- Server logs
- Like most websites, our server records each request (the page or API address, the time, the result and your IP address). Our hosting provider keeps these logs for a limited time. The logs our own server writes hide API keys and one-time links.
- Visitor statistics
- To see how many people use the site and which pages help them, our public pages and the phone app load Cloudflare Web Analytics. It counts page views without cookies and without tracking you across sites or building a profile of you: it records the page address, the site you came from, your browser and device type, your country and how fast the page loaded. Cloudflare sees your IP address to work out your country, as any website you visit does. It isn't loaded on pages that confirm a sign-up or sign-in, show a key, take payment or unsubscribe, and those pages don't pass their own address on to the next page you open. It never reads what you type into forms.
- The phone app (My products and the barcode scanner)
- The free Recall Relay app (at recallrelay.com/app, and installed on your phone from there) needs no account and no email. Products you save to "My products" stay in your phone's browser storage, not on our server (along with the last answer for them, which the app reuses for a minute). Each time you open the app it sends the saved words or barcodes to recallrelay.com only to check them for recalls; we don't store or log them, and the answer goes back to your phone. Removing a product, or clearing the browser's data for our site, deletes it. When you scan a barcode, the camera image is read on your phone and is never sent to us or anyone else; only the barcode's numbers are searched, like typing them. The app also keeps a copy of its own design files on your phone so it can show a page when you're offline.
- Checking a car (Does my car have a recall?)
- On recallrelay.com/cars and in the app, the year, make and model you choose are sent to NHTSA (the U.S. National Highway Traffic Safety Administration) to look up that model's recalls. We keep NHTSA's answer for each model, and its lists of makes and models, for about a day so the next person gets them faster; that answer isn't linked to you, and apart from the ordinary server logs described above we don't keep who asked. If you enter a VIN, it is sent to NHTSA's VIN decoder only to identify the vehicle's year, make and model. We don't store or log your VIN, and it never appears in a web address: the results page's address shows only the year, make and model.
- Shopify stores using our Shopify app
- When a Shopify store uses the Recall Relay app for Shopify, the app's server asks us on the store's behalf and tells us the store's myshopify.com address, its plan in the app and whether it keeps the launch prices. We keep, per store, when it was first and last seen, that plan and price status (and when they changed), how many requests it made each day, and whether we blocked it and why. We don't receive the store's customers or orders from these requests, only the products being checked, which we answer and don't store. The Shopify app has its own privacy policy for what the app itself keeps.
Searching on this website, using Is my product recalled? or Does my car have a recall?, or using the phone app needs no account and no email.
How long we keep it
- Your email, key fingerprint, plan, usage counts and alerts: while your key exists. A key that is switched off is kept on record so it can't be reused by mistake.
- One-time sign-up, sign-in and roundup confirmation links: removed about a week after they're created.
- The email log: 30 days. Queued emails: 60 days after they're sent or given up.
- Per-network sign-up and email counters: 30 days.
- NHTSA's answers for the car check: deleted after two days at most. VINs: never stored.
- Shopify stores: a store's daily request counts for 90 days and its error records for 30 days; its address, first and last request, plan, price status and block record until the store asks us to delete them.
- Weekly roundup: your address until you unsubscribe (the link at the bottom of every roundup email, or your mail app's Unsubscribe button). Unsubscribing deletes it straight away, including from our record of the roundups we sent you; the unsubscribe-link fingerprints are deleted after about 13 months.
- Backups: every night we save a copy of the whole database to private storage at Railway and keep the newest 14, so anything deleted is also gone from the backups within about two weeks.
- Payment records: Stripe keeps its own records as the law requires; see Stripe's privacy policy.
Deleting your data: email support@recallrelay.com from the address on your key and ask us to delete your account. We'll delete your key, email, usage and alerts (and cancel any subscription) and confirm when it's done.
Who helps us run the service
- Railway hosts the website, the API and the database, and stores our nightly backups.
- Stripe processes payments for paid plans.
- Resend sends our emails (sign-up links and other messages about your key).
- Cloudflare runs our domain's DNS, forwards email sent to our addresses, and provides our cookieless visitor statistics (Web Analytics, described above).
They handle your information only to provide their service to us. We don't sell or share it with anyone else, unless the law requires us to.
Separately, the car check asks NHTSA, a U.S. government agency, for recalls by year, make and model, and sends a VIN you enter to NHTSA's decoder, as described above.
Cookies
We only use cookies that keep someone signed in: one for the site owner's admin page and one for the account page when you sign in (it holds your email address, signed so it can't be altered, and lasts 7 days or until you sign out). There are no tracking, advertising or analytics cookies.
Alerts you set up
When a new recall matches one of your alerts, we send the recall's public details to the address you gave us. Make sure you control that address.
Children
Recall Relay is a service for businesses and adults. It isn't directed at children under 13, and we don't knowingly collect their information.
Changes
If we change this policy, we'll update the date at the top. If a change affects how we use information we already hold, we'll email customers first.
Contact
Questions or requests about your information: support@recallrelay.com. See also our Terms of Service.