BlackHart
Go live
Browser extension

Privacy policy

Last updated 2026-11-15 · BlackHart Inc.

In short

The BlackHart browser extension shows BlackHart Risk Index scores for DeFi protocols and prediction markets on the sites where you meet them, and before you sign a transaction with a scored contract.

To do that, it sends data to blackhart.io:

  • Usage events, tied to a random install ID the extension creates on your device.
  • Your API key, with its requests, if you save one. Those requests are then tied to your account.
  • Your email address, only if you subscribe to hack alerts on the welcome page.

Everything it sends goes to blackhart.io. We do not sell it or transfer it to anyone. The extension has no setting to turn usage events off today. Uninstalling it stops everything it sends.

What the extension does

  • It runs only on a fixed list of DeFi apps, block explorers, token-data sites, wallet dashboards, social sites and prediction-market sites. The list ships with the extension and is published at blackhart.io/api/v1/protocol-map.
  • On those sites it reads the page on your device to find the protocol or market it is about: a subdomain, cashtag, contract address, token symbol or market link. On X, Discord and Telegram it reads posts and messages on your device to find cashtags, addresses and Polymarket links.
  • It fetches the score for what it found from blackhart.io and shows it as a chip or panel on the page.
  • On supported DeFi apps it wraps your wallet so it can show the target contract's score before your wallet opens. It reads the contract on your device and matches it against the protocol map it downloaded. It never changes, signs, rejects or blocks a transaction. The request always goes on to your wallet, which keeps full control of every approval. You can turn this check off in the extension's settings.

What it never sends

  • Page text, or the text of posts and messages on X, Discord and Telegram. The one exception is the t.co address of a Polymarket link on X, described below.
  • The addresses, paths or titles of the pages you visit. Usage events name only the host of a supported site, such as app.aave.com.
  • Your wallet address, or the address of the contract you are about to sign with.
  • The image made when you share a score as a picture. It is copied to your clipboard or saved on your device.

Prediction-market risk signals

When you view a Polymarket market, the extension displays BlackHart Market Risk Signals: automated, probabilistic indicators derived from public on-chain and market data. These may reference third-party wallet addresses that are publicly visible on the blockchain. They are risk signals for your own due diligence, not accusations. The signals are about market activity, not about you. The extension never sends your wallet address.

Permissions, justified

The extension asks for these permissions and no others. It has no access to all sites and no optional permissions.

PermissionWhy we need it
storageSaves your settings, watchlist, API key and install ID on this device, and caches scores for a few minutes so pages don't refetch them. Your settings sync through your Chrome profile. Your API key and install ID do not.
activeTabCaptures the visible tab only when you ask to share a score as an image.
notificationsShows the alerts you turn on: a sharp score drop or a new hack for a protocol on your watchlist.
alarmsWakes the background worker on a schedule to refresh watched scores, the hacks feed and your plan quota, and to send queued usage events.
clipboardWriteCopies a score link, share text or your API key when you click Copy or Share.
host_permissions (342 named sites)Shows score chips and panels on a fixed list of DeFi apps, block explorers, token-data sites, wallet dashboards, social sites and prediction-market sites (for example app.aave.com, etherscan.io, coingecko.com, debank.com, x.com and polymarket.com), and fetches scores from blackhart.io. On those DeFi apps it also wraps the wallet so it can show a contract's score before you sign. There is no access to all sites.

Score lookups and the install ID

What is sent
The protocol or market the extension found, and the install ID. The extension creates the install ID at random when you install it, keeps it on this device and never syncs it. If you saved an API key, the key goes too.
When
When a chip needs a score that is not cached, when you open a chip or the popup, and every 30 minutes to check your plan and remaining lookups.
Why
To return the score, and to count the free allowance per install.
Who receives it
blackhart.io only.
How long we keep it
The lookup counters for your install are deleted two days after their daily or monthly window ends. Our request log keeps the API path, the protocol and, if you saved a key, the key's ID for 30 days. It does not store the install ID.
How to stop it
Uninstall the extension. It cannot show scores without these lookups.

Usage events

What is sent
Events posted to blackhart.io/api/v1/telemetry, with the install ID, the extension version and your plan:
  • Session starts, with how long ago the extension was installed.
  • How many chips showed each day, per supported site (host name only) and per protocol.
  • The first chip ever shown, chip opens, shares, hitting your plan limit and upgrade clicks.
  • Error reports: the error name, a cleaned message (addresses, emails, links and long hex strings removed), the host name of the page, the part of the extension involved and a short fingerprint of the stack trace.
When
The extension queues events on this device. It sends them about every 15 minutes, when 20 are waiting, or at once for the first chip, a share or hitting your plan limit.
Why
To see how the extension is used, which sites and protocols the lookups go to, and what breaks.
Who receives it
blackhart.io only. No third-party analytics service receives them.
Tied to
The install ID. If you saved an API key, the request carries it, so the events can be tied to your account.
How long we keep it
30 days. A daily cleanup deletes older events.
How to stop it
The extension has no setting to turn usage events off today. Uninstall it to stop them. Without a saved API key they stay tied to the install ID only, not to an account.

Market meter

What is sent
The market a chip shows and the install ID, posted to blackhart.io/api/markets/meter.
When
Each time a market chip shows while no API key is saved.
Why
A market lookup counts against the free allowance, like a score lookup.
Who receives it
blackhart.io only.
How long we keep it
The server does not store which market it was. The allowance counter is deleted two days after its daily or monthly window ends.
How to stop it
Save an API key: the meter is then skipped and your plan covers the lookups. Or uninstall the extension.

Install attribution

What is sent
The install ID, posted to blackhart.io/api/v1/attribution/bind. Your browser sends any blackhart.io cookies it holds with this request. The server reads one of them: the link cookie set when you followed a BlackHart link.
When
Once, when the welcome page opens after you install.
Why
To match the install to the BlackHart link that led to it, so we know which links bring installs.
Who receives it
blackhart.io only.
How long we keep it
We have not set a retention period for this record yet. Write to privacy@blackhart.io to have it deleted.
How to stop it
Clear your blackhart.io cookies before you install, and no link is matched. The install ID is still recorded.

Polymarket links on X

What is sent
The t.co address of a link in a post that points to Polymarket, sent to blackhart.io/api/markets/resolve, with your API key if you saved one. No other page text is sent.
When
When a post on X links to Polymarket through a t.co address.
Why
X shortens links. Our server follows the t.co address to find the market and its score. Your browser does not visit t.co for this.
Who receives it
blackhart.io only.
How long we keep it
We do not store it. The answer is cached for a few minutes so repeat lookups are fast.
How to stop it
Uninstall the extension.

Your API key

What is sent
The key you paste in, or the one blackhart.io hands to the extension after checkout. Paid plans are bought on blackhart.io, not in the extension.
Where it is kept
In chrome.storage.local on this device. It is never synced to your Google account or other devices.
When
With the extension's requests to blackhart.io, in the Authorization header. It is never sent anywhere else.
Why
To apply your plan. It also ties your score lookups, usage events, shares and watchlist to your account.
How long we keep it
On this device until you clear it or uninstall. Your account data follows the site-wide privacy policy.
How to stop it
Click Disconnect or Clear key in the extension's options, or never save a key.

Watchlist sync

What is sent
The protocols and markets you pinned, sent to blackhart.io/api/v1/watchlist with your API key.
When
Only while an API key is saved: when you open the popup and when you change your watchlist.
Why
To keep your watchlist the same in the extension and on your blackhart.io account.
Who receives it
blackhart.io only.
How long we keep it
With your account, under the site-wide privacy policy.
How to stop it
Don't save an API key. Your watchlist then stays on this device.

Your email address

What is sent
The email address you type on the welcome page, posted to blackhart.io/api/v1/subscribe.
When
Only if you subscribe to hack alerts there.
Why
To send you hack alerts.
Who receives it
blackhart.io. Alert emails go out through our email provider, named in the site-wide privacy policy.
How long we keep it
Unsubscribing stops the emails and marks the address as unsubscribed. It does not delete it. We have not set a deletion period yet. Write to privacy@blackhart.io to have it deleted.
How to stop it
Don't subscribe, or click the unsubscribe link in any alert email.

Share links

What is sent
When you click Share, the extension asks blackhart.io for a short link. It sends the protocol or market, the platform you picked and, if you saved one, your API key. The share also counts as a usage event.
When
Only when you click Share.
Why
To make a link that opens the score.
Who receives it
blackhart.io only.
How long we keep it
The link records only the protocol or market and the platform, not who made it. We keep it so the link keeps working.
How to stop it
Don't click Share. A score you share as a picture stays on your device.

Other requests

The extension also fetches public data from blackhart.io: the protocol map, scores and market details, the hacks feed, share images, and a live score stream that opens when your browser starts. Requests made through its API client carry the install ID, and your API key if you saved one. If you open billing from the extension's options, it sends your key to start a billing session.

Like any website, blackhart.io sees your IP address on each request. The usage-event endpoint does not store it. Our security logs are covered by the site-wide privacy policy.

Third parties

The extension sends data to blackhart.io only. No ad network or third-party analytics service receives it. We do not sell or transfer your data to third parties. Two things reach other sites:

  • Market pictures in market chips and the popup load from Polymarket's image host, because the market data carries that address. Your browser fetches the picture like any image on a web page.
  • Share buttons open X, Telegram, WhatsApp, Reddit or Facebook, and only when you click one.

Stored in your browser

In chrome.storage.local, on this device only:

  • The install ID.
  • Your API key, if you save one.
  • Your watchlist and pinned markets.
  • A cached copy of the protocol map, and recent scores for a few minutes.
  • Usage events waiting to be sent, and the daily chip counts they report.

In chrome.storage.sync: your settings and site filter, so they follow you across the Chrome profiles you are signed into. They hold no secrets.

Removing the extension deletes all of it from your browser.

Your choices

  • Uninstall the extension to stop every request above and delete what it stored in your browser.
  • Use it without an API key and your requests stay tied to the random install ID, not to an account.
  • Remove a saved key with Disconnect or Clear key in the extension's options.
  • Leave hack alerts with the unsubscribe link in any alert email.
  • Turn off the check before you sign in the extension's settings.
  • Ask us to delete data at privacy@blackhart.io.

The extension has no setting to turn usage events off today.

Changes to this policy

We will update this page when the extension's behavior changes, for example when it adds a permission, a content script or a new request. The date at the top shows the latest revision.

Contact

Privacy questions and deletion requests: privacy@blackhart.io. Vulnerability reports related to the extension: security@blackhart.io.

Source

The extension is open source. Source is maintained at github.com/hartmade/blackhart-public MIT licensed.