QR generation and scan logging
Where is that QR code image built?
Many WordPress QR plugins draw the code with a library on your site or in the browser. Others request a third-party generator and send the encoded URL or text in that image call. Dynamic QR tools may also log scans when someone follows a redirect. Compare the documented setups below. Referral plugins that only use a QR helper for sharing have a separate page.
Based on plugin documentation, not tests of your site. Generation host, encoded content, and scan logging decide what leaves the page. This is not legal advice or a compliance rating.
Scan your site for third-party requestsThis scan checks requests made by a visitor's browser on a page showing a QR image. It can show remote generator requests made by that browser. It does not inspect server-side generation, admin-only requests, stored scan logs, or what happens when someone scans a printed code with a phone.
Local libraries vs remote generators
QR images built on your site or in the browser
Prefer plugins that ship a local QR library or generate PNGs on your server. Check what text or URL you encode, and whether dynamic redirects store scan counts in your database. Document retention for any scan logs you keep.
Third-party QR image APIs and outside logging
Some plugins send the URL or text to a remote QR generator such as api.qrserver.com. Check whether the request comes from your server, an admin screen, or the visitor's browser. Review image generation separately from redirects and scan logging, including which service receives each request and what it keeps.
QR code setups
No paid placement. Local generation tools appear first, followed by any remote-generator group, then unreviewed rows. Local tools may still store scan counts when dynamic redirects are enabled. Names are alphabetical within each group.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| AppsPlus Dynamic QR Manager Documented self-hosted dynamic QR redirects on your WordPress domain. Destination URLs can change without reprinting the code. The listing says QR generation, redirects, and total scan counts stay on your site with no external QR service required, and redirect plus scan data is kept in the WordPress database. Review what scan totals you store and how long you keep them. Browser hosts were not verified for this snapshot. | QR image built on your site or in the browser | Browser hosts not verified | Not assessed | Not tested |
| |
| EffortLess QR Code Generator Documented local QR generation with client-side JavaScript or server-side PHP PNG rendering. The listing says all code is bundled locally, no data is sent to external services, and server-rendered images can be cached under uploads. Shortcodes can encode a URL or other data. Review render mode and what you encode. Browser hosts were not verified for this snapshot. | QR image built on your site or in the browser | Browser hosts not verified | Not assessed | Not tested |
| |
| Kaya QR Code Generator Documented local QR generation. The listing says no external service, API, or third-party dependency is required, and the QR library is included with the plugin (based on qr.js). Shortcodes, a Gutenberg block, and a widget can encode text, URLs, or the current page URL. Privacy section says the plugin does not connect to external services to generate codes. Review what content you encode before publishing. Browser hosts were not verified for this snapshot. | QR image built on your site or in the browser | Browser hosts not verified | Not assessed | Not tested |
| |
| Conductor QR Generator Documented file-to-QR flow with a short download URL. The listing discloses a fallback request to api.qrserver.com that sends the short URL as the data parameter to obtain a QR image, with optional caption and branding. Files and download counts are stored locally. The docs do not establish whether the API request is made by the server or the visitor's browser. Review the encoded short URL and generation settings. Visitor-browser hosts were not verified for this snapshot. | QR image request can go to a third-party generator | Browser hosts not verified | Not assessed | Not tested |
| |
| Simple URL to QR Code Documented admin-panel URL-to-QR tool. The listing says generation uses the QR Server API (goqr.me) and sends the URL being converted plus basic image size parameters. No data storage is claimed. This path is described as an admin workflow, so visitor-page hosts were not verified for this snapshot. Review which URLs you submit to the generator. | QR image request can go to a third-party generator | Browser hosts not verified | Not assessed | Not tested |
|
What this table does and does not prove
This table describes documented QR generation and redirect workflows, not tests of your site. Consent timing, live generator payload contents beyond the cited docs, and retention lengths have not been assessed. Check local vs remote generation, what you encode, and any scan logging. Referral sharing helpers that call a QR API are covered on the referral page.
Documentation snapshot: Oct 8, 2026. Sources are linked in each reviewed row.
Related pages
Scan your site for third-party requests/wp-qr-code-plugin-privacy