Cookie Policy
Last updated: 3 July 2026
This Cookie Policy explains the small number of cookies and similar on-device technologies that Qubit Quant uses across the Services, why we use them, and how you can control them. We keep this list short and honest: we use what is needed to sign you in, remember your theme, and attribute affiliate referrals fairly — and, as of the date above, nothing else.
1Scope and Definitions
Who we are. "Qubit Quant", "we", "us" and "our" mean the two-engineer software publisher that operates the Qubit Quant website, dashboard, and free quant tools (together, the "Services"), including the [[ENTITY]] legal entity through which the Services are provided. We publish MetaTrader 5 Expert Advisors and free/beta analysis tools. We are not a broker, fund, investment adviser, or signal service; we do not execute trades, give personalised advice, or hold client money.
You. "You" and "your" mean any person who visits or uses the Services, whether or not you hold an account.
This Cookie Policy forms part of, and should be read together with, our Terms, Privacy Policy, Risk Disclosure, and Refund Policy. Where those documents govern liability, disclaimers, governing law, or dispute resolution, they control and are incorporated here by reference. Governing law and jurisdiction are as set out in the Terms; where a jurisdiction must be stated, it is [[JURISDICTION]].
Our honesty stance is unchanged here: every published performance metric reconciles with a raw MT5 report generated on Dukascopy tick data, the tools ship free and in beta, and we test on our own money before we ask for yours. None of that constitutes a warranty, guarantee, or advice — see the disclaimers below.
2What Are Cookies
Cookies are small text files that a website asks your browser to store on your device. On each later request, the browser may send certain cookies back, which lets a site recognise your session or remember a setting. Cookies can be "first-party" (set by the site you are visiting) or "third-party" (set by another domain); they can last only for a browsing session ("session") or persist for a defined period ("persistent").
We also rely on related on-device technologies — principally your browser's local storage and IndexedDB. Unlike cookies, data kept in local storage stays on your device and is not automatically transmitted to us with each request. In this Policy, references to "cookies" include these similar technologies where the context allows, so that this list is complete.
3Cookies & Local Storage We Use
Essential — required to provide the Services. These cannot be switched off while you use the relevant feature, because the feature will not work without them.
- Authentication and session (Firebase) When you sign in with Google, our authentication provider (Google Firebase) stores sign-in and session tokens in your browser's local storage / IndexedDB so you stay signed in and can reach the dashboard. Our server APIs authenticate each request from these tokens (as a bearer credential), not from a cookie. Without this, sign-in and the authenticated dashboard do not function.
Referral / Marketing — set with your consent. Referral attribution (qq_ref) is not strictly necessary to use the site and is set on the basis of your consent where required. You can decline it without losing access to the dashboard.
- Affiliate attribution — qq_ref A first-party, httpOnly cookie set by our own server when you arrive through a referral link (/r/<code>). It stores only the referral code and a server-stamped click time, has a maximum lifetime of 30 days, is limited to first-party context (SameSite=Lax), and is marked Secure in production. "httpOnly" means client-side scripts cannot read it. It is used solely to attribute an affiliate referral for up to 30 days, and it is cleared once your account records an attribution. It is not strictly necessary, and declining it does not affect sign-in or the dashboard.
Functional — kept on your device, not sent to us. This improves your experience but is not shared with our servers.
- Theme preference — qq_theme Stores your light/dark appearance choice in your browser's local storage so the site renders in your preferred theme without a flash on load. It lives entirely on your device and is never transmitted to us. Clearing it simply resets the appearance to default.
Analytics, advertising, and tracking — none in use. As of the date of this Policy, the Services do not set third-party analytics, advertising, cross-site tracking, retargeting, social-media, or profiling cookies, and we do not sell or share cookie data for advertising. If we later introduce any non-essential or analytics technology, we will update this Policy to describe it before or when it is deployed, and will obtain consent where required by applicable law.
4Why We Use Them
We use the technologies listed above only for the following purposes:
- Sign-in and session to authenticate you and keep you signed in to the dashboard, and to secure that session.
- Referral attribution to fairly and verifiably attribute an affiliate referral for up to 30 days from a referral click, using a server-set, tamper-resistant record.
- Preferences to remember your light/dark theme so the site loads the way you left it.
- Security and operation to operate, maintain, and protect the integrity of the Services.
We do not use these technologies to build advertising profiles, to serve behavioural ads, or to sell your personal data. How we handle the underlying data is described in our Privacy Policy.
5Managing Cookies
You can view, delete, and block cookies, and clear local storage / IndexedDB, through your browser settings — controls vary by browser and device, and your browser's help pages explain the steps. Signing out and clearing this site's stored data will remove the theme preference and the Firebase sign-in tokens held on your device.
Essential technologies are required. If you block or delete the essential cookies and local storage described above — sign-in and the authenticated dashboard — those features will not work correctly or at all. Declining the non-essential referral cookie (qq_ref) only affects affiliate attribution, not your access to the site. To the maximum extent permitted by applicable law, we are not responsible or liable for any loss of functionality, access, referral attribution, or other consequence that results from your decision to block, restrict, or clear these technologies.
Do Not Track. Because there is no common, finalised industry standard for interpreting "Do Not Track" browser signals, and because we do not operate cross-site tracking, we do not currently respond to such signals in a standardised way. To the maximum extent permitted by applicable law, our practices are governed by this Policy rather than by any particular browser signal.
6No Advice, Trading Risk & No Warranty
Nothing here is advice. Nothing in this Policy, and nothing accessed through cookies or the Services, is or should be construed as financial, investment, legal, tax, or trading advice, a recommendation, or a solicitation. We are a software publisher, not a broker, fund, adviser, or signal service.
You assume the trading risk. Trading foreign exchange, CFDs, and other leveraged instruments carries a substantial risk of loss and is not suitable for everyone; past or simulated performance — including any figure shown on the Services — is not indicative of future results. To the maximum extent permitted by applicable law, you assume full responsibility for any trading decision you make and for all resulting losses, and we give no warranty of profitability, performance, or fitness for any trading purpose. See the Risk Disclosure.
7Disclaimers, Limitation of Liability & Indemnity
As is / as available. To the maximum extent permitted by applicable law, the Services and all cookies and similar technologies are provided "as is" and "as available", without warranties or conditions of any kind, whether express, implied, or statutory, including any implied warranties of merchantability, fitness for a particular purpose, title, non-infringement, accuracy, and uninterrupted, secure, or error-free operation.
Limitation of liability. To the maximum extent permitted by applicable law, we, [[ENTITY]], and our engineers will not be liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, or for any loss of profits, revenue, data, goodwill, or trading losses, arising out of or relating to this Policy, cookies, or your use of or inability to use the Services, even if advised of the possibility. Our total aggregate liability to you is limited as set out in the Limitation of Liability section of our Terms of Service, which controls.
Indemnification. To the maximum extent permitted by applicable law, you agree to indemnify, defend, and hold harmless Qubit Quant, [[ENTITY]], and our engineers from and against any claims, damages, losses, liabilities, costs, and expenses (including reasonable legal fees) arising out of or related to your misuse of the Services, your circumvention or tampering with cookies or attribution technologies, or your breach of this Policy or the Terms. These disclaimers, limitations, and indemnities operate in addition to those in the Terms; if there is any conflict, the order-of-precedence clause in the Terms governs.
8Changes to This Policy
We may update this Policy from time to time to reflect changes to the technologies we use or to legal requirements. The "Last updated" date at the top shows when it last changed. Where a change is material, we will take reasonable steps to make it visible on the Services. To the maximum extent permitted by applicable law, your continued use of the Services after an updated Policy takes effect constitutes your acceptance of it.
Contact. Questions about this Cookie Policy can be sent to legal@qubitquantglobal.com.
Questions about this document? Email legal@qubitquantglobal.com.