01What this covers
This policy covers the MarketTrace website (markettrace.ai) and the MarketTrace Crypto MCP, the server at api.markettrace.ai/mcp (listed in the MCP registry as ai.markettrace/agent-feed), and the paid Pro plan. MarketTrace is a read-only market-data product: it serves public cryptocurrency market statistics. It has no trading functionality and never asks for exchange API keys, wallets, or funds.
02Who is responsible
The controller of personal data processed through MarketTrace is its operator, a sole proprietor (FOP) registered in Ukraine. Privacy contact: [email protected].
03Data we collect on the website
Browsing the website needs no account. An account is used only for Pro: you sign in with a one-time code sent to your email. Stytch, the provider behind the MCP sign-in, handles it (see below). Your account is created with the email you pay with: Creem passes it to us and we pass it to Stytch without storing it ourselves. We use Google Analytics 4 to understand aggregate usage: pages visited, referrer, device and browser type, and coarse location derived by Google. Some pages also carry an advertisement served by an ad network, which runs its own collection in your browser (see Advertising below). If your browser or an extension blocks analytics or ads, the site works identically.
04Partner links and banners
Some pages carry links or banners to partners, such as exchanges and other products, and we may earn a commission if you sign up through one. These are fixed placements we choose ourselves, and we pass no data about you to the partner. Following a partner link takes you to that company's own site, where their privacy policy applies, and they may see that the visit came from MarketTrace. When no partner placement is booked, the same slot shows an advert from an ad network instead (see Advertising).
05Advertising
The in-content slot on the perpetuals module pages can show an advertisement served by Bitmedia, a cryptocurrency advertising network. When that slot is about to come on screen, Bitmedia's script runs in your browser and builds a device fingerprint: your user agent, screen, language, time zone, memory and processor hints, installed fonts and plugins, and hidden test renders through canvas, WebGL and the audio engine. It hashes these into an advertising identifier and stores it in a cookie named bitmedia_fidon markettrace.ai, which your browser may keep for up to about 400 days, and in your browser's local storage, which has no expiry. It sends that identifier, the address of the page you are on and your user agent to Bitmedia to count the page view and request an advert, and it passes the identifier to syncbm.com, a Bitmedia domain that recognises the same visitor across other sites in its network. The advert loads in a frame from Bitmedia, and the advertiser may fire its own measurement pixels inside it. The script also checks for a cryptocurrency wallet extension. MarketTrace never asks for wallet access, so in current browsers no address is exposed to the page; if your wallet does expose one, the script sends it to Bitmedia together with the identifier and the page address. None of this data reaches us: Bitmedia collects it directly and decides how it is used, under its own privacy policy at bitmedia.io/privacy. Blocking ads, or clearing cookies and site data for markettrace.ai, stops all of it.
06Data we collect on the MCP
Connecting an AI agent to the MCP uses OAuth sign-in handled by Stytch, our authentication provider. We receive and store your email address (used for the magic-link sign-in) and an account identifier. Signing in on the website uses the same Stytch account, so the same email gives the same account identifier. For a Pro account we also store your plan, the status of your subscription and the date the current paid period ends. For each request to the MCP, our server logs the account identifier, the time, the tool called and its arguments, the name and version of your MCP client, its user agent, your IP address truncated to its network prefix (/24 for IPv4, /48 for IPv6), your country as reported by our CDN, and the response status and timing. We do notreceive or store your AI conversations: the server only sees the tool calls an agent makes (e.g. "market state for BTC"), never the chat around them. The market data itself is public and contains no personal information.
07Payments
Pro is sold through Creem, our Merchant of Record. Creem is the seller of the subscription: it takes the payment, calculates and collects taxes, and issues invoices and refunds. It collects your name, email address, country, billing details and payment details under its own privacy policy (https://www.creem.io/privacy). We never see or store your card details. From Creem we receive your customer and subscription identifiers, the plan, the subscription status, the dates of the billing period, and the account identifier we attach at checkout so that Pro is switched on for the right account. We keep these subscription records in a billing log on our server for as long as accounting and tax rules require.
08Pro waiting list
If you leave an email address under "Notify me when it's live" in the Pro window or "Get early access" on the Pro page, we store that address on our own server, in the list and in a daily backup copy of it, to send you one message when Pro is available. After that message, or 12 months after you signed up if Pro has not launched by then, we delete the list and its copies. We do not add it to any other mailing, share it, or pass it to an advertiser. To limit abuse, the server counts submissions per IP address in memory for up to an hour and does not store that count. The address is not stored with your IP, but like every request to this site, the submission passes through our web server logs, which record the IP address and are deleted after 14 days. The site also records, without any identifier, that the Pro window or the Pro page was opened, that its button was pressed and that an address was saved, with the page, the language and whether this browser first visited more than 7 days ago; your browser keeps a note of which of these it has already sent so each is counted once.
09Prism waiting list
If you leave an email address in the Prism window on the homepage, we store that address on our own server, in the list and in a daily backup copy of it, to send you one message when Prism is available. After that message, or 12 months after you signed up if Prism has not launched by then, we delete the list and its copies. We do not add it to any other mailing, share it, or pass it to an advertiser. To limit abuse, the server counts submissions per IP address in memory for up to an hour and does not store that count. The address is not stored with your IP, but like every request to this site, the submission passes through our web server logs, which record the IP address and are deleted after 14 days. The site also records, without any identifier, that the Prism window was opened, that an address was saved and that its Pro button was pressed, with the page, the language and whether this browser first visited more than 7 days ago. Your browser keeps a note that it left an address, so the window opens on its second step next time.
10How we use data
To operate and secure the service (authentication, per-account rate limits, abuse prevention), to understand aggregate usage, and to contact you about the service if ever needed. We do not sell your data, and we pass no account data to third parties for their own marketing. The ad network described under Advertising collects and uses its own identifier directly in your browser, on its own terms.
Legal bases
We provide your account and Pro to perform our contract with you. We keep billing records to meet accounting and tax obligations. We keep request logs, rate limits and other security measures in our legitimate interest in running a secure and reliable service.
11Processors and third parties
Creem (payments; as the Merchant of Record it is the seller of Pro and an independent controller of payment data), Stytch (authentication), Google Analytics (website usage), Cloudflare (CDN and network security), Hetzner (hosting, EU data center). Each processes data only to provide its function. Bitmedia (advertising, including its syncbm.com identity-sync domain) is different: it decides for itself what its script collects and how long it keeps it, so it acts as an independent controller of that data, not as our processor. Market data displayed on the site originates from public exchange feeds (Binance, Bybit, OKX, Hyperliquid) and contains no user data.
12Security
We serve the site and the MCP over HTTPS only, keep keys and secrets out of our code and logs, limit server access to the people who run MarketTrace, and never handle card details.
13Retention
Operational logs are kept for a limited period and rotated; MCP request logs are kept for up to 400 days. Pro waiting-list addresses, and the daily backup copies of the list, are kept until the one message announcing Pro is sent, and for no more than 12 months. Prism waiting-list addresses, and the daily backup copies of that list, are kept until the one message announcing Prism is sent, and for no more than 12 months. Your account record at Stytch persists until you ask us to delete it. Pro status is kept while your account exists. Billing records are kept for as long as accounting and tax rules require. The advertising identifier lives in your browser, not on our servers (see Advertising for its lifetime and how to remove it).
14Your rights
Email us to access, correct, export or delete the data tied to your account, to restrict or object to how we use it, or to remove your address from the Pro waiting list. We remove it from the list and from its backup copies. The same goes for the Prism waiting list. We act on requests within 30 days. You can also complain to the data protection authority in your country.
15Changes
Material changes to this policy update the date above. The current version always lives at this URL.
Contact
[email protected] · see also Terms of Service, Refund Policy and the MCP documentation.