Cookie Policy

Solo Clash L.L.C-FZ (Meydan Free Zone, Meydan Grandstand, 6th Floor, Meydan Rd, Nad Al Sheba 1, Dubai, UAE; license: 2538558.01) explains its cookie usage on soloclash.com. This policy should be read alongside the Privacy Policy. Cookies that are not strictly necessary are set only after you accept them in the cookie banner, and you can change that answer at any time (see section 6).

Cookies are small text files placed on your device when you visit a website, enabling the website to recognise your device and store information. Types include:

• Session Cookies — expire when the browser closes.
• Persistent Cookies — remain for specified periods.
• First-party Cookies — set by the Company.
• Third-party Cookies — set by external providers.

The Site uses three groups of cookie, and one choice in the banner controls the third:

• Strictly Necessary Cookies — required for the Site to function, to record the cookie choice itself, and to keep Company staff signed in to the internal content tools. These cannot be switched off.
• Preference Cookies — remember the language you selected so you return to it.
• Analytics and Advertising Cookies — set only after you accept them, and used to understand how the Site performs and which of our adverts brought you here. Four of them: Google Analytics, the Meta (Facebook and Instagram) advertising pixel, PostHog, which measures how the plan and advert pages themselves are read, and our own sc_journey, which links the pages of a visit that arrived through one of our campaign links.

The banner is a single choice rather than a set of category switches. Accept, and analytics and advertising storage are enabled together. Decline, and the Site runs on strictly necessary and preference cookies alone.

The Company sets no advertising cookies of its own. Accepting does allow one advertising provider, Meta, to set its cookies so the Company can measure which of its adverts led to a visit; those cookies can be used by Meta to recognise the same browser on other sites carrying its pixel, which is why they are set only with your consent and are deleted when you withdraw it. The cookies in use are:

• cookieConsent (first-party, 1 year) — your answer to the banner, so you are not asked again and so the Site knows whether the analytics and advertising scripts may load.
• sc_locale (first-party, 1 year) — the language you last selected.
• Sign-in session cookies (first-party, up to 30 days, names beginning soloclash or __Secure-soloclash) — issued only on signing in to the Company's internal content tools, which is limited to Company staff. The Site has no public account area, so an ordinary visitor never receives these. They cannot be read by scripts in your browser. Signing in also writes one entry to the browser's local storage so that signing out in one tab signs out the others.
• _ga and _ga_* (Google Analytics, expiry set by Google, typically up to 2 years) — set only after you accept analytics.
• _fbp and _fbc (Meta, 90 days) — set only after you accept, and only once you open one of the landing pages our adverts link to. _fbp holds a random identifier for this browser; _fbc holds the click identifier carried by an advert you followed here. Together they let Meta report which adverts led to a visit. Declining, or withdrawing later, deletes both.
• ph_*_posthog (first-party, 1 year) — set only after you accept, and only once you open the accounts page or one of the landing pages our adverts link to. It holds a random identifier for this browser and the reference of the current visit, so that the pages of one visit can be read as one visit. It is stored twice, as a cookie and as one matching entry in your browser's local storage; declining, or withdrawing later, deletes both.
• sc_journey (first-party, 30 days) — set only if you accept analytics and arrived through one of our own campaign links. It holds a random identifier and nothing else, no name, no email, no campaign detail. It lets us see which pages you visited before choosing a plan, so we can tell which of our own emails and posts are worth sending. It cannot be read by scripts in your browser, it is never shared, and withdrawing your consent deletes both the cookie and everything recorded under it.
• intercom-id-*, intercom-session-* and intercom-device-id-* (Intercom) — the support chat, so a conversation can continue when you come back. Lifetimes are set by Intercom: the session cookie lasts about a week, the others up to several months. The chat also keeps one entry in your browser's local storage to remember whether its window was open. See section 4.

The network that delivers the Site may also set short-lived security cookies of its own (for example __cf_bm) to tell real visitors from automated traffic, as may Cloudflare Turnstile, the anti-spam check that runs when you submit one of our forms. These are security measures, are set before any choice in the banner can apply, and cannot be switched off.

Four third parties can set cookies through the Site:

• Google Analytics — loads wherever it is configured for the Site, but its consent signals start at denied, so it stores nothing on your device until you accept. Accepting enables Google's analytics and advertising storage signals together, because the banner is one choice; declining, or withdrawing later, returns them to denied and removes the Google Analytics cookies already on your device.
• Meta— provides the advertising pixel that measures the Company's Facebook and Instagram campaigns. Unlike Google Analytics it is not loaded at all until you accept: while the banner is unanswered or declined, nothing is requested from Meta and no identifier of yours reaches it.

  It is loaded on one kind of page only: the landing pages the Company's adverts link to. Everywhere else on the Site — the home page, the accounts page, the blog, these policies — the pixel is not loaded, sets nothing on your device and is sent nothing, whatever you answered on the banner.

  On an advert landing page it records that you opened it, and a small, fixed set of things you did there: that you read it (measured as ten seconds on screen, or scrolling half way down), that the list of plans came into view, that you played or finished the trader video, that you moved through the payout certificates, and that you followed a checkout link away from the Site. The checkout event carries which plan you chose and its price. None of these carry your name, your email address or your telephone number: the pixel feature that would collect those from forms on the page is switched off in the Company's installation, and no other event on this Site sends them.

  Each of those events is sent twice, once by your browser and once by the Company's own server, and both copies carry the same reference so Meta discards the duplicate and counts one. The server copy exists because browsers and privacy extensions frequently block the first, which would otherwise leave the Company unable to tell which adverts worked. It is sent from the Company's server rather than yours and therefore also carries your IP address, your browser's user-agent string and the values of the two Meta cookies described in section 3. It is sent only while your consent stands, is not stored by the Company, and stops the moment you withdraw.

  Meta decides on its own account what it does with what it receives and may connect it to an account you hold there, so its privacy policy governs that use. Withdrawing your consent stops both copies and deletes its cookies.

• PostHog— measures how two kinds of page are read: the accounts page, and the landing pages the Company's adverts link to. It is not loaded anywhere else on the Site, and like the Meta pixel it is not loaded at all until you accept.

  On both of those, it records which of them you opened, where you clicked and moved the pointer, and how far down you scrolled. Those are combined with everyone else's into a heat map of the page: the Company sees where a page is read and where it is abandoned, not who did the reading.

  On the advert landing pages only, it additionally records the visit itself, so that it can be replayed: the page as your browser drew it, and the pointer movement, clicks and scrolling on top of it. Anything you type is masked before it leaves your browser and is never transmitted, so the recording shows that a field was filled in but not what was put in it. The Company's installation is configured to discard the IP address of everything it receives, and no name, email address or telephone number is ever attached to a recording. Recordings are deleted automatically after 30 days; the other measurements are kept for 12 months.

  The data is held in PostHog's European infrastructure and is governed by its privacy policy. Withdrawing your consent stops the recording at once, stops all of the above, and deletes what PostHog stored on your device.

• Intercom — provides the support chat. The Company treats reaching a person as part of the service this Site exists to offer, so the chat loads on every page rather than waiting for an answer in the banner, and its cookies are not governed by the analytics choice. Intercom offers no setting that keeps the chat working without them: it either runs and stores an identifier, or is switched off entirely. If you would rather not have them, you can block them in your browser, or reach us through the contact form or [email protected] instead, neither of which stores anything on your device.

Purchases are completed on a payment provider's own site rather than on this one. Once you follow a checkout link away from the Site, that provider's cookies and privacy policy govern what happens there.

The Company accepts no liability for their use and directs users to review each provider's privacy policy.

Strictly necessary cookies are required to provide a service you have requested and cannot be disabled. Preference cookies store a setting you chose yourself. Analytics and advertising cookies rely on your consent, which you may withdraw at any time and as easily as you gave it, using the controls in section 6. Withdrawing does not merely stop future collection: the Google Analytics, Meta and PostHog cookies already on your device are deleted, along with the local storage entry PostHog keeps beside its own; the Meta pixel is signalled to stop and the Company's server stops sending its copy of any event; any recording in progress ends at that moment; and the sc_journey cookie is deleted along with every page view recorded under it.

The banner appears on your first visit. Afterwards, Cookie Preferences in the footer of every page reopens it, so you can change or withdraw your answer at any time. A change applies from the moment you make it.

Your browser settings can also block or delete cookies, including the ones described as strictly necessary. Blocking those will stop the Site from remembering your answer to the banner, so it will ask again on every visit. Declining analytics and advertising, or withdrawing later, changes nothing else about how the Site works.

Separately from cookies, the Company measures how its pages and campaigns perform without using any cookie, local storage, or other identifier stored on your device. That measurement is described in sections 5, 7 and 9 of the Privacy Policy, and it honours the Global Privacy Control and "Do Not Track" signals your browser can send.

The cookies described in section 3 store a preference, a session reference, an analytics identifier, or an advertising identifier. They do not store your name, email address, or payment details.

Where the Site records how a page was used, it derives coarse information from the request (approximate country from the network, device category, and language) and stores an identifier derived by irreversible hashing that changes every day. Your IP address and browser user-agent string are used to produce that identifier and are not stored alongside it.

Each cookie in section 3 states its lifetime. The Company sets no session-only cookies of its own: every first-party cookie above has an explicit lifetime, and the longest of them is one year. Cookies set by Google Analytics follow Google's own expiry, typically up to two years, and Meta's expire 90 days after they are set or last refreshed. Any cookie can be deleted from your browser at any time.

A journey recorded under sc_journey is deleted in full 30 days after it began, whether or not the cookie is still on your device. Retention of the measurement records described in section 7 is set out in section 9 of the Privacy Policy.

Policy amendments take effect upon publication on the Site. Continued use of the Site after amendments constitutes acceptance.

This Policy is governed by Dubai International Financial Centre (DIFC) and applicable UAE law, with exclusive DIFC court jurisdiction for any dispute.

For questions about this Policy: [email protected]