// storage & privacy disclosure

Cookie & Local Storage Policy

Last Updated: September 21, 2026 Version 2.4 Scope: Browser Client

01 Overview & Zero Tracking Guarantee

This Cookie & Local Storage Policy describes how kallme-relay (kallme-relay.lol) uses web storage technologies.

We do not use advertising cookies, third-party analytics trackers, tracking beacons, cross-site profiling scripts, or canvas fingerprinting.

Unlike conventional web apps that transmit session identifiers to backend databases on every request, kallme-relay is architected as a decentralized, privacy-first interface. All application state is maintained exclusively on the client device using W3C HTML5 Web Storage (window.localStorage).

02 Technical Distinction: HTTP Cookies vs. Local Storage

Understanding our storage posture requires understanding the technical difference between cookies and Web Storage:

  • HTTP Cookies: Small key-value pairs appended automatically to every outgoing HTTP header (Cookie: ...). Because they traverse the network with every request, cookies can expose user activity to third-party CDNs and logging systems. kallme-relay sets zero third-party or advertising cookies.
  • HTML5 Local Storage: Sandboxed client-side key-value storage managed directly by your browser engine. Data stored in localStorage is never transmitted over HTTP headers, cannot be inspected by external origins, and is accessible only to scripts executing directly on kallme-relay.lol.

03 Comprehensive Itemized Storage Inventory

The following table details every key written by the playground application, its technical purpose, and its lifecycle:

Storage Identifier Data Structure & Purpose Persistence
kallme_relay_sessions_v1 Serialized JSON array containing active conversation history, message roles (user/assistant/thinking), timestamps, and turn tokens. Stored locally to allow resuming chat sessions between browser reloads without server persistence. Persistent (until user purges)
kallme_relay_settings_v4_pico8010 JSON configuration object storing UI accent palette, custom hex values, active system prompt presets, thinking budget limits, max token overrides, and relay endpoint URL preferences. Persistent (until user purges)
kallme_relay_last_model String identifier representing the user's most recently active inference checkpoint (e.g., claude-sonnet-4-5 or huijv/gpt-6-astra). Persistent (until user purges)
kallme_relay_pinned_models_v2 Array of model IDs starred or pinned to the top of the developer dropdown selector for quick switching. Persistent (until user purges)
kallme_relay_sidebar_width Numeric pixel value recording the user's custom drag-resized sidebar width. Persistent (until user purges)

04 Legal Classification under EU ePrivacy Directive & GDPR

Under Article 5(3) of the European Union ePrivacy Directive (Directive 2002/58/EC as amended by Directive 2009/136/EC) and national implementations across the EEA and UK:

  • Strictly Necessary Exemption: The storage keys identified above are strictly necessary to deliver the explicit functionality requested by the developer (maintaining your prompt drafts, storing theme accessibility preferences, and managing model endpoints).
  • No Consent Banner Requirement: Because we process zero behavioral tracking or advertising data, no invasive tracking consent banners or cookie walls are required or deployed.

05 Third-Party Scripts & CDNs

External assets are restricted to essential operational utilities:

  • Typography: Google Fonts (fonts.googleapis.com / fonts.gstatic.com) for rendering JetBrains Mono and Inter. Google’s servers receive standard HTTP referrers and IP requests for font asset delivery; no cookies are exchanged.
  • Markdown Engine: The markdown parsing library (marked.min.js) is self-hosted on our local origin and executes completely client-side.

06 Operator Controls & Storage Erasure

Because storage resides exclusively on your machine, you maintain complete, absolute authority over its deletion at all times:

  • Single-Click Data Deletion: Use our integrated Data Deletion Tool to execute an instantaneous localStorage.clear() call, resetting the application to pristine default state.
  • Browser Inspection & Deletion: In Chrome, Firefox, Safari, or Edge, press F12 $\rightarrow$ Application / Storage $\rightarrow$ Local Storage $\rightarrow$ https://kallme-relay.lol to inspect or remove individual keys manually.
  • Incognito / Private Browsing: Launching kallme-relay in Private Browsing mode guarantees that all stored session transcripts and preferences are automatically discarded by your browser upon closing the window.

07 Inquiries & Contact

For technical inquiries regarding client-side storage architecture, privacy verification, or regulatory questions, contact:

chantelwertz6450+dfemz8vk9j@outlook.com