Privacy, in plain sight.

1. Purpose & operator

DireBitViewer is operated by DIRE MONEY TRANSMITTER LLC. This policy covers the DireBitViewer Chrome extension and direbitviewer.com.

The extension displays cryptocurrency prices and available market price history. It offers a default watchlist of TRX, BTC, SOL, ETH, BNB, LTC, and XRP, display currencies USD, EUR, and GBP, and optional CoinGecko IDs or public HTTPS JSON sources.

DireBitViewer does not provide wallets, custody, trades, money transfers, or investment advice. It does not access balances or transaction histories. “History” in a chart means market price history, not your browsing history.

2. Information on your device

Local settings. Your settings, watchlist, selected currency, and public custom-source URLs and configuration are saved in Chrome’s storage.local. The extension does not encrypt that storage or intentionally synchronize it through storage.sync. This information is not uploaded to a developer backend; there is no developer backend.

Optional API key. A CoinGecko Demo API key is held only in memory in the current popup or options page. It is not saved in storage.local or storage.session. Closing or reloading that page discards the key. Memory-only handling is not an encrypted vault and does not protect a compromised device. Use only a restricted market-data key, never wallet secrets or trading credentials.

Public URLs. Custom endpoints must be public HTTPS URLs without credentials or secret query values. Saved URLs are not encrypted; never put tokens, passwords, or API keys in them.

Temporary data. Fetched prices, history, and token-icon metadata are cached in memory, not persisted in extension storage. Icon metadata is cached for approximately one hour. These in-memory caches disappear when the relevant extension context ends. Logo image files are different: Chrome may save them in its normal HTTP image cache on disk. Closing the extension does not necessarily clear that browser-managed cache.

3. Requests to data & image providers

CoinGecko is the default data provider. Required host access to https://api.coingecko.com/* is declared at installation; opening the interface can request quotes, price history, and token-icon metadata without an additional permission prompt. Custom HTTPS JSON hosts are contacted only after you configure them and explicitly grant the necessary optional host access.

Requests go directly from your browser to the provider. Providers receive your IP address, requested URLs and asset identifiers, currency and history parameters where applicable, normal network metadata, and any API key configured for the relevant API request. Custom sources receive the parameters in their URLs, which may appear in provider logs. Providers can learn which assets you query even though your complete settings are not uploaded as a developer account profile.

Quote, history, and icon-metadata API fetches use HTTPS, omit credentials (credentials: 'omit'), send no referrer (referrerPolicy: 'no-referrer'), and reject redirects (redirect: 'error'). They do not attach browser cookies or a referring page URL. This does not hide your IP address or prevent provider logging.

Token logos

Logo metadata comes from https://api.coingecko.com/api/v3/coins/markets. A configured Demo API key is sent only in an API header to api.coingecko.com, never to the image CDN.

Logo URLs must use HTTPS and the exact hosts coin-images.coingecko.com or assets.coingecko.com. Images load with anonymous CORS (crossorigin="anonymous") and no referrer (referrerpolicy="no-referrer"), without cross-origin credential cookies or an API key. The image host receives your IP address, requested logo URL, and normal request metadata. Chrome may include a CORS Origin header; this is not a referring webpage URL. API redirect rejection does not apply to browser image loads. Images may be stored in Chrome’s HTTP cache, including on disk.

Custom JSON assets without CoinGecko metadata keep initials; the extension does not guess a logo from their ticker. There is no icon telemetry.

Providers determine their own logging, retention, and privacy practices. Review CoinGecko’s privacy policy and any custom provider’s policy. DireBitViewer cannot delete their logs or control their subsequent processing.

4. Permissions & no telemetry

The storage permission saves local settings. CoinGecko API host access supports default data and metadata requests. Accepted CDN logo images do not require additional host permission. Custom-host permission is requested for the origin needed by your action; optional HTTPS permissions do not automatically grant access to every website.

DireBitViewer does not inject content scripts, read the websites you visit, or request tabs or browsing-history access. There is no developer account, telemetry, analytics, advertising, tracking pixel, or developer-operated data-collection service. The extension does not send your saved watchlist or key to the developer, sell user data, or use it for advertising, profiling, or credit decisions.

5. This website

This static website is hosted by Hostinger. Hosting and security systems may process access logs containing IP addresses, user agents, requested paths, timestamps, and related request metadata to deliver and secure the site.

The website code contains no analytics, cookies, cross-site tracking, external scripts, or externally hosted fonts. The screenshots and images on this website are served locally with the site; they do not request live quotes or token logos from CoinGecko.

Links to providers, and the Chrome Web Store when its official link is available, take you to third-party services with their own privacy policies. Review Hostinger’s privacy policy for its practices. This site does not include a support form or user account.

6. Support & privacy email

If you email support@direbitviewer.com, DIRE MONEY TRANSMITTER LLC receives the sender information, message content, and any attachments you choose to send. Messages are processed through Hostinger email and used to respond to your request, troubleshoot issues, and meet applicable legal obligations.

Do not send passwords, API keys, wallet secrets, or other sensitive credentials. Support correspondence is kept only as needed to resolve the request or comply with legal obligations; there is no fixed retention period promised here. You may contact the same address to request access to or deletion of support information, subject to applicable requirements.

7. Retention, deletion & your choices

Local settings remain until changed or removed, extension storage is cleared, or the extension is uninstalled. Edit or remove configuration in the extension where available. Uninstalling removes its Chrome-managed local storage, but not device backups or provider logs.

Closing the relevant popup or options page discards its in-memory key and data caches. Browser-managed image caches can remain; use Chrome’s browsing-data controls to manage cached images. Revoke a key with its provider if it may have been exposed.

You can decline optional custom-host permission, manage granted site access in Chrome’s extension settings, or disable or uninstall the extension to stop its requests. Revoking host permission alone does not erase saved configuration. There is no developer account or developer-side copy of extension settings to delete. Hosting logs and provider records are subject to the relevant service’s practices and applicable requirements.

8. Contact & policy updates

For privacy questions or requests, contact DIRE MONEY TRANSMITTER LLC at support@direbitviewer.com.

We may update this policy when the extension, website, or relevant practices change. The effective date at the top identifies the current version.