OptionForge
Legal & support

Customer Responsibilities & Safe Use

Corporate identity: OptionForge is a software product owned and operated by NeuroQuant Financial Technologies Inc. References to OptionForge identify the product; NeuroQuant is the owner/operator where a legal entity is required.

User responsibilities for data validation, model review, credential protection, device security, and safe trading decisions.

Last updated: August 24, 2026Policy package v72Support: [email protected]
Current distribution model: OptionForge itself is free to download from Microsoft Store. OptionForge does not charge a subscription or purchase price for the current public release. Third-party broker, market-data, exchange, connectivity, or other external-service charges may still apply under those providers' terms.
This static page is part of the current OptionForge free-release legal/support package and is designed to remain directly reachable outside the React app shell.

Page sections

Input responsibility

Users are responsible for the accuracy of symbols, expirations, strikes, option types, position quantities, prices, dividends, rates, commissions, tax assumptions, margin assumptions, and custom data entered into the app.

Imported or copied data should be verified against the original source before calculations are used.

Trading responsibility

OptionForge is an analytics tool. Users remain solely responsible for trading decisions, account selection, risk tolerance, position sizing, order entry, tax review, and professional advice decisions.

The app does not place trades, hold funds, custody assets, guarantee margin treatment, or replace a broker, adviser, accountant, lawyer, or compliance officer.

Device and credentials

Users should protect their device, Microsoft account, market-data credentials, API keys, local files, backups, screenshots, logs, and exports.

Do not send passwords, full payment data, private keys, seed phrases, or unrelated confidential information to support.

Review and records

Professional users should keep their own records of assumptions, approvals, data sources, model versions, screenshots, exports, and decisions. App outputs should be reviewed before use in reports, client communications, or compliance workflows.

Related legal and support pages