TL;DR: Blockchair does not collect personal data or share it with third parties. We don't track you.
Why is this important?
One of the key advantages of cryptocurrencies is that they enable (pseudo)anonymous transactions. In most cases the user’s address and transaction details are made public and cannot be deleted, but their personal identity remains unknown if no link exists between the user and their blockchain data.
Privacy is at risk when you share any information with third parties. Cryptocurrency exchanges with KYC policies, online retailers that require delivery addresses and web wallets associated with phone numbers all require you to share information.
What’s more, most web servers maintain default logs of your IP address and User Agent (browser name and operating system), the dates and times of your browsing activity and, most importantly, the URLs you visited. Ordinarily, a cryptocurrency address page is only visited by the address owner, while the transaction page is visited by the transaction parties. Blockchain explorers can therefore easily trace the digital fingerprint that links addresses and transactions. Unfortunately, this data is also picked up by the web analytics tools (Google Analytics, Baidu Tongji, Yandex.Metrica), advertising platforms and similar third-party services.
User data can be traced in others ways too. CDN providers like Cloudflare, Incapsula and AWS Shield act as reverse proxies, which means some websites require you to request data from a CDN in order to use the site. You therefore share your information with the provider.
In addition to these data tracking services, there are several other ways how users can be identified online.
- HTTP referer: a client request header that allows a server to trace the previous site you visited. Say you visit example.com followed by explorer.com/1YourBitcoinAddress then the former will receive information that you have come from the latter;
- Web beacon (bug): an invisible web page element that confirms a user has visited a web page. This is used to collect user analytics;
- Cookies: user activity data stored in the user’s browser. Third-party cookies can also be embedded in the site’s code (if it contains elements from other sites);
- Device / browser fingerprint: the device and browser information collected for user identification;
- Browser extensions.
Why is it unsafe to share you personal data?
Most blockchain explorers and cryptocurrency companies store user information, including available balances, lists of transactions and types of cryptocurrency.
They might sell this information, publish it, share it with government agencies, or they might be hacked. If it becomes public knowledge that you have significant funds stored in cryptocurrency, you’re likely to be targeted by cyber criminals. Your personal safety may be at risk too.
Why is Blockchair the safer option?
- When you connect to Blockchair your browser automatically sends us information about your computer, User Agent, IP address, and the page you want to visit. Since this data may expose your identity, we do not permanently store information about you;
- Your browser won’t send HTTP referer headers when leaving Blockchair.com. This means you can move to other sites without your browsing activity being traced by those sites;
What data do we store and how do we use this data?
We only collect anonymous aggregated data that allows us to improve our website features. We count visitors, analyze popular searches, cryptocurrencies, sortings and other queries.
We also store the incoming IP addresses for short periods of 5 to 10 minutes. This is to limit the rate of API requests.
Your device may store technical cookies, such as those that keep the night mode on. In this case, only the client part of the site interacts with them.
Collected data is used to improve user experience and compile website traffic statistics.
We might activate logging procedure to safeguard our services since we're not protected from certain types of third-party network attacks. If this happens, we will post a notification in the site header to let you know we're collecting additional information during the attack. Once the attack has been stopped, all logs will be deleted along with the notification.
Please share your comments and suggestions at email@example.com.