No advertising runs on DelayPilot. This site loads no ad script, calls no ad network, and carries no consent-management platform. Nothing on any page is paid placement. What follows is the standing rule set — the positions an ad may occupy, the positions it may never occupy, and the information that never reaches an advertiser under any of them.
The one rule the rest of this page serves
An ad must never be confusable with a flight, a refund, a rebooking, a claim, a contact control, or anything safety-related. A traveler reading this product is often tired, often late, and often about to spend money they will not get back. A unit that borrows the look of a control at that moment is not an ad — it is a trap, and no revenue justifies it.
Where an ad may appear
This list is complete. An ad may appear in these positions and nowhere else; a position that is not on this list is forbidden even if nothing below explicitly names it.
- On the homepage, after the complete demonstration and the first explanatory section.
- In the middle of a guide, after a substantial amount of the article has been read.
- At the end of a guide.
- On an airport or airline page, after the main answer that page exists to give.
- On a free trip result, only after the complete action checklist, with strong visual separation from it.
A trip cockpit shows at most one ad, and only after the complete action area — the checklist, the rights estimate, and the next useful step all come first. Advertising is what happens after the product has finished being useful, never instead of it.
Where an ad may never appear
- Above the primary flight search.
- Inside any form.
- Between a warning and the action that answers it.
- Inside a passenger-rights card.
- Inside or next to an action checklist.
- Next to a "Contact airline", "Request refund", or "Save evidence" control.
- On sign-in, checkout, account, admin, privacy, terms, error, or status pages.
- Anywhere in a paid, signed-in experience.
The page you are reading is itself on that list, as are the privacy and terms pages. A policy page carrying an ad would be advertising against the credibility of the policy.
How the rule is enforced, rather than just written down
A placement policy that lives only in prose is a policy that survives exactly until the first hurried change. Two mechanisms hold this one in place:
- The position is part of the type. The design system's ad wrapper accepts only the five permitted positions above. There is no free-text option and no escape hatch, so a forbidden position cannot be expressed at all — it has to be added to the shared component first, in a change a reviewer sees.
- The build refuses the output. Every page is checked after it is generated, and an ad container found on any forbidden route fails the build rather than shipping. On this build there is no ad container on any page at all.
Paid plans are ad-free
When paid plans exist, they are ad-free — not ad-reduced. A Trip Pass makes the trip it covers ad-free for its whole monitoring window; Plus and Family are ad-free across the entire signed-in experience. No paid surface carries an ad, a sponsored module, or a partner link dressed as a feature. No plan exists to buy today: there is no billing integration, no price is charged, and no purchase control is rendered anywhere on this site.
Consent comes before the ad, not after
Where consent is required for advertising or for the tracking that funds it, no ad script loads until that consent is recorded. Refusing is one action and no harder than accepting. A refusal is remembered and not re-asked on every page. There is nothing to consent to today, because no ad code and no consent platform exists — and a consent banner asking permission for tracking that does not happen would be theatre.
What is never sent to an advertiser
- No itinerary detail, ever. Not a flight number, not a route, not an airport pair, not a travel date, not a disruption state. Itinerary data never reaches ad targeting, an ad request, or an affiliate parameter.
- No booking reference. DelayPilot never asks for one, so there is none to leak — not to an advertiser, not to a log, not to a web address.
- No personal identifiers. No email address, no display name, no account identifier, and no raw IP address is passed into an ad request or a targeting key.
This is the reason DelayPilot will never run behavioral targeting built on trip data, even though a flight-disruption audience is exactly what such a system would pay most for.
How a slot behaves
- Labelled. Every slot carries a visible label identifying it as advertising.
- Dimensions reserved. A slot holds its width and height whether or not it fills, so nothing on the page moves under your finger. The design system's slot container already enforces this: both dimensions are required, and an unfilled slot stays reserved and empty rather than collapsing.
- No refresh on a timer, and no refresh when the page quietly re-checks flight status in the background. An ad impression is never bought by re-rendering a traveler's live status view.
- Dropped from print. An evidence packet is a record of what happened to your flight, not an inventory surface.
- Off in local, test, screenshot, and demo-review modes, so that no screenshot, test run, or demonstration ever shows an ad in a position review has not approved.
Advertising never reaches the writing
No article, guide, or passenger-rights explanation on this site is commissioned, sponsored, paid for, or reviewed by an advertiser, and no advertiser sees one before it is published. There are no advertisers today, which makes that easy to state and easy to check; the rule is published now so that it is already binding on the first one. How guidance is actually sourced and reviewed is the editorial policy.
Why there is no ads.txt file
An ads.txt file names the companies that may sell advertising inventory on a domain. Publishing one before any advertising integration exists would assert something about this site that is not true. The file ships with the ad integration itself, together with the placement tests that enforce everything on this page — not before it.
How this page changes
This page is rewritten, not appended to, in the same change that enables advertising. It will then name the network, the slots that exist, the consent mechanism, and the date the change took effect. Until then, the accurate summary is the first line: no advertising runs on DelayPilot.
Related policies
- Affiliate disclosure — commercial links and how they are marked.
- Privacy — what is collected today, and what never will be.
- Editorial policy — why no advertiser can influence guidance.