License & privacy

Transparent boundaries for this demonstration.

MIT License

BlockTrack’s source is released under the MIT License. You may use, modify, distribute, and sublicense it, including commercially, provided the copyright and permission notice are retained. The software is provided “as is,” without warranty. The full terms are included in the LICENSE file. Third-party dependencies retain their respective licenses.

Demonstration data

Charts, asset counts, logs, agents and transaction examples are synthetic. They are not operational claims, customer records, or security advice. Independent security review and live integration work are required before production monitoring use.

Contact and newsletter

Forms validate input in the browser only. Information is not transmitted, subscribed or retained by this application. The interface explicitly confirms that no submission was sent.

Wallet connections

Wallet sign-in requests a signed message, validated by hosted auth to establish an analyst account. Connecting alone does not sign you in. Signing in does not submit a transaction or request payment. Session and connector state may be stored in your browser. Use Sign out to end your session. Your seed phrase and private key are never requested.

Third-party requests

Fonts are loaded from Google Fonts. Wallet functionality may request public Polygon RPC data. External links to PolygonScan and Polygon documentation open third-party services with their own privacy policies.

AI threat assessments

Evidence submitted on the Threat assessment page is sent to AI Gateway for AI-assisted triage. Do not submit secrets or personal data. Raw incident inputs are not stored by BlockTrack. Assessments are saved to your private account only when you choose Save privately; findings may contain excerpts of your submitted evidence. Gateway processing and request logs remain subject to workspace policies. AI access-block status is also stored. Findings require analyst review and are not on-chain verification.

Session-only investigations

Simulated chat messages, local proofs and log selections are held in memory and reset when the page reloads. No live AI model or telemetry collection service is used by those demos. Proof exports are downloaded only when you select Export proof.

Private customer records

Explicitly saved traces and assessments, dashboard configurations, setup inventories, support tickets and replies are retained in your account. Customer records are isolated by account ownership. Enterprise features require owner-confirmed access; connecting a wallet does not confirm payment. Saved investigations and dashboards can be deleted in the portal. Support tickets remain available for follow-up; support notifications and response-time commitments are not configured.

Customer administration & usage

Approved administrators can view customer setup inventories and saved dashboard configurations, manage customer tiers, and read, update and reply to support tickets. Administrative changes are recorded in an audit trail. Successful record saves and ticket actions are recorded as usage events, without incident content. These events are not AI token counts, payment records or live monitoring traffic. Administrators see investigation counts, not private assessment or trace contents.