Privacy Policy

Introduction

RecallAlert (“we,” “our,” or “us”) provides information about product recalls. This policy explains the information used to operate our app and website, personalize requested alerts, and respond to support requests.

Information We Collect

Browsing, Search, and Service Diagnostics

When you browse or search, the app sends the search text, selected filters, and requested recall identifiers to our API so we can return matching results. Requests may include a random installation identifier. Selecting a state is a recall filter; the app does not request your GPS location.

Our Cloudflare hosting service processes network information, including IP addresses and approximate location derived from the connection, and retains short-lived operational logs containing requested URLs, including search terms and filters, and technical information about request processing, timing, status, and errors. These logs help us operate, secure, and troubleshoot the service and may be linked to an installation. Cloudflare Workers logs are retained for up to seven days.

Notifications and Alert Preferences

We use installation identifiers and delivery tokens generated by Apple or Google to operate notification services. On Android, Firebase Cloud Messaging initializes when the app starts and may generate a Firebase installation identifier and delivery token before you enable notifications. The app also registers an installation with our API and saves notification settings; disabling notifications stops delivery but does not prevent this service initialization. We also store the notification categories, keywords, risk settings, saved vehicle years, makes and models, selected recall countries, and notification choices you provide, together with app version and locale. We use this information to deliver recalls matching your preferences and maintain the service. These identifiers are not an account name and are not used to create an advertising profile.

When you use My Cars in supported iOS and Android app versions, vehicle details are saved on your device and included in your notification preferences sent to RecallAlert. We match these details to recall records; we do not ask for or store a VIN for this feature. Removing a saved car updates your server preferences when the app next connects successfully.

Voluntary Support Requests

If you send feedback in the app, we collect the message, topic, and optional email address you submit. The website contact form also offers an optional name field. You can leave the optional contact fields blank. In-app feedback is stored with an installation identifier so we can prevent duplicate submissions and investigate the request. Please do not include sensitive personal or medical information in feedback.

Data Stored on Your Device

Saved recall bookmarks, cached recall details, and the recent-search list are stored locally. Saved vehicle details, browsing settings, and notification settings are also saved locally for your convenience. Selected browsing filters are sent with API requests, and notification preferences are stored by our service as described above. Opening a saved recall may contact our API to refresh its details.

Your Notification Choices

Push notifications are optional. You can change your category and risk preferences or turn notifications off in the app. You can also change the system permission in your device settings. Turning notifications off disables future delivery; installation and operational records may remain subject to the retention practices below.

Third-Party Services

Cloudflare hosts our website and API, serves recall images, stores notification preferences and in-app feedback, and processes service diagnostics.

During the app update transition, older app releases continue to use Supabase for recall feeds, images, and notification preferences while updated releases move to Cloudflare.

Apple Push Notification Service and Firebase Cloud Messaging deliver the notifications you enable on iOS and Android. Firebase also processes installation identifiers, app version, and technical information about the app, operating system, and device to provide and maintain its service. This app does not include Firebase Analytics or Firebase Crashlytics.

Resend handles delivery of voluntary website contact-form messages to our support team. In-app feedback is stored by our service; forwarding that feedback by email may be delayed or unavailable.

Optional in-app tips are processed through Apple's App Store on iOS and Google Play Billing on Android, under the respective store's terms and privacy practices. The app receives purchase status and transaction identifiers or purchase tokens to complete and restore applicable transactions. RecallAlert does not receive your payment card details or maintain a separate server-side tip purchase history. All recall features are available without tipping.

Links to official recall notices, reporting services, and other external websites open those services, whose own privacy practices apply.

Retention and Your Choices

Notification tokens and preferences are retained to provide the alerts you select. We may retain limited installation, delivery, and feedback records for service reliability, abuse prevention, support, and legal obligations, and delete or de-identify them when they are no longer reasonably needed. Cloudflare Workers operational logs are retained for up to seven days.

Request Deletion of RecallAlert Data

You can request deletion of your RecallAlert data without creating an account. Send an email to [email protected] with the subject “RecallAlert data deletion request.” Include the email address used for feedback, if any, an approximate submission date, and whether you use iOS or Android. Do not send passwords or payment details.

Support may ask for additional information to locate and verify the relevant installation or support request. Once we can verify and locate your records, we can delete the associated feedback message and email address, notification token, notification preferences, watchlist keywords, saved vehicle details, and installation record. We cannot reliably locate a particular installation from your name alone because RecallAlert has no user accounts.

We may retain limited records where needed for security, abuse prevention, unresolved support issues, or legal obligations. If an exception applies to your request, we will explain which records must be kept and the applicable retention period in our response. Cloudflare Workers operational logs expire within seven days. Firebase installation data and App Store or Google Play transaction records are subject to those providers' retention and deletion practices.

Deletion requests are handled by support. Turning notifications off or uninstalling the app does not automatically delete server records. To remove locally saved recalls and preferences on Android, clear the app's storage in device settings or uninstall it. You can also use the email address above to request access to your support or installation data.

Changes to This Privacy Policy

We may update this policy as our services change. The current version and its update date will be available on this page.

Safety on your terms

RecallAlert for iOS and Android

Search and save recalls without creating an account.