Soar
Privacy Policy
Soar uses account, strategy, wallet, runtime, and audit information to provide the trading-assistant experience. Sensitive credentials and exchange access must only be handled through approved secure flows.
The application should not expose API keys, secrets, tokens, passwords, cookies, payment data, or exchange credentials in public pages, screenshots, repository artifacts, logs, or issue comments.
Operational evidence may record route names, status summaries, timestamps, and validation results. It must not store raw secret values or private exchange payloads.
If you suspect secret exposure, unauthorized access, or incorrect account isolation, stop the affected workflow and contact the project operator for a security review.