Privacy Policy

This Privacy Policy applies to the Bitmessa Explorer web interface and Explorer API modules operated by Bitmessa. It describes Explorer-specific processing based on the current implementation. If you use other Bitmessa products or the broader bitmessa.com website, additional policies may apply to those services.

The Explorer may involve the following categories of information:

• Voluntary browser-side preferences: Transaction Watch settings and watchlists stored locally in your browser (see Local Browser Storage).
• Technical and operational data: information generated when your browser or API client communicates with Bitmessa servers, such as request timestamps, requested paths, HTTP metadata, and network identifiers commonly used for security, rate limiting, and operations.
• API-related information: when you use the central Bitmessa API platform, authentication and usage metadata associated with API keys and requests may be processed according to that platform's configuration.
• Public blockchain data: Bitcoin blockchain data queried through the Explorer (see Blockchain Data).

Like most web applications, Explorer requests are processed by Bitmessa application and network infrastructure. This may include processing of:

• IP address and network information
• Browser or client user-agent strings
• Request timestamps, routes, and response status
• Security, error, and performance logs
• Aggregated operational metrics used to monitor service health

Explorer API rate limiting is configured in the application (default: 120 requests per 60 seconds per client, subject to deployment configuration). Rate-limiting relies on client-identifying network information.

The Explorer's Transaction Watch feature stores data in your browser's localStorage, including:

• Watchlist transaction IDs and related watch metadata
• Alert preferences (sound settings, confirmation threshold, desktop notification preference)

This data remains on your device unless you clear site data or remove watch entries. Bitmessa does not receive your watchlist contents through this local storage mechanism alone.

The Explorer interface code reviewed for this release does not use sessionStorage for persistent preferences beyond standard browser session behaviour.

The Explorer-specific frontend does not implement dedicated third-party advertising or analytics cookies within the Explorer source modules. When you access the Explorer through www.bitmessa.com, the hosting website or your browser may still use cookies or similar technologies for essential operation, security, or other site-wide features outside the Explorer modules described here.

Developer and programmatic access to Explorer endpoints is provided through the central Bitmessa API platform, which includes API key management. API keys, authentication events, and request metadata may be processed to provide, secure, and operate the API service. Do not embed API keys in client-side Explorer pages or public repositories.

Bitcoin blockchain data displayed in the Explorer is public network data. Querying, indexing, or presenting public blockchain information through the Explorer does not, by itself, convert that public data into private personal information held by Bitmessa. However, combining public on-chain data with other information could have privacy implications depending on context and use.

Bitmessa operates internal observability for the Explorer API, including aggregated performance and reliability metrics (for example API latency, RPC health, indexer status, and category-level workload metrics). Operational event records may be retained for a configured period (production default: 30 days for metric history, subject to deployment configuration). This telemetry is used for operations and service improvement, not for marketing profiles. Diagnostics endpoints are access-controlled in production deployments.

Retention varies by data category:

• Browser local storage (Transaction Watch): retained on your device until you remove it or clear site data.
• Operational metrics and events: retained according to Explorer observability configuration (default 30 days unless configured otherwise).
• Historical mempool persistence (backend): subject to configured retention (default 21 days in Explorer API configuration unless overridden).
• Server logs: retained according to Bitmessa operational and security practices for the deployment environment.

Bitmessa applies reasonable technical and organizational measures appropriate to the operation of its application infrastructure, including access controls for operator diagnostics and API protections such as rate limiting. No method of transmission or storage is completely secure.

Explorer data is sourced from the Bitmessa Bitcoin node, Bitmessa indexer, and Bitmessa analytics services. It is not sourced from external blockchain explorer services. External links (for example donation or documentation pages on bitmessa.com) may direct you to other Bitmessa web properties or third-party resources governed by their own terms and policies.

We may update this Privacy Policy to reflect changes in Explorer functionality or operational practices. The "Last updated" date at the top of this page indicates the latest revision.

For privacy-related questions about the Explorer, contact Bitmessa through the Contact page or Support page at bitmessa.com.