Last updated: [PLACEHOLDER — insert date before publishing]
[PLACEHOLDER: List every category of data the tool stores — wallet addresses, trade history, LLM conversation history, equity curves, strategy parameters, session tokens, audit logs, etc.]
TraderDude encrypts wallet private keys at rest using PBKDF2HMAC key derivation before writing them to disk. The passphrase is never stored — it is required at startup.
[PLACEHOLDER: Confirm exact encryption algorithm, salt storage, and any other security measures in place. Have a security professional review before publishing.]
To generate trading analysis, TraderDude sends portions of your trade history and market data to external LLM providers you configure.
[PLACEHOLDER: List the specific LLM providers that may receive data (e.g. OpenAI, Anthropic, Google, self-hosted models). State whether data processing agreements (DPAs) are in place with each. Confirm what data is included in prompts — strategy context, price history, wallet balances?]
[PLACEHOLDER: State how long trade history, LLM logs, audit logs, and board messages are kept. State whether users can request deletion before that period. See also item-026 (User Data Deletion) in the vibe-check checklist.]
[PLACEHOLDER: Describe how a user can request a copy of their data, correct inaccurate data, or have their data deleted. Under GDPR/UK GDPR these are legal rights; under CCPA similar rights apply for California residents. Provide a mechanism (email address or in-app request flow).]
TraderDude uses a single HTTP-only session cookie to authenticate the dashboard. No tracking or analytics cookies are used.
[PLACEHOLDER: Provide a contact email or postal address for privacy requests. GDPR requires a named controller and a contact method.]