No analytics profile
The current build does not set analytics cookies to study visitor journeys, return visits, or campaign behavior across the site.
This Cookie Policy explains how the TireSwift website uses local browser storage while we help people book tire and wheel services. Storage use is intentionally small. This page states what is stored, what is not stored, how you can control it, and how to ask a question. TireSwift uses the site to explain bookings, bay hours, and appointments. The storage described here does not build a profile of which service page you open.
TireSwift provides fast, reliable, and professional tire care. Cookie and privacy questions go to [email protected], telephone +441216010443, 41 Dudley Rd, Oldbury B69 3DP, United Kingdom. Operator: TireSwift Tire Bay. Read this page with the Privacy Policy and the Terms of Use. No tracking tool is implied beyond the description below. Drive Smoothly. Drive Safely. Drive with TireSwift. The same bay answers cookie questions and booking changes.
Cookies are small text files a website can place on a device. Local storage can keep a simple value until you clear it. Some sites use many cookies for analytics, advertising, logins, and carts. TireSwift does not do that in this static build. The visitor-facing purpose is remembering that you acknowledged the cookie notice so the banner does not repeat on the next visit.
For a tire bay site, that limited approach matters. Drivers often arrive looking for puncture help, seasonal changes, balancing, pressure checks, or tire advice. They need clear service text and a contact route, not a web of trackers. Keeping storage small also reduces confusion on shared devices in homes or workplaces where someone else may later open the same browser.
The storage key name above is technical. Its function is a simple acknowledgement that the notice was dismissed. It does not store your name, your vehicle, payment details, or browsing history on other websites. It is not used to sell advertising audiences. If you clear site data, the notice can appear again.
TireSwift is first a tire bay. Drivers need a clear appointment, a bay note, and a way to reach Oldbury. Heavy tracking is not required. Small storage also keeps things simpler for one-time visitors who only want to see how a puncture repair or seasonal change is arranged. If analytics, a newsletter, or chat is added later, this policy will be expanded before those tools go live. A booking is not more accurate because a cookie watched you read it.
Seasonal peaks, fleet mornings, and urgent flat lanes already create enough operational detail without adding visitor profiling. The notice preference exists only so returning visitors are not blocked by the same banner on every load. Declining to store that preference does not block reading service pages. You can keep the notice visible and still review tire guides.
No analytics, advertising pixels, account cookies, or checkout cookies are used in this build. TireSwift does not place ad-network tags for remarketing. There is no cart cookie because this website build does not sell tires through an online checkout. There is no login cookie because public accounts are not part of this build. Hosting logs may record ordinary technical requests for security.
You can clear localStorage and cookies in your browser at any time. Menu names differ by browser, but the path is to open privacy or site settings, find this website, and remove stored data. The notice may then show again. Private browsing often discards storage when the session ends. TireSwift does not run a preference center for dozens of vendors. On a shared computer, clear site data when you finish.
Clearing storage does not cancel a bay booking you already confirmed by phone or email. Booking records live in ordinary correspondence handled by staff, not in the cookie notice flag. If you want both a clean browser and an updated appointment, clear the local preference and also write or call the bay with the change.
Some tools that keep a site usable can be strictly necessary, such as remembering a notice or supporting basic security. TireSwift limits visitor storage to that acknowledgement. If a later release needs storage for a newsletter, fraud prevention, or load balancing, this page will describe the purpose, duration, and whether it is optional. We will not turn the notice flag into an advertising identity.
The current pages are first-party content for TireSwift. If a later page embeds video or another tool that sets its own cookies, that third party would control them under its own policy. Until then, do not assume video or ad cookies are present just because other automotive sites use them. Treat this page as the description of the live build. Photographs here are image files served with the site.
Send cookie questions to [email protected]. You may also call +441216010443 or write to 41 Dudley Rd, Oldbury B69 3DP, United Kingdom. Describe the browser, the device, and what you saw, such as a notice that returned after you cleared storage. The bay is reviewed on weekdays. This policy may be updated when storage practices change. After an update, review the revised text.
In short, TireSwift stores one local preference so the cookie notice does not repeat. This build has no advertising or account cookies. Clear browser data anytime to reset the notice. Bay messages are covered by the Privacy Policy and the Terms of Use, not by this small preference. You can read every service menu with the notice still visible if you prefer not to store the acknowledgement. Drive Smoothly. Drive Safely. Drive with TireSwift.
Right now the site remembers only one small preference: whether you have already dismissed the cookie notice. It exists to reduce repetition for returning visitors, not to build a profile of which tire services you open.
If you want the notice to appear again or simply prefer a fully reset browser state, clearing the related local storage entry through your browser settings is enough.
The current build does not set analytics cookies to study visitor journeys, return visits, or campaign behavior across the site.
There are no ad-network cookies or tracking pixels here for remarketing, audience building, or campaign personalization.
Because this website build has no public checkout cart and no account login, it also has no cart state, login-session cookies, or saved account preferences.
If the build ever adds new storage for analytics, a newsletter, or another visitor-facing feature, this page should expand to describe that change in direct language.