Got a digital radio at home? Many people have these days, and you might be aware of the digital switchover that’s coming not later than 2015. By then all AM stations will have gone, and all FM content will be on DAB. No problem for your kitchen because DAB radios start at £30 this days, but what about your car? Only a handful have built-in DAB and it’s an expensive option on luxury vehicles. Here’s the problem; on most cars today the audio head unit is usually built into the dash. There’s no standard slot about the size of a letterbox any more. Such integration makes radios less nickable and allows smarter cabin design. But it also means you can’t just replace your stereo with a new one. Standalone in-car DAB radios are available – the Pure Highway is the best known – but they’re about £80. Here’s something else you probably didn’t know and which will have to be sorted. If you have a sat-nav system in your car that receives live traffic updates, it relies on an FM signal so you’ll need to buy a new one of those, too. The UK car industry and the Government know all this stuff and are working hand in hand to make sure everything happens as it should. But you’re still going to have to put your hand in your pocket at some point.
We use essential cookies to ensure our site is safe and works properly. We also use analytics cookies to offer you a more personalised experience and to improve our site. To find out more and manage your cookie preferences, please choose ‘Manage’ or view our cookies policy.
This Cookies Policy sets out how startrescue.co.uk (“We”), use cookies on this website.
About Cookies
A cookie is a small file that is downloaded to a device (e.g. a Computer, Tablet or Smartphone) when a website is visited. The cookie allows the website to recognise a user’s device and store information based on the user’s previous actions and preferences.
For a complete definition of cookies, please visit the Information Commissioner’s Office (ICO) website here.
Essential Cookies
The table below explains the essential cookies We use and why.
Provider | Cookies | Purpose |
---|---|---|
startrescue.co.uk | srsm | We use security cookies to authenticate users, prevent fraudulent use of login credentials, and protect user data from unauthorised parties. |
srcl | We use security cookies to authenticate users, prevent fraudulent use of login credentials, and protect user data from unauthorised parties. | |
temp_srsession | We use security cookies to authenticate users, prevent fraudulent use of login credentials, and protect user data from unauthorised parties. | |
__RequestVerificationToken | This cookie is used to protect against Cross-Site Request Forgery (CSRF) attacks. This is set when you visit the page and is sent back to Our server whenever you submit a form in order to ensure any form submissions originated from Our site. | |
sr_aggr | This cookie is used to attribute your purchases with our partners. | |
sr_discount | This cookie is used to ensure customers receive discounts when purchasing through online advertisements. | |
_cookieconsent | This cookie indicates preference for the use of non-essential cookies. | |
Application Insights | ai_user ai_session | These cookies are used to collect information about issues, dependencies and exceptions which may occur when browsing this website. This data is purely for telematics and error detection, triage and diagnoses. For more information click here. |
The table below explains the analytics cookies We use and why.
Provider | Cookies | Purpose |
---|---|---|
Google Analytics | _ga _gid _gat AMP_TOKEN _gac_ <property-id> | Used to distinguish users. Used to distinguish users. Used to throttle request rate. Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Contains campaign related information for the user. For more information on the use of Google Analytics Cookies please click here. |
Optimise | OMG-{MID} | Read by the Optimise conversion tag to provide a backup means to attribute a sale to a specific Affiliate. |
HotJar | _hjid
| Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behaviour in subsequent visits to the same site will be attributed to the same user ID. |
_hjTLDTest | When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed. | |
_hjIncludedInPageviewSample | This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit. | |
_hjIncludedInSessionSample | This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's daily session limit. | |
_hjFirstSeen | This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. |
Information on controlling cookies using specific web browsers can be found on the Information Commissioner’s Office (ICO) website here.
Any changes We may make to Our Cookies Policy in the future will be posted on this page. We advise that you check this page regularly to keep up to date with any necessary changes.