A cookie is a small text file that a website asks your browser to store and hand back on later visits. Local storage and session storage do much the same job, keeping data in the browser rather than sending it back with every request. This page covers all of them, because from your point of view they behave alike.
NewCookware uses a small number of them. What follows is what each kind does and how to switch them off. The wider picture of what the site collects is on the privacy policy page.
The categories in use
Strictly necessary
These make the site work at all. WordPress sets a cookie to confirm that your browser accepts cookies, and sets login and session cookies for anyone signing in to the administration area. That second group only applies to the people who run the site, not to readers. The contact form may set a short-lived token to guard against automated submissions. These cannot be turned off from inside the site, because doing so would break it, although your browser can still block them.
Performance and caching
Pages here are served from a cache so they load quickly. The caching layer uses cookies to decide which stored version of a page to give you, for example a mobile version rather than a desktop one, or an uncached version for a logged-in editor. These cookies hold technical flags about the request. They do not carry a name, an email address or a browsing history.
Store components
The product pages are built on WooCommerce, the standard WordPress commerce toolkit, because it is a convenient way to organize a catalog of 197 appliances into categories and specification tables. Nothing is sold here and no payment is ever taken. WooCommerce may still set its usual cart and session cookies, since it does not know it has been repurposed as a filing cabinet. They hold no order or payment data, because there are no orders.
Analytics
The site runs first-party analytics rather than a third-party advertising network. To tell a returning reader from a new one, and to avoid counting one person as five visitors, the script stores a random identifier in your browser using local storage plus a first-party cookie, with a session identifier in session storage that disappears when you close the tab. The identifier is a random string with no name attached. It measures how many people read a page and which pages lead onward to a product. It is not used to build an advertising profile and it is not sold.
Outbound link tracking
When you click a product button, the click is recorded and may pass through a redirect on a domain we operate before you land on Amazon. That handler sets a first-party cookie so a click can be recognized later. It can persist for up to two years unless you clear it. Its purpose is to count clicks and to reconcile them with affiliate reporting, described on the affiliate disclosure page.
Sharing buttons
Social sharing buttons appear on some pages. If you actually use one, the network you are sharing to may set its own cookies at that point, under its own rules.
Amazon’s cookies are not ours
This is the part worth reading twice. The moment you follow a product link out of this site, you are on Amazon, and Amazon sets its own cookies. Amazon uses them for its affiliate attribution, for its own analytics, for personalization, and for the advertising it runs across its properties and elsewhere. That process is entirely Amazon’s, governed by Amazon’s cookie notice and privacy notice.
We do not control those cookies, cannot read them, cannot configure them, and cannot turn them off on your behalf. Refusing cookies here has no effect on what Amazon does once you arrive there. To limit that, you have to manage it in your browser or in your own Amazon account settings. We say so plainly because a cookie banner here would otherwise imply a level of control over the whole journey that nobody publishing an affiliate link actually has.
How to manage cookies yourself
Your browser is the real control panel, and it outranks anything a website tells you. Every major browser lets you view stored cookies and site data, delete them for one site or all sites, block third-party cookies, block cookies from a specific site, and clear everything automatically when you close the browser. Private or incognito windows discard cookies and storage when the window closes.
- Chrome: Settings, then Privacy and security, then Third-party cookies and Site settings.
- Firefox: Settings, then Privacy and Security, then Cookies and Site Data.
- Safari: Settings or Preferences, then Privacy, then Manage Website Data.
- Edge: Settings, then Cookies and site permissions.
- Mobile browsers: the same options usually sit under Settings, then Privacy.
Blocking cookies from this site will not stop you reading anything. Pages, categories and product write-ups all work fine without them. The practical effects are that our audience counts become less accurate and that you may see a cached page variant intended for a different device.
Changes and questions
Plugins get added and removed, and the cookies a site sets change with them. This page is updated as that happens. If something is unclear, or if you find a cookie here that is not explained above, write to [email protected] and we will look into it.