WHO TO FOLLOW LIVE · UPDATED 7 SEPTEMBER 2026

Cookies & storage

We use necessary storage for requested functionality and optional choices for analytics and embedded media. You can reject optional features and keep using the directory and your account. Privacy preferences.

Storage set by this website

wtf_session — necessary cookie

An opaque sign-in token for Google, Twitch or Kick sessions. Set by Who to Follow for seven days, HttpOnly and SameSite=Lax, Secure on HTTPS. The database stores a token hash. Signing out or deleting your account removes the browser cookie; sessions are also removed server-side.

wtf_oauth — necessary cookie

Protects a sign-in or account-linking attempt. Set for ten minutes, HttpOnly, SameSite=Lax and Secure on HTTPS; cleared when the callback is completed. It is not used for advertising.

wtf_privacy — necessary preference cookie

Stores the policy version, choice date and yes/no choices for analytics and embedded players. No user ID. Valid for 180 days from saving; stale, malformed or earlier-version choices are treated as unset. Set on this site with SameSite=Lax and Secure on HTTPS.

wtf-region — necessary localStorage preference

Your selected discovery country code. Stored on this browser until changed or cleared, with no automatic expiry. Select Worldwide to reset regional ranking. Region may also appear in page URLs and saved searches.

wtf-research-draft:* — necessary sessionStorage

Unsaved research notes, tags, status and collection names, scoped to your account and the item being edited. Used to recover interrupted editing. Removed after a successful save, cancelling a collection edit, or explicit browser sign-out; otherwise retained for the browser tab’s session. It is not analytics storage.

Our ChatGPT sign-in service and other sign-in providers can set their own authentication storage when you choose to sign in. This is separate from the cookies implemented by the application. Cookie names and lifetimes on provider-owned services are controlled by those providers.

Optional usage analytics

Analytics is off by default. When allowed, we send small event records to our own server, not a third-party analytics SDK. Each event has a new random receipt; there is no persistent analytics visitor ID, analytics cookie, localStorage identifier or session replay. Do Not Track and Global Privacy Control keep optional analytics disabled. Essential payment reconciliation and security controls operate independently of analytics.

Optional streaming players

Allowing embedded media enables Twitch, Kick and independent Owncast players. They may use cookies, local storage and other identifiers under their own policies. Their storage lifetimes vary and are not set by Who to Follow. Players are isolated in frames; rejecting media prevents those frames loading. Remote images still contact their image hosts, and external links work without embedded-media consent.

See Twitch privacy and Kick privacy. Independent broadcasters have their own policies.

Change or withdraw

Use Privacy preferences in every page footer to reject or change optional choices. Turning players off removes the active frames and closes our picture-in-picture windows. New optional analytics stop. The choice is shared with other open same-origin tabs where the browser supports it and rechecked when returning to a tab.

No optional first-party analytics identifiers are stored to clear. We keep the necessary rejection preference so you are not asked on every page. We cannot delete another domain’s cookies; clear them in your browser if wanted. If your browser blocks preference storage, optional features remain off.

Advertising and native apps

The website currently has no active AdSense script or advertising storage. Advertising needs its own approved consent setup before activation. Native media consent uses a device preference with a 180-day validity period; it is separate from this browser choice. Native app guest saves and hidden-creator preferences stay on the device until you choose to import them. Signed-in saves, collections and hidden preferences sync through your account. The app stores encrypted account caches and local import acknowledgements; Google consent choices remain separate from this browser. See the app privacy information.