Privacy
Fare Drop tracks prices for flights you’ve already booked and alerts you when it finds a lower fare.
Fare Drop is operated by an individual sole proprietor based in Colorado, USA. For questions or privacy requests, contact the Fare Drop Team at hello@faredroptracker.com.
Fare Drop is a free invited beta. There is no charge. Joining the waitlist does not create an account.
What is stored
- The account email and name from Google sign-in, and the id Google gives that account.
- Flights you add or that a scan imports: airline, flight number, airports, date and time, fare, the price you paid, and later price checks. The account email and the price you paid are ordinary fields. They are not sealed with the confirmation encryption.
- New saves of a confirmation code and a traveler name are sealed with AES-256-GCM. A credit code, when you save one, is sealed the same way. A stored value that is not in that sealed form is still read as stored text. This page does not claim that every existing row has been sealed.
- Rebook savings stay on your account.
- If you connect Gmail, an encrypted refresh token. A scan lists mail newer than 13 months in reservations, from an airline or booking sender, or containing a booking phrase, then downloads each match in full, including the body. That body is not kept on the saved flight, and the saved flight does not keep the Gmail subject. A forwarded message, and an Outlook message if that connection is on, can keep the subject. A scan note can keep short strings from the booking.
- A waitlist entry is separate: an email, the time, and an optional note of up to 200 characters.
- An invite is an email an admin added.
- Help and feedback you type in the app. If you choose to attach a note, it can include whether mail is connected and the airline, route, and date of a flight you pick. That note is not a copy of your mail. A pattern check can remove some tokens and some confirmation or traveler text already stored for you. It does not catch every secret. AI help is off, so this text is not sent to a model. A technical failure can also save a short code, the page path, the release, and a repeat count. It does not include the fare, a confirmation, or what you typed. A fare check that finds no lower price is not one of these reports.
Who else handles it
- Google signs you in. Gmail connect is optional. It asks for read-only access so Fare Drop can look for flight confirmations for your account. You can add a flight by hand, or forward a confirmation, instead. This is separate from accepting the terms. Connecting Gmail, or starting a scan from the app, requires the current terms record. A mailbox that is already connected keeps being scanned on the schedule when that account has no recorded terms version. A missing terms record does not delete the stored mail token, and accepting the terms is not a new permission for a vendor.
- Microsoft mailbox connect is in the software. Microsoft sign-in is not configured for this beta, so that path is not in use here. The software does not revoke a Microsoft token.
- Render hosts the app. Postgres on Render stores the account and flights. This app does not state whether that database has backups.
- Resend sends price alerts and can receive a confirmation you forward. This app does not set how long Resend keeps a received message.
- A fare check sends the route and date to the price lookup. It does not send your email or confirmation code.
- When a scan uses a model, a filtered excerpt of a matching message can be sent to api.x.ai or api.openai.com. This app does not set whether those companies keep that text or use it for training.
Fare Drop does not sell this data.
Deletion
Deleting the account removes that account row. Flights, wins, credits, help and feedback, and scan rows tied to the account go with it. The forwarding address stops working. Before a fare, schedule-change, disruption, credit, promo, or wallet notification is sent, the job reads the account again. If the account is already gone, that message is not sent. A message the mail sender has already accepted is not recalled. Deleting the account does not recall text already sent to the mail sender, api.x.ai, or api.openai.com. This page does not state how long they keep it. A scan that has already fetched messages can finish that pass. The next scheduled run does not scan that mailbox or send those notifications.
Fare Drop asks Google to revoke the Gmail token. If Google does not accept that request, the account is still deleted here. You can also remove Fare Drop in your Google account permissions.
Deleting the account does not delete a waitlist entry. That entry is the email and optional trip note from a separate request. It also does not delete the monthly count of fare searches, which is a total and not a list of people. Old alert-dedupe keys can still contain an account id and a flight id. They are not a copy of the flight. This page does not claim they are anonymous, and it does not state a backup or mail-provider retention period.
Scan notes older than 13 months are removed only when a later scan runs for that account. That is not a promise that every old note is gone if no later scan runs. A flight is not deleted because of its age.
Questions about privacy, deletion, or this beta: hello@faredroptracker.com.