Data handling and privacy
This page describes how the current product works. Updated October 14, 2026. Contact xbbdkj@gmail.com with questions.
Website information and reports
When you start an audit, the service processes the submitted public URL and fetches public pages. It stores task state, page evidence, reports, and selected fix instructions in Cloudflare storage. A browser check can run the public entry page’s scripts and store first-screen screenshots. Do not submit secret-bearing URLs or pages you are not entitled to examine.
Access and retention
Reports and screenshots require a random access credential and become unavailable 24 hours after the original scan. Expired storage is removed by periodic cleanup; loss of the credential means the report cannot be recovered through an account. Download links expire after 15 minutes. Your browser keeps the latest report credential in session storage so a refresh can restore it. Protect that credential like a private link.
Service protection and measurement
The service uses short-lived hashed request-source counters to limit abuse. Cloudflare processes requests and operational logs as the hosting provider. Aggregate service counts record real audit and task activity without the submitted website URL. Optional report-view and copy measurements stay in Cloudflare and are sent only when you enable usage measurement. You can turn that preference off in the audit page footer. No Google Analytics or other third-party marketing script is enabled in this release.
Optional AI interpretation
If the service owner configures OpenAI or Anthropic, selected report evidence can be sent to that provider to produce a written interpretation. Reports label whether model interpretation was used. Provider credentials stay on the server. The evidence report and basic repair instructions work without that connection. The current public release does not claim that an AI visibility observation service is connected.
Questions or deletion requests
Email xbbdkj@gmail.com for questions about the current data handling or a deletion request. Do not email credentials or private page contents. There is no registration or payment information collected by an account or checkout flow in this version.
Make the next fix a clear one.
Start with public-page evidence. Let your coding assistant find the right files, then verify the change.
Run a website audit