This page explains which of your information CoinVair touches and which it doesn't. We'll keep it plain so you can judge for yourself. The core of it in one line: this is a static content site — there are no accounts, and we don't collect your trading data.
Your Binance account, login credentials, passwords, verification codes, seed phrase, funds and trade history — we don't have them and won't try to collect them. You don't need to register, log in, or fill in any personal details to read everything here and use every tool.
The calculators on this site (position size, liquidation, DCA, halving locator and so on) all run purely in your browser: the numbers you enter are computed on your own device, never uploaded to our servers, and we can't see what you calculated.
Although we don't actively collect personal information, running a website does involve some standard technical data. Here it is, plainly:
CoinVair is served through Cloudflare. The server behind it doesn't write access logs, so there's no visit log on our side. Cloudflare, sitting in front, processes your IP address, the URL you requested and your browser type in order to deliver the page and fend off attacks; that's covered by Cloudflare's privacy policy.
Cloudflare also loads a Web Analytics script on our pages (from static.cloudflareinsights.com). It shows us how many times pages were opened, which sites referred readers and how quickly things loaded, all as overall figures. According to Cloudflare, it doesn't depend on cookies or localStorage, and it doesn't use IP addresses or browser characteristics to work out who a visitor is.
To show live prices and market mood on the page, your browser makes requests directly to the following public data feeds when the relevant pages load:
These are requests for public market data and don't involve any of your account information; but because your browser connects directly, the other side may see your IP and basic network details. Their respective privacy policies are their responsibility and outside our control.
We use Google Analytics 4 (GA4) to understand page visits, interactions, device and browser information, and approximate region. GA4 uses cookies and similar technologies, and Google processes the resulting data. GA4 keeps sending visit data even when cookies are blocked; an extension that blocks tracking scripts is what actually stops it, along with the Cloudflare script above.
This site contains referral links to Binance (code BN771) and links to other external sites. Once you click away from CoinVair, your activity is governed by the destination site's own privacy policy (e.g. Binance's), not ours.
CoinVair does not set advertising cookies. Some small interface states may be stored in your browser’s localStorage. We use Google Analytics 4 (GA4) to understand page visits, interactions, device and browser information, and approximate region. GA4 uses cookies and similar technologies, and Google processes the resulting data. You can delete these cookies in your browser at any time; to keep the analytics from running in the first place, use a blocking extension.
Because we don't create accounts or actively collect information that identifies you, the usual "delete my account data" doesn't really apply here — there's no such data to delete. If you are in a region covered by the GDPR or a similar regime, you retain your rights of access, rectification, erasure, restriction, objection and portability with respect to any personal data (for example the connection data described above). Since we hold very little such data, most of it is handled by Cloudflare, Google and the third-party feed providers under their own policies. If you have any question about how your data is processed, write to us at [email protected] and we'll help point you in the right direction.
Crypto and stock trading are not suitable for minors. This site is intended for adults; we don't target minors and won't knowingly collect their information.
This privacy policy may be adjusted from time to time, effective immediately on posting. Significant changes will be noted in the corrections, and the "last updated" date at the top will be kept in sync.