Privacy Policy

RecallAlert

This policy describes exactly what RecallAlert stores. It is written from the application's database schema rather than from a template.

What is collected

DataWhyWhen
Email addressIdentifies your account, lets you sign in and recover access, and delivers optional product tips if you explicitly enable themAt sign-up; optional tips only after opt-in
Password hashAuthentication. Hashed with bcrypt; the password itself is never stored or loggedAt sign-up
Alert preferencesSelected recall categories, nationwide/ZIP/state coverage, alert level, daily brief, quiet hours, and device time-zone offsetWhen you save alert settings
Email consent and delivery stateRemembers whether optional tips are enabled and prevents a sequence step from being sent twiceWhen you opt in or out and when a sequence step is attempted
Saved product detailsChecks your watchlist against recalls. May include a name, brand, model, serial or lot number, barcode, VIN, and notes that you choose to enterWhen you save a product while signed in
Recall review stateRemembers alerts you save, review, or dismissWhen you take one of those actions
Community messagesShown to other signed-in membersWhen you post
Optional rating and coarse areaContext on a community messageOnly if you provide it
Product feedback and votesShows requested improvements and ranks the ideas members support mostWhen you post, vote, or report on the feedback board
Aggregate app analyticsDaily counts of approved feature events by platform, used to improve RecallAlert. No account, device, session, location, search, scan, product, or free-text value is includedOnly if you turn on anonymous app analytics
Device notification tokenDelivers recall alerts to your deviceOnly if you allow notifications
Subscription statusUnlocks Premium across devices and restores purchasesWhen you subscribe or restore through Apple or Google
Reports and blocks you createCommunity safety and moderationWhen you report or block

What is not collected

Recall data

Recall information comes from the U.S. Food and Drug Administration, the Consumer Product Safety Commission, and the National Highway Traffic Safety Administration. Routine recall-feed requests are made by our server and contain no information about you. Searches, barcode lookups, and vehicle lookups send the query needed to answer the request. A VIN lookup sends the VIN to the RecallAlert API and NHTSA; it is not retained as search history. A VIN saved to a signed-in watchlist remains stored until you remove it or delete the account.

Who else processes your data

Your data is not sold, rented, or shared for advertising.

Your controls

Retention

Account data is kept until you delete your account. Deletion is immediate and cascades to everything linked to the account. Moderation reports are retained while the report is open so that safety decisions remain reviewable. Password-reset token digests expire after 30 minutes and are removed after use. Anonymous daily analytics aggregates are automatically removed after 13 months.

Lifecycle email delivery records contain step names, status, attempt counts, and timestamps. They do not duplicate message bodies or addresses and are removed when the account is deleted.

Security

Traffic is served over HTTPS. Passwords are hashed with bcrypt. Sessions use short-lived signed tokens. Device tokens are never returned by the API and are never written to logs in full.

Children

RecallAlert is not directed at children under 13 and we do not knowingly collect their information. Contact us if you believe a child has created an account and we will remove it.

Contact

J&A Appworks LLC
jacobkhalil@gmail.com