Support compliance decisions
Understanding a customer and intended use helps determine whether a request aligns with policy, applicable obligations and platform risk standards.
KYC & Responsible Use
Proportionate identity checks for a stronger foundation of trust
Know Your Customer (KYC) is one of PuraRoute's risk-control tools. When account, transaction, use-case or regulatory signals call for it, we may ask for identity, organization or business-purpose information to help identify abuse and make a proportionate risk decision.
Whether KYC is triggered—and the scope of information requested—depends on risk and compliance needs. This page does not mean every customer follows the same process.
PuraRoute Trust Layer
KYC · Risk review
Triggered
Initiated by risk signals, product context or compliance requirements
Proportionate
Information requested is matched to the identified risk and review purpose
Context-aware
Human review may consider context instead of relying on a single signal
Ongoing
Approval does not prevent later action on unusual or prohibited activity
Why KYC matters
KYC creates a more trusted basis for working together
Reasonable customer due diligence helps a platform understand risk, protect legitimate users and remain cautious about high-risk uses or requests without a credible explanation.
Reduce abuse risk
Identity, organization and use-case signals can help uncover fraud, unauthorized access and other activity that may harm the network.
Protect trusted customers
Clearer risk boundaries help maintain network quality so legitimate teams can use proxy resources in a more controlled environment.
A possible review path
Risk-based, not a one-size-fits-all workflow
These stages describe measures we may use. Whether a review is needed, its sequence and the material requested depend on the actual risk of the account and use case.
01
Identify risk signals
Consider account, transaction, product, use-case and security signals to decide whether more context is needed.
02
Request relevant information
We may request contact, identity, organization, business-site or intended-use information related to the review purpose.
03
Check and assess
Review consistency, plausibility and risk context, and ask for clarification or further material where appropriate.
04
Take proportionate action
Based on the result, provide service normally, apply limits, continue monitoring or decline a request that does not meet requirements.
What we may review
The information scope should match the risk purpose
Not every category is requested in every review. Scope depends on the customer type, risk level and reasonable compliance need.
Individual or contact details
Information used to identify a person connected with the account or an authorized contact, plus necessary communication details.
Organization and business context
Company identity, registration or operating context, business website, and a reasonable basis for the contact to act for the organization.
Intended use case
Target types, data sources, access purpose and risk controls that help establish whether a use is reasonable and lawful.
Additional risk context
Where information conflicts, risk is elevated or behavior is unusual, we may ask for clarification and reassess.
Information protection
Review information deserves careful handling
Identity and business materials may contain sensitive information. We process relevant data for defined service, security and compliance purposes and use technical and organizational measures to reduce unnecessary access.
- Request information relevant to the current risk and compliance purpose
- Limit internal access to review materials and protect account sessions
- Manage retention according to applicable requirements and business need
- Treat KYC as one risk input—not a certification of future behavior
A trusted network
Make compliance awareness a shared foundation
Before using the service, ensure your business objective, data sources and access methods are lawful and appropriately authorized.