ForkScoreForkScore
Sign In

Cookie Policy

What we set, why, and how to control it.

Effective April 27, 2026 · v2026-04-27

What are cookies?

Cookies are small text files that websites place on your device to remember information about you. ForkScore uses cookies and similar local-storage technologies (such as localStorage and service-worker caches) for the purposes described below.

Cookies we use

Strictly necessary

These cookies are required for the Service to function. We cannot disable them without breaking core functionality, and they do not require consent under EU/UK ePrivacy law.

  • Authentication session — set by Supabase Auth. Maintains your signed-in state. Expires when you sign out or after session timeout.
  • CSRF token — protects against cross-site request forgery on form submissions.
  • Cloudflare Turnstile — distinguishes humans from bots on signup and certain endpoints. May set short-lived cookies.
  • Locale preference — remembers your selected language (cookie name: forkscore_lang).
  • Affiliate code — preserves a referral code included in a link you arrive on so it can be applied at signup (cookie name: forkscore_redirect; query parameter?ref=).

Functional / preference

These cookies remember your choices to improve the experience. They are not strictly necessary but disabling them degrades convenience.

  • Feed view mode — remembers whether you prefer the swipe or scroll feed on /home (key: forkscore-feed-view-mode).
  • Onboarding state — remembers which tutorial steps you have completed.

Analytics

We use first-party analytics from Vercel to understand traffic and performance. These products are designed to be privacy-respecting and, per the providers, do not use cross-site tracking cookies.

  • Vercel Analytics — page views and aggregate usage. Operates without persistent client cookies; uses anonymized request-side measurement.
  • Vercel Speed Insights — Core Web Vitals measurement. Same model.

Where required by law (notably the EU/UK ePrivacy Directive), we will request your consent before activating analytics. In jurisdictions that classify these tools as not requiring consent, we rely on legitimate-interest processing.

How to control cookies

  • Browser settings: most browsers let you block or delete cookies in their privacy settings. Disabling strictly necessary cookies will prevent you from signing in.
  • Do Not Track / Global Privacy Control: we honor the GPC signal as a valid opt-out request under CCPA/CPRA. We do not currently respond to legacy DNT headers.
  • Mobile installs: when ForkScore is installed as a PWA, the same browser controls apply since the PWA is a sandboxed instance of the underlying browser engine.

Updates

We may update this Cookie Policy as we add or remove tools. The version date at the bottom of the page reflects the most recent change. For questions, contact privacy@forkscore.ai.

Notice on legal advice: This document is provided for informational purposes only and does not constitute legal advice. Adkins Labs, a sole proprietorship operated by Edward McNichols recommends that users consult licensed counsel in their jurisdiction regarding questions about their rights under this policy.

Adkins Labs, a sole proprietorship operated by Edward McNichols

Questions: legal@forkscore.ai