Skip to content

Privacy Policy

Your privacy, in plain English

Honeyroute works without an account. Here is exactly what a search involves, what the site stores, and what it passes on.

Draft for review. Written on Mon, Oct 12, 2026 from how the site’s code works today. It has not been reviewed by a lawyer, and items marked “Owner input needed” must be filled in before launch.

Effective date: Owner input needed: Effective date of the reviewed Privacy Policy and Terms.

The short version

  • There are no accounts, and you never give us your name, email or payment details to search.
  • One cookie keeps count of your daily searches. Your browser also remembers the programs you picked.
  • To find fares, the details of your search are sent to the travel data services that power it.
  • The site’s code includes no advertising or analytics tools.

What we collect and why

Your search

The airports, date, cabin and points programs you choose. They are used to run the search and show your results. Finished results are held in the server’s memory for 10 minutes so that changing filters doesn’t start a new search.

A search allowance cookie

When you first search, the site sets one cookie named pt_sid. It holds a random, signed identifier, not your name or anything about you. It is only sent with search requests, can’t be read by scripts on the page, and expires after 30 days. It exists so the site can apply the free daily search limit.

Your IP address

Every website receives the IP address of the device that visits it. Honeyroute uses it while handling a search to apply rate limits and protect the service from abuse. Those counters are kept in the server’s memory, not in a database. The site’s own log line for each search records the outcome, timing, cabin, how many data requests it made, and a short scrambled tag made from the IP address and cookie. It doesn’t record the route or dates.

The hosting service may keep its own request logs, including IP addresses:

Owner input needed: Where the site is hosted, and how long the host keeps request logs.

Saved preferences in your browser

The search form remembers which card and airline programs you selected, using your browser’s local storage. That stays on your device and isn’t sent to us except as part of a search you run.

Who else sees your search

A search can’t happen without outside data. The site’s server sends the airports (sometimes including other airports in the same city), date, cabin and the relevant programs to an award availability data service and a flight fare data service. These requests come from our server, so those services don’t receive your cookie or your IP address from us.

Owner input needed: Whether the award and fare data services can be named, and how.

Fare results returned by the fare data service are saved in our database so later searches for the same route and date can be answered faster. They describe flights and prices, not who searched. Currency exchange rates are fetched from a public source to convert taxes, which involves no information about you.

Links to airlines and card programs take you to their own sites, where their own privacy policies apply.

How long things are kept

  • The search allowance cookie: up to 30 days, or until you delete it.
  • Search results in memory: about 10 minutes. Search counters in memory: reset daily, and whenever the server restarts.
  • Programs remembered by your browser: until you clear your browser’s site data.
  • Saved fare results in the database: they are not deleted automatically today.Owner input needed: How long cached fare results are kept in the database.
  • Request logs kept by the hosting service: Owner input needed: Where the site is hosted, and how long the host keeps request logs.

Your choices

  • You can delete the cookie and the remembered programs at any time in your browser’s settings for this site.
  • If you block the cookie, searching still works; each search simply starts a new allowance session, and the limits per network still apply.
  • For any question or request about your data, contact: Owner input needed: A monitored support email address.

Who runs this site

Operator: Owner input needed: Who operates the site (a person or legal entity).

Address: Owner input needed: Operator address, if the applicable law requires one.

Changes to this policy

If the way the site handles data changes, this page will be updated and its date changed.

Questions about this page? See Contact.