Security and Responsible Issue Reporting

[Admin]

Use private reporting for security-sensitive issues.

Do not publish exploit instructions, live vulnerabilities, authentication or license-bypass details, API keys, secrets, passwords, account numbers, OAuth codes, session tokens, license keys, private logs, or personal information in a public topic.

A useful report includes

• Desktop app or forum version
• The affected component and the security impact you believe is possible
• The smallest reproducible steps, with every secret and personal value removed
• Date, time, time zone, and whether the market was open
• Sanitized error text, logs, screenshots, and expected behavior
• Whether the issue affects only your computer or may affect other members

Contact the ComputeX administrator privately for suspected credential exposure, authentication or licensing bypass, unauthorized account access, order-execution defects, or anything that could put another person or brokerage account at risk. Do not test against another member, computer, account, or service without explicit authorization.

If trading safety may be affected

Use Stop All Trading, review open orders and positions directly with the broker, revoke exposed provider keys, change affected passwords through the provider's official site, and contact the broker immediately when account activity is unexpected. A forum post is not a substitute for urgent broker or account-security action.

Public Development & Security topics are appropriate for sanitized design discussions, non-sensitive bugs, hardening ideas, and completed fixes that do not expose members.