Account information
Trading Boy uses account email and API-key based access to authenticate users, recover access, and connect product workflows.
Privacy
Trading Boy privacy overview
This page summarizes how Trading Boy thinks about account data, support data, and paper-trading workflow records. The Terms of Service remain the controlling legal document.
Product records
Paper-trading records, agent decisions, review logs, and benchmark opt-in data are used to operate the product and show user-requested workflows.
Privacy requests
Email privacy@tradingboy.ai for data access, deletion, or privacy questions.
Analytics
Trading Boy uses Google Analytics to understand aggregate site usage, page views, signup clicks, pricing-plan clicks, docs clicks, and SEO CTA clicks. Analytics events should not include API keys, private account identifiers, or paper-trading journal content.
Data areas to understand
Trading Boy is a paper-trading workflow product, so privacy review should distinguish website analytics, account access data, support messages, paper-trading records, and public benchmark opt-in data.
| Data area | Used for | Privacy expectation |
|---|---|---|
| Website analytics | Aggregate page views, signup clicks, docs clicks, pricing clicks, and SEO CTA clicks. | Do not place private API keys, account secrets, or journal content in analytics event labels. |
| Account access | Authentication, starter-key recovery, billing support, and product access. | Support may ask for account email, but should not ask for full private keys or seed phrases. |
| Paper-trading records | Agent review, journal workflows, risk checks, and simulated benchmark calculations. | Use the paper trading data privacy checklist before sharing records outside the private workflow. |
| API key context | Permission labels, rotation notes, and whether a key was avoided for paper trading. | Use the API key safety checklist and AI trading agent permission boundaries; do not share full API key values. |
| Public opt-in data | Leaderboard aliases, simulated metrics, and methodology context. | Public pages should use opted-in aliases and avoid exposing private account identifiers. |
How to make a request
Email privacy@tradingboy.ai with the account email, request type, and whether the request concerns account access, support history, paper-trading records, analytics, or leaderboard opt-in data.
What not to include
Do not include full API keys, exchange credentials, private wallet keys, seed phrases, or unrelated financial account records in privacy emails.
Public benchmark opt-in
The public leaderboard should only expose opted-in public aliases and benchmark metrics. Do not publish private account identifiers or full API keys. For methodology details, read Leaderboard Methodology; for record hygiene, use the Paper Trading Data Privacy Checklist; for account help, use Support.