Web browsers increasingly limit how cookies are stored and accessed to improve user privacy. Fresh Relevance uses first‑party cookies to identify visitors and track activity on your site, so it is important to understand how each browser’s restrictions affect data capture, session tracking, and device identification.
As browser privacy controls have increased, many browsers now limit or block certain types of cookies. Cookies are a common mechanism for identifying shoppers and tracking on‑site behavior.
There are two types of cookies:
First-party - cookies set on your own domain and only accessible within it.
Third-party - cookies set on another vendor’s domain, for example Google, for tracking across multiple sites.
Fresh Relevance uses first-party cookies. Because these are limited to use for a single site, they normally don’t contravene the privacy measures put in place by browsers.
Common browser status updates
Here's the current status for the most common browsers and how it affects Fresh Relevance:
Chrome
Blocks third-party cookies. This doesn’t affect Fresh Relevance as we use first-party cookies.
Firefox
Blocks third-party cookies. This doesn’t affect Fresh Relevance as we use first-party cookies.
Edge
Blocks third-party cookies. This doesn’t affect Fresh Relevance as we use first-party cookies.
Safari
Blocks third-party cookies. This doesn’t affect Fresh Relevance as we use first-party cookies.
Currently limits all first-party cookies to a maximum lifespan of 7 days.
Since January 2020, Fresh Relevance has been storing the device ID that is found in our cookie in the browser's
localStorage. This doesn't currently have the same time limit imposed.If the script detects a missing cookie but finds a device ID in
localStorageit recreates the cookie using the ID to allow continued identification.