Keep the scan small, explain the data, respect the person.

The public check receives the hostname or HTTPS endpoint submitted for the scan, the authorization confirmation, technical observations needed to produce the report and limited request metadata used for reliability, rate limiting and abuse prevention. The form does not ask for passwords, private keys, API tokens or application data.

• To connect to the authorized public endpoint and return a time-specific report.
• To prevent excessive or abusive requests and protect the service.
• To diagnose errors, maintain availability and improve the clarity of the product.
• To respond to a product, privacy, abuse or opt-out request.

Request data should be limited to the public endpoint needed for the check. Access is restricted to the systems and people needed to operate the product, and reports should not contain secrets or application data. Do not submit personal or confidential information into a scan field. Retention should be limited to the operational and legal purpose for which data is kept.

If you want to ask about access, correction, deletion or the handling of information connected with a Q-Ready request, email support@aiagents007.tech. Include enough detail to identify the request, but do not include secrets. We may need to verify the request before acting on it.

As the product moves from public checks toward optional accounts or paid access, this notice must be updated before those workflows are introduced. The live product should be treated as the source of the current data boundary.