privacy

the website (pdata.world)

The website is hosted by Vercel. It sets no cookies and stores nothing in your browser (no local storage, session storage or IndexedDB), which is why there is no consent banner. Vercel Web Analytics counts page views, and Vercel Speed Insights measures how fast pages load.

PostHog, in its EU region, records the pages you open (their address, including any search words in it, and the page you came from), the links and buttons you click, and when you leave a page, along with your browser, operating system and screen size. Its identifier for you exists only in the open page's memory, so a reload or a new tab starts a new one. PostHog does not store your IP address; it keeps the country and city it looks up from it. Session recording is off. A visit that arrives from an AI assistant, such as a link in a ChatGPT answer, is tagged with the assistant's name. These requests go through pdata.world's own address (/_ph), and PostHog keeps the records for one year.

If a page fails in your browser, an error report goes to Sentry, which stores it in the US: the error, the page address, your browser and operating system, and your IP address. Sentry keeps error reports for 30 days.

The search box and some live parts of the pages call the API from your browser, so those requests are recorded as described next.

the API and MCP server (api.pdata.world)

Requests pass through Cloudflare before they reach pdata.world's server in the EU.

The server's web log records, for each request, your IP address, the time, the address requested (including any search words), the response status and size, the page you came from and your user agent. It is kept for 15 days and then deleted.

The API's own log records your IP address, the time, the address requested and the response status. When an assistant calls a tool on the MCP server, this log also records the API request the tool makes, with its parameters (for a search, the search words). The log is limited to 1 GB and three weeks, whichever is reached first; at November 2026 traffic it reaches back about four days.

Once a day the web log is summarised into counts by type of client (such as AI crawler or MCP client), user-agent name and response status, with the number of distinct addresses and pages but not the addresses or pages themselves. These counts are kept for 180 days.

Search text sent to the API, including text typed into the search box on this site, is also counted by day: lower-cased, cut to 80 characters, with a rough count of how many results it found and without your address. These counts are kept for 60 days. MCP use is counted by day by client name and version, user-agent, tool, outcome and the names of the arguments a tool was called with; the values of the arguments are not part of these counts, and neither is your address. They are kept for 400 days. The MCP server keeps no session between calls.

the public database (pg.pdata.world)

Its connection pooler logs each connection: your IP address, the database and user name, and when you connected and disconnected. These logs are kept for about nine weeks.

The database does not log the text of queries that succeed. A query that fails is written to the database's error log with its text and time but without your address; that log has no set deletion date.

who handles it

Cloudflare, Vercel, PostHog and Sentry process the data above for pdata.world, each under its own privacy policy. pdata.world uses it to keep the service running, fix errors and see how the site and API are used. The market data the site serves comes from the venues' own public APIs, as the methodology page describes.

Questions about this page, or about data that concerns you: support@pdata.world. Changes to this page are dated at the top.