Privacy
This page has not been written yet.
TapeBench is at beta v0.14. Until this page carries real text, treat it as empty: it is a placeholder, not a statement of privacy practice.
The declaration below is not that text: it is the machine’s own list of the reads that leave this device — where each one goes, how often, and what it leaves behind.
Venue symbol-catalog warm — the search itself runs on-device, but a cold (or expired) call asks each venue for its tradable-symbol list — the venue learns you asked for its catalog, never your query
destinationsapi.binance.com · stream.binance.com · data.binance.vision · www.bitstamp.net · ws.bitstamp.net · api.exchange.coinbase.com · ws-feed.exchange.coinbase.com · api-pub.bitfinex.com · api.kraken.com · ws.kraken.com · api.derivws.com · ws.bitso.com · api.gemini.com · api.hyperliquid.xyz · horizon.stellar.org · xrplcluster.com
cadenceat most once per venue per 24 h — inside that window every search is served from the catalog already on this device, with no request at all
fetchestrue
persistseach venue’s symbol catalog (the venue’s own list — not your searches) · IndexedDB on this device (groovy-pebble:symbol-catalog, per profile) · ttlMs 86400000
Cloud-relay token health probe — one GET of the bench token’s own /t/<token>/health on the relay — the relay learns the token was probed (it already holds that token’s registry); no chart data, no query, and the answer carries token state, client presence and the pairing fingerprint
destinationsmcp.tapebench.com
cadenceonly when the read is called, and only while an issued token exists — no token, no request at all; while local-only mode is ON the probe is refused typed and nothing leaves — unless the cloud relay pairing you connected still stands: that pairing keeps its relay admitted (admission-only — a later lockdown never cuts a live pairing), so the probe still goes out until the pairing ends
fetchestrue
persistsnull
On-chain feed-health sweep — one transient health probe per configured on-chain market (the latest public trade / candle, to check the feed still decodes) — no account, key or order data is ever sent
destinationsapi.hyperliquid.xyz · horizon.stellar.org · xrplcluster.com
cadenceonly when you (or your agent) call it — idempotent while a sweep is in flight. The PERIODIC sweep is off by default and never runs while local-only mode is ON
fetchestrue
persiststhe sweep’s health report (per-feed status rows — no market data) · IndexedDB on this device (groovy-pebble:onchain-audit, a ring of 500 reports) · ttlMs null
hosttapebench.com
kindour-edge
Same-origin paths are served by tapebench.com — OUR server, not your machine. It sees which instruments and date ranges you pull, and the venue shims fetch them on your behalf (the venue sees our server; we see you). This is the same request metadata the data servers already see, held by us instead of them — run the desktop companion to serve these paths from your own machine instead.
paths/data/ — the trade-bar archive · /bitso-proxy/ — Bitso history (the venue ships no CORS headers) · /fxcm-proxy/ — FXCM’s weekly candle archive (no CORS headers) · /dukascopy-proxy/ — Dukascopy’s .bi5 archive (CORS locked to their own origin)
This page runs no JavaScript, so it cannot re-check who is serving it: the row above is the declaration for the origin named in host. If that is not the host in your address bar — a local preview, the desktop companion — it is not the answer for where you are.
Nothing here is written for machines only: this page is a second rendering of published data, not a second version of it — every row on it is the chart.privacy read.