Cookie Policy

Effective Date: February 12, 2026 · Last Updated: February 12, 2026

1. What Are Cookies

This Cookie Policy (“Policy”) explains how MongoTrader (“Company,” “we,” “us,” or “our”) uses cookies and similar tracking technologies when you access or use the MongoTrader platform, website, and all related services (collectively, the “Platform”). This Policy should be read in conjunction with our Privacy Policy and Terms of Service, which are incorporated herein by reference.

Cookies are small text files containing a string of alphanumeric characters that are placed on your computer, mobile device, or other internet-connected device when you visit a website or use an online service. Cookies are widely used by website operators to make their websites function, to improve operational efficiency, and to provide analytical and reporting information. A cookie set by the website you are visiting is referred to as a “first-party cookie,” while a cookie set by a domain other than the one you are visiting is referred to as a “third-party cookie.”

In addition to traditional HTTP cookies, we employ a range of similar technologies to collect and store information when you interact with the Platform. These include, without limitation:

Local Storage (Web Storage API): A browser-based storage mechanism that allows websites to store key-value pairs of data locally on your device with no predefined expiration date. Data stored in local storage persists until explicitly cleared by the user, the application, or the browser. Unlike cookies, local storage data is not automatically transmitted to our servers with each HTTP request.
Session Storage: A browser-based storage mechanism functionally similar to local storage, except that data stored in session storage is scoped to the individual browser tab and is automatically deleted when the tab or browser window is closed. We use session storage for temporary application state that does not need to persist beyond a single browsing session.
Web Beacons (Pixel Tags / Clear GIFs): Small, transparent graphic images embedded in web pages or emails that enable the detection of whether a page has been viewed or an email has been opened. Web beacons typically operate in conjunction with cookies and are used to measure user engagement and the effectiveness of communications.
WebSocket Connections: Persistent, bidirectional communication channels between your browser and our servers that enable real-time transmission of market data, trading activity updates, and platform notifications without requiring repeated HTTP requests.

Unless otherwise specified, all references to “cookies” in this Policy shall be construed to include all such similar technologies as described above.

2. How We Use Cookies

The Company uses cookies and similar technologies on the Platform for the following purposes, each of which is described in greater detail in subsequent sections of this Policy:

Authentication and Session Management: To verify your identity upon login, maintain your authenticated session state as you navigate the Platform, and protect against unauthorized access to your account.
Security: To implement cross-site request forgery (CSRF) protection, detect and prevent fraudulent activity, and enforce other security measures essential to the integrity of the Platform.
User Preferences and Personalization: To remember your interface customization choices, including but not limited to sidebar collapse state, portfolio selection, watchlist display modes, chart configurations, and theme preferences, so that these settings persist across sessions.
Payment Processing: To facilitate secure payment transactions and subscription management through our third-party payment processor, Stripe, Inc., including fraud detection and prevention during the payment lifecycle.
Performance and Analytics: To monitor and analyze Platform performance, including page load times, error rates, WebSocket connection stability, and aggregate user engagement patterns, for the purpose of improving reliability and user experience.
Real-Time Data Functionality: To support the proper functioning of real-time market data feeds, live portfolio valuations, and trading simulation operations that depend on persistent connection state management.

We do not use cookies for behavioral advertising, cross-site tracking for advertising purposes, or the sale of personal information to third parties.

3. Types of Cookies We Use

The cookies deployed on the Platform can be classified into the following categories based on their function and purpose. Each category is described below, together with the legal basis for its use and the consequences of disabling such cookies.

3.1 Strictly Necessary Cookies

Strictly necessary cookies are essential for the operation of the Platform and enable core functionality without which the Platform cannot function as intended. These cookies do not collect information about you for marketing or advertising purposes. Because these cookies are indispensable to the provision of the services you have requested, they cannot be disabled without rendering the Platform inoperable.

Strictly necessary cookies deployed on the Platform serve the following functions:

Authentication: Session tokens issued upon successful login that identify you as an authenticated user and maintain your logged-in state as you navigate between pages and features of the Platform. Without these cookies, you would be required to re-authenticate on every page load.
Session Management: Cookies that preserve the continuity of your session, prevent session hijacking or fixation attacks, and ensure that your trading activities, portfolio views, and other stateful interactions remain consistent throughout your use of the Platform.
CSRF Protection: Tokens embedded in forms and API requests that verify the authenticity of state-changing requests and prevent malicious third-party websites from executing unauthorized actions on your behalf.
Callback URL Management: Cookies that store the intended redirect destination during the authentication flow, ensuring that you are returned to the correct page after completing the login process.
Load Balancing and Infrastructure: Cookies that distribute user sessions across our server infrastructure to ensure optimal performance, fault tolerance, and service continuity.

Disabling strictly necessary cookies will prevent you from logging in to your account, executing simulated trades, participating in competitions, and accessing all authenticated features of the Platform.

3.2 Functional Cookies

Functional cookies enable the Platform to provide enhanced functionality and personalization based on your prior interactions and expressed preferences. These cookies may be set by the Company or by third-party providers whose services have been integrated into the Platform. If you disable functional cookies, some or all of the personalization features described below may not operate correctly, and you may be required to reconfigure your preferences each time you visit the Platform.

Functional cookies deployed on the Platform include:

Sidebar State Persistence: Cookies that remember whether you have collapsed or expanded the Platform’s navigation sidebar, preserving your preferred layout across sessions and page navigations.
Portfolio Selection: Cookies that store the identifier of the portfolio you were last viewing or actively trading within, enabling seamless continuation of your workflow when you return to the Platform or navigate between features.
Watchlist Display Modes: Cookies that remember your preferred watchlist view configuration, including list versus grid layout, column visibility, sort order, and grouping preferences.
Theme and Appearance: Cookies that store your dark mode preference and other appearance-related settings, ensuring that the Platform renders in your chosen visual style without delay or flash of unstyled content.
Chart Configuration: Cookies that persist your preferred chart type (e.g., candlestick, line, OHLC), timeframe selection, technical indicator overlays, and drawing tool state.
Language and Localization: Cookies that remember your language preference and regional settings for currency display formatting, date rendering, and number localization.

3.3 Performance and Analytics Cookies

Performance and analytics cookies allow the Company to measure and analyze how visitors use the Platform, enabling us to identify and resolve technical issues, optimize performance, and improve the overall user experience. All information collected by these cookies is aggregated and anonymized; it does not identify you personally.

Performance and analytics cookies help us:

Monitor page load times, rendering performance, and time-to-interactive metrics across different devices, browsers, and network conditions
Track error rates, JavaScript exceptions, and failed API requests to diagnose and resolve technical issues that may degrade user experience
Analyze aggregate user engagement patterns, including feature adoption rates, navigation flows, and session duration, to inform product development decisions
Evaluate the stability and latency of real-time WebSocket connections used for market data delivery and live portfolio updates
Measure the effectiveness and adoption of new Platform features, interface updates, and performance optimizations following release

If you disable performance and analytics cookies, the Company will be unable to monitor the technical health of the Platform as it relates to your specific sessions, which may impede our ability to identify and resolve issues affecting your experience.

3.4 Third-Party Cookies

Certain third-party service providers integrated into the Platform may set their own cookies on your device. The Company has limited control over the content and operation of these third-party cookies, and the third-party providers’ use of cookies is governed by their own respective cookie and privacy policies.

Stripe, Inc. — Payment Processing: The Platform integrates Stripe, Inc. (“Stripe”) as its sole payment processor for the management of subscription billing, recurring charges, and payment transactions. When you navigate to payment-related pages or interact with Stripe’s embedded payment elements, Stripe may set cookies on your device for purposes including, but not limited to: fraud detection and prevention across Stripe’s merchant network; secure transmission and processing of payment credentials; session continuity during multi-step payment flows; and implementation of Strong Customer Authentication (SCA) and 3D Secure protocols as required by applicable payment network regulations.

For comprehensive information regarding Stripe’s cookie practices, data collection methodologies, and applicable privacy safeguards, please consult Stripe’s Cookie Policy, available at https://stripe.com/cookies-policy/legal.

3.5 Advertising Cookies

For users on the free tier, the Platform displays advertising served by Google AdSense. With your consent, Google and its advertising partners may set cookies to serve ads and to personalize them based on your visits to this and other websites. These cookies are loaded only if you accept non-essential cookies through our cookie banner; if you select “Essential only,” they are not set. Paid subscribers (Premium and Max) are not shown ads. See Section 7.2 for details and opt-out options.

5. Local Storage and Similar Technologies

In addition to the cookies described above, the Platform makes extensive use of browser-based local storage and session storage mechanisms to enhance functionality and user experience. It is important to understand how these technologies differ from traditional HTTP cookies.

5.1 Distinction from Cookies

Unlike cookies, data stored in local storage and session storage is not automatically transmitted to our servers with each HTTP request. Local storage data resides exclusively on your device and is accessed only by client-side JavaScript executing within the Platform’s web application. This distinction means that local storage data does not impose additional bandwidth overhead and is not visible to our server infrastructure unless the client-side application explicitly transmits it via an API call.

5.2 Local Storage Uses

The Platform uses local storage to persist the following categories of data:

User interface state and layout configurations that do not require server-side synchronization, including panel sizing, column widths, and component visibility toggles
Cached market data snapshots used to reduce redundant server requests and improve the responsiveness of the trading interface during periods of high-frequency data updates
Draft order configurations and trade parameters entered prior to submission, preventing data loss in the event of an accidental page refresh or navigation
Custom watchlist compositions, asset groupings, and user-defined screening criteria
Chart drawing objects, trendlines, annotations, and technical analysis markup persisted across sessions
Competition notification preferences, leaderboard display settings, and league filter configurations

5.3 Session Storage Uses

The Platform uses session storage for temporary data that is scoped to a single browser tab and does not need to persist beyond the current browsing session:

Transient application state required during multi-step workflows, such as order entry wizards and account configuration flows
In-tab navigation history metadata used to optimize back/forward navigation within the Platform’s single-page application architecture
Ephemeral notification and alert state, including read/unread status of in-session messages and toast dismissal tracking
Real-time market data buffers used to throttle and batch WebSocket message processing for optimal rendering performance

5.4 Managing Local and Session Storage

You may clear local storage and session storage through your browser’s developer tools (typically accessible via F12 or the browser’s settings menu under “Site Data” or “Application Storage”) or by clearing all browsing data. Please be aware that clearing local storage will reset all locally persisted preferences and customizations, requiring you to reconfigure your Platform settings, chart annotations, and layout preferences.

6. Managing Your Cookie Preferences

You have the right to decide whether to accept or reject cookies. Most web browsers are configured to accept cookies by default, but you may modify your browser settings to decline cookies, delete existing cookies, or receive a notification each time a cookie is set. The methods for managing cookies vary by browser; please consult the instructions below for your specific browser.

6.1 Browser-Specific Instructions

Google Chrome

Click the three-dot menu icon (…) in the upper-right corner and select “Settings.”
Navigate to “Privacy and security” in the left-hand panel, then select “Cookies and other site data.”
Choose your preferred configuration: “Allow all cookies,” “Block third-party cookies in Incognito,” “Block third-party cookies,” or “Block all cookies.”
To manage or delete individual cookies, select “See all cookies and site data” and search for the relevant domain.

Mozilla Firefox

Click the three-line menu icon (≡) and select “Settings.”
Select “Privacy & Security” from the left-hand navigation panel.
Under “Enhanced Tracking Protection,” choose from “Standard,” “Strict,” or “Custom” protection levels, each of which applies different cookie-blocking rules.
To manage existing cookies, scroll to “Cookies and Site Data” and click “Manage Data…” to view and remove cookies by domain.

Apple Safari

Open the Safari menu and select “Settings” (or “Preferences” on older versions).
Navigate to the “Privacy” tab.
Configure your cookie preferences under “Cookies and website data.” Safari blocks cross-site tracking cookies by default through Intelligent Tracking Prevention (ITP).
Click “Manage Website Data…” to view and remove stored cookies by domain.

Microsoft Edge

Click the three-dot menu icon (…) in the upper-right corner and select “Settings.”
Navigate to “Cookies and site permissions” in the left-hand panel.
Click “Manage and delete cookies and site data” to configure blocking behavior.
Choose to allow all cookies, block third-party cookies, or block all cookies. You may also add site-specific exceptions.

6.2 Consequences of Disabling Cookies

Should you choose to disable or block cookies, you should be aware that such action may materially impact your ability to use the Platform. Specifically:

Authentication Failure: Blocking strictly necessary cookies will prevent you from logging in to the Platform entirely, as session tokens cannot be established or maintained. The Platform will be functionally inaccessible in an authenticated state.
Security Degradation: Disabling CSRF protection cookies may expose your account to cross-site request forgery attacks, potentially allowing unauthorized parties to execute actions on your behalf.
Loss of Personalization: Blocking functional cookies will prevent the Platform from remembering your preferences, requiring manual reconfiguration of sidebar state, portfolio selection, watchlist views, and theme settings upon each visit.
Payment Processing Disruption: Blocking third-party cookies from Stripe may prevent you from subscribing to paid tiers, updating payment methods, or completing payment transactions.
Degraded Performance Monitoring: Disabling performance cookies will impair the Company’s ability to detect and resolve technical issues that may affect your experience on the Platform.

For general information about cookies and how to manage them across different browsers and devices, you may visit www.allaboutcookies.org or www.youronlinechoices.com.

7. Third-Party Cookies

The Platform integrates with third-party service providers that may independently set and access cookies on your device when you interact with their services through the Platform. The Company does not control the content, behavior, or retention periods of these third-party cookies, and their use is governed exclusively by the respective third parties’ own cookie policies and privacy policies.

7.1 Stripe, Inc. — Payment Processing

The Company uses Stripe, Inc. (“Stripe”) as its exclusive payment processor for subscription billing, payment card processing, and related financial transactions. Stripe is a PCI-DSS Level 1 certified service provider. When you access any payment-related functionality on the Platform — including subscription signup, plan upgrades or downgrades, payment method management, or billing history views — Stripe may set cookies on your device for the following purposes:

Fraud Prevention and Risk Scoring: Stripe employs machine learning models that analyze device fingerprints, behavioral signals, and cookie-derived session data across its global merchant network to detect and prevent fraudulent payment attempts. The __stripe_mid cookie (duration: one year) serves as a persistent device identifier for this purpose.
Payment Session Integrity: The __stripe_sid cookie (duration: thirty minutes) tracks individual payment sessions to ensure transactional integrity, prevent duplicate charges, and detect anomalous session behavior indicative of account takeover or session hijacking.
Strong Customer Authentication (SCA): Stripe may set additional cookies in connection with 3D Secure authentication flows, biometric verification, and other multi-factor authentication protocols required by payment networks and applicable regulatory frameworks such as PSD2.
Embedded Payment Element Functionality: Stripe’s embedded payment forms (Stripe Elements) rely on cookies to render correctly, maintain form state, and securely tokenize payment credentials prior to transmission.

For comprehensive information regarding Stripe’s data processing practices, please consult the following resources:

Stripe Cookie Policy: https://stripe.com/cookies-policy/legal
Stripe Privacy Policy: https://stripe.com/privacy

Please note that blocking third-party cookies originating from Stripe domains will prevent you from completing subscription purchases, managing your payment methods, or processing any financial transactions through the Platform. The Company cannot override or bypass Stripe’s cookie requirements, as they are integral to PCI-compliant payment processing.

7.2 Google — Advertising (AdSense)

For free-tier users who accept non-essential cookies, the Platform serves advertising through Google AdSense. As a third-party vendor, Google uses cookies to serve ads based on a user’s prior visits to the Platform and other websites. Google and its partners may use advertising cookies to:

Ad Delivery and Frequency: Select which ads to display, limit how many times you see a given ad, and measure ad performance.
Personalization: Tailor ads to your interests based on your browsing across sites that use Google’s advertising services, where you have consented.
Fraud and Abuse Prevention: Detect and prevent invalid traffic and other abusive activity.

Advertising cookies load only after you accept non-essential cookies, and you can withdraw consent at any time by selecting “Essential only.” You can also control or opt out of personalized advertising directly:

Google Ads Settings: https://adssettings.google.com
How Google uses cookies in advertising: https://policies.google.com/technologies/ads
Industry opt-outs: aboutads.info / youronlinechoices.eu

8. Do Not Track Signals

Certain web browsers transmit a “Do Not Track” (DNT) signal to the websites and online services with which the browser communicates. The DNT signal is an HTTP header field that indicates a user’s preference regarding tracking by third parties across websites. As of the date of this Policy, there is no universally accepted standard for how website operators should interpret or respond to DNT signals, and no industry consensus, regulatory mandate, or formal specification has been finalized.

At this time, the Platform does not alter its data collection, cookie deployment, or tracking practices in response to DNT signals transmitted by your browser. This position is informed by the following considerations:

The majority of cookies deployed by the Platform are strictly necessary for authentication, security, and core functionality, and cannot be conditionally disabled without rendering the Platform inoperable.
The Company does not engage in cross-site behavioral tracking, interest-based advertising, or the sale of user data to third parties — the primary activities that DNT signals are intended to address.
In the absence of a uniform, legally mandated standard for DNT compliance, selective implementation risks creating an inconsistent and potentially misleading user experience.

Notwithstanding the foregoing, you retain full control over cookie settings through your browser’s built-in configuration tools as described in Section 6 of this Policy. Should a binding legal standard or widely adopted industry specification for DNT signals be established in the future, the Company will reassess its practices and update this Policy accordingly.

Users subject to the California Consumer Privacy Act (CCPA) or the California Privacy Rights Act (CPRA) should note that this provision constitutes the Company’s disclosure regarding its response to “Do Not Track” browser signals as required under California Business and Professions Code Section 22575.

9. Changes to This Cookie Policy

The Company reserves the right to amend, modify, or replace this Cookie Policy at any time and in its sole discretion to reflect changes in our cookie practices, the adoption of new technologies, modifications to Platform features, changes to applicable laws or regulations, or for other operational, legal, or regulatory reasons.

When the Company makes material changes to this Policy, we will notify you through one or more of the following methods:

Updating the “Last Updated” date displayed at the top of this Policy
Posting a prominent notice on the Platform, such as a banner or modal dialog, for a reasonable period following the effective date of the changes
Sending a notification to the email address associated with your account, where the changes are of sufficient significance to warrant direct communication
Displaying an in-app notification within your account dashboard

Your continued use of the Platform following the posting of any revised version of this Cookie Policy shall constitute your acceptance of and agreement to the modified Policy. If you do not agree with any changes to this Policy, you should discontinue your use of the Platform and may contact us to request deletion of any cookies previously set.

We encourage you to periodically review this Cookie Policy to remain informed about how the Company uses cookies and similar technologies. Archived versions of prior Cookie Policies may be made available upon written request to the contact address provided below.

10. Contact Information

If you have any questions, concerns, complaints, or requests regarding this Cookie Policy, our use of cookies and similar technologies, or wish to exercise any rights you may have under applicable data protection legislation with respect to cookie-derived data, please contact us using the information provided below:

MongoTrader — Privacy Inquiries

Email: [email protected]

Subject Line: Cookie Policy Inquiry

The Company will acknowledge receipt of all inquiries and endeavor to provide a substantive response within thirty (30) calendar days. For general privacy inquiries, data subject access requests, or to exercise rights under the California Consumer Privacy Act (CCPA), the General Data Protection Regulation (GDPR), or other applicable data protection laws, please refer to our Privacy Policy or direct your correspondence to the address above.

For matters relating to our Terms of Service or general legal inquiries, you may also contact us at [email protected].