Privacy Policy
Last updated: November 16, 2026
Contents
Who we are
PublicAML is a free crypto AML/KYT screening service at publicaml.org, together with the PublicAML Intelligence API (intelapi.publicaml.org), the PublicAML app for ChatGPT and other MCP clients (mcp.publicaml.org), and the PublicAML Telegram bot. This policy covers all of them. Contact: [email protected].
What we collect
Addresses and transaction hashes you submit. When you screen a wallet, trace funds or check a transaction (on the website, through the API, in the Telegram bot or through the ChatGPT/MCP app), we receive the blockchain address or transaction hash, the chain, and any options you set, for example the number of hops to follow. These are public blockchain identifiers. We do not ask for, and you should not enter, names, government IDs, payment card details, passwords or private keys.
Account data, only if you sign in. Checks do not require an account. If you create one, we store your email address, your login session, and the checks and case reports tied to your account.
Reports you file. If you report a scam or theft, we store what you put in the report: the addresses involved, the category, your description, and whether you chose to make it public.
Check records. When you check an address on the website (in the check box, on an address page or in your dashboard), we record the address, the chain, the time, which of these pages it came from, your IP address, the network and country that IP belongs to, your browser's user agent and screen size, and your account if you are signed in. The network and country are looked up in a database kept on our own servers; your IP is not sent to any outside lookup service. Why we do this is explained under "Checks and abuse prevention".
API request log. Our API records every address it is asked about, with the time, the API key or the website page that asked, and the IP address the request came from. For checks on the website this is your IP. Checks from the Telegram bot and the ChatGPT/MCP app reach the API from our own servers, so the log holds our server's IP, not yours; checks from the bot are recorded under the bot or under an API key linked to your Telegram account.
Technical data. Like any web service we process request metadata (time, endpoint, response code, duration) to deliver responses, enforce the anonymous rate limit and investigate errors. API keys are identified by a short hint and are never stored in plain text in logs.
Website analytics, cookies and local storage. The website uses Google Tag Manager / Google Analytics to measure page visits. It sets one cookie of its own, a random visitor identifier, so that several checks from the same browser can be recognised as one visitor, and stores a few values in your browser (login session, language and theme preferences). The API, the MCP app and the Telegram bot do not use analytics cookies.
Live on-chain data. When you open an address page, your browser asks a public blockchain node run by a third party (for example publicnode.com, blastapi.io, llamarpc.com, mevblocker.io, bnbchain.org, trongrid.io or solana.com) for the current state of that address. If the address is a token contract on Ethereum, BNB Chain or TRON, your browser also sends the contract address to GoPlus Security (api.gopluslabs.io) for the token signals shown on the page. These requests go directly from your browser, not through PublicAML, so the node operator and GoPlus receive the address you are viewing together with your IP address and browser details, under their own privacy policies. They can see that the request came from publicaml.org; we send no cookies and no page address with it, and we do not store the results on our servers.
Checks and abuse prevention
People who steal crypto sometimes use screening services too: to look at a victim's wallet before an attack, or at their own wallets before moving stolen funds. We keep check records so that, when an address later turns out to belong to a hack, a drainer, a scam or a sanctioned party, we can see who checked it beforehand and help investigate.
- Only PublicAML staff can see check records. Lists show IP addresses shortened (for example 203.0.113.x). The full IP address is shown only when a staff member opens a single record, and every such opening and every export is logged.
- We take no automatic action against anyone based on these records: no blocking, no bans, no emails and no publication.
- We give check records to law enforcement or other authorities only when the law requires it.
- We do not sell check records and do not use them for advertising. We link checks to one another only to investigate abuse of the service.
The ChatGPT and MCP app
The app exposes read-only tools: screen_address, trace_funds, trace_source_of_funds, list_counterparties, list_transactions, screen_transaction and follow_swap. Each tool receives only the address or transaction hash, the chain and the tool's own options. It does not receive your chat history, your name, your email or your ChatGPT account details, and it never moves funds or changes anything on-chain.
Tool results contain public blockchain data and our analysis of it: AML score and risk level, category and labels, sanctions and incident exposure, counterparties, transfers, and where funds came from or went. The MCP server itself records only which tool was called, how long it took and whether it worked; it does not record the address you looked up. It passes your request to the PublicAML Intelligence API, which logs the address as described under "API request log", with our MCP server as the caller. Your IP address does not reach us: ChatGPT calls our server on your behalf.
How we use data
- To return the screening, tracing and transaction results you asked for.
- To run your account, show your check history and publish reports you mark public.
- To keep the service up: rate limiting and error diagnosis.
- To detect and investigate abuse of the service, as described under "Checks and abuse prevention".
- To understand aggregate usage and improve coverage.
We do not sell personal data and we do not use it for advertising.
Who receives it
- Our infrastructure providers: hosting and Cloudflare (network delivery and protection), which process requests on our behalf.
- Google, for website analytics, and for sign-in if you choose Google login.
- Error monitoring, run on our own servers, which receives technical details of failed requests.
- OpenAI, when you use the ChatGPT app: your conversation is handled by OpenAI under its own privacy policy; we receive only the tool inputs described above.
- The public, only for reports you explicitly publish, and for risk labels on blockchain addresses (not on people).
- Authorities, only when the law requires it.
How long we keep it
- Website check records: the IP address and the user agent are deleted after 180 days; the rest of the record (address, time, page, network, country, account) after 365 days.
- API request log, including IP addresses: 90 days.
- Usage counters per API key and endpoint: kept, but they contain no addresses and no IP addresses.
- Error reports: up to 90 days.
- The visitor identifier cookie: one year.
- Account data and check history: until you delete your account.
- Published reports and address risk labels: kept while they are relevant to screening; you can ask us to withdraw a report you filed.
Your choices and rights
- Use every screening feature without an account.
- Ask for a copy of your account data, including the check records tied to it, or for it to be corrected or deleted, by writing to [email protected].
- Withdraw a report you filed, or dispute a label on an address you control, at the same address.
- Block analytics with your browser settings or an ad blocker; the service keeps working.
- Disconnect the PublicAML app in ChatGPT at any time from ChatGPT's settings.
We answer requests within 30 days.
Changes
When this policy changes we update the date at the top of this page. Material changes to what the ChatGPT/MCP app collects will be reflected here before they ship.
The update of November 6, 2026 added check records and abuse investigation, and corrected what we said about the API request log: it keeps addresses and IP addresses for 90 days, not aggregate counters only for 30.
