Privacy policy
TickerInside is published by VoidLab. This policy covers the website at tickerinside.com, the JSON API under /api/, the MCP server at https://tickerinside.com/mcp, the feeds under /feeds/, the files for agents, and the packages that read the same files.
In short
There are no accounts, no sign-in and no cookies, and no IP address is stored. A request to the API, to the MCP server, to a feed or for a file for agents writes one pseudonymous usage record, kept three months. A call to a tool of the MCP server is recorded with the tool's name and up to eight of the tickers it asks about, never an amount, a weight or any other argument. Visits to the pages are counted by Simple Analytics, which sets no cookie.
What a request records
Each request under /api/, to /mcp, to the A2A agent at /a2a, to a feed under /feeds/ or for a file for agents (/llms.txt, /llms-full.txt, /AGENTS.md, /skills/, /.claude-plugin/, /.well-known/ and /context7.json) writes one record of thirteen fields to Cloudflare Workers Analytics Engine, which also stores its time: the family of the file asked for; the ticker, file or page asked for, or for /mcp and /a2a the method or tool called; the kind of client, read from the User-Agent; the country Cloudflare assigns; the first 120 characters of the User-Agent; a caller code; the status; the host, never the path, of the Origin header and of the Referer header; Sec-Fetch-Site; CF-Worker; the name of the network the request comes from, such as a hosting company or an internet provider; and the name and version an MCP client gives, the answer engine a visitor came from, or whether a computed answer was asked as CSV or found in the edge cache. The privacy section of the API reference describes each field.
The home page, the fund pages under /etf/, the stock pages under /stock/, the assistant page under /agent/, the ETF ownership page at /etf-ownership/, the ETF flows page at /etf-flows/, the pages under /private-companies/, /diversify/ and /xray/, by their path and never their query, write the same record in three cases only: an assistant fetching one of them for a person who asked it something; a visitor arriving on one of them from an answer engine; and any program asking for one of them as Markdown, by an Accept header that ranks text/markdown above text/html, as Claude Code and OpenCode do, which gets the page's Markdown version. Any other visit to a page writes none.
The caller code is the first 16 hexadecimal characters of a SHA-256 hash of the IP address and the User-Agent, salted with a string that includes the day's date. It counts distinct callers within a day, and the same caller gets a new code each day. The IP address is used to compute it and is not stored.
Calls to the MCP server
An assistant that calls a tool at https://tickerinside.com/mcp sends the tool's name and its arguments. The record keeps the name and, from the arguments that name a fund or a stock, up to eight values shaped like a ticker. Nothing else of the arguments is recorded: a portfolio passed to get_etf_portfolio_lookthrough gives its tickers, never its amounts or weights, and a search query is never kept. A word passed where a ticker goes, such as apple, is kept as APPLE, since nothing checks it against the list of tickers. A prompt of the server is recorded by its name, never its arguments. The record says how a call ended: answered, ticker not covered, input refused or failed. What the assistant keeps of the conversation is governed by its provider's privacy policy.
Answers computed when asked
/api/v1/overlap, /api/v1/lookthrough, /api/v1/batch, /api/v1/screen and /api/v1/diversify, and /diversify/ and /xray/ with a query, answer from the files when asked. Each answer is kept in Cloudflare's edge cache for up to a day under its query, weights included, and served again only to the same query. Its record keeps up to eight of the tickers the query names, never a weight or an amount.
The website and the packages
Simple Analytics counts the visits to the pages, sets no cookie and collects no personal data. The overlap checker, the x-ray, the stock lookup and the comparison builder run in your browser: they fetch the public files of the tickers you enter, and each fetch is recorded like any request to the API. The amounts you type into the x-ray never leave your browser: the page's address carries each fund's weight in percent, so that a result can be shared as a link, and keeps the amounts after its # sign, which a browser does not send, so that a reload restores them. These tools also add one to a daily count of the action taken, such as a portfolio run or a table downloaded, kept by its name and day with nothing else. Two choices are kept in your browser's local storage and never sent: that you hid the assistant banner, and the code language you picked on the API reference.
The npm package tickerinside-mcp runs the same tools on your own machine, and the client packages read the same files. They record nothing themselves: each file they fetch is a request to the API, recorded as above with the ticker or file it asks for, and the amounts given to them stay on that machine.
Why
To answer each request; to count how the service is used, how many distinct callers a day, which files, tools and clients, and which requests fail or ask for a ticker that is not covered, so that it can be run and improved; and to detect abuse. There is no profiling, no advertising and no sale of data.
Legal basis
VoidLab handles the data of each request, and keeps the usage records, on the basis of its legitimate interest in running a public service and measuring how it is used. The records hold only what that needs: they are pseudonymous, keep no argument of a call but its tickers, and are kept three months.
Who processes it
Cloudflare, Inc. hosts the site, the API and the MCP server, receives each request in order to answer it, and stores the usage records on behalf of VoidLab under its data processing addendum. It may process them in the United States. Simple Analytics counts the visits to the pages. The records are not sold or shared with anyone else.
How long
Usage records are kept three months. Daily totals made from them, such as how many requests and callers asked for each fund or stock on a day, carry no caller's code and are kept longer, to know which funds are looked for. The Workers request logs of the site and of the count of the tools' actions are turned off, so no log of each request's headers is kept beside the records. The service's own status checks keep the results of their probes, which carry no visitor data, and are not counted as usage.
Your rights
You have the right to see the records about you, to have them corrected or erased, to have their use restricted and to object to their use. Write to contact@tickerinside.com and say which. The records carry no name, account or IP address, so yours can be looked for only from what you give: the days of the requests, the IP address they came from and the User-Agent of the program that made them. You can also complain to your data protection authority.
Children
The service is not directed to children under 13 and asks no one for personal data.
Changes
A change to this policy is listed on What changed, and the policy that applies to a request is the one on this page on the day it is made. The publisher and the host are named on the legal notice, and the conditions of use are in the terms of service.
