Cookie Policy

TokLab (toklab.ai) uses cookies and browser storage for sign-in, preferences, advertising measurement and site analytics. Google Ads, Pageview, Rybbit and Cloudflare Web Analytics load automatically. X advertising measurement also loads automatically when enabled for the site, unless you have turned it off in X privacy choices. There is no site-wide consent banner; X privacy choices only controls X. We do not sell what we store.

What we set

• Session cookie. Set when you sign in, so the site knows you are you on the next request. Without it you cannot stay signed in. It is removed when you sign out.
• Language cookie. Remembers which language version of the site you are reading.
• Theme preference. Remembers whether you chose the light or dark theme. This one is stored in your browser's local storage rather than a cookie, and never leaves your device.

Advertising and site analytics

• Google Ads. The Google tag loads automatically, without waiting for an X setting. It measures visits and advertising conversions and may use cookies and browser identifiers. For registration and purchase conversions, our code also supplies account email and, when available, name to the Google tag for enhanced conversions. Purchase events can include the transaction identifier, amount and currency.
• Pageview. Its analytics script loads automatically and sends page views, page addresses and referrers to measure site traffic.
• Rybbit. Its analytics script loads automatically to measure visits and interactions, using page/referrer information, browser information and visitor identifiers. Its script can use browser storage.
• Cloudflare Web Analytics. The Cloudflare beacon loads automatically to measure traffic and page performance.

These services receive browser and network information when contacted. Their storage and processing are governed by their respective policies. Turning X off does not disable Google Ads, Pageview, Rybbit or Cloudflare Web Analytics.

X advertising measurement

When enabled for the site, the X Pixel loads automatically and measures visits, new accounts, API key creation and confirmed Stripe or PayPal top-ups. X receives an opaque conversion ID, the X click ID when available, and the actual amount and currency for a paid top-up. X also receives browser and network information when its script loads. We do not send email addresses, phone numbers, prompts, generated content or API keys through this integration.

While X tracking is active, we store a random tracking identifier and the campaign identifiers twclid, utm_source, utm_medium, utm_campaign and utm_content in first-party cookies for up to 30 days. Campaign information is saved while X tracking is active. Server-side conversion receipts link this source to the account or checkout and remain with the account until deletion. A short-lived registration receipt lasts 10 minutes. Browser storage also keeps opaque IDs to prevent duplicate events. X may set its own attribution cookies while measurement is active.

When you turn X off, we request a 400-day lifetime for the opt-out cookie and also save the choice in local storage. If the cookie expires while the saved choice remains, X stays off. You can explicitly turn it back on. If both copies are cleared, or you use another browser or device, we cannot recover that choice and the site's default applies.

Use X privacy choices on any page to turn X measurement off or back on. Turning it off clears our campaign cookie, stops new X events and reloads the page to stop the loaded X script. Activity while X tracking is off is not replayed. Data already sent cannot be recalled by the browser. Blocking cookies or ads may prevent measurement but does not prevent registration, API key creation or payment.

Third parties

Our payment processor may set its own cookies on the hosted checkout page while you are paying. That page is theirs, not ours, and its cookies are covered by its own policy.

Controlling cookies

You can delete cookies or block them in your browser settings. Blocking the session cookie means you will not be able to sign in, but the public pages of the site will still work.

Changes

If this policy changes we will post the new version here and update the date at the top of this page. Questions go to [email protected].