Last updated: May 1, 2026
CodeFence uses minimal storage — no advertising cookies, no third-party trackers. Here is exactly what runs on codefence.cc:
Clerk session cookies
Set by our authentication provider (Clerk) when you sign in. These keep you logged in across browser sessions. Required for the service to function.
Expires: when you sign out or after session timeout
auth_token (localStorage)
Your authentication token stored in browser localStorage. Used to authenticate API requests to CodeFence. Cleared when you sign out.
Expires: on sign out
Stripe cookies
Set by Stripe during checkout and billing management. Used for fraud prevention and payment processing. Only active when you visit billing pages.
Governed by Stripe's Privacy Policy
Page visit tracking (sessionStorage)
We track which pages of codefence.cc are visited to understand what content is useful. This uses browser sessionStorage — it is not a cookie, it does not persist after you close your browser, and it contains no personal identifiers. We only record the page path and referrer URL. Logged-in users are excluded from this tracking.
Expires: when browser tab is closed
You can clear cookies and localStorage at any time through your browser settings. Clearing auth cookies will sign you out of CodeFence. Since we do not use advertising cookies, there is no cookie consent banner — the cookies we set are strictly necessary for the service to function.
Questions about our cookie use? Email [email protected].