Privacy and data
When your assistant works on your site, its requests pass through AI Puffer’s hosted relay to your WordPress site, and the answers go back the same way.
What passes through
Section titled “What passes through”- The relay sees your site’s address, the WordPress user your assistant acts as, the permissions of the connection, and what each request is: which tool, on what, with which result.
- Your content (a post you asked about, a product’s price) goes to your assistant, because it asked for it. Your assistant’s own privacy terms apply to it there.
- Cloud reporting records keep operational information, not full pages or chat transcripts. Your WordPress site has a separate private operation journal, which can retain request inputs and results.
Connection diagnostics
Section titled “Connection diagnostics”Activity records include basic troubleshooting details, such as request status, timing, error category, the reason for an access change, and why a change was refused. For a refused change, that means where in the request the problem was (a field location, never its value) or the counts that didn’t match. Cloud diagnostics do not store page content, field values, prompts or credentials. More detailed errors may remain in your WordPress site’s private activity log.
Private chatbot tests
Section titled “Private chatbot tests”A private chatbot test sends your question and the selected knowledge context to the configured AI provider. Its reply returns to WordPress and your assistant, whose privacy terms also apply. The test is not a visitor conversation, but its question and reply can remain in the private WordPress operation journal. Cloud diagnostics do not store those prompts or replies.
A successful test uses one website action. Inference is separate: it spends Cloud AI credits, or your provider bills your own API key.
Upload checks
Section titled “Upload checks”Your assistant can find an image you’ve just uploaded to WordPress using a temporary reference. That reference stays with the request on your site and in your assistant’s response; Cloud reporting does not store it. The check uploads nothing and uses no website actions or AI credits.
Requested browser page checks
Section titled “Requested browser page checks”A page check sends a public URL on your site and a device size to a fresh Cloudflare browser. It does not log in, click, submit forms or load resources from other sites. The results go through WordPress to your assistant.
You can make 10 browser launch attempts per Cloud account per UTC day, with one running at a time. Failed launch attempts count. Each successful check uses one website action; failed or blocked checks use none. No AI credits are used. Temporary limits affect page checks only.
Requested Lighthouse audits (Beta)
Section titled “Requested Lighthouse audits (Beta)”A Lighthouse audit sends your public page URL and device choice to Google PageSpeed Insights. Google loads the page and its public resources. No WordPress credentials are sent, and you don’t need your own Google key.
The Beta allows 10 audit attempts per Cloud account per UTC day, with one running at a time. Failed calls to Google count. Audits run only when requested; availability and limits may change. Failed or blocked audits use no website actions, and other website tools remain available.
The report goes to your WordPress site and assistant. Cloud stores basic usage records, not the full report. Google’s API terms and privacy policy apply.
Where it lives
Section titled “Where it lives”- The relay runs on Cloudflare. Your account and allowance live in AI Puffer Cloud, on Vercel, with recent reporting stored in Neon.
- Your WordPress site keeps its own activity log of everything your assistants did.
- Saved workflows are kept only in your WordPress database, as private records of the user who saved them. Their instructions pass through the relay when your assistant saves or reads one, like any other request.
See the privacy policy and terms.