Customer verification policy
This Customer Verification Policy explains how WebGears Services d.o.o. (the “Company“), operating the CyberYozh Data platform, checks who its paying Clients are before and while it provides paid Services. It is binding on Clients to whom it applies and it reflects how we actually run the platform, not an aspiration on a page. Verification exists to protect the real people whose IP addresses power our residential Proxy Network and to keep the platform trustworthy for everyone using it.
1. Why We Verify
1.1 Our residential proxy IPs are ethically sourced from real, consenting participants. Their consent is only meaningful if we know who routes traffic through them and for what purpose. Verification is how we honour that consent and enforce our published standards for ethical data collection and a transparent proxy network.
1.2 Verification is risk management and consent protection, not an accusation. A verification request is not a statement that we suspect you of wrongdoing. We aim to keep the process proportionate: as light as possible for low-risk use, and more thorough only where the risk to real people is higher.
1.3 We add this step deliberately, and we accept that it creates some friction. Some applications are declined. We consider that a fair cost of running the platform the way we say we do.
2. Who This Policy Applies To
2.1 This Policy applies to every Client who pays the Company for Services (the “Client,” “you”), whether you are a new applicant or an existing account holder. There are no blanket exceptions.
2.2 The open-source yozh-scraper engine and the Yozh Crawler are free to download, self-host and run with no verification of any kind. This Policy does not attach to using the free tools on your own infrastructure.
2.3 Verification attaches when you buy proxy traffic (especially residential proxies) or managed scraping from us. Residential-network access is the highest tier of review, for the reasons in section 1.
3. When Verification Is Triggered
3.1 We take a risk-based, tiered approach. Verification may be required before we activate a paid Service, and again at any point while you hold an account. High-risk use-cases and conditional Target Sites are governed in detail by our Restricted Targets Policy, which is where the use-case review concept is defined.
- Lower-risk products may require little or no additional checking beyond normal account and payment details.
- Residential proxy access and sensitive use-cases receive the deepest review, because those requests can affect real people or third parties directly.
3.2 We may request further information whenever a factor changes that we reasonably consider relevant to risk (see section 8).
4. Information We May Require
4.1 Depending on the product and risk level, we may ask you to provide some or all of the following:
- Identity details, and for higher-risk cases a government-issued photo ID such as a passport or driver’s licence;
- Business details, such as a certificate of incorporation or business registration, tax identification and proof of address;
- A description of your intended use-case — what you plan to collect, from where, and why;
- Beneficial-ownership or control details, where applicable;
- Verification that you control the contact email address or domain you sign up with.
4.2 You must give information that is accurate, complete, current and not misleading, and keep it up to date. Providing false or misleading information is grounds for refusal or termination.
5. How Verification Works
5.1 Verification runs in stages: an onboarding intake where you provide details; a risk evaluation that combines automated checks with review by a person on our compliance team; and ongoing monitoring after you are approved.
5.2 A member of our team reviews the account, the Client and the declared use-case. It is not a purely automated gate.
5.3 For the highest-risk approvals, including some residential-access requests, we may ask for enhanced verification — for example a live video or liveness check, a government ID, or a short call to review your use-case. We use these only where they are proportionate to the risk.
5.4 Where verification status is shown or actioned, you will find it in your dashboard at app.cyberyozh.com.
6. Approved-Use Scope
6.1 Access is granted only for the use-case we reviewed and approved. Requests or activity that fall outside that approved scope may be blocked or denied. Permitted uses are enumerated in our Use Policy, and conditional Target Sites are gated under our Restricted Targets Policy.
6.2 If you want to use our Services for a materially new or different purpose, tell us first. A new use-case may require further review before we allow it.
7. Sanctions and Legal Screening
7.1 As a Serbian entity serving global traffic, we screen Clients against applicable sanctions lists (including OFAC, EU and UN measures) and, where relevant, for adverse media or politically exposed status. We do not onboard Clients located in, or clearly serving, comprehensively embargoed jurisdictions, and we do not knowingly route proxy traffic to sanctioned destinations.
8. Ongoing Monitoring and Re-verification
8.1 Verification is not only a sign-up gate. We may re-verify existing Clients periodically and monitor for activity that diverges from your declared purpose. This supports our fast abuse response standard.
8.2 We may re-verify or request clarification when we become aware of:
- a change of beneficial ownership or control of your account;
- a change of payment method or billing details;
- suspicious or anomalous activity;
- a materially new or different use-case; or
- any other factor we reasonably consider relevant to risk.
8.3 The Company also applies customer-vetting standards at the network level; those are described in our Network Sourcing Standards, which defer to this Customer Verification Policy for the authoritative KYC steps.
9. Prohibited Uses
9.1 Verification enforces the acceptable-use rules in our Use Policy. Prohibited categories — including fraud, unauthorised access or hacking, spam, abuse of intellectual property or personal data, and malicious automation — are enumerated there and are not restated here. Where a use-case falls into those categories, we will decline it.
10. Refusal, Suspension and Offboarding
10.1 We may, at our reasonable discretion, refuse, restrict, suspend or terminate access where verification is not satisfactorily completed or where risk warrants it. A share of applications is declined for this reason.
10.2 If you do not complete verification or provide requested clarifications, we may decline or suspend access. Refunds in that situation are handled under our Payment and Refund policy, and are given only where required.
11. Verification Providers and Your Data
11.1 We may use a reputable third-party identity-verification or screening provider, acting as a sub-processor of the data you submit through it, consistent with our Data Handling Policy. Verification data is used only for verification, fraud prevention and legal compliance, as described in our Privacy Policy.
11.2 We retain verification records for as long as your account is active and for a reasonable period afterwards to meet our legal obligations and to enable future review. Our Privacy Policy sets out the detail, and our Cookie Policy covers cookies used on our sites. Our practices are designed to align with GDPR, CCPA and ISO 27001.
12. Raising Concerns and Contact
12.1 To report abuse or misuse of the platform, email abuse@cyberyozh.com. We acknowledge abuse reports within one business day.
12.2 For questions about verification or your account, contact support@cyberyozh.com or help@cyberyozh.com, or reach us on Telegram at @CyberYozh_support_bot.
13. Related policies
This Policy works together with the other documents in our Legal Center: