A proxy network that is clean at the source can still be abused downstream. Vetting customers is how a vendor limits that, and it is also what a compliance reviewer on your side is entitled to ask about.
What good looks like on a public page
- It says what is asked at sign-up and what triggers a further check.
- It says the vendor may refuse an account, and on what grounds.
- It links the acceptable use policy, published before purchase.
- It says what happens after an abuse report: who reads it, and what the vendor may do.
Questions to put in writing
- Which use cases do you refuse, and can you give an example of a refusal?
- Is verification applied to every customer, or to some products, filters or volumes?
- How do you handle a report about traffic from a customer's session?
- Do you re-check an account whose usage changes?
Answers that should worry you
A vendor that cannot describe any refusal, a policy that appears only in the terms and not before purchase, and a verification step that exists in marketing but that no customer you speak to has met. None proves wrongdoing; each is a reason to ask more. See our own answers on the vetting page, including what we do not yet publish.