Cookie Policy
This site sets no cookies. Not one — no analytics, no advertising, no tracking, and therefore no banner asking you to accept any. Here is what we do store in your browser instead, and how to get rid of it.
The short version
Visiting Niagara Falls sets no cookies. We run no analytics, no advertising pixels, no session tracking and no profiling. There is nothing to accept, so we do not interrupt you to ask.
Most travel sites open with a consent banner because they load a dozen third-party trackers before you have read a word. We decided not to build the site that way. That choice is why this page is short, and why it can make a claim most cookie policies cannot: there is no list of advertising partners at the bottom, because there are no advertising partners.
Two things are worth knowing all the same. We store a small amount of data in your browser to make the wishlist and trip planner work — explained below, and never sent to us. And when you go on to book, you leave this site for our booking partner's checkout, which does use cookies of its own.
This page covers visitingniagarafalls.com. For everything else we do with data, see the Privacy Policy.
What cookies actually are
A cookie is a small file a website asks your browser to keep and hand back on your next request. That is genuinely useful for keeping you logged in or holding a basket together. It is also the mechanism behind most tracking on the web: a cookie set by an advertiser and read across thousands of sites is how a pair of boots follows you around the internet for a fortnight.
Cookies are not the only way to store things in a browser. Local storage, session storage and cache storage do a similar job through different mechanisms, and a policy that only mentions cookies can be technically true while telling you very little. So this page covers all of it. In the UK and EU, the rules on "storing information on a user's device" — PECR and the ePrivacy Directive — apply to local storage exactly as they do to cookies, and we have written this page to that standard rather than the narrower one.
Cookies we set
None, in any category. Set out the way a cookie policy normally sets it out:
| Category | What it would normally do | What we use |
|---|---|---|
| Strictly necessary | Sessions, logins, baskets, security tokens | None — the site has no accounts and no basket |
| Preferences | Remember language, currency or region choices | None — currency follows your browser each visit |
| Analytics | Measure visits, pages, journeys and drop-off | None — we run no analytics of any kind |
| Advertising | Retargeting, conversion pixels, audience building | None — we run no advertising tags |
| Social media | Embedded feeds, like and share buttons | None — our social links are plain links |
You can check this yourself in about a minute. Open your browser's developer tools on any page of this site, go to the Application or Storage tab, and look at the cookie list for this domain. It is empty.
What we store instead
Two features need to remember something between pages, and both use your browser's local storage. This data stays on your device and is never transmitted to us — we have no copy of your wishlist and no copy of your trip plan.
| Name | Type | What it holds | How long it lasts |
|---|---|---|---|
vnf_wishlist | Local storage | The tours and attractions you have saved with the heart icon | Until you clear it |
vnf_tripplan | Local storage | The itinerary the trip planner last generated for you | Until you clear it |
Both are created only when you use the feature. Browse the site without touching the heart icon or the trip planner and nothing is written to your device at all.
Under the UK and EU rules these fall within the exemption for storage that is strictly necessary to provide a service the user has explicitly requested — you asked for a wishlist by saving to it — which is why they do not require a consent prompt. They are also why the two features are device-bound: your wishlist does not follow you to your phone, because there is no account for it to follow you through.
Third parties your browser contacts
Loading any web page means your browser fetching files from wherever they live, and each of those requests reveals your IP address and browser to that host. That is true of every site on the internet, and it is worth being straight about which hosts are involved here:
| Host | What it serves | Cookies |
|---|---|---|
| Vercel | The site itself and our booking endpoints | None set |
| Cloudinary, Unsplash | Photography | None set on our pages |
| Google Fonts | The typefaces | None set |
| jsDelivr | The country flag icons on listings and filters | None set |
These are static asset hosts: they hand over an image, a font or a stylesheet and nothing else. We embed no third-party scripts, no tag manager, no chat widget, no social feed and no maps iframe — the map links on our attraction pages are ordinary links that open in a new tab, so nothing is loaded from Google until you choose to click one.
To be precise about the basis for that third column: it reflects what these hosts are — asset CDNs that answer with a file and no Set-Cookie header — rather than a continuous audit of every response they send. We do not control a third party's behaviour, and theirs is governed by their own policies rather than ours. What we can control is how many of them there are, and we keep that number small deliberately. If you ever observe a cookie from any of them on our pages, tell us and we will correct this page.
When you go to book
We do not take payment on this site. Choosing an experience hands you to our booking partner's secure checkout to enter your traveller and payment details.
That checkout is not covered by this policy. Like any payment flow, it uses its own cookies for the session, fraud prevention and its own analytics. From the moment you arrive there, their cookie policy and privacy policy apply.
Nothing you do on their checkout writes anything back to this site, and we receive no cookie from them. What happens to your booking data at that point is set out in the Privacy Policy, and the split of responsibility between us and the operator is in the Terms of Service.
Why there is no cookie banner
Consent banners exist to obtain permission for storage that is not strictly necessary — analytics, advertising, profiling. We do none of that, so there is no permission to obtain. A banner here would be theatre: a dialogue asking you to approve a list with nothing on it, in exchange for a click.
The two items of local storage we do use fall under the strictly-necessary exemption described above, because they exist only to deliver a feature you actively asked for. We are also not required to obtain consent under the CCPA or CPRA, since we neither sell nor share personal information for cross-context behavioural advertising.
If that position ever changes, the banner arrives before the tracking does — see below.
Clearing and blocking storage
Everything on your device is yours to remove, and you do not need our permission or a preference centre to do it. Clearing site data for this domain deletes the wishlist and trip plan; nothing else on the site depends on them, and every page keeps working normally.
| Browser | Where to look |
|---|---|
| Chrome | Settings › Privacy and security › Third-party cookies, or Site settings › View permissions and data stored across sites |
| Safari | Settings › Privacy › Manage Website Data (macOS), or Settings › Safari › Advanced › Website Data (iOS) |
| Firefox | Settings › Privacy & Security › Cookies and Site Data › Manage Data |
| Edge | Settings › Cookies and site permissions › Manage and delete cookies and site data |
Browsing in a private or incognito window discards everything when you close it. Blocking storage for this site entirely is fine too — the wishlist and trip planner simply stop remembering between pages, and the rest of the site is unaffected.
Do Not Track and Global Privacy Control
We run no cross-site tracking, so there is nothing for a Do Not Track or Global Privacy Control signal to switch off. We honour those signals by default, in the only way that really counts: by not doing the thing they are designed to disable.
If this ever changes
If we ever add analytics, advertising or any other non-essential storage, we will update this page and the date at the top before it goes live, and put a genuine consent mechanism in front of it — one where declining is as easy as accepting, and where nothing loads until you choose. We will not quietly start tracking and update a policy page afterwards.
Contact us
Visiting Niagara Falls
Email: info@visitingniagarafalls.com
Or use the contact form.
If you have found something on this site storing data we have not listed here, we want to know. Tell us what you saw and where, and we will investigate and correct this page.