Site policy
Cookie Policy
This policy explains how cookies are used on this website. It describes what cookies are, which categories the site uses, and how you can control them through your browser. This site is an independent guide to Fireaway pizza delivery in the UK.
Read this first
Cookies on this site do one of two jobs: they keep a page working the way you left it, and — where a visitor tool is present — they tell us which pages people find useful so we can rewrite the ones they don't. They are not used to advertise to you, and they are not used to build a picture of you as an individual visitor across other websites.
Everything below applies to fireawayy.com. Where a third-party service sits inside a page — an embedded video, for example — that company's own cookie policy applies to what it sets, not this one.
Where to go next
Questions about this policy can be sent by post to 142 High Street, Croydon, CR0 1ND, United Kingdom, or by telephone on +44 20 8680 1234. Written enquiries can also go to [email protected].
Contact usWhat cookies are
A cookie is a small text file that a website asks your browser to store on your device. Two files are worth separating here, because people often use the word cookie for both.
A session cookie lasts only while your browser is open. It helps a single visit hold together — keeping a form half-finished if you flip to another page, for instance — and it is discarded when you close the tab.
A persistent cookie stays on your device for a set period, so the site recognises your browser on a return visit and remembers a setting you chose, such as a text size or a dismissed notice. It carries no memory of what you did elsewhere and no file from your device travels with it.
Neither kind runs a program. A cookie is read-only content that only the site that set it can read back, and it cannot reach your documents, your photos, or any other file on the device.
Cookies used on this site
The guide runs on a small, deliberately limited set of cookies. They fall into two groups, and nothing outside these two groups is set by this site.
Always on
Functional cookies
These keep the site working the same way between visits. They remember interface preferences — whether you left a navigation panel open, how you last ordered a list of branches, or that you have already dismissed a notice — and they support the contact form so a message reaches us intact rather than arriving empty. This site cannot function as intended without them, so they are not switched off by a preference toggle.
Where present
Analytics cookies
If analytics tools are in use on a given page, they record aggregate information about visits — which pages are opened, how often, and roughly which part of the country a visit came from. The figures are counts, not profiles: they tell us that a branch page or an opening-hours page is doing its job, or that a section is being skipped. A visitor is never named in that data, and it is not matched against anything else you do.
Blocking these in your browser will not lock you out of the guide. It will simply mean the site forgets your preferences between visits.
Why we use them
Functional cookies exist so the guide behaves consistently. If a setting you chose on Monday is gone by Tuesday, the page feels broken even when the information on it is right — that is the small thing these files prevent.
Analytics, where present, do a different job. They show which parts of the guide people actually use: whether the branch list answers the question someone arrived with, or whether they leave from the opening-hours table. That tells us what to rewrite and what to leave alone, and it is the main reason the figures are collected at all.
What is not collected
- No cookies are set for advertising, and nothing here feeds an ad profile.
- No attempt is made to match a visit here against your activity on other websites.
- No profile of an individual visitor is built, sold, or shared for marketing.
- Nothing in the analytics figures identifies you by name, address, or device.
Third-party cookies
Some features on a page may be run by another company rather than by this site. The clearest example is embedded content — a video player, a map on a page that carries one, or a share control borrowed from a social platform. When that kind of feature loads, the company behind it may set its own cookies on your device.
Those files are outside our control. We cannot read them, we do not decide how long they last, and we do not see what they record. What they do is set out in the privacy and cookie policies of the companies that place them, and those policies — not this page — govern that part of your visit.
If you would rather those companies set nothing at all, most browsers let you block third-party cookies while still allowing the first-party cookies this site needs. The next section explains where that setting lives.
Read the Privacy PolicyBrowser settings
Managing cookies in your browser
You are in charge of what your browser stores. Every major browser — Chrome, Safari, Firefox, Edge, and the rest — carries the same three controls in its settings, and the help section of yours will walk you through them.
Blocking everything is a valid choice. The guide still reads fine; the only thing you lose is the small conveniences that a remembered preference provided.
Three controls, in order of severity
Block third-party cookies only
The gentlest option. Pages continue to load as normal, embedded content from other companies stops setting files, and this site's own functional cookies stay in place. The setting lives in the privacy or site-data part of your browser's preferences.
Delete cookies already stored
Removes everything already sitting on your device, including files set months ago. It is a clean slate rather than a change of rule: unless you also block them, sites will set new files on your next visit.
Block all cookies
The strictest setting. Nothing is stored at all, which is exactly what some people want. Be aware that on many sites it makes forms impossible to complete and logins impossible to hold, because those processes depend on a session cookie existing between pages.
On this guide, blocking all cookies may affect how parts of the site function, but the branch details, opening hours, and menu information remain readable.
Changes to this policy
This policy is revised when the cookies used on the site change — when a feature is added, when an embedded service is removed, or when the way a tool records visits is altered. Smaller edits that only clarify wording are folded in without a separate note.
The version published on this page is the current one. If you want to check whether anything has moved since you last read it, this page is the place to look — there is no separate register of earlier drafts kept elsewhere.
Contact
Questions about this cookie policy — or about how this Fireaway pizza delivery guide handles data — can be sent through the contact form on this site, by post to 142 High Street, Croydon, CR0 1ND, United Kingdom, or by telephone on +44 20 8680 1234.