Cookie Policy

This Cookie Policy explains how Coinrule Limited, hereinafter also referred to as “Coinrule” or “we/us/our”, uses cookies and similar technologies on our website coinrule.com (the "Website") and in our software (the "Software"), what they do, and how you can control them.
9 October 2026 Coinrule Limited
1
What are cookies?

This Cookie Policy forms part of our Privacy Policy and our Terms & Conditions of Use. Where cookies collect personal information, that information is processed as described in the Privacy Policy.

You can review or change your cookie choices at any time:

A "Cookie Settings" link is also available in the footer of every page.

  1. What are cookies?

  • 1.1
    Cookies are small text files that are placed on your computer or mobile device when you visit a website. They are widely used to make websites work, to make them work more efficiently, to remember your preferences and to provide reporting information to the website owner.
  • 1.2
    Cookies set by Coinrule are called "first-party cookies". Cookies set by parties other than Coinrule are called "third-party cookies". Third-party cookies enable third-party features or functionality to be provided on or through the Website, such as analytics and advertising measurement. The parties that set third-party cookies can recognise your device both when it visits the Website and when it visits certain other websites.
  • 1.3
    Cookies may be "session" cookies, which are deleted when you close your browser, or "persistent" cookies, which remain on your device until they expire or you delete them. In this Policy, "cookies" also refers to similar technologies such as pixels, web beacons, local storage and session storage, which are described in Section 7.
  • 1.4
    Scope. This Policy applies to the Website (coinrule.com and its subdomains) and the web application at web.coinrule.com. Our iOS and Android applications do not use browser cookies; the device identifiers, software development kits and push notification tokens they use are described in Section 4.10.4 of our Privacy Policy. Our API and MCP server set no cookies; access through them is authenticated by credentials as described in Section 4.10.5 of our Privacy Policy.

  2. How we use cookies

  • 2.1
    We group the cookies used on the Website into three categories:
    • 2.1.1
      Strictly necessary cookies: required for the Website and the Software to operate, including security, bot protection, load balancing, authentication, session handling, referral-programme attribution and remembering your cookie choices. These cookies cannot be switched off and do not require your consent (Section 4).
    • 2.1.2
      Analytics cookies: help us understand how visitors use the Website and the Software, which pages and features are used, and where errors occur, so that we can improve them. These are set only with your consent (Section 5).
    • 2.1.3
      Marketing cookies: set by our advertising partners to measure the performance of our campaigns and show you relevant advertising on other websites. These are set only with your consent (Section 6).
  • 2.2
    We do not use cookies to collect special category data, and we do not sell cookie data. Where cookie data is "shared" for cross-context behavioural advertising within the meaning of US state privacy laws, you can opt out as described in Section 3 and in Section 16 of our Privacy Policy.
  • 2.3
    The specific cookies in use may vary depending on the pages you visit and on changes made by our third-party providers. The tables in Sections 4 to 6 list the cookies we are aware of at the date of this Policy.

  3. Your choices and consent

  • 3.1
    Cookie banner. When you first visit the Website we show a cookie banner. Analytics and marketing cookies are not set until you click "Accept all" or enable them in "Preferences". If you click "Decline", only strictly necessary cookies are used. Choosing not to interact with the banner has the same effect as declining.
  • 3.2
    Changing your mind. You can change or withdraw your consent at any time by clicking "Open cookie settings" above or "Cookie Settings" in the footer of any page. If you withdraw consent for a category, we stop using those cookies, delete the ones we control and reload the page. Withdrawal does not affect the lawfulness of processing before it.
  • 3.3
    How your choice is stored. Your choice is stored in a first-party cookie named cr_consent (and mirrored in local storage) for 180 days, after which we will ask you again. We will also ask you again if we materially change this Policy or the cookies we use. We keep a record of your consent (categories, timestamp and policy version) to demonstrate compliance.
  • 3.4
    Global Privacy Control. If your browser sends a Global Privacy Control (GPC) signal, we treat it as a decision to decline analytics and marketing cookies and as an opt-out of the "sale" or "sharing" of your personal information, without showing the banner. You can still enable categories manually via cookie settings.
  • 3.5
    Google Consent Mode. We use Google Consent Mode. Until you consent, Google tags are instructed that analytics storage and advertising storage are denied; after you consent, the relevant permissions are updated to reflect your choice.
  • 3.6
    Cookies set by the Software. When you log in to the Software, strictly necessary cookies are set to keep you signed in and secure your session. Your cookie choice made on the Website applies across coinrule.com and its subdomains.

  4. Strictly necessary cookies

  • These cookies are essential to provide the Website and the Software, to keep them secure, to operate our referral programme and to honour your cookie choices. They are set on the basis of our legitimate interest in operating a secure service and are exempt from the consent requirement.
    NameProviderPurposeTypeDuration
    cr_consentcoinrule.comStores your cookie consent choices and the policy version you consented to.HTTP cookie / local storage180 days
    __cf_bmCloudflare (coinrule.com)Bot management and protection against malicious traffic.HTTP cookie30 minutes
    cf_clearanceCloudflare (coinrule.com)Records that a security challenge has been passed.HTTP cookieUp to 1 year
    csrf_token, csrftokencoinrule.comProtects forms and the Software against cross-site request forgery.HTTP cookie29 days
    sessionid (and similar)coinrule.comKeeps you signed in to the Software and secures your session.HTTP cookieSession / up to 14 days
    cr_region_noticecoinrule.comRemembers that you dismissed the EU/EEA availability notice.Session storageSession
    _fprom_tid, _fprom_ref, _fprom_trackFirstPromoter (coinrule.com)Attributes your visit and any subsequent sign-up to the affiliate or referral link you arrived from, so that the referral programme can operate and the referrer can be rewarded. Used solely for this purpose; not used for advertising.HTTP cookieUp to 1 year
    atlasIdentity*, atlasUserHash*, atlasBaseDomainAtlas (web.coinrule.com)Powers the support chat widget in the web application: identifies your chat session so that conversations with our support team persist between visits and, when you are signed in, verifies that you are the account holder. Not used on the marketing Website and not used for advertising.HTTP cookie / local storage30 days

  5. Analytics cookies

  • These cookies collect information about how visitors use the Website and the Software, in aggregate or pseudonymised form, so that we can measure and improve performance. Session analytics tools may reproduce your interactions as a replay; password, payment and API key fields are masked. Set only with your consent.
    NameProviderPurposeTypeDuration
    _gaGoogle AnalyticsDistinguishes users by assigning a randomly generated client identifier.HTTP cookie13 months
    _ga_#Google AnalyticsPersists session state for Google Analytics 4.HTTP cookie13 months
    _gidGoogle AnalyticsDistinguishes users for statistical reporting.HTTP cookie24 hours
    _gat#Google AnalyticsThrottles request rate.HTTP cookie1 minute
    _clckMicrosoft ClarityPersists the Clarity user ID and preferences so that activity is attributed to the same user.HTTP cookie12 months
    _clskMicrosoft ClarityConnects multiple page views into a single session recording.HTTP cookie1 day
    _cltkMicrosoft ClarityStores interaction data for the current session.Session storageSession
    CLIDMicrosoft Clarity (clarity.ms)Identifies the first time Clarity saw this user on any site using Clarity.HTTP cookie12 months
    MUID, MR, SMMicrosoft (clarity.ms, bing.com)Microsoft user identifier and synchronisation cookies used by Clarity.HTTP cookieSession to 13 months
    c.gifMicrosoft ClarityPixel used to transmit session analytics data.PixelSession
    atlas-recorder-session-idAtlas (web.coinrule.com)Session replay of your interactions in the web application, used by our support team to troubleshoot problems you report. Password, payment and API key fields are masked. Only active in the web application and only where you have consented to analytics cookies.Session storageSession
    Searchable Analyticstracker.searchableanalytics.comPrivacy-focused, cookieless page view and referrer statistics.Script (no cookie)n/a

  6. Marketing cookies

  • These cookies are set by our advertising partners. They measure whether our advertising campaigns lead to sign-ups, prevent the same advertisement from being shown repeatedly and allow our partners to show you relevant advertising on other websites. The partners may combine this information with other data they hold about you under their own privacy notices. Set only with your consent.
    NameProviderPurposeTypeDuration
    _gcl_au, _gcl_lsGoogle AdsStores and measures ad click information for conversion attribution.HTTP cookie / local storage90 days / persistent
    test_cookieGoogle (doubleclick.net)Checks whether the browser supports cookies.HTTP cookie15 minutes
    ga-audiencesGoogle AdsRe-engages visitors likely to convert, based on behaviour across websites.PixelSession
    _fbp, _fbcMeta (Facebook)Identifies browsers for advertising measurement and delivery via the Meta Pixel.HTTP cookie90 days
    lastExternalReferrer, lastExternalReferrerTimeMeta (Facebook)Records how you reached the Website for attribution.Local storagePersistent
    _rdt_uuidRedditReddit Pixel identifier used to measure advertising conversions.HTTP cookie90 days
    rp.gifReddit (alb.reddit.com)Pixel used to transmit conversion events.PixelSession
    _twpid, personalization_idX (Twitter)X Pixel identifiers used to measure advertising conversions.HTTP cookie13 months / 2 years
    bcookie, bscookie, lidc, li_sugr, UserMatchHistory, AnalyticsSyncHistory, ar_debugLinkedInLinkedIn Insight Tag cookies used for campaign reporting, audience matching and routing.HTTP cookie1 day to 12 months
    ANONCHK, SRM_BMicrosoft Advertising (bing.com)Ad tracking and optimisation for Microsoft/Bing advertising.HTTP cookie10 minutes / 13 months
    initialReferrercoinrule.comStores the referrer of your first visit for marketing attribution.HTTP cookie24 hours

  7. Other tracking technologies

  • 7.1
    Pixels and web beacons. Pixels are tiny graphics or scripts that contain a unique identifier and are used to recognise when someone has visited the Website or opened an email. We use them to measure traffic between pages, to understand whether you reached the Website from an online advertisement, and to measure the success of email campaigns. Pixels belonging to the analytics and marketing categories are blocked until you consent.
  • 7.2
    Local storage and session storage. These are browser storage areas similar to cookies. We use them for strictly necessary purposes (such as remembering your cookie choice and dismissed notices) and, with your consent, for analytics and marketing purposes as listed above.
  • 7.3
    Tag manager. We use Google Tag Manager to load analytics and marketing tags. The tag manager itself is loaded only after you consent to at least one non-essential category, and each tag inside it is subject to the consent category it belongs to.
  • 7.4
    Email tracking. Our marketing and some service emails contain pixels and tracked links that tell us whether an email was opened and which links were clicked. You can prevent this by disabling image loading in your email client or by unsubscribing from marketing emails.

  8. Browser controls and opt-outs

  9. Changes to this Policy

  • We may update this Cookie Policy from time to time to reflect changes to the cookies we use or for other operational, legal or regulatory reasons. The date at the top of this page indicates when it was last updated. Where changes are material, we will ask for your consent again through the cookie banner.

  10. How to contact us

If you have any questions about our use of cookies or other technologies, email us at support[at]coinrule.com or write to:

Coinrule Limited
Office One, 1 Coldbath Square
London EC1R 5HL
United Kingdom

Coinrule Limited Registered Address: Office One, 1 Coldbath Square, EC1R 5HL, London.
Email: support[at]coinrule.com
Website: coinrule.com