What we collect, what we don't, and why.

1. What we collect

TravelTSA collects two categories of data: anonymous usage signals and user-submitted trip inputs that you explicitly type into the site.

Anonymous usage signals

When you load the site, your browser sends us a small event that includes the page path, a coarse geographic region (city and country derived from your IP, never your exact location), and a referrer if one is present. We do not link these events to an identifier we can use to re-contact you. We use them to understand which airports and guides are useful, and to size infrastructure.

User-submitted trip inputs

When you use the flight number lookup or iCal converter, the inputs you type (flight number, airline code, uploaded duty plan PDF) are sent to our cache service so it can fetch the live data you asked for. We do not store these inputs after the request completes, with two exceptions: the iCal converter issues a feed URL that you choose to save, and that feed URL maps to the flights you uploaded; you can revoke it at any time.

2. What we do not collect

• We do not require accounts or passwords.
• We do not sell or share data with advertisers.
• We do not run third-party advertising trackers.
• We do not store your precise GPS location. The "use my location" feature, if you grant it, is resolved in your browser and used only to sort airports by distance.
• We do not store full IP addresses beyond what is needed for short-term request logs (standard web-server access logs, rotated within 30 days).

3. Cookies and local storage

TravelTSA uses localStorage (not cookies) to remember your theme preference, pinned favorite airports, and recent flight searches. These values live only in your browser, are not sent to our servers, and can be cleared by clearing site data.

4. Third parties

The live airport data comes from the airports themselves. When you visit TravelTSA, your browser does not contact those airports directly — our scraper does on a scheduled basis. The flight number lookup fetches schedule and fare context from commercial aviation APIs; those providers receive only the flight identifier you entered, not who you are.

5. Data retention

Anonymous usage events are retained for up to 90 days and then aggregated. iCal feed mappings are retained for up to 180 days after last access and then deleted. Flight lookup responses are cached for minutes, not days.

6. Contact

To request deletion of an iCal feed you created, or to ask any other privacy question, reach us through the contact page.

7. Changes to this policy

We will update the "last updated" date above when the policy changes. Material changes will also appear on the updates page.