Privacy, Credentials, and Account Security
Posted: Sun Sep 13, 2026 9:40 pm
Plain-language privacy and security summary — not a substitute for a formal privacy notice.
Never publish or send trading credentials through the forum.
Do not post broker passwords, market-data API keys or secrets, account numbers, OAuth or multi-factor codes, session tokens, license keys, order identifiers when sensitive, government identifiers, payment data, personal addresses, or unsanitized screenshots and logs. ComputeX staff and moderators should not ask you to publish these values.
Desktop credentials
Broker and market-data credentials should be entered only in the desktop Setup page. The desktop application is designed to protect saved secrets for the current Windows user and to avoid displaying them again. Local protection reduces exposure but cannot make a compromised computer safe. Protect the Windows account with a strong password, current security updates, disk encryption where appropriate, and malware protection. Do not share the Windows profile used for trading.
ComputeX account, license, and forum data
License validation and approved-member access can require the activation key, a computer-binding identifier, validation timestamps, and ordinary service-security records such as IP address and request logs. The forum can store the member username, profile settings, posts, messages, moderation history, and technical logs needed to operate and protect the service. Brokerage passwords and market-data secrets should not be included in forum or license-service requests.
If a secret may be exposed
Independent educational guidance: Investor.gov: Protect Your Online Investment Accounts From Fraud. This link is educational and does not imply government endorsement or affiliation.
Never publish or send trading credentials through the forum.
Do not post broker passwords, market-data API keys or secrets, account numbers, OAuth or multi-factor codes, session tokens, license keys, order identifiers when sensitive, government identifiers, payment data, personal addresses, or unsanitized screenshots and logs. ComputeX staff and moderators should not ask you to publish these values.
Desktop credentials
Broker and market-data credentials should be entered only in the desktop Setup page. The desktop application is designed to protect saved secrets for the current Windows user and to avoid displaying them again. Local protection reduces exposure but cannot make a compromised computer safe. Protect the Windows account with a strong password, current security updates, disk encryption where appropriate, and malware protection. Do not share the Windows profile used for trading.
ComputeX account, license, and forum data
License validation and approved-member access can require the activation key, a computer-binding identifier, validation timestamps, and ordinary service-security records such as IP address and request logs. The forum can store the member username, profile settings, posts, messages, moderation history, and technical logs needed to operate and protect the service. Brokerage passwords and market-data secrets should not be included in forum or license-service requests.
If a secret may be exposed
- Use Stop All Trading and review open orders and positions directly with the broker
- Revoke and replace the affected API key or session through the provider's official site
- Change affected passwords and enable multi-factor authentication where supported
- Contact the broker immediately about unexpected account activity
- Send only sanitized details to the ComputeX administrator through a private approved channel
Independent educational guidance: Investor.gov: Protect Your Online Investment Accounts From Fraud. This link is educational and does not imply government endorsement or affiliation.