Privacy Policy

Goliath runs travel searches for your assistant without an account. It stores a session, usage counters and shared caches of public travel prices. It doesn’t keep your trip plans, and the search details it does keep aren’t linked to you.

Last updated 18 November 2026

What Goliath is

Goliath is a free tool your AI assistant connects to. Your assistant sends it a travel search; Goliath asks travel suppliers and returns what they say. It has no accounts: you never give it a name, an email address or a password.

The operator who runs Goliath decides how the data on this page is used. Their details are under Contact.

What is stored

WhatWhyKept for
A random workspace ID, and a hash of the session token that an HttpOnly cookie keeps in the browser where you approve a connectionSo the assistants you connect from that browser share one daily allowanceThe session lasts 30 days. A workspace with no session left is deleted after 90 days.
OAuth records: the name and callback address your assistant registered, and the authorization grant and tokens issued to itTo let that assistant call Goliath on your behalfAccess tokens last one hour, refresh tokens 30 days. A connection ends 30 days after you approve it. An assistant’s registration is kept for 90 days, renewed while it’s in use.
Counters: how many search calls a workspace made today, in total and per supplierTo enforce free daily limits fairly35 days
A keyed hash of your network address (for IPv6, its /64 block) and the date, with a count of new workspaces, new assistant registrations, searches run from the search box on Goliath’s home page, or wrong tokens entered on the operator’s sign-in pageTo stop one network from creating unlimited free workspaces. Goliath’s database keeps only the hash, made with a secret key so it can’t be reversed by trying every address. The address itself is not stored.2 days
Only if this server offers it and you connect your own Seats.aero Pro account: its sign-in tokens, encrypted, and the date your subscription ends. Never your Seats.aero name, email, searches or results.So your assistant’s Seats.aero searches can use your Pro accountUntil you disconnect, Seats.aero stops accepting the tokens, 30 days after Goliath last used them, or your workspace is deleted, about 90 days after it was created, whichever comes first
Supplier health: which supplier and tool was called, whether it worked, when, and for a failure its kind (an error code and status)To route around suppliers that are failing. It holds nothing about what was searched.The latest outcome until the next call replaces it. A failure’s code and status stay until the next failure.
Response times: which supplier and tool was called, whether it worked, when, and how long each step tookTo find slow suppliers and make searches faster. It holds nothing about what was searched or who searched.30 days
The shared fallback cache: public supplier answers and the requests that produced them, described belowTo answer when a supplier fails, times out or limits requestsUp to 72 hours after the last answer, and up to 7 days of refreshing after someone last asked
The award cache: award prices from Goliath’s own airline sources, kept when someone’s assistant runs a live search on one of them. Each entry has the route, date, cabin, points, taxes, seats left, flights and the time seen, and notes dates checked with no seats.So later searches can show recent prices without asking the airline again. It records nothing about who searched, and every user’s assistant can read it.Until the departure date passes, or 30 days after the price was last seen
Crawler routes: for an airline that has authorized Goliath’s crawler, a route someone searched (the two airports, with no dates) can join the crawler’s list for that airline, up to 200 routes eachSo the crawler checks routes people actually ask about. Nothing records who searched it.Until 90 days after someone last searched that route

What is not stored

  • Your trip as a whole. Goliath keeps no record of what you searched and links no search to your workspace. Route, date and party details survive only in the shared caches on this page, with nothing that says who asked.
  • Search results, except in the shared caches on this page.
  • Anything else from your chat. Goliath sees only what your assistant puts in a tool call, such as airports, dates, a points balance, card-offer terms or a trip request to plan. It uses these to answer and keeps none of them. Its tools have no field for card numbers or passwords, and connecting Seats.aero happens on seats.aero’s own sign-in page.

The shared caches

Some answers are the same for everyone: a bank’s published list of transfer partners, an airline’s award chart, or a public cached award listing for a route and date range. Goliath may keep up to 200 of these supplier responses, with the supplier request that produced them. A stored answer is used for up to 36 hours (award listings) or 72 hours (reference pages). When an assistant’s search produced the request, Goliath asks the supplier again, at most a few times a day, for 7 days after someone last asked, then deletes the entry once its last answer is too old to use.

Stored answers are used only when the supplier fails, times out or limits requests, and are labeled Cached. A stored request holds search settings only, such as airports, dates, cabin, number of seats and program or bank filters. It is not linked to a workspace.

The award cache in the table above works the same way: it records prices and the time they were seen, never who asked.

Why Goliath uses this data

  • To run the service you ask for: sessions, connections, searches and a Seats.aero connection you choose to make. Legal basis: performing the agreement with you in the terms.
  • To keep a free service fair and safe: daily limits, network hashes, logs and supplier health. Legal basis: legitimate interests in preventing abuse and keeping Goliath working.
  • To answer later searches and cover supplier failures: the shared caches. Legal basis: legitimate interests. They hold no link to you.

You don’t have to give Goliath anything, but it can’t search without the details your assistant sends.

Processors and transfers

Cloudflare hosts Goliath, its database and its logs, runs a browser for some supplier searches, and provides Turnstile. Oracle Cloud hosts the relay server. Each processes data only to run Goliath, under its data processing terms.

Cloudflare handles requests in data centers around the world, so data about people in the EU, the UK or Switzerland can be processed in other countries. Goliath relies on each provider’s data processing terms for those transfers.

This website

Goliath sets only the cookies it needs to work: the session cookie above (30 days), a cookie that protects the approval form (10 minutes), a cookie that ties a Seats.aero connection to the browser that started it (15 minutes), and, for the operator only, an admin sign-in cookie (8 hours). None is used for tracking or advertising. Goliath doesn’t track you across sites, so it treats every visit the same whether or not your browser sends Do Not Track or Global Privacy Control.

Security

Goliath uses HTTPS. In its database it keeps session tokens only as hashes, network addresses only as hashes made with a secret key, and Seats.aero tokens encrypted. Its cookies are Secure and HttpOnly. No system is perfectly secure, so Goliath can’t promise data will never be exposed.

Children

Goliath isn’t meant for children and doesn’t knowingly process data about anyone under 16. It collects no names or contact details, so it can’t tell a user’s age. If you think a child used it, contact the operator.

Your rights and choices

  • Disconnect Goliath in your assistant’s settings at any time. Its tokens stop working when they expire or are revoked.
  • Clear this site’s cookies in your browser to end the browser session. A later connection starts a new workspace.
  • Depending on where you live, you can ask to access, correct or delete data about you, to restrict or object to its use, and to receive it in a portable form. You can also complain to your data protection authority. To make a request, ask your assistant for your Goliath workspace ID (its get_service_status tool shows it) and send it to the operator.

Goliath has no names or email addresses, so without that ID it usually can’t tell which records are yours, and may not be able to act on the request. Every record is deleted on the schedule above anyway. Goliath doesn’t sell or share personal information, use it for advertising, or make automated decisions about you.

Contact

Operator contact details have not been added to this page yet.

Changes

If these practices change, this page changes first and the date at the top is updated.