Last updated 13 November 2026.
What this document is
AMDT AI Traffic Analytics is a free WordPress plugin that is installed on your site. The data it records is stored in your own site’s database and is never sent to AMDT.
This page is therefore not AMDT’s privacy policy. It describes the data the plugin processes, so that you, as the operator of the site where it is installed, can comply with yours. You, not AMDT, are the controller of that data.
This document states technical facts and is not legal advice.
What the plugin records
Everything below is stored only in your site’s database.
| From whom | What is stored |
|---|---|
| Declared AI bots | IP address, User-Agent and the page requested |
| Whoever reads llms.txt | IP address, User-Agent and the page requested |
| People arriving from an AI assistant | Landing page, User-Agent, referring address and only the network of their IP, never the full address: for IPv4, up to the third block; for IPv6, the first forty-eight bits |
| Automated browsers posing as an iPhone | The request, with its full IP address |
| Requests signed with Web Bot Auth (currently those from Google-Agent and ChatGPT agent) | IP address, User-Agent and the page requested, plus their three signature headers (Signature-Agent, Signature-Input and Signature) and the result of checking them |
| Whoever opens a Grok calibration link (only if you create one; it expires after 24 hours and records at most 20 visits) | Date, full IP address, the network it belongs to (looked up via DNS), User-Agent and the request headers, except cookies, credentials and headers carrying IP addresses. Kept until you delete it or create another link. |
| Ordinary visitors | Nothing |
How long it is kept
Thirty, sixty or ninety days, as you choose in the settings.
What is not stored
- Nothing is stored about an ordinary visitor.
- Nothing is stored in your visitors’ browsers: no cookies, no local storage. Pages carry a small script that, only when the visitor arrives from an AI assistant, tells your own server about it.
- The full IP address of people arriving from an assistant is never stored.
One exception is worth stating out loud: the automated-browser detector could, in theory, mistake a person for one and record their request with the full IP address. It needs two matching signals to do so, which makes it unlikely, but not impossible.
Diagnostic log
It ships switched off. If you switch it on, the plugin also writes IP addresses and User-Agents to a file with a random key in its name, inside its own folder within your site’s uploads folder (amdt-ai-traffic-analytics/). That folder denies direct access on servers that read .htaccess, such as Apache. If you choose to delete the data when uninstalling, the log is deleted too. The file remains under your control.
Connections outside your server
None of them reach AMDT, and the plugin carries no telemetry. There are five:
- A daily download of the public IP address lists published by OpenAI (four lists), Anthropic and Perplexity. It ships switched off until you enable it; when you activate the plugin, a notice asks whether you want it.
- A download of the public keys that Google-Agent and ChatGPT agent use to sign their requests, only from
agent.bot.googandchatgpt.com, and never from an address taken from the request. It depends on the same switch as the IP lists, and it only happens when a signed visit from one of them arrives and the stored key has expired. - Queries to your server’s DNS to resolve the addresses of bots, of whoever reads llms.txt and of whoever opens a Grok calibration link. They are never made for people arriving from an assistant.
- Requests to your own site when you open the plugin’s dashboard or settings: to your home page, at most twice a day, to check whether a cache sits in front of WordPress, and to your
/llms.txt, at most once a day, to check that it is served correctly. - Requests to your own site when you run Agent-Readiness: to the pages it analyses, to
/llms.txt, to/robots.txtand to the addresses where an ARD manifest may be found, always with the certificate checked. No other site is contacted.
Third parties
The plugin shares the data it records with no one. The downloads of the public IP address lists and of the signing keys are HTTPS requests whose only identification is the plugin’s name and version: they send OpenAI, Anthropic, Perplexity and Google no data about your site or your visitors.
Agent-Readiness results include a link to PageSpeed Insights. It is an ordinary link: the plugin sends nothing to Google, and PageSpeed Insights only receives what you send it if you open it.
What falls to you
As the controller, it is for you to decide the lawful basis for this processing, to describe it in your own privacy policy and to handle the rights of the people concerned. The plugin adds suggested wording to the WordPress privacy guide (Settings → Privacy) for you to review and adapt.
Uninstalling
On uninstall, the data is not deleted by default. If you want it removed, untick “Keep data on uninstall” in the settings before uninstalling. While the other edition of the plugin remains installed, it is never deleted.
Changes
Any change in what the plugin processes will be published on this page with a new update date.