Describing a strategy without revealing confidential details

An account manager can protect proprietary details while providing a description useful for risk review. There is a middle ground between publishing every line of code and saying only that the method is confidential: explain its scope, expected behaviour and limitations, backed by evidence appropriate to the claims.

Describe what matters for understanding risk

Identify markets and instruments, typical holding horizon, use of long and short positions, the relationship between position size and capital, and dependence on liquidity. Explain whether decisions are manual, automated or combined, and the role of human oversight. These details need not reveal entry formulas or source code, yet they provide a more useful risk picture.

Separate economic rationale from promises

A method can seek to exploit a market behaviour without claiming that behaviour will persist. Explain which conditions could weaken the premise and how adverse outcomes would appear. Labels such as artificial intelligence, proprietary algorithm or advanced technology do not themselves establish an edge or effective loss control.

A hypothetical description

Instead of a confidential robot with permanent profits, a description might identify specific instruments, short holding periods and sensitivity to execution costs, but only where those statements genuinely match the method. Minimum sizes and conditions prompting review should also be explainable. This example does not describe a real manager or confirm that such a method is available on the platform.

Match evidence to the claim

• For history: period, source, costs and the boundary between live trading and tests.
• For risk: exposure types, declines and data-quality limitations.
• For execution: sizes, partial fills, rejections and sensitivity to delay.
• For oversight: responsible people, review timing and decision records.
• For changes: description version, effective date and differences from the previous version.

Keep secrets out of public introductions

Do not include passwords, API keys, private keys, recovery phrases, investor identifiers or sensitive infrastructure details in text or screenshots. Removing a name is not always sufficient anonymisation: combinations of times and amounts may identify a person. Public evidence should preserve the information needed to support the claim rather than conceal everything until review becomes impossible.

Limited review is not unlimited access

If independent review needs more information, define scope, purpose, recipient, retention period and permissions in advance. A confidentiality agreement alone is not a reason to hand over trading authority or account secrets. Do not send sensitive information in an initial introduction or assume a secure upload or review facility exists without verifying it.

Update the description when the method changes

Changed instruments, horizons or exposure sizes may make an old description unrepresentative. Retain earlier versions and change reasons for reconciliation. Good results after a change do not justify removing unfavourable earlier history. A transparent description also does not prove that live behaviour follows it; ongoing comparison with records remains necessary.

Start a manager cooperation inquiry with non-confidential, reviewable information. When browsing account information, do not substitute a method’s name for evidence. This framework provides neither automatic manager approval nor a recommendation to disclose intellectual property, and it promises no returns.