WispFile

Cookie Policy

Last updated 24 September 2026

WispFile itself sets one cookie, and only when you sign in. On its information pages (guides, comparisons, pricing and the like) it can also use Google Analytics, which sets cookies only if you allow it when asked. It uses no advertising cookies. Analytics never runs on the pages that send or receive files, on inboxes, or when you sign in.

Cookies

NameSet byPurposeLasts
wf_sessionapi.wispfile.com, when you sign inKeeps you signed in. HttpOnly (page scripts cannot read it), Secure, SameSite=Lax. We store only a fingerprint of it.30 days, or until you sign out
_gaGoogle Analytics, on information pages, only if you allow itCounts visits to those pages so we can see which ones help people. Your files, links and keys never reach it.Up to 2 years, or until you change your choice

Cloudflare Web Analytics also counts visits to the information pages. It sets no cookies and does not track you across sites.

Cloudflare, which delivers the website, may set its own strictly necessary security cookies to tell people from bots. Stripe sets its own cookies on its checkout pages, and Google on its sign-in pages, under their policies.

Other storage in your browser

WispFile keeps some things in your browser, never sent to us:

WhatWhyLasts
Inbox keys (local storage)So your inbox links can be shown again on your account page. They never leave your browser.Until you clear site data
Swarm cache (IndexedDB)In swarm mode, the encrypted pieces a receiver passes on to others.Deleted when you leave the page; anything a closed tab left behind is removed the next time a swarm download starts
Download helper (service worker)Streams large downloads to disk in browsers that cannot write to a folder directly.Until you clear site data

Your choices

You can block or delete cookies in your browser settings. Sending and receiving files work without any cookie; only signing in needs wf_session.

Questions: [email protected]. See also the Privacy Policy.