1. What these technologies are
Cookies are small values a website asks a browser to store. Local storage performs a similar browser-side function. Fader Club also uses server logs, privacy-preserving analytics, and embedded media requests. This notice covers those technologies because they can remember a choice, maintain a session, attribute a referral, secure the service, or measure product use.
2. Strictly necessary storage
Authentication and security storage keeps you signed in, refreshes an authorized session, protects account routes, and supports fraud and abuse controls. The platform cannot provide signed-in functionality without it. These values are not used for advertising. Logging out, account security events, or browser expiration may remove or replace them.
3. Preferences and local storage
Fader Club may remember language, appearance, interface state, and separate product-analytics and advertising choices on the device. Each preference records only granted or denied. The advertising choice is also mirrored in a first-party SameSite=Lax cookie so the server can honor it. Clearing site data removes local preferences and may cause the platform to ask again. The preference values themselves are not used to build an advertising profile.
4. Affiliate referral attribution
When you open an approved affiliate link, Fader Club may store a signed referral value for up to 30 days. The current model attributes an eligible purchase to the most recent valid referral. The value supports commission attribution and anti-manipulation checks; it is not used for cross-site advertising. Blocking or clearing it may prevent attribution without preventing a direct purchase.
5. Vercel Web Analytics
Fader Club may use Vercel Web Analytics for aggregate page and performance totals. According to Vercel's current product documentation, it does not use cookies, does not retain IP addresses for this analytics purpose, and reports aggregated data that is not linked to an identifiable end user. Fader Club does not send names or email addresses as custom analytics properties.
6. Optional PostHog and Meta measurement
PostHog starts only after separate product-analytics consent and may receive pathname-only page views, selected product events, a pseudonymous account identifier after sign-in, aggregate click or scroll positions, and masked session replay. Creator-owned Meta Pixel and Meta Conversions API start only after separate advertising consent and measure visits, course or product views, checkout, and payment-confirmed purchases for advertising performance and remarketing. Fader Club does not use one global creator-sales Pixel: an event is sent only to the active dataset selected by the relevant course or product creator, and mixed-creator commerce events are separated by destination. That creator and Meta may access the event in Meta business tools; generic pages, another creator's catalog, and another creator's attributed value are not sent to that dataset. Meta Pixel may set the first-party _fbp and _fbc identifiers. Server events may include normalized email or phone transformed with SHA-256 when available; hashing does not make that data anonymous. To enforce withdrawal, Fader Club keeps a service-only pseudonymous consent-authority record containing a random consent ID, version, status, and timestamps for up to 400 days; after withdrawal, it is retained solely as a technical tombstone that prevents delayed requests from restoring consent and is not sent to Meta. Temporary consent and Meta browser identifiers stored with an order are kept for at most seven days and removed earlier after successful Purchase delivery or withdrawal. To prove that a browser AddToCart event followed a successful cart change, the service keeps a user-bound one-time receipt tied to the account, product, event ID, destination, and pathname; it is valid for up to ten minutes and consumed on first use. URLs sent for either category are limited to the site origin and pathname, without queries or fragments. Declining or withdrawing a category stops its future optional collection; withdrawing Meta consent also removes accessible _fbp and _fbc cookies and cancels unsent events. Disconnecting a creator integration deletes the retained token but does not automatically erase data already delivered to Meta. The roles of Fader Club, the relevant creator, and Meta, international transfers, rights routing, and provider/account retention settings require final contractual and legal review before commercial activation.
7. Third-party media
A creator profile may contain an embedded SoundCloud player or another approved media integration. Loading or playing that content connects your browser directly to the third-party provider, which may receive technical request data and apply its own storage under its terms and privacy policy. Fader Club does not use that provider response for cross-site advertising. Avoid loading embedded media if you do not want to contact the provider.
8. Managing choices and updates
Use the two independent controls on this page to allow or decline optional PostHog product analytics and Meta advertising. Consent is optional and may be withdrawn for future processing at any time. Browser settings can remove or block cookies and local storage, but blocking strictly necessary storage can prevent sign-in or protected access. Material changes to analytics or advertising purposes or technologies will be reflected here and may trigger a renewed choice. Privacy rights and contact instructions are in the Privacy Policy.