What Loupely reads from your site #
When a capture runs, the Loupely WordPress Plugin and Chrome extension read diagnostic data from your WordPress installation: PHP error logs, Hook Execution records, REST API responses, WooCommerce pipeline events, active plugin versions, server configuration details, and browser-side signals from the current page. This data is assembled into a capture payload and sent to Loupely’s servers to generate the diagnosis.
Reading this data requires an authenticated connection. The Chrome extension authenticates to your WordPress site using the connection key you configured. Without that key, the extension can read browser-side data only, with no access to server-side information.
What the capture payload contains #
The payload contains technical diagnostic data, not your site’s content. It does not include the text of your posts or pages, your user database, your customer records, your order history, or any customer personal data. It reads the state of the WordPress execution environment at the moment of capture, which is error logs, Hook Execution, server configuration, and the technical signals that indicate why something failed.
If a PHP error happens to include a database query that contains a customer’s email address, the credential scanner will check that value against known credential patterns, but customer PII embedded in error messages is not specifically redacted. Review capture files before sharing them with third parties if your site handles sensitive customer data.
Transmission and storage #
The capture payload is transmitted over HTTPS to Loupely’s servers. The diagnosis is generated and the result is returned to the extension popup. The content of the payload is then discarded server-side: the PHP Errors, Hook Execution details, and REST API responses are not written to a database. What is stored is session metadata only: the URL, the failure class, the triage route, and the timestamp. See What Data Loupely Collects About You for the complete breakdown.
The WordPress Plugin’s footprint on your site #
The Loupely WordPress Plugin adds a small persistent logging layer to your WordPress installation. It records PHP Errors, Hook Execution, and WooCommerce pipeline events to a local log that the 60-second capture buffer draws from. This data is stored in the WordPress Database on your own server, not on Loupely’s servers. It is retained according to the retention setting in the plugin settings page (default 30 days). It is only read when you trigger a capture. The plugin does not send data to Loupely continuously. It collects locally and transmits only when you initiate a diagnosis.