Privacy

Privacy, in plain language

This is a plain-language summary written by the developer who runs the site, not legal advice. The short version: this site is built to need as little of your data as possible, and it collects accordingly.

No cookies, no third-party trackers

The site sets no cookies, loads no third-party analytics scripts, and carries no ad pixels. There is no consent banner because there is nothing to consent to.

A first-party anonymous event beacon

To learn which pages and tools are actually useful, the site records interaction events: which tool was used, which action was taken (like copying a code snippet or clicking through to a listing), and the page path. These events carry no identifiers: no user ID, no fingerprint, no cross-site anything. They answer “was this feature used?”, not “who used it?”.

Two more things ride along, and both are worth stating plainly. If you arrived through a link that carried campaign labels in the address bar (utm_source, utm_medium, utm_campaign), those labels are recorded, so we can tell whether a post we wrote actually sent anyone here. And the hostname of the site you came from is recorded, never the full referring address, which can contain a search query. To avoid counting the same visit twice, the labels are kept for the life of the browser tab insessionStorage and discarded when you close it. That is not a cookie, it is not shared between tabs or sites, and it still contains no identifier of any kind — which is also its limit: it counts arrivals, not people.

Demo searches are transient

When you run a live demo or free tool, your query (a route, a date, a hotel name) is processed to answer that request and cached briefly, keyed by the query itself, not by you, so repeated searches don't cost extra API calls. Queries are not tied to a profile, because no profile exists.

Pasted API keys are never stored

The key checker on the pricing page forwards the key you paste once, to the live API, to see whether it authenticates. It is not stored, not logged, and not sent anywhere else.

The one thing we ask for: an email address

There is a single form on this site that asks for anything, and it asks for one field. If you give it an address, that address is stored so we can send you an email when something ships that changes what you can build: a new endpoint, a changed field, a deprecation, a price move. That is the whole purpose. It is not shared, not sold, not passed to the marketplaces, and not used to build a profile of you.

Stored with it: where you signed up from (which tool or page), when, and the campaign labels described above if your link carried any. No name, no company, no tracking pixel in the mail. Every email carries an unsubscribe link, and the unsubscribe page works without one, straight from the address. Opting out takes effect immediately and needs no reason.

Nothing on the site is withheld behind that form. The quickstart, the docs and the free tools are open to everyone, with or without an address.

Server logs

Like every website, the servers keep standard infrastructure logs (request paths, status codes, timestamps) for debugging and abuse prevention. They are ordinary operational logs, not an analytics system.

The marketplaces are separate

If you subscribe to the APIs, that happens on RapidAPI or Apify, under their accounts and their privacy policies. This site never sees your card, your marketplace account, or your usage data there.

Questions

If you want to know anything about how this site handles data, ask directly: the contact page reaches the person who wrote this page.