Privacy

Browsing and preferences

We do not offer user accounts. Your theme preference is stored in your browser and can be removed by clearing site data. We do not currently use a separate on-site click analytics service.

Hosting and network providers may process access and security logs under their own policies.

Access protection

To limit bulk scraping, we use a security cookie that lasts about 30 minutes, hashes of network addresses and browser identifiers, and access counters. Security state is retained for no more than three days after your last visit and is not used for advertising profiles. Your browser may perform a lightweight access check.

Inputs to local tools

JSON formatting, account conversion and cost estimates run in the current browser page. Entered and imported content is not uploaded or saved in our database, browser storage or the URL. Refreshing or closing the page clears the input.

Copying and downloading happen only when you request them, placing the result on your clipboard or in a local file. Account previews mask tokens, but copied and downloaded output contains full credentials. Keep it secure. JSON masking recognizes common credential field names, not every kind of private information. Review the result before sharing it.

API connectivity tests

Only when you click Send does your browser send one request containing the key, model ID and prompt to the HTTPS target shown. The request does not pass through a BuYaoAI proxy. Inputs remain in page memory and are not saved in our database, browser storage or the URL. The target provider sets its own retention and billing policies.

Generation requests may incur charges. An output token limit is not a spending limit. A timeout, cancellation or closed page does not undo a request already accepted by the provider. The target must allow cross-origin browser access; failure to receive a response does not establish an outage. Responses mask common credential fields and the key you supplied, and copied curl commands use a placeholder key. Check the output before sharing it.

Submissions, reports and enquiries

Forms ask only for information needed to handle the request, such as a public URL, description, evidence links and reply address. A reply address is optional for reports. Do not include passwords, API keys or other credentials.

We review email manually. We do not create a submission tracking database or provide a public ticket tracker. If a reply is needed, we use the address you supplied.

Preparing and sending email

Forms validate and prepare an email subject and body in the current page. They do not automatically upload or send your input, or save it in our database or browser storage. Copy the message and send it through your usual email service to kev7n#qq.com (replace # with @ when sending). Unsent input may be lost when you refresh or close the page.

Copying a message or opening your email app does not send it. Your email provider and the receiving email service process the message under their own policies. We receive and review it in our mailbox.

External links

Once you visit a model, tool or service website, its privacy policy and terms apply. Promotional links are identified separately. Any commission does not affect our data or ranking rules.

Correcting or deleting contact information

To correct or request deletion of contact information you previously emailed us, write to kev7n#qq.com (replace # with @ when sending) or select “Correct or delete personal information” on the contact page. Include enough detail to identify your request.