Terms of Service

By downloading, installing, accessing, or using ApexQuant ("the Software"), you ("the User", "Client") agree to be bound by these Terms of Service ("Terms"). If you do not agree to these Terms, do not use the Software.

ApexQuant is a self-hosted automated trading software tool developed and licensed by ApexQuant ("we", "us", "vendor"). These Terms govern all access to and use of the Software, including any updates, patches, or documentation provided.

By using the Software, you confirm that you:

• Are at least 18 years old (or the age of majority in your jurisdiction, whichever is greater) and have full legal capacity to enter into this agreement
• Are of legal age to trade cryptocurrency in your jurisdiction
• Are not located in, a resident of, or accessing the Software from any jurisdiction subject to comprehensive trade sanctions or embargo, and are not a person or entity on any applicable sanctions or denied-party list
• Are not prohibited by any applicable law from using cryptocurrency trading software, and are solely responsible for determining whether your use is lawful in your jurisdiction
• Understand and accept the risks of automated cryptocurrency trading
• Have read and understood this Risk Disclosure in full
• Are solely responsible for all trading decisions made by or through the Software, including any trades executed automatically based on your configured parameters
• Comply with all applicable laws and regulations in your jurisdiction

Risk Disclosure

2.1 No Guarantee of Profit
The Software uses machine learning models, technical indicators, and macro data to assist in generating automated execution conditions based on user-defined configurations. These execution conditions are probabilistic in nature. No trading strategy or algorithm can guarantee profitable results. The Software may generate losing trades, including extended losing streaks.

2.2 Historical and Backtested Performance
Any backtested results, historical win rates, ML precision figures, or performance statistics displayed are based on historical data and are provided for informational purposes only. Historical performance is not indicative of future results. Backtests are subject to look-ahead bias, survivorship bias, and overfitting. Real trading conditions including slippage, fees, and liquidity constraints may differ significantly from backtested conditions.

2.3 Market Risk
Cryptocurrency markets are highly volatile and operate 24/7. Prices can move significantly in short periods due to market sentiment, regulatory announcements, exchange outages, liquidity crises, and other factors entirely outside the Software's control.

2.4 Technical Risk
The Software may experience technical failures including but not limited to: internet connectivity issues, exchange API outages, server downtime, software bugs, incorrect signal generation, or failed order execution. Such failures may result in missed trades, unintended positions, or financial loss.

2.5 Exchange Risk
The Software connects to third-party cryptocurrency exchanges (currently Binance only). The vendor is not responsible for actions, outages, insolvency, regulatory actions, or changes in terms of service of any exchange. Users are solely responsible for their exchange accounts and any funds held therein.

2.6 Configuration Risk
Incorrect configuration of the Software, including but not limited to position sizing, stop-loss levels, API permissions, and risk limits, may result in significant financial loss. The User is solely responsible for reviewing and correctly configuring all Software parameters before live trading.

2.7 Not Financial Advice
Nothing in the Software, its documentation, or any communications from the vendor constitutes financial, investment, legal, or tax advice. The vendor is not a licensed financial advisor, broker, or investment manager.

2.8 Manual Override Risk
The Software provides optional manual trade control features (Manual Sell and Manual Buy) available to subscribers on every tier. When a User exercises manual trade control, all automated protective gates — including the ML signal gate, market regime filter, FOMC blackout window, AI Commentary layer, and position cooldown — are intentionally bypassed. Trades executed via manual override are initiated solely at the User's discretion. The vendor accepts no responsibility for financial losses arising from the use of manual trade control features. The User acknowledges that manual overrides circumvent the Software's risk management framework and that any resulting losses are solely the User's responsibility.

2.9 Strategy Selection and Parameter Risk
ApexQuant offers several strategies; each license runs one of them. The vendor does not select, recommend, or optimise strategies on your behalf. You are solely responsible for: (a) choosing which strategy to enable, (b) configuring all strategy parameters, (c) deciding when to activate live trading, and (d) monitoring strategy performance over time. The Directional strategy is explicitly marked EXPERIMENTAL and has not been validated to produce consistent returns across all market conditions. No strategy defaults should be assumed to be optimal. The framework provides tooling; outcomes depend entirely on your configuration decisions.

2.10 Funding Harvest Strategy — Binance Futures Disclosure
When the Funding Harvest strategy is enabled, ApexQuant will trade on both your Binance Spot account and your Binance Futures (perpetuals margined in your chosen currency, USDT or USDC) account. Specifically, the Harvest module opens a spot long position and a perpetual futures short position of equal notional size. By enabling the Funding Harvest strategy, you acknowledge and agree that:

• You must have Binance Futures enabled on your account prior to enabling this strategy
• Your Binance API key must have both Spot Trading and Futures Trading permissions enabled
• ApexQuant does not move funds between your Spot wallet and your Futures wallet: you must keep enough of your chosen currency (USDT or USDC) in each wallet for the strategy, and you move funds between them yourself
• Futures trading carries risks beyond spot trading, including but not limited to: liquidation risk, funding rate reversals, and increased counterparty exposure
• You are solely responsible for ensuring your Binance account is correctly configured to allow both account types

All other strategies (Directional, DCA, Grid) trade exclusively on your Binance Spot account and do not require Futures account access or Futures API permissions.

2.11 Grid Bot Strategy — Range Selection and Trend Risk
When the Grid Bot strategy is enabled (PRIMARY_STRATEGY=grid), ApexQuant places and manages a series of limit buy and sell orders within a user-defined price range. By enabling the Grid Bot, you acknowledge and agree that:

• Grid Bot profitability depends entirely on price remaining within the configured range. In a sustained downtrend, all buy levels will fill and you will accumulate inventory that continues to decline in value.
• You are solely responsible for selecting the price range (GRID_LOWER_PRICE, GRID_UPPER_PRICE), the number of levels, the total allocation, and the range break behaviour (GRID_BREAK_ACTION). ApexQuant does not recommend, validate, or optimise these parameters on your behalf.
• When price exits the configured range, the Range Break Action determines behaviour: pause (halt new orders, keep inventory), close (release inventory to the exit manager for take-profit/trailing exit — not force-sold by the grid), or hold. Inventory released to the exit manager is subject to its own exit logic; fills occur at prevailing market prices and may differ from any target price (slippage). ApexQuant is not liable for losses resulting from market movement, slippage, or the range break behaviour you select.
• Grid Bot does not use AI Commentary, ML signals, or regime filters to adapt order placement. It is a purely mechanical, rule-based strategy. It will continue placing orders in deteriorating market conditions according to your configured range and Range Break Action until the break action triggers or you manually pause or reset it.
• Running multiple ApexQuant instances with Grid Bot active on the same Binance account or Binance sub-account without careful allocation management may result in overexposure. You are responsible for total capital allocation across all instances.
• No profit is guaranteed. Past performance of grid strategies in any market condition is not indicative of future results.

2.12 DCA (Dollar-Cost Averaging) Strategy — Averaging-Down and Open-Ended Exposure Risk
DCA is the default primary strategy (PRIMARY_STRATEGY=dca) and operates in one of two user-selected modes. By enabling DCA you acknowledge and agree that:

• In DROP mode, ApexQuant buys additional inventory each time price falls by DCA_DROP_STEP_PCT% below the last entry, continuing until your allocated budget or maximum number of legs is reached. Averaging down increases your position size and total cost exposure as the asset declines; if the asset does not recover, your accumulated losses will be larger than a single entry would have produced.
• When the exit mode is set to none, the strategy never sells automatically — positions are held indefinitely until you manually exit, regardless of drawdown depth.
• In TIME mode, ApexQuant accumulates on a fixed schedule with no market-timing and no downside protection; the position tracks the asset's performance, including sustained declines.
• You are solely responsible for the drop step, take-profit/trailing parameters, budget, maximum legs, and exit mode (DCA_DROP_STEP_PCT, DCA_TP_PCT, DCA_TRAIL_ARM_PCT, DCA_TRAIL_DISTANCE_PCT). ApexQuant does not recommend, validate, or optimise these on your behalf and does not guarantee recovery, profit, or any outcome.
• The kill switch halts new DCA buys but does not force-close existing positions; open inventory remains subject to market risk until it exits via your configured take-profit/trailing rule or manual action.
• No profit is guaranteed. Past performance of dollar-cost-averaging in any market condition is not indicative of future results.

2.13 Directional Strategy — Experimental Signal Risk
The Directional strategy is marked EXPERIMENTAL (see 2.9) and generates entries and exits from machine-learning models, technical indicators, and regime/macro filters. By enabling it you acknowledge and agree that:

• Signals are probabilistic and may produce false entries, whipsaw losses in ranging or choppy markets, and degraded performance as live conditions diverge from the data the models were derived on.
• It has not been validated to produce consistent returns across all market conditions, and no parameter defaults should be assumed optimal.
• You are responsible for enabling it, configuring its parameters, and monitoring its performance. ApexQuant guarantees no outcome.

2.14 Status Display and Safety-Feature Risk
The Software's dashboards, status indicators, health checks, equity and drawdown figures, alerts, and protective features (including but not limited to the kill switch, drawdown limits, automated halts, and any “operational” or healthy-state indicator) are provided on a best-effort basis and may fail, be delayed, display inaccurate or stale information, or indicate a healthy or operational state while the Software is in fact malfunctioning. You must not rely on any status indicator, health check, equity figure, or safety feature as a guarantee that the Software is functioning correctly or that your funds are protected. You remain solely responsible for independently monitoring your exchange account, open orders, balances, and positions directly on the exchange. The vendor is not liable for any loss arising from reliance on the Software's displayed status, from the failure, delay, or inaccuracy of any safety feature or indicator, or from the Software placing duplicate, missed, partial, or unintended orders, including following a restart, recovery, or reconnection.

2.15 Pre-Release / Active Development
The Software is under active development and may contain defects, errors, or incomplete features. New versions may change behaviour. You use the Software at your own risk and are responsible for testing in a non-live (paper or testnet) mode before committing real funds, and after any update.

Limitation of Liability

3.1 The vendor shall not be liable for any direct, indirect, incidental, special, consequential, or punitive damages arising from or in connection with:

• Trading losses incurred through use of the Software
• Loss of profits, revenue, or anticipated savings
• Technical failures, bugs, or incorrect signal generation
• Exchange outages, API failures, or connectivity issues
• Unauthorised access to the User's server or exchange account
• Incorrect configuration by the User
• Any decision made in reliance on the Software's output
• Inaccurate, delayed, or stale status indicators, health checks, equity or drawdown figures, or alerts
• Failure, delay, or malfunction of any safety feature, kill switch, drawdown limit, or automated halt
• Duplicate, missed, partial, or unintended orders arising from software malfunction, restart, or recovery

3.2 The User acknowledges that they are solely responsible for the security of their own server infrastructure, including SSH access controls, firewall configuration, API key management, and protection of configuration files.

3.3 In any event, the vendor's total liability to any User for any claim arising from the Software shall not exceed the amount paid by the User for their license in the three (3) months immediately preceding the claim.

3.4 The User agrees to indemnify and hold harmless the vendor from any claims, losses, or damages arising from the User's use of the Software, violation of these Terms, or violation of any applicable laws or regulations.

3.5 Nothing in these Terms excludes or limits any liability that cannot be excluded or limited under applicable law. Where any limitation, exclusion, or disclaimer in these Terms is held unenforceable or invalid, it shall be severed and the remaining limitations, exclusions, and provisions shall continue to apply to the maximum extent permitted by law. The total-liability cap in 3.3 applies in aggregate across all claims, whether in contract, tort, or otherwise.

Platform & Exchange Disclaimer

4.1 Binance Only
ApexQuant currently supports Binance exchange only (including Binance Testnet for paper trading). Support for other exchanges is not currently available and is not guaranteed to be added in future versions.

4.2 No Affiliation
ApexQuant is an independent software product and is not affiliated with, endorsed by, or officially connected to Binance or any other cryptocurrency exchange. All product names and trademarks are the property of their respective owners.

4.3 Exchange Terms
Users are responsible for ensuring their use of the Software complies with Binance's Terms of Service, including any restrictions on automated trading in their jurisdiction.

Data Integrity Risk
The Software relies on third-party market data feeds and external APIs including Binance, CoinGecko, FRED, and others. Market data may be delayed, incomplete, interrupted, or inaccurate. The Software may generate incorrect or unintended outputs due to faulty, stale, or unavailable data inputs. The vendor makes no representation as to the accuracy, completeness, or timeliness of any data used by the Software.

Execution Variance
Actual trade execution price and quantity may differ from requested values due to market slippage, partial fills, liquidity constraints, exchange-imposed filters (such as LOT_SIZE or MIN_NOTIONAL), or Binance API behaviour. Such differences are outside the vendor's control and the vendor is not liable for any losses arising from execution variance.

No Fiduciary Relationship
Use of the Software does not create any fiduciary, advisory, agency, or investment management relationship between the User and the vendor. The vendor is a software tool provider only. Nothing in these Terms or the operation of the Software constitutes financial, investment, tax, or legal advice.

4.4 Base Currency Requirement
ApexQuant trades in one base currency per account, which the User chooses: either USDT (Tether) or USDC, on Binance (for example BTCUSDT and ETHUSDT on a USDT account, BTCUSDC and ETHUSDC on a USDC account). The User's Binance Spot wallet must hold the chosen currency as the base trading currency. Other stablecoins, including but not limited to BUSD and FDUSD, are not traded and may result in failed orders or unintended behaviour. A stablecoin the User holds that is not the chosen currency is not managed by ApexQuant: it is shown separately, valued at the live exchange rate, and never used for trading. The User may change the base currency later; ApexQuant then asks the User what is to be done with any open orders and any coin already held, and acts only on the User's choice. Any conversion between USDT and USDC that ApexQuant offers is optional, is carried out only when the User chooses it, and uses the live exchange rate at that time; ApexQuant never assumes that one stablecoin equals another. ApexQuant and its vendor are not liable for any losses, failed orders, or account issues arising from the use of an unsupported currency, or from a conversion or switch the User chooses, including price differences between the two stablecoins. Users are solely responsible for ensuring their account holds the chosen currency before activating live trading.

4.5 Third-Party Data Services
ApexQuant integrates data from the following third-party services. The vendor makes no warranties regarding the accuracy, availability, or continuity of these services, and is not liable for any losses arising from data errors, API outages, or changes in third-party terms of service.

4.6 API Key Security
API keys are stored solely on the User's own server and are never transmitted to or stored by the vendor. Users should create API keys with trading permissions only — never enable withdrawal permissions on API keys used with the Software. Customers are strongly encouraged to use Binance sub-accounts for ApexQuant API keys to limit exposure to their primary holdings.

4.6a Binance Sub-account Usage
Using a dedicated Binance sub-account for ApexQuant is strongly recommended for all tiers. A sub-account provides fund isolation: the bot only has access to funds explicitly transferred to the sub-account, and cannot interact with the user's main account holdings. Users on regional Binance entities that do not support sub-accounts should dedicate a separate full account to ApexQuant, or accept the main-account risk with documented awareness.

4.7 Binance API Key Best Practices
Users are strongly advised to follow these security guidelines when creating API keys for use with ApexQuant. Failure to follow these guidelines may result in unauthorised access to your trading account.

License & Permitted Use

Upon purchase of a valid license key, the vendor grants the User a limited, non-exclusive, non-transferable license to install and use the Software on a single server for personal or commercial trading on their own account.

The User may not:

• Redistribute, resell, sublicense, or share the Software or license key with any third party
• Reverse engineer, decompile, or modify the Software
• Use the Software to trade on accounts belonging to others without explicit written authorisation from the vendor
• Remove or alter any proprietary notices or license validation mechanisms
• Use the Software for any unlawful purpose

License keys are bound to the server on which they are first activated. License transfers must be requested through the vendor. Violation of these license terms will result in immediate suspension of the license without refund.

Single instance restriction: Each license key may only be activated on one (1) machine and operated by one (1) individual for trading on their own account. The following are expressly prohibited and constitute a material breach of these Terms:

• Installing or running ApexQuant in multiple directories, containers, screen sessions, or server instances under a single license key
• Using one license key to serve multiple end-users or trading accounts belonging to others
• Sharing, sublicensing, reselling, or otherwise providing access to the Software or license key to any third party

Violations will result in immediate key revocation without refund and may be reported to the relevant authorities where commercial resale without authorisation constitutes a legal offence.

Privacy Policy

6.1 Data Collected
When you purchase a license or contact us, we collect your name and email address for the purpose of license management and customer support. This data is stored in encrypted form on our licensing server.

6.2 License Verification Data
When the Software performs a periodic license validation, the following data is transmitted to our licensing server:

• Your license key (for validation purposes only)
• A server identifier token (non-reversible, cannot identify you personally)
• Your Software version number
• Your server's IP address (used for licensing verification only)

6.2a Trial Telemetry
Trial installations (unlicensed instances using the free trial period) periodically transmit anonymous telemetry to our licensing server to validate trial usage and display live trial activity to the vendor. This telemetry consists of:

• A hashed machine fingerprint (one-way hash — cannot identify you or your server)
• Your Software version number
• Trial days remaining (a counter only)

No API keys, account balances, trading history, positions, or personal data are included in trial telemetry. This telemetry ceases once a valid license key is activated.

6.3 What We Do Not Collect
We have no access to and do not collect:

• Your Binance API keys or account credentials
• Your trading history, balances, or positions
• Any data from your trading dashboard
• Any other data from your server beyond the items listed in 6.2

6.4 Data Retention
Licensing records are retained for support and abuse prevention purposes and are deleted when no longer needed. Customer name and email are retained for the duration of the license and up to 2 years after expiry for billing records.

6.5 Data Sharing
We do not sell, share, or transfer your personal data to any third party except as required by law or to prevent fraud. We use Telegram for internal alerting only — no customer data is transmitted to Telegram beyond what is necessary for the vendor's own operational monitoring.

6.6 Governing Law & Dispute Resolution
These Terms shall be governed by and construed in accordance with the laws of the jurisdiction in which the vendor maintains its principal place of business, without regard to conflict-of-law principles. Any dispute, claim, or controversy arising out of or relating to these Terms or the Software that cannot be resolved amicably shall be referred to and finally resolved by binding arbitration. The seat, governing arbitral rules, and language of the arbitration shall be those designated by the vendor at the time the dispute arises, conducted in the English language unless otherwise agreed. Each party shall bear its own costs of the arbitration. Nothing in this clause prevents the vendor from seeking injunctive or equitable relief in any court of competent jurisdiction to protect its intellectual property or enforce its license terms. To the extent any mandatory consumer-protection law of the User's place of residence grants rights that cannot be waived by agreement, nothing in these Terms removes those rights.

Third-Party Services & Attributions

ApexQuant integrates with a number of third-party services, APIs, and open-source libraries. By using the Software, you acknowledge that your use is also subject to the terms and policies of these services. ApexQuant is not affiliated with, endorsed by, or officially connected to any of these providers.

All third-party trademarks, service marks, and trade names are the property of their respective owners. ApexQuant claims no ownership over any third-party intellectual property referenced herein.

General

9.1 Entire Agreement
These Terms (together with the license terms and any policy referenced herein) constitute the entire agreement between the User and the vendor regarding the Software and supersede all prior understandings or representations.

9.2 No Waiver
The vendor's failure to enforce any provision of these Terms is not a waiver of its right to do so later. No waiver of any term is effective unless in writing.

9.3 Severability
If any provision is held invalid or unenforceable, the remaining provisions continue in full force and effect (see also 3.5).

9.4 Assignment
The User may not assign or transfer these Terms or any license without the vendor's prior written consent. The vendor may assign these Terms in connection with a merger, acquisition, or sale of assets.

9.5 Acceptance
By purchasing, downloading, installing, or using the Software, the User acknowledges that they have read, understood, and agree to be bound by these Terms.

9.6 Tax Responsibility
The User is solely responsible for determining, reporting, and paying any taxes arising from their trading activity or use of the Software.

Headings are for convenience only and do not affect interpretation.

Contact

For license support, questions about these Terms, or data requests, contact us at:

{email}

These Terms were last updated in June 2026. We reserve the right to update these Terms at any time. Continued use of the Software following notification of changes constitutes acceptance of the updated Terms.