Cookies and local storage
1. The short version
WispChart sets no cookies of its own. There is no analytics product here, no advertising network, no social widget and no tag manager. One small value is written into your browser's session storage when you answer the notice at the bottom of the page, and it never leaves your device. Separately, Cloudflare — the delivery network standing in front of this site — may set technical cookies of its own so that pages arrive quickly and automated traffic can be told apart from readers. The same network may also inject a small performance script of its own, which measures how quickly pages load and sets no cookies.
2. Everything that can be stored
| Name | Category | Purpose | Duration | Party |
|---|---|---|---|---|
wcConsent |
Preference (session storage, not a cookie) | Records that you answered the storage notice, holding the value accepted or declined, so the notice is not shown again while you read |
Until the browser tab is closed | First party, kept on your device and never transmitted |
__cf_bm |
Security | May be set by Cloudflare to tell automated traffic apart from a person opening the page | Up to 30 minutes | Third party — Cloudflare, Inc. |
cf_clearance |
Security | May be set by Cloudflare after a protection challenge has been passed, so the same challenge is not repeated | Up to 30 days | Third party — Cloudflare, Inc. |
The two Cloudflare entries are conditional: they appear only when Cloudflare's protection layer decides a check is warranted, and many readers will never see either of them. They carry no identifier of the operator's making and are not used to profile anyone.
3. Why the notice exists at all if nothing is tracked
Because being told is better than being assumed. The notice states plainly what the network in front of the site may do, and gives you a way to acknowledge it. Choosing Decline does not disable anything, because there is nothing of the operator's to disable — it simply records your answer so the panel stops appearing in that tab. The value written is exactly the one named in the table above, and no other.
4. Cloudflare performance measurement
Cloudflare may add a small script of its own to measure how quickly a page rendered on your device. It is injected by the network layer rather than written into these files, it reports timing figures only, and it is described here so that the account of what runs on the page stays accurate. The operator draws no report from it and keeps no dashboard.
5. Clearing or blocking what is listed
Closing the tab removes the session-storage value on its own. To clear it sooner, or to remove Cloudflare's cookies, use your browser's page or site settings — usually under Privacy, then Cookies and site data. Browsers set to refuse third-party cookies will still display this site correctly, and refusing storage entirely only means the notice reappears each time you arrive.
6. Changes and questions
If a further technical file is ever introduced, this table is rewritten before the change goes live and the effective date at the top is updated. Anything unclear can be raised with Harpreet Singh at notes@wispchart.com, and the wider account of data handling is set out in the privacy notice.