What sits in your browser

Effective August 4, 2026. Category lists cannot be checked. Names can, so this page uses names.

The single entry this site sets

Name

st_choice_2026

Kind

Local storage, not a cookie

Contents

One word, yes or no, recording which button you pressed on the storage card

Written when

You answer that card, which appears at the lower left shortly after a first visit

Lifetime

Until browser storage is cleared. It carries no expiry of its own

Transmitted anywhere

Never. Local storage does not travel with requests, and nothing here reads it back out to anywhere

Reason

So the card stops appearing on every page

No session cookie, no visitor identifier, no measurement identifier, no advertising identifier and no consent identifier beyond that one word. Blocking it costs nothing except that the card returns.

The search desk, and the moment anything changes

The desk on the front page is worth setting out step by step, because the timing is what most places in this trade leave vague.

While a reader types

Nothing at all leaves the browser. The town and airport suggestions come out of a list file served by this paper, exactly as its typefaces are

What this paper keeps

Nothing. What is typed is not written to storage here and never reaches this desk

On pressing the button

The browser travels to the booking host below, carrying one line that spells out the route, the two dates, the class and how many are going

Where it lands

avia.thesuntraveller.com, our own subdomain, but Travelpayouts answers on it

Who writes storage there

Travelpayouts, under their policy, from the instant that page opens. None of it is this paper's to control

Who receives the search

Travelpayouts. This paper receives none of it

Because those belong to the service rather than to this paper, their names and durations are the service's to alter, with no obligation to tell anybody here. The part under this paper's control, and the part that will not move, is that none of it starts until a reader decides to send a search.

Absent, named individually

• No measurement of any kind. No page counter, no heatmap, no session recorder.
• No advertising pixels, conversion tags, retargeting or tag containers.
• No social buttons, embeds or trackers.
• No comment system, live chat or notification prompt.
• No fonts, images, scripts or stylesheets loaded from anybody else on any page whatsoever, the

front page included. Typefaces, code and the place list all come from this domain.

• Nothing attempting to recognise somebody coming back a second time.

Left alone, the desk included, this paper talks to nobody at all, which is rare enough now to deserve a sentence.

Clearing any of it

The card. Press either button and the answer is recorded. Choosing the second still records something, since recording a preference is the only way to honour it.

Removing it. Every browser can clear site data for one site from its settings, usually under privacy or site permissions. Doing so removes the entry and the card returns next visit.

Storage blocked entirely. No part of the site fails. The card reappears every visit, since there is no place to put the answer.

Avoiding the search entirely. The desk does nothing until its button is pressed. No redirect, no pop up, no second window. Leaving it be means nothing external is ever contacted.

Why a card at all for one entry

A consent card for a single local storage entry is arguably more ceremony than the situation deserves. It is here because the alternative, writing quietly to a reader's browser and mentioning it three levels down in a policy, is the habit this paper is trying not to acquire.

Disagreements and changes

Should the site and this page ever disagree, treat the page as correct and the site as broken, and send the discrepancy to archivist@thesuntraveller.com.

A change to what gets stored means this text moves before the behaviour does, under a fresh date. Related: how data is handled for anything you send, and the flight search page for that arrangement in full.