Version 2026-10-11. Part of the Terms of Use. This policy explains what TradersLake collects when you use TradersLake, why, and what we do with it.
We keep as little as we can. We never store your IP address in our usage data, we set one cookie (your session), we do not sell or share data for advertising, and your private keys never come near us. Blockchain activity, including your wallet address and your transactions, is public by its nature and visible to anyone, not only to us.
| Data | When | Why |
|---|---|---|
| Email address and a salted password hash | You create an email account | To sign you in and reach you about your account |
| Wallet address | You sign in with, or link, a wallet | To identify your account and verify payments from it |
| Sign-in messages and signatures | Wallet sign-in | To verify the sign-in; the request is kept briefly and then deleted |
| Payment records: transaction hash, amount, plan, dates | You pay for a plan | To activate the plan and keep financial records |
| Usage events: pages opened, time on page, controls used, searches, coins viewed, errors, page speed, API calls per route | You use the site or API | To run, secure and improve the product, and to show aggregate figures such as how many people opened a coin (never who) |
| Device class, browser family, operating system, country (from our network provider), a visitor identifier that is a one-way hash which changes every day | Every visit | To tell visitors apart within a day and to spot abuse — none of it identifies you across days or reveals your address |
Session cookie (tsd_session) | You sign in | To keep you signed in; HttpOnly, 30 days |
| Preferences such as theme, board filters and watchlist | You set them | Stored only in your own browser, never sent to us |
| Agent tool calls: tool, door (MCP or HTTP), outcome, time taken, answer size, the arguments' shape (a SQL text only as a length and a hash) | Your agent calls a tool with your key | To meter your plan, show you your usage, and stop abuse |
| Promotion records: kind, token, wallet, transaction hash, amount, dates, and the content you submitted | You buy a promotion or an ad | To show it, label it and keep financial records |
| Votes, red flags and notes on coins | You vote on a coin | To show the community read; notes are public, your identity is not |
| Messages you send us | You contact us | To reply |
What we do not collect. We do not store IP addresses in usage data, full user-agent strings, anything you type into fields (other than searches, which are kept as search terms), private keys, recovery phrases, or payment-card details. We run no advertising trackers and no third-party analytics.
We do not sell personal data, and we do not share it for advertising. We may disclose data to comply with law, to enforce the Terms, to protect the Service or others, or to a successor of the Service.
Passwords are stored as salted hashes; sessions are HttpOnly cookies sent only over HTTPS; the Service runs isolated from our other systems with the minimum database access it needs; payments and sign-ins are verified on our own node. No system is perfectly secure, and we cannot guarantee that data will never be accessed or disclosed without authorisation.
The Service is not for anyone under 18, and we do not knowingly collect data from them.
Data is processed where our infrastructure and providers operate. If you are outside that jurisdiction, your data may be transferred to it. By using the Service you consent to that transfer to the extent the law allows.
We may update this policy; the version at the top changes when we do, and material changes are announced on the Service.
Privacy questions and requests: the contact address on the home page.