Last updated: October 3, 2026
1. About this notice
This notice explains how Tribl AB ("TRIBL", "we") uses cookies and similar technologies on tribl.app, including our blog at tribl.app/blogs. For how we handle personal data in general, see our Privacy Notice. Questions: info@tribl.app.
Cookies are small text files that a website stores in your browser and reads back on later visits. Local storage and session storage are similar: they keep data in your browser, but only the website that wrote it can read it, and it is not sent with every request. Session storage is cleared when you close the tab. A cookie is first party when it is set on tribl.app, and third party when it is set on another company's domain (for example facebook.com) while you are on our site.
Under the Swedish Electronic Communications Act (lagen om elektronisk kommunikation) and the GDPR, we may only store or read information on your device without your consent when it is strictly necessary to provide a service you asked for. Everything else needs your consent first.
2. How your consent works
- On your first visit we show a banner with three categories: strictly necessary (always on), analytics and marketing. You can accept all, reject all, or choose per category. Rejecting is as easy as accepting.
- Nothing in the analytics or marketing categories is loaded before you choose. Google tags start in Google Consent Mode (version 2) with analytics storage, ad storage, ad user data and ad personalisation all set to "denied", and ad data redaction switched on. When you consent, we update those signals to match your choice.
- Google Analytics, Google Ads, Microsoft Clarity and the TikTok, X and Quora pixels are all loaded through one Google Tag Manager container. The TikTok Pixel does not respect Google Consent Mode, so we only load Google Tag Manager when you have accepted both analytics and marketing. If you accept only one of the two, none of those tools are loaded.
- The Meta Pixel is loaded separately, and only when you accept marketing.
- We store your choice in a first-party cookie called
tribl_consent, together with a random ID, the date of your choice and the version of this policy. It lasts 182 days (about 6 months), after which we ask again. We also ask again sooner if we add a new purpose or provider that your earlier choice did not cover. The choice is kept only in your browser; we do not send it to any third party. - You can change or withdraw your consent at any time via here or in the footer of every page. When you withdraw a category, we delete that category's cookies on tribl.app and reload the page so the tools stop running. We cannot delete cookies that other companies have set on their own domains; you can remove those in your browser.
- You can also block or delete cookies in your browser settings. If you block strictly necessary cookies or local storage, parts of TRIBL, such as signing in or paying, will not work.
3. Strictly necessary (always on)
These make the site work and keep it secure, so they do not need your consent. Unless marked otherwise, the TRIBL items are kept in your browser's local storage.
| Name | Provider | First / third party | Purpose | Duration |
|---|---|---|---|---|
tribl_consent (cookie) | TRIBL | First party | Remembers your cookie choices (see section 2) | 182 days |
token, pre-token, fanToken, fanEmail, username | TRIBL | First party | Keeps you signed in as a Creator or Fan | Until you sign out; the sign-in itself expires after 24 hours |
tribl.kyc.resume (session storage) | TRIBL | First party | Remembers where you were in a payout when you leave TRIBL to verify your identity, so you can continue when you come back | Until the tab is closed |
signup-info, signupfullinfo, signupProfileInfo, imageinfo, signup-pic, signup-pic-value, comingFromSigninPreRegister, email | TRIBL | First party | Remembers what you entered while you create an account or reset your password, such as your username, email address, name and chosen profile photo, so you don’t lose your progress between steps | Stays in your browser until TRIBL clears it (on completing signup or signing in again) or you clear your browser data |
otpExpiry, withdrawOtpExpiry | TRIBL | First party | Times the verification codes we send you by email or SMS | Until the code expires |
gift_cart_items, success-cartItems, transactionId, totalAmount | TRIBL | First party | Keeps your gift basket and the status of your payment | Until checkout is completed or you clear it |
b | TRIBL | First party | Remembers that an account has been restricted, so the right message is shown | Until you sign out |
consent, focusFeature, fromMembership, profileEditPicture | TRIBL | First party | Interface state, e.g. that you confirmed you are 18 or over, or which screen to return to | Until cleared |
__stripe_mid, __stripe_sid | Stripe | First party (set by Stripe’s script) | Fraud prevention for card payments. Set by Stripe’s script, which is loaded on Creator pages, the gift checkout and the Creator earnings pages | 1 year / 30 minutes |
_GRECAPTCHA | Google (reCAPTCHA) | Third party (google.com) | Protects the Creator signup form against bots. Only loaded on the signup page | 6 months |
_grecaptcha (local storage) | Google (reCAPTCHA) | First party (set by Google’s script) | Stores reCAPTCHA’s risk-analysis data on the signup page | Until cleared |
Some steps take you to another company's page, which may set its own necessary cookies there under its own policy: the identity verification page of Didit, the Google or Apple sign-in page and Stripe's payment pages.
4. Analytics (only with your consent)
These help us understand how visitors use TRIBL so we can improve it. They are loaded through Google Tag Manager, which itself does not set cookies. Because Google Tag Manager also carries our marketing tags, it only loads when you accept both analytics and marketing (see section 2). This means that if you accept analytics alone, no analytics tools are loaded at the moment. We use two Google Analytics 4 properties. Microsoft Clarity records how pages are used (clicks, taps, scrolling and mouse movement) to produce heatmaps and session replays; it masks text you type into forms.
| Name | Provider | First / third party | Purpose | Duration |
|---|---|---|---|---|
_ga | Google Analytics | First party | Distinguishes visitors | 2 years |
_ga_0Z19Y2V9VH, _ga_WBE0J0F01G | Google Analytics | First party | Keeps track of your session for each of our two Analytics properties | 2 years |
_clck | Microsoft Clarity | First party | Recognises your browser across visits and stores Clarity settings | 1 year |
_clsk | Microsoft Clarity | First party | Joins page views into one session recording | 1 day |
CLID | Microsoft Clarity | Third party (clarity.ms) | Records when Clarity first saw your browser on any site | 1 year |
MUID, MR, SM, ANONCHK | Microsoft | Third party (clarity.ms, bing.com) | Identifies your browser across Microsoft sites and keeps that ID in sync (Clarity does not use it for advertising) | MUID 1 year, MR 7 days, SM session, ANONCHK 10 minutes |
5. Marketing (only with your consent)
These measure how well our ads work and let us show TRIBL ads to people who have visited the site. The Meta Pixel loads when you accept marketing, even if you reject analytics. Google Ads and the TikTok, X and Quora pixels run inside Google Tag Manager, so they load only if you accept both analytics and marketing: if you accept marketing alone, only the Meta Pixel is loaded. We use three TikTok Pixels.
| Name | Provider | First / third party | Purpose | Duration |
|---|---|---|---|---|
_fbp | Meta (Facebook / Instagram Pixel) | First party | Recognises your browser so visits can be linked to our ads | 90 days |
_fbc | Meta | First party | Stores the ad click that brought you here (only set when you arrive from a Meta ad) | 90 days |
fr | Meta | Third party (facebook.com) | Ad delivery and measurement for Meta account holders | 90 days |
_ttp, _tt_enable_cookie | TikTok Pixel | First party | Recognises your browser so visits can be linked to our TikTok ads; checks that cookies can be set | 13 months |
ttcsid, ttcsid_<pixel ID>, ttclid | TikTok Pixel | First party | Session and ad-click identifiers used by newer versions of the TikTok Pixel (ttclid only when you arrive from a TikTok ad) | 13 months |
_gcl_au | Google Ads | First party | Links conversions on TRIBL to our Google ads | 90 days |
_gcl_aw | Google Ads | First party | Stores the ad click that brought you here (only set when you arrive from a Google ad) | 90 days |
_twpid, _twsid | X (Twitter) Pixel | First party | Recognises your browser so visits and signups can be linked to our ads on X | 13 months |
| Cookies on x.com, twitter.com and t.co | X | Third party | Set by X on its own domains when the pixel reports a visit, for ad measurement | Set by X; see its privacy policy |
| Cookies on quora.com | Quora Pixel | Third party | The Quora Pixel stores nothing on tribl.app; Quora may use cookies on its own domain to link the visit to its users and our ads | Set by Quora; see its privacy policy |
Meta, TikTok, Google, X and Quora may combine this data with other information they hold about you, under their own privacy policies: Meta, TikTok, Google, X, Quora. For the part of the processing where we decide together with Meta, TikTok, X or Quora how the data is collected, we act as joint controllers with them; see the Privacy Notice.
6. Things that don’t store anything but do see your IP address
Loading some parts of TRIBL makes your browser contact other companies directly. They do not set cookies on tribl.app, but they receive your IP address and basic browser information, as with any web request. These are strictly necessary for the feature you use and are described in the Privacy Notice:
- IP lookups with ipinfo.io, api.ipify.org and jsonip.com, used to show prices and forms for your country, to detect fraud at checkout and to give Creators anonymous country and city statistics about their visitors.
- Images and videos uploaded to TRIBL, served from Amazon Web Services.
- On media kits, thumbnails of a Creator's posts loaded from Instagram, TikTok and YouTube.
- Country flag images from flagcdn.com, GitHub Pages and Wikimedia, and gift-card images from Reloadly.
- Tools used by Creators in their dashboard: emoji images from the jsDelivr network, and the Beefree email editor, which is loaded from Beefree's servers (getbee.io).
7. Changes
We update this notice when we change the cookies or similar technologies we use, and change the "Last updated" date above. If we add a new optional purpose or provider, we will ask for your consent again.