Back to sign in

Legal information

Cookies & Local Storage

The browser storage DK CMS currently uses and why it is needed.

Last updated: 16 August 2026

Review notice: Draft for operational review. Before public release, confirm the operator’s full legal name and postal address, the controlling language, the final retention schedule, and the applicable provider agreements and transfer safeguards.

1. Current position

DK CMS currently uses security cookies, user-requested preferences and local email drafts. The verified application does not currently load advertising cookies, analytics tags or behavioural-tracking pixels.

Because the current storage is necessary for sign-in/security or directly requested functionality, the application does not show a cosmetic consent banner. This decision must be reviewed before adding analytics, advertising, embedded third-party media or new tracking technology.

2. Cookies

  • __session — secure authentication cookie used to keep a verified account signed in; configured for up to seven days and removed on sign-out.
  • __Host-dk-csrf (or dk-csrf in local non-secure development) — protects state-changing requests against cross-site request forgery; configured for up to seven days and removed on sign-out.

3. Local storage

  • dk-cms-theme — remembers whether the user selected automatic, light or dark appearance.
  • dk-cms-locale — remembers whether the interface should appear in Greek or English.
  • dk-csrf-token — mirrors the security token required for authenticated write requests.
  • dk-cms:email-draft:* — saves a user’s unsent inbox message locally so work is not lost before sending or discarding it.
  • Notification read status is stored securely in the application database and is not kept in browser local storage.

4. Your controls

You can change language and theme in the interface, discard an email draft, sign out, or clear site data through your browser. Clearing storage may sign you out, remove preferences and delete unsent local drafts.