OptionForge
Legal & support

Crash Reporting & Error Telemetry

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.

Crash, diagnostics, error log, support-file, and redaction rules for OptionForge support and reliability workflows.

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

Purpose

This page explains how crash reports, startup logs, app exception logs, packaging diagnostics, Store installation/access errors, broker/data integration errors, and support diagnostics should be handled.

It supplements Diagnostics & Logs, Data Security & Retention, Support Attachments & Log Redaction, and API Keys, Credentials & Secrets.

Local-first diagnostics

The desktop app should prefer local logs and user-controlled support sharing. Local diagnostics may include timestamps, module names, exception messages, app version, Windows version, packaging state, entitlement status, and provider error categories.

Local diagnostics should not intentionally collect brokerage passwords, full payment card details, seed phrases, private keys, or unrelated personal information.

User-submitted logs

When a user sends logs or screenshots to support, those materials are processed for troubleshooting, reliability, licensing, security, and support-quality purposes.

Users should review and redact logs before sending. Support may request additional details only when necessary to diagnose the issue.

Crash and telemetry changes

If automatic crash telemetry or remote diagnostics are added later, the Privacy Policy, Diagnostics & Logs, Cookie Policy, and this page should be updated before public deployment.

Retention

Diagnostic records should be retained only as long as reasonably needed for troubleshooting, security, quality, legal, and audit purposes, unless a longer period is required for disputes, abuse prevention, or compliance.

Related legal and support pages