FreePass.news
FreePass uses a small number of first-party cookies. This release does not activate advertising cookies or optional analytics cookies.
Necessary cookies support a service you requested or protect the service. Because FreePass currently has no optional analytics or advertising cookies, there is no hidden tracking category to opt into. The banner records acknowledgement of this fact; it does not turn a necessary cookie into consent-based processing.
The generated FreePass session cookie lasts for the browser session and is used for authentication state, CSRF protection, region/language preferences and other security-critical session state. It is Secure on HTTPS, HttpOnly and SameSite=Lax.
When you explicitly request a publisher while not signed in, FreePass may set fp_visitor for up to 12 months. It contains a random token and is transformed server-side into a pseudonymous hash used to deduplicate demand and protect metric integrity. It is Secure on HTTPS, HttpOnly and SameSite=Lax.
fp_cookie_notice lasts up to 6 months and remembers that this cookie notice was acknowledged. It does not contain an advertising identifier or reader profile.
None are active in this release. If FreePass later introduces non-essential analytics, advertising or similar tracking, they must remain off by default where required and a separate, specific choice must be offered before activation.
You can clear cookies through your browser. Clearing the session cookie signs you out; clearing fp_visitor may prevent FreePass from linking earlier anonymous demand in that browser; clearing the notice cookie makes the banner appear again.