Public data · Access boundaries · Your rights

Data compliance statement

Why we process data, what to avoid submitting, and how to make a data request. Clear boundaries, not blanket compliance claims.

Updated October 9, 2026

Data and purpose

Free tools process submitted URLs or text, public page content and check results to perform the requested check. Real AI checks also process the necessary brand context and test questions.

Account services process sign-in information, roles, tasks and reports. Necessary source identifiers, timestamps, states and errors may be recorded to prevent abuse, enforce limits and diagnose failures.

Before you submit

Only submit material you are authorized to use. Do not paste passwords, API keys, identity documents, customer lists, unpublished contracts or other sensitive information. Publicly visible personal data is not unrestricted data.

Validation and redaction reduce risk but cannot identify every sensitive item. Remove irrelevant personal information and trade secrets before submitting.

AI services, cloud processing and location

Static checks do not require AI calls. Real AI checks send necessary questions and public context to the model service used for that check; its policies and terms may affect the answer.

Accounts and tasks use cloud services. Providers may differ in processing location, retention and terms. This statement does not promise all processing stays in your country or claim an unverified zero-cross-border guarantee. Confirm suitability before submitting regulated or sensitive data.

Results, cache and access

Actual AI answers and static checks are distinguished. Cached results reuse an earlier check and are not a fresh model query; read the source and detection time shown.

Private tasks and reports require account permissions and are not part of public descriptions or entity metadata. These public information pages do not read or display customer tasks, raw answers or account records. A private report URL is not an anonymous share feature.

Retention and security limits

Task evidence supports traceability; necessary operational records support diagnostics and abuse prevention. We do not invent a universal retention period for every record.

Validation, public-URL restrictions, frequency controls and permissions reduce risk; no system can promise absolute security. Report suspected exposure privately and do not continue retrieving or spreading others’ data.

Data requests

For data concerns, export or deletion requests, contact hohoqi@qq.com with the relevant URL or task reference. Do not send passwords, keys or identity documents. We need to verify identity and authorization for account records.

We assess the records, permissions and applicable obligations involved. Deleting a task does not necessarily reverse processing already performed by a model provider; relevant limits will be explained when handling the request.