1. Purpose and scope
This policy explains when Infatica may request KYC/KYB, business identity verification, beneficial ownership information, sanctions screening, source-of-funds checks, use-case review, end-client review, or other compliance information before activating or continuing access to the Services.
This policy applies to customers, resellers, partners, end clients where applicable, authorized users, and any party accessing or using Infatica services through a customer, reseller, or partner relationship.
2. Why Infatica performs review
Infatica uses KYC/KYB and use-case review to support compliance, fraud prevention, abuse prevention, sanctions screening, security, network integrity, restricted-target review, and enforcement of Infatica’s agreements and policies.
3. When review may be required
| Review trigger | Description |
|---|---|
| Before activation | Review may be required before customer, reseller, partner, or end-client access is activated. |
| During onboarding | Review may be required as part of customer, reseller, partner, or end-client onboarding. |
| Higher-risk services or targets | Review may be required before access to higher-risk services, target websites, categories, platforms, or use cases. |
| Usage change | Review may be required when usage patterns, traffic type, volume, target category, or stated use case changes. |
| Risk signal | Review may be required where compliance, abuse, security, platform, legal, or reputational risk is identified. |
4. Information Infatica may request
Infatica may request information reasonably necessary to assess restricted targets, blacklist exceptions, use cases, compliance risks, or suspected misuse. Requested information may include:
- customer identity and whether the customer is direct, reseller, partner, or end client;
- business identity information and beneficial ownership information where required;
- end-client information where applicable;
- target domain, website, category, platform, or service;
- business purpose and use-case description;
- expected traffic type, traffic pattern, volume, and duration;
- whether login, account access, API interaction, or data collection is involved;
- sanctions screening, source-of-funds checks, or additional compliance information where required;
- confirmation that the activity does not involve fraud, unlawful access, credential abuse, payment circumvention, identity masking for financial accounts, child-safety-sensitive abuse, or violation of applicable law or platform terms.
5. Restricted targets and higher-risk categories
For safety and compliance purposes, certain websites, domains, categories, or services may be inaccessible by default or require manual approval. Access may require manual review and approval for categories such as:
- financial services platforms;
- marketplaces and ticketing platforms;
- social networks and messaging platforms;
- advertising platforms and ad exchanges;
- platforms requiring login or account access;
- platforms with fraud, security, anti-abuse, age-assurance, or child-safety systems;
- high-volume or high-risk public web data workflows;
- cybersecurity research, vulnerability scanning, or security testing unless the customer owns or is authorized to test the target.
Access through the Services is generally prohibited for target categories where proxy use may create legal, compliance, platform-safety, child-safety, fraud, abuse, or reputational risk, unless expressly approved by Infatica where appropriate.
6. Customer obligations
Customers must:
- provide accurate, complete, and current information requested for KYC/KYB, use-case review, end-client review, and compliance review;
- not change the approved use case, target, traffic type, or end-client structure without notice where such change may affect risk or approval;
- ensure that users, end clients, and downstream customers comply with the applicable agreement, Acceptable Use Policy, and applicable law;
- promptly cooperate with Infatica in investigating suspected misuse, abuse complaints, legal notices, platform complaints, governmental requests, vulnerability reports, security incidents, sanctions concerns, or policy violations.
7. Review process and outcomes
| Operational item | Position |
|---|---|
| KYC/KYB provider | KYC/KYB and compliance checks may be conducted internally by Infatica or through third-party verification, sanctions-screening, fraud-prevention, or compliance service providers, where appropriate. |
| KYC trigger | KYC/KYB, business identity verification, beneficial ownership review, sanctions screening, source-of-funds checks, use-case review, or end-client review may be required before activation, during onboarding, before access to higher-risk services, when usage patterns change, or where compliance, abuse, security, platform, legal, or reputational risk is identified. |
| Use-case review owner | Use-case review may be coordinated by Infatica’s sales, compliance, legal, support, security, or management functions, depending on the customer type, requested service, risk profile, and information provided. |
| Review timeline | Review timelines depend on the completeness of information provided, customer risk profile, service type, target websites or categories, required approvals, and any additional compliance checks. Access may be delayed until review is completed. |
| Escalation path | Higher-risk, incomplete, inconsistent, or suspicious requests may be escalated to Infatica’s compliance, legal, security, management, or relevant operational owners for further review, restriction, suspension, rejection, or termination. |
Infatica may approve, deny, condition, restrict, suspend, or revoke access at its sole discretion. Approval of one use case or target does not guarantee approval of any other use case, target, customer, reseller, end client, geography, volume, or traffic pattern.
8. Failure to provide information or failed review
Infatica may refuse, restrict, suspend, or terminate access where the customer does not provide required information, provides inaccurate or incomplete information, fails screening, changes its use case without notice, or creates legal, compliance, security, abuse, platform, or reputational risk.
9. Resellers and downstream customers
If a customer resells, makes available, or otherwise enables access to the Services by any third party, the customer remains responsible for the acts and omissions of such third party. Infatica may require the customer to suspend or terminate downstream access where Infatica reasonably suspects that a downstream user, end client, or customer is violating the agreement, the Acceptable Use Policy, applicable law, or platform requirements.
10. Changes to this policy
Infatica may update this policy from time to time to reflect changes in laws, services, platform risks, abuse patterns, technical controls, or business practices. The updated version will be posted in the Trust Center or otherwise made available by Infatica.
