LEGAL
Privacy Policy
1. Who We Are
ZecBlock (zecblock.com) is an open-source Zcash blockchain explorer operated by Atmosphere Labs (“we”, “us”, “our”).
2. Information We Collect
You can browse without creating an account. The information processed depends on the pages and tools you use.
- Requests and diagnostics: Our hosting, API and security services process connection information such as IP addresses, requested URLs and browser headers to deliver responses, limit abuse and diagnose failures. Infrastructure providers may retain operational logs; we do not promise that requests are unlogged.
- Explorer lookups: Looking up an address, transaction or block sends that public identifier to our services. Public chain data and derived observations are indexed for the explorer. Shielded addresses, amounts and memos cannot be read from public chain data without the required keys or a voluntary disclosure.
- Viewing keys: The memo and inbox tools process viewing keys in your browser. The application does not send those keys to our API. It requests blockchain data and matching transaction data, which can reveal requested ranges or transaction identifiers to the services supplying them. Keep viewing keys, recovery phrases and private keys out of search fields, Ask and support messages.
- Zift answer ratings: When you rate an answer, we add one to daily counters for the vote (useful or not useful), any reason you pick from a fixed list, the type of answer (for example SQL result, chart, explanation, decline or clarifying question), whether a fallback summary was used, the answer language and the page. These counters contain no questions, answers, SQL, addresses, IP addresses or user identifiers and expire 30 days after their last update. If you also tick Share, we keep that question, Zift’s answer and any SQL it ran, together with the same rating details and a random ID created in your browser for that one answer (not linked to you or your other answers) so a later change can replace or withdraw it. Shared answers are stored without your IP address, are read only by the ZecBlock team to fix answers, are capped per day and expire 30 days after they were shared. Unticking Share within 24 hours deletes the copy. Ratings are rate-limited per connection in server memory only. They do not automatically train the AI.
- Research counters: Where research is enabled, we count query outcomes, duration bands, public dataset names and query features in daily aggregates. These counters contain no questions, SQL, query fingerprints, addresses, IP addresses or user identifiers, and expire 30 days after their last update. They do not automatically train the AI. Queued SQL and results are temporary execution state with a one-hour expiry; result caches expire after 30 seconds. Analyses you choose to save stay in your browser or downloaded file.
- Swaps and support: Swap providers process the addresses and transaction details you supply. If you contact us, the contact service receives the information you submit. Do not post private keys or other secrets in public issues or social messages.
3. Third-Party Services
We integrate with third-party services that have their own privacy policies:
- Hosting and analytics: Vercel hosts the frontend. We use Vercel Web Analytics for aggregate visits to selected public landing pages. Our analytics filter removes query strings and fragments and excludes individual address, transaction and block pages, Ask, and sensitive tools. See Vercel’s analytics privacy documentation.
- Zift (formerly Ask): Free-form questions, recent conversation context and relevant public data are sent to our API and, when AI is enabled, its configured provider (OpenAI or Anthropic). The OpenAI integration disables optional response storage; this does not guarantee zero provider retention. Public-data explanations may be cached briefly. Zift and its MCP server store no IP addresses or identifiers derived from them, hashed or otherwise: their usage limits are site-wide counters shared by all visitors. A short-lived in-memory limiter uses your IP address only to count requests in the past minute and keeps nothing after that. Cloudflare Turnstile can process browser and connection information for abuse prevention. Do not submit confidential or personal information to Ask.
- NEAR Intents (1-Click Swap): Cross-chain swap quotes and execution. When you initiate a swap, your transaction data is shared with NEAR Intents to facilitate the exchange.
- Fiat on-ramp providers: If you purchase cryptocurrency with a credit card through an embedded widget, you interact directly with the provider (e.g. MoonPay). They may require identity verification (KYC). We do not receive or store your payment information.
4. Cookies & Tracking
The app uses local or session storage for preferences such as theme, currency, feed layout, custom address labels and dismissed announcements. You can remove these through your browser’s site-data controls; doing so also removes saved preferences and labels. Vercel Web Analytics is cookieless. We disable Vercel Web Analytics when the browser sends Do Not Track or Global Privacy Control. External swap, purchase and security providers follow their own storage and privacy policies.
5. Data Sharing
We do not sell, rent, or share your personal information with third parties for marketing purposes. We may disclose information if required by law or to protect the security of our service.
6. Data Security
We use HTTPS encryption for all connections. Our servers are secured with standard industry practices. However, no method of transmission over the internet is 100% secure.
7. Retention & Your Choices
Public blockchain records are permanent and cannot be removed from the blockchain by us. Browser preferences remain until cleared or expired by your browser. Operational, provider and correspondence retention depends on the service and applicable requirements. Depending on your location, you may have rights to access, correct or delete personal information, or object to its processing. Contact us to make a request; do not include sensitive information in a public post.
8. Changes
We may update this policy from time to time. Changes will be posted on this page with a revised “last updated” date.
9. Contact
Questions? Reach us on X / Twitter or open an issue on GitHub.