Privacy Policy
TapeRadar is designed to work directly in the browser. Market data retrieval, filtering and terminal rendering occur on the client side.
Personal data
In this version, TapeRadar does not require registration, login or sending personal data to use the terminal. To measure product use and organic growth, the browser creates a random pseudonymous identifier. It contains no name, email, wallet or exchange account.
Relevant flow moments may remain in the browser's local storage for up to six hours to calculate subsequent price variation. TapeRadar does not send this history to its own server.
Product metrics
Essential events, such as session starts, opening the sharing feature and visits from shared links, are summarized locally in the browser and exposed technically through the dataLayer. In this static version, the website does not send these events to a first-party endpoint or maintain a user database. The external analytics connector remains disabled until a valid identifier is configured.
If Google Analytics 4 is enabled by the website owner, it is loaded only after the visitor's permission. The integration sends a limited allowlist of product events and aggregate fields; it does not send the browser's internal identifier, parameterized sharing URLs or the name used to sign cards. Advertising cookies and Google Signals remain disabled.
The analytics choice is stored locally and can be changed through "Analytics settings" in the footer. When permission is refused or revoked, the site stops new events and attempts to remove Google Analytics technical cookies accessible to the page.
To distinguish direct access, search, referral and organic mentions, the browser may store the first visit source locally. Only UTM parameters and the referring domain are considered; the full address of the referring page is not stored.
Opening an exercise from an educational page adds only the public guide identifier
(tr_content) and a preset name (tr_preset) to the link. They
apply predefined filters and measure aggregate content-assisted activation. They do not
contain an answer, study progress, trade or personal data. After observing ten seconds
and five eligible trades, the visitor may voluntarily share an exercise card; its link
carries the same guide, preset and setup, without a certificate or score.
Educational guides can also generate sharing links with a pseudonymous reference
(tr_gref), limited depth (tr_gchain) and the
tr_gshare marker. These parameters measure the guide → exercise →
activation chain and contain no contact, message, personal reading or correct answer.
When the exercise is opened, only these markers and channel origin follow the visitor
into the terminal.
The "Take a screen capture" button works only after a click. When a native screen picker is available, the visitor chooses the screen, window or tab. On mobile browsers without that feature, a library loaded from the site itself renders only the currently visible TapeRadar area. One frame is converted to PNG locally and handed to native sharing or download; TapeRadar does not upload, store or analyze the image, and the action creates no sharing statistic.
To compare exercise-sharing friction, the browser deterministically chooses between the
full editor (modal_v1) and opening WhatsApp directly with text and a social
preview (whatsapp_fast_v1). The tr_flow variant travels in the
link for aggregate amplification measurement, contains no browser identifier and does
not change radar data.
A trader may voluntarily provide a handle to sign cards. It is saved only in the browser and becomes a public part of the shared PNG and link. The signature does not create a profile, account or identity verification and can be removed by leaving the field empty.
When a chain is reshared, the voluntary handle of the person who started it may continue
in the link as a portable origin (tr_origin), even when another trader signs
the new share. This origin appears on the card and in the caption and is always labeled
unverified. It creates no ranking, profile or proof of authorship. Anyone with the link
or image can see and reproduce this handle.
The permanent-link button creates, only in the browser, a URL for a bio, description,
newsletter or community. It may contain the current setup, pseudonymous referral,
voluntary signature and the tr_creator and creator_setup
markers. The link does not create a profile, personal page or account; anyone who
receives it can copy its parameters. Arrivals through it are classified as organic
mentions for aggregate measurement.
The Feed or Stories card preference is also saved locally. The selected format travels in the link so aggregate performance can be compared when an external analytics tool is connected.
The browser deterministically selects one of two sharing messages so aggregate results
can show which invitation produces more opens and active use. The variant
(tr_variant) travels in the link, contains no visitor identifier and does
not change market data, setup or recommendations.
For contextual whale, sweep or absorption moments, the browser also deterministically
chooses between opening the full editor and preparing a direct WhatsApp share. The
variant (tr_mflow) travels in the link to compare aggregate completion and
activation without including the browser's internal identifier. Sharing still requires
a trader click, and TapeRadar does not read contacts or messages.
The optional reading challenge adds only a radar category at that moment to the link
(tr_read: buy, sell or neutral) plus the tr_challenge marker.
When someone replies, tr_reply marks the response and
tr_prev preserves only the previous category to form
“received → my read.” The recipient compares the latest category with current flow only
after activation. There is no vote, scoreboard, central history, call or proof of
accuracy.
The optional group setup mode adds only the tr_community marker and the
community_setup campaign to the same portable link. It does not create a
room, member list, presence, chat, ranking or central count: the full setup remains in
the URL and is applied only in the recipient's browser. A recipient can reshare it only
after local activation with live flow.
PNG cards include a QR code containing the same shareable link. It is calculated entirely in the browser without sending the URL to an external QR service. Like the regular link, the code may contain the setup, pseudonymous referral, chain, portable origin and the trader's voluntary signature. Anyone who receives the image can read this QR code.
The session recap temporarily accumulates volume and observed event counts since the radar's last adjustment. This data remains in page memory and only becomes part of a PNG or link when the trader chooses to share it.
Today's radar aggregates, only in this browser until the local day changes, observed volume, trade count, whales, sweeps and absorptions. The totals persist between sessions in local storage and do not represent the trader's orders, wallet, profit or performance. A shared link carries the setup but not these totals; they only appear in text or a PNG the trader chooses to share.
This week's radar keeps an equivalent local aggregate from Monday through Sunday and
records only how many days contained observed eligible flow. It resets on Monday, is
stored as taperadar.weekly_flow.v1, and has the same limits: it contains no
orders, wallet, profit, identity or proof of performance. Totals leave the browser only
when the trader chooses to include them in a caption or image.
To distinguish a visit from active use, the page temporarily counts visible time and the number of eligible trades observed. Activation requires ten visible seconds and five trades; time in a hidden tab is not counted. Visitors arriving through a shared link may see this progress in an on-page guide. It is ephemeral, can be closed, creates no profile and does not send the counters through the link.
Each day this threshold is reached may extend a flow-reading streak. The last active date, current count and personal best remain only in local browser storage. Consented analytics may receive the counts and whether a milestone was reached, but never the dates. A streak measures use of the radar, not trades, profit or financial performance.
The streak panel can generate, only after a click, a calendar file with a daily 6 PM reminder and a public TapeRadar link. It is created entirely in the browser and sends no data to the website. Once imported, the trader's chosen calendar app or provider handles that reminder under its own rules.
TapeRadar can be installed as an app. A service worker stores only the essential static shell needed to open the terminal offline; trades, prices, WebSockets and shared links with parameters are never added to that cache. Install availability, prompt and completion can emit technical events to the dataLayer.
Cookies and third parties
External services, such as data providers, exchanges, analytics or advertising platforms, can apply their own privacy policies when integrated into the website.