Privacy notice

A supplier check processes the company name or Unified Social Credit Code you enter. If the follow-up step needs another identifier, it also processes a website, a city, or an Alibaba shop URL. The service sends company identifiers to registry, search, and litigation-data providers. Court results are lawsuit and enforcement counts, not a legal opinion.

This notice explains the information used to provide Supplier Verify AI, including company lookups and court-record checks, and to answer support requests.

Updated

Information used for supplier checks

When you start a check, we process the company name or Unified Social Credit Code you enter. The name may be English or Chinese. If a later step is needed to tell companies apart, we also process a website, a city, an en.alibaba.com shop URL, or a verified.alibaba.com assessment report URL. The first input box does not treat a shop link as a website. The service also processes retrieved company information, source records, assessment results, and technical records needed to operate the check.

Company identifiers can be sent to a business-registry provider, to search providers, and to a litigation-data provider. The litigation lookup asks for lawsuit and enforcement records. It does not collect the dishonest-judgment list, and the counts shown on a report are not a legal opinion or a statement that no other case exists. Individual query results are not published as public pages.

Inputs, investigation records, and results may be stored to deliver results, reuse previously retrieved information, troubleshoot failures, and control abuse and service costs. Individual query results are not included in our public sitemap or guide library.

Contact and support

If you use the contact form, we process your email address, optional name, message, and subsequent conversation. These records are stored so we can respond and maintain the support conversation. Email delivery services may process notification and reply information.

A private conversation link contains an access token. Keep that link private because someone who has it may be able to read the conversation. Support and administration pages are excluded from our public analytics component and carry instructions against search indexing.

Website analytics and cookies

The public website uses Google Analytics to understand visits and actions such as starting a check, displaying a result, viewing the sample, or opening the contact form. Analytics can process browser and device information, referral information, and cookie-based identifiers.

Our custom usage events use action and outcome labels. They do not include the supplier name, credit code, support message, email address, or report contents. Public page addresses sent by our analytics component omit query strings and fragments.

You can control cookies in your browser and use Google's Analytics opt-out browser add-on. Read how Google uses information from sites using its services. Administrator sessions also use a cookie for access control.

Service providers and processing locations

Providers supporting hosting, databases, company data, litigation lookups, web retrieval, AI processing, email, and analytics may process information needed to deliver those functions. For example, a company name or credit code may be sent to a registry provider, a search provider, or a litigation-data provider. Providers may process data in countries other than your own.

Do not submit confidential personal documents or information unrelated to the supplier check. A public source can still contain personal information; only provide what is necessary for your request.

Retention and your requests

Retention depends on the record and its operational purpose, including delivering assessments, responding to support, preventing abuse, and maintaining backups. This service does not offer an automatic deletion deadline for every record.

To ask about information you submitted, request a correction or deletion, or raise a privacy concern, email a1753568497@gmail.com. Provide enough information to identify the relevant request without including passwords or a private conversation token. We may need to verify that the request concerns your information.

Changes to this notice

We will update this page when the described practices change. The date above identifies the current version.