Customer Use-Case Review Policy

1. Purpose and scope

This policy explains when Infatica may request use-case review, end-client review, restricted-target 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 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. Permitted business use cases

Subject to the applicable agreement, the Acceptable Use Policy, this policy, and applicable law, common legitimate business use cases may include:

• market intelligence and pricing research;
• brand protection and anti-counterfeit monitoring;
• ad verification and campaign quality assurance;
• SEO, SERP, and search visibility monitoring where lawful;
• cybersecurity research on systems the customer owns or is authorized to test;
• public web data collection for lawful and legitimate business purposes;
• availability, localization, and content quality testing;
• other approved business workflows reviewed by Infatica where required.

Permitted use does not mean guaranteed technical access to any website, platform, domain, geography, IP pool, or third-party service. Infatica may deny, restrict, or revoke access at any time where required for compliance, safety, legal, technical, platform, network-integrity, or reputational reasons.

4. When review may be required

5. 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;
• 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;
• 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.

6. Blocked and restricted targets

For safety and compliance purposes, certain websites, domains, categories, or services may be inaccessible by default or require manual approval.

Blocked targets

• banks and financial account access portals
• payment systems, fintech platforms, payment circumvention services, and wallet services
• government websites, public-sector resources, tax portals, voting systems, and similar civic infrastructure
• educational institution portals and student account systems
• .gov, .mil, .edu, or similar restricted categories where proxy use may create legal or compliance risk
• targets associated with child-safety-sensitive, age-restricted, platform-safety-sensitive, fraudulent, abusive, or unlawful activity
• any website or service where access through the Services may violate applicable law, third-party rights, or platform restrictions

Restricted targets

• 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

7. Customer obligations

Customers must:

• provide accurate, complete, and current information requested for use-case review, end-client review, restricted-target 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.

8. Review process and outcomes

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, end client, geography, traffic pattern, or future request.

9. 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.

10. Relationship with other Trust Center documents

This policy should be read together with Infatica’s Acceptable Use Policy, Privacy Policy, Data Protection Addendum, and any applicable customer, reseller, partner, or services agreement. The Acceptable Use Policy contains additional prohibited-use, abuse-prevention, and access-restriction rules. The Privacy Policy explains how Infatica processes compliance, security, and rights-request data.

11. 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.