This Privacy Policy describes what data the LLMPress WordPress plugin (“LLMPress”, “the Plugin”) processes, where it goes, and who controls it. LLMPress is developed and distributed by LLMPress (llmpress.net) (“we”, “us”).
LLMPress runs on your own WordPress installation. For the purposes of data protection law (e.g. GDPR), the site owner running LLMPress is the data controller of any personal data processed through their site; LLMPress acts as a data processor only for the specific remote calls described below.
1. Data processed entirely on your server
The core, free features of LLMPress never leave your WordPress installation:
- Markdown conversion — page/post HTML is converted to Markdown in pure PHP and served at
any-url.mdand . No content is sent to any external server to perform this conversion. - Settings — your configuration (conversion mode, exclusion rules, cache preferences) is stored in the WordPress
wp_optionstable, like any other plugin setting. - Cache — generated Markdown/
llms.txtoutput may be cached locally (transients/options) to avoid re-conversion on every request. Cached content is your own site content; it is not transmitted anywhere.
None of the above involves a third party or leaves your server.
2. Data sent to LLMPress’s own servers
2.1 License activation (Pro)
If you activate a Pro license key, the Plugin contacts our license server at license.llmpress.net to activate, validate, and deactivate the key. This sends:
- the license key you entered,
- a randomly generated instance identifier for your site,
- your site’s URL,
- the installed plugin version.
This data is used only to enforce license terms (e.g. number of active sites per key) and to provide update/support eligibility. It is not used for advertising or sold to third parties. If you do not enter a Pro license key, this call never happens.
2.2 AI-crawler analytics (Pro only, opt-in by feature)
On sites with an active Pro license and the Analytics feature enabled, LLMPress logs requests to your own Markdown/llms.txt endpoints that match known AI-crawler user agents (e.g. GPTBot, ClaudeBot, PerplexityBot, Google-Extended). Each log entry stored in your own WordPress database contains:
- the bot name (matched from a known list),
- the requested URL,
- the HTTP response code,
- a timestamp.
No IP addresses, cookies, or other visitor-identifying data are collected. Logs are stored in a dedicated database table on your own server, are never transmitted to us or any third party, and are automatically pruned after 90 days. Free installations never run this logging code at all, regardless of license status.
3. Data sent to third parties
3.1 Google Search Console (optional integration)
If you choose to connect Google Search Console from the Plugin’s Search Console page, LLMPress uses an OAuth flow (proxied through license.llmpress.net for the token exchange) to obtain an access token scoped to the Search Console API, then calls googleapis.com directly from your server to retrieve indexing/search-performance data for properties you authorize. This is entirely optional and only occurs if you explicitly start the connection flow. You can disconnect at any time from the same page; disconnecting revokes the stored token. Google’s own privacy policy governs its processing of this request:
3.2 No analytics, tracking, or advertising services
LLMPress does not embed any third-party analytics, tracking pixels, or advertising SDKs, and does not transmit your site’s visitor data to any ad network.
4. Data from your site visitors
LLMPress serves Markdown and llms.txt content to any client that requests it (browsers, AI crawlers, tools). Serving these responses follows the same logging behavior as the rest of your WordPress installation (e.g. your web server’s own access logs) — LLMPress itself does not add visitor tracking beyond the optional, non-PII crawler analytics described in §2.2.
5. Data retention
- License activation records are retained on the license server for as long as the license is active, per our license server’s own retention rules.
- Crawler analytics rows (Pro) are stored in your database and auto-deleted after 90 days by a daily cron job.
- All plugin settings, cache, and logs are deleted from your database when you delete the Plugin (via
uninstall.php), not merely on deactivation.
6. Your rights
Because your WordPress installation is the data controller for your site, requests regarding personal data collected through your site (e.g. GDPR access/erasure requests from your visitors) should be handled by you as the site operator. For data we hold directly (license records tied to your account), contact us at the address below to request access, correction, or deletion.
7. Changes to this policy
We may update this Privacy Policy as the Plugin evolves. Material changes will be noted in the Plugin’s changelog.
8. Contact
LLMPress — For privacy questions specific to LLMPress, please use the support channel listed on the plugin’s WordPress.org page.
Last updated: September 3, 2026
Install LLMPress Free