⌘K
🛡️ Institutional Transparency & Heimdall & Bor Standard

Terms of Service & Privacy Policy

Effective Date: September 2026 · Version 3.0 (Polygon PoS Production)

1. Acceptance of Terms & Scope

By accessing or using PolygonScanner (polygonscanner.com) and its associated APIs, web portals, micro-widgets, or machine interfaces (/llms.txt), you agree to be bound by these Terms of Service. PolygonScanner provides an indexing, search, verification, and Heimdall & Bor 6-shard telemetry interface for Polygon PoS and decentralized Web3 ecosystems.

2. Zero-Custody & Privacy Commitments

🔐 Non-Custodial Architecture

PolygonScanner never holds, requests, transmits, or stores your private access keys, recovery seed phrases, or wallet credentials. All portfolio tracking, multi-account watchlists, and settings operate strictly in client-side LocalStorage.

🚫 Zero Account Tracking

We do not sell, broker, or monetize your search queries, named account lookups, or IP addresses. Queries made to our public explorer are served via distributed in-memory caches and public POL JSON-RPC 2.0 Fullnodes.

3. Public Blockchain Data & Disclaimers

All block heights, transaction hashes, execution receipts, and storage staking records displayed on PolygonScanner are fetched directly from decentralized Polygon PoS nodes across all 6 Heimdall validators. The POL blockchain ledger is immutable and cryptographically secured. PolygonScanner has no authority or technical ability to modify, pause, revert, or censor transactions executed on decentralized networks.

Important Disclaimer: On-chain data, validator APY projections, contract bytecode analyses, and fee estimates provided on this site are for informational and diagnostic purposes only. They do not constitute financial, investment, or legal advice.

4. Developer API Fair Use & Rate Limits

Public developer endpoints (Developer Portal) are provided for dApp builders, research analysts, and algorithmic systems under fair use terms. High-frequency queries should adhere to the headers returned (X-RateLimit-Remaining) and use batched RPC endpoints where applicable.

5. Responsible Disclosure & Contact

If you discover a security vulnerability or discrepancy in our parser or telemetry pipelines, please submit an issue via our security desk or contact our core engineering team directly at [email protected].

POL
$5.45 0.00005 POL