Cookie Privacy Policy

Some traces of a visit stay in a browser; others stay on a server. The distinction matters here because the typed arithmetic check on Contact works without sending your answer to an outside captcha provider.

The theme’s own footprint

The custom Czarsblend theme sets no analytics, advertising or preference cookies. It uses no local-storage visitor identifier. The menu opens with a small local script, while fonts and study images are downloaded from the site. Ordinary browser caching of these files is not an advertising cookie.

The Contact form sends a signed challenge and a WordPress request-security token as form fields. Server-side temporary records limit repeated sends and mark a challenge as used. Those records are not stored in your browser as cookies and are not shared with an external verification company. Further detail appears in the Privacy Policy.

Layers outside that footprint

WordPress may use necessary cookies for authenticated administration. Hosting, security or caching services may also set technical cookies according to their configuration. Existing article embeds can contact another provider and may introduce storage or tracking that the theme itself does not add. Following an outbound link takes you to a separate site’s practices.

The absence of theme analytics is not a guarantee that every plugin, hosting layer or older embedded article is cookie-free. Any new non-essential measurement or advertising service should be assessed before activation, documented here and, where required, held back until consent is obtained. This theme does not supply a consent manager.

Your browser is the control cabinet

Use browser settings to inspect, block or remove site data. Clearing cached files may cause them to download again; blocking necessary session cookies can interrupt administrative sign-in. Different browsers and devices keep separate stores, so a choice on one does not necessarily carry to another.

If you see an unexpected cookie on czarsblend.com, send its name and the page where it appeared. Do not copy its value, session tokens or account credentials into the message. Reviewing that observation can help distinguish a necessary technical record from a service that needs a different consent arrangement.