Cookie Policy
Last Updated: June 25, 2026
Flynk AI LTD ("Flynk AI", "we", "us") operates Cite42, a pay-per-call AI search visibility API and MCP server. This Cookie Policy explains the limited set of cookies and similar technologies used on our website and dashboard (the "Service") and how you can manage them. It supplements our Privacy Policy.
What are cookies?
Cookies are small text files placed on your device by a website. They allow the site to recognize your browser, remember preferences, keep you signed in, and gather usage information. A "session" cookie is deleted when you close your browser; a "persistent" cookie remains for a set period or until you delete it. We may also use functionally similar technologies (such as local storage); references to "cookies" in this policy include those technologies where relevant.
Our approach
Cite42 uses the minimum number of cookies needed to run a paid API product securely, plus optional analytics, marketing, and preference cookies that we set only with your consent. We currently use Google Analytics (via Google Tag Manager) to understand aggregate site usage. We do not currently run Meta Pixel, Hotjar, Contentsquare, or similar advertising or session-replay tools, but if we introduce them we will place them in the appropriate consent category, disclose them in this policy, and keep them blocked until you consent where consent is required.
Cookies we use
| Cookie | Purpose & Category | Provider | Duration |
|---|---|---|---|
| __client (essential) | Authentication token that keeps you signed in across visits to the Cite42 dashboard. | Clerk (Clerk, Inc.) | Persistent (up to 12 months; cleared on sign-out) |
| __client_uat (essential) | Tracks whether your authenticated session is still valid; updated when the session changes. | Clerk (Clerk, Inc.) | Persistent (updated periodically) |
| __session (essential) | Short-lived JWT cookie used to validate requests within an active session. Works with __client to keep you securely signed in. | Clerk (Clerk, Inc.) | ~60 seconds (continuously refreshed) |
| __stripe_mid / __stripe_sid (essential, when checking out) | Fraud prevention during credit top-up checkout. Set only on pages that load Stripe Checkout or Elements. | Stripe | __stripe_mid: 1 year. __stripe_sid: 30 minutes. |
| flk_consent (essential) | Records your cookie-banner choice (which categories you accepted) so we don't ask again on every page. | Flynk AI (first-party) | 180 days |
| _ga (analytics: consent required) | Distinguishes unique visitors to measure aggregate site usage. Set only after you accept analytics cookies in our banner. | Google Analytics (via Google Tag Manager) | 2 years |
| _ga_<container> / _gid (analytics: consent required) | Used by Google Analytics to persist session state and distinguish visitors. Set only after you accept analytics cookies. | Google Analytics (via Google Tag Manager) | _ga_<container>: 2 years. _gid: 24 hours. |
| _gcl_* / _fbp (marketing: not currently active) | Reserved for advertising conversion measurement, retargeting, or campaign attribution if we enable Google Ads, Meta Pixel, or similar tools in the future. These cookies are not currently set by Cite42. | Google Ads, Meta, or similar marketing providers | Provider-dependent; disclosed here before activation. |
| locale / theme (preferences: not currently active) | Reserved for optional site preferences such as language, region, or theme if we add them in the future. These cookies are not currently set by Cite42. | Flynk AI (first-party) | Up to 12 months if activated. |
Notes.
- The Clerk authentication cookies do not store your email or name in plain text. They contain encrypted tokens. They are strictly necessary: without them the dashboard cannot sign you in or keep you signed in.
- The Stripe cookies are placed by Stripe when you load a checkout page to top up credits. They are set for the limited purpose of fraud detection during the payment flow. If you never top up credits, they are never set. Stripe's own cookie practices are described at stripe.com/cookies-policy/legal.
- Marketing and preference categories are available in the consent banner so you can make a granular choice if we add those tools later. We do not currently set the listed marketing or preference cookies.
Global Privacy Control and Browser Signals
We honour Global Privacy Control (GPC) signals to the extent applicable: if your browser sends a GPC signal, we treat it as opting you out of non-essential analytics and marketing cookies where those categories are offered. Some browsers also offer Do Not Track (DNT) settings; because DNT is not implemented consistently across browsers or websites, you should use our cookie preferences control or your browser's cookie settings to manage non-essential cookies. We do not change the behaviour of strictly necessary cookies, which are required regardless of these signals.
Managing cookies in your browser
Every major browser lets you view, delete, and block cookies:
- Chrome: Settings → Privacy and security → Cookies and other site data.
- Firefox: Settings → Privacy & Security → Cookies and Site Data.
- Safari (macOS): Settings → Privacy → Manage Website Data.
- Safari (iOS): Settings → Safari → Privacy & Security.
- Microsoft Edge: Settings → Cookies and site permissions.
Updates to this policy
We will update this Cookie Policy when we add or remove a cookie, change a provider, or change our cookie practices. The "Last Updated" date at the top reflects the most recent change. For material changes, particularly the introduction of non-essential cookies, we will notify you in-product before they take effect.
Contact
Questions about cookies: support@cite42.dev. Company details and postal address are on the Legal Notice page.