Cookie Policy

1. What this policy covers

This Cookie Policy explains the cookie and browser-storage behavior currently established for the public KodeFrames website. It should be read together with the Privacy Policy.

A cookie is a small value stored by a browser and associated with a website. Cookies can support security, authentication, preferences, analytics, advertising, or other functions depending on how a site is implemented.

2. Strictly necessary security cookie

The verified KodeFrames application runtime currently sets an ASP.NET Core antiforgery cookie. The cookie supports request-security protections used by the application framework.

The exact generated suffix of the cookie name is implementation-specific and is not treated as a permanent identifier in this policy.

Cookie family

.AspNetCore.Antiforgery.*

Category

Strictly necessary / security

Purpose

Supports ASP.NET Core antiforgery and request-security protection.

First or third party

First-party application cookie.

HttpOnly

Yes in the verified runtime; client-side JavaScript cannot read it through document.cookie.

SameSite

Strict in the verified runtime.

Path

/

Persistence

No persistent expiry was observed in the verified runtime, so the observed cookie behaves as a session cookie.

3. Analytics, advertising, and marketing

KodeFrames does not currently configure analytics, advertising, or marketing cookies on the public website.

The verified browser baseline also showed no application values in localStorage or sessionStorage and no third-party resource origin or iframe embed on the tested public Cookie Policy page.

If non-essential tracking or preference technology is introduced later, this policy will be updated and appropriate controls will be considered before that technology is treated as part of the production baseline.

4. Managing cookies

Most browsers allow you to inspect, delete, or block cookies through browser settings. Browser controls differ by product and version.

Blocking a cookie that is necessary for application security can interfere with the intended operation or security behavior of the website. The current KodeFrames cookie is used for the application's antiforgery security mechanism rather than behavioural advertising or audience profiling.

5. Third-party websites and embedded content

KodeFrames links to external websites and platforms, but an ordinary external link does not by itself mean that the third party has embedded a cookie or tracking resource into the KodeFrames page.

The current verified public-site baseline does not include third-party iframe embeds. When you follow an external link, the destination website may use its own cookies or other storage under its own policies.

6. Changes to cookie use

Website functionality can change over time. KodeFrames will update this policy when a material change introduces a new cookie category, analytics technology, embedded third-party content, or another browser-storage practice that should be disclosed.

Cookie attributes can also vary with browser behavior, framework updates, HTTPS deployment, or security configuration. Production behavior is reviewed as part of website release verification.

7. Relationship with the Privacy Policy

Where a cookie or related technical mechanism involves personal data, the Privacy Policy provides additional information about purposes, lawful bases, retention, security, service providers, and data-subject rights.