Cookie Policy
Last updated: November 21, 2026
This page shows the cookie section of our Privacy Policy.
7. Cookies and Tracking Technologies
7.1 What We Use
| Cookie/Technology | Type | Purpose | Duration |
|---|---|---|---|
| Session cookie | Essential | Authentication and session management | Session |
| CSRF token | Essential | Security (cross-site request forgery protection) | Session |
| Preferences | Functional | Remember your settings (theme, timezone) | 1 year |
| Cookie consent | Functional | Remember your cookie preference | 1 year |
fanflet_vid | Performance | First-party unique-visitor identifier for Speaker analytics and program reporting (see the pseudonymous activity record in Section 5). Set only when analytics cookie consent is granted (or where consent is not required). Not used for advertising | 365 days |
| Analytics events | Performance | Server-side event tracking for usage analytics | Event detail: 37 months, removed with that month's records. Unique-visitor key and pseudonymous activity record: until the Speaker or fanflet is deleted (a Sponsor's copy: see Section 5) |
| Google Tag Manager | Analytics | Site traffic on Fanflet's own marketing pages and the ad landing page. Loaded only after cookie consent where a choice is required. Not loaded on a speaker's public pages, audience pages, or signed-in dashboards | Varies |
Meta pixel (_fbp, _fbc) | Advertising | Set by the Meta (Facebook) pixel, which Google Tag Manager loads. _fbp identifies your browser to Meta. _fbc holds the ad click identifier and is set only when you arrive from a Meta ad. See Section 7.2 | 90 days (set by Meta) |
ff_attrib | Analytics | First-party record of how you first reached Fanflet (landing page, referring site, campaign tags). Also holds the Facebook ad click identifier (fbclid), only when cookie consent is granted (or where consent is not required) | 30 days |
ff_new_account | Advertising | Set only when a new account is created through Google sign-up and cookie consent is accepted. Used once to tell Meta that an account was created, then deleted. Holds the value 1 and nothing about you | Up to 1 hour |
7.2 Third-Party Analytics and Advertising Cookies
Fanflet uses Google Tag Manager (GTM) to analyze traffic on our marketing pages and understand how visitors interact with the site. GTM may set third-party cookies from Google Analytics and related services.
GTM also loads the Meta (Facebook) pixel. We advertise Fanflet on Facebook and Instagram, and the pixel tells Meta about visits to our site. It sends Meta the address and details (such as the title) of the page you viewed, what you did there (a page view, a button you clicked, a form you submitted on an ad landing page, a Fanflet account you created, or a trial checkout you completed), the pixel's cookies (_fbp, and _fbc when you came from a Meta ad), your IP address and browser details. Account creation and trial checkout are reported for any visitor who has the pixel loaded, not only visitors who came from an ad. Meta uses this to measure our ads and to decide who sees them. We do not send your name or email address to Meta through the pixel.
When you arrive from a Meta ad, we also keep the ad click identifier (fbclid) in our own ff_attrib cookie. We keep it only if you have accepted cookies or no consent is required for you, as described below.
For users in the United States and Canada, we show the cookie banner on Fanflet's own marketing pages, sign-in pages, and sign-up pages, and we load Google Tag Manager and the Meta pixel only if you accept. On the ad landing page (/start), those tags load when your choice is saved as accepted, which happens automatically in the United States and Canada. On a speaker's public pages, audience pages, and signed-in dashboards, Google Tag Manager and the Meta pixel do not load. US and Canadian law does not currently require opt-in consent for analytics cookies.
For users outside the United States and Canada, Google Tag Manager and the Meta pixel stay blocked until you accept through our cookie banner, and they load only on Fanflet's own marketing pages and the ad landing page. If you decline, those tags do not load. Product analytics (PostHog) follows the same cookie choice. Our server-side analytics and Vercel Analytics continue to operate regardless of your choice.
7.3 What We Do Not Use
- Other than the Meta (Facebook) pixel described in Section 7.2, we do not use third-party advertising cookies or cross-site tracking pixels
- Other than advertising Fanflet through Meta (Facebook), we do not participate in ad networks or retargeting programs
7.4 Your Choices
Essential cookies are required for the Services to function.
You can change your cookie choice at any time, in any country, with the Cookie Preferences link in the footer of our marketing pages (including this page) and of public fanflet pages. It reopens the cookie banner. You can accept analytics, advertising, both, or neither. If you turn advertising off, GTM and the Meta pixel are no longer loaded on later visits in that browser. They may keep running on the page you have open until you reload or close it. Turning a category off does not delete cookies that were already set (for example _fbp, _fbc and ff_attrib); you can delete them in your browser settings.
If you previously accepted or declined analytics cookies, you can also clear the cookie_consent cookie from your browser to reset your preference. If the cookie banner applies to you (see Section 7.2), you will see it again on your next visit.
Questions about this policy? Contact us or email support@fanflet.com.