What data CoinView tries not to collect.
CoinView does not require an account, password, wallet connection or exchange API key to read pages or use browser-side calculators. Most tools run locally in the browser and are designed so a reader can test scenarios without sending private portfolio details to CoinView.
For US and international readers, privacy and disclosure language is written with GDPR, CCPA, FTC endorsement guidance, SEC investor alerts and CFTC derivatives risk in mind. Local rules can still be stricter than this page.
Data that may exist in normal operation.
Server logs, security logs, browser user-agent strings, referrer paths, error reports and basic analytics events may be processed to keep the site available, detect abuse and understand which pages need maintenance. Those records should be treated as operational data, not as a profile for trading advice.
If a reader sends email to privacy@coinguan.com, CoinView will receive the address, message content and any attachments the reader chooses to include.
Cookies, affiliate links and third parties.
Affiliate links use the internal path /go/binance.html before sending a reader to Binance. Binance and other third-party sites may set their own cookies and apply their own privacy policies after the reader leaves CoinView.
CoinView does not control the data practices of exchanges, wallet providers, analytics vendors, font providers or embedded data sources.
Legal basis and rights.
Depending on location, readers may have rights under GDPR, CCPA or similar privacy laws to request access, correction, deletion or limitation of personal data. Requests should be sent to privacy@coinguan.com with enough context to locate the relevant record.
CoinView may retain limited records when required for security, legal compliance, fraud prevention or correction history.
Security and retention.
No website can promise perfect security. CoinView keeps the intended data footprint small and avoids collecting account credentials. Operational logs are kept only as long as needed for security, debugging and legal reasons.
Do not send seed phrases, exchange passwords, API secrets, identity documents or account screenshots unless a specific legal process requires it.