YINNET Terms of Service

Last Updated: 22 October 2026

Effective Date: 22 October 2026

Time Standard: Singapore Time (SGT, UTC+8)

Please read these Terms of Service, together with the specifications, prices, and applicable policies for your selected product, before registering, purchasing, or renewing a service.

1. Services and Scope

1.1 Service Provider

The platform provides and operates cloud servers, networking, IP resources, and related infrastructure services under the name YINNET.

In these Terms, “YINNET,” “we,” “us,” and “our” refer to the provider of YINNET services. “User,” “you,” and “your” refer to the individual or organisation registering for, purchasing, or using our services.

1.2 Scope of Services

Service specifications, prices, billing cycles, resource limits, and additional features are governed by the product description and order details applicable at the time of purchase.

Unless expressly included in the product description or a written agreement between the parties, services do not include system administration, application maintenance, data backups, or data recovery. You are responsible for managing your operating system, applications, security settings, access permissions, and data stored within the service.

1.3 Agreement Documents

These Terms, your order details, and the product policies clearly provided to you and accepted before purchase collectively form the service agreement.

If these documents conflict, the following order of precedence applies:

1. A separate written agreement signed by both parties.

2. Special conditions expressly agreed in the order.

3. Policies specific to the applicable product.

4. These Terms of Service.

None of these documents excludes rights or responsibilities that cannot be excluded under applicable law.

1.4 Contact Information

For service, billing, refund, or complaint matters, please submit a support ticket through the client area.

If you cannot access your account, contact [email protected]. To protect account security, we may request information necessary to verify account ownership.

The scope of support, support hours, and supported languages are as published on our website.

2. Lawful Use and Prohibited Activities

2.1 Lawful Use

You must comply with the laws binding on the relevant transaction and use of the service, including applicable laws where the server is located and where you are located.

You are responsible for obtaining the permissions, authorisations, and third-party consents required for your business, content, and data-processing activities.

2.2 Prohibited Activities

You must not use YINNET services to conduct, assist, or facilitate:

• Network attacks, DDoS attacks, unauthorised access, brute-force attacks, or other unauthorised attacks.

• Unauthorised port scanning, security testing, exploitation of vulnerabilities, or system probing.

• Spam, phishing messages, malicious bulk messaging, or unauthorised mass communications.

• Distribution of viruses, trojans, ransomware, or other malware, or operation of botnets.

• Piracy, counterfeiting, or infringement of copyright, trademarks, or other third-party rights.

• Publication, storage, or distribution of pornographic content, or any content involving the sexual exploitation or abuse of children or adolescents.

• Gambling, fraud, money laundering, unlawful payment activities, fraudulent investment schemes, or other financial fraud.

• Spoofing network sources, circumventing resource limits, or materially interfering with the platform, upstream providers, or other users.

• Deployment, forwarding, proxying, storage, or other material assistance for the activities listed above.

2.3 Investigations

YINNET may investigate suspected violations using technical records, specific complaints, upstream provider notices, and legal requirements.

A single complaint or risk flag does not automatically establish a violation. Where there is an ongoing attack, a serious security risk, or a legal requirement to act immediately, we may first take necessary protective measures and then provide notification and review under Section 8.

3. Account Information, Registration, and Payment Security

3.1 Accurate Information Requirements

When registering an account, placing an order, purchasing, paying, or renewing, you must provide truthful, accurate, complete, valid, and current information as required by the relevant forms.

This includes your real name, country or region, contact address, email address, and any telephone, billing, or payment information required by the forms.

When purchasing on behalf of a company or another organisation, you must provide its genuine name and necessary details and ensure that the person acting on its behalf is duly authorised.

You must not register or purchase using fictitious identities, randomly entered information, false addresses, another person’s information without authorisation, or unauthorised payment methods.

3.2 Maintaining Information and Contact Details

You must ensure that your registered email address and other contact methods remain functional and can receive invoices, service notices, security verification requests, and support responses.

Update your information promptly in the client area when it changes. If outdated or incorrect information prevents delivery of notices or affects orders, invoices, or identity verification, you must cooperate in correcting and resolving the issue.

3.3 Verification and Irregularities

For service delivery, payment security, fraud prevention, or legal compliance, YINNET may request additional information directly relevant and necessary to the matter concerned.

We will explain the purpose of verification, the information required, and how to submit it. Requests will be limited to what is reasonably necessary.

If information is clearly false, materially inconsistent, or you refuse reasonable and necessary verification, we may delay activation, reject the relevant order, or restrict, suspend, or terminate affected services under Section 8.

For ordinary errors that can be corrected, we will generally first ask you to correct them. Information issues do not automatically result in forfeiture of payments; funds will be handled under Section 7 and applicable law.

A shared IP address, email address type, or single risk flag will not be the sole basis for determining fraud or permanently banning an account.

3.4 Account Protection

You must safeguard passwords, multi-factor authentication details, API keys, and other access credentials, and manage the persons authorised to use your account.

Notify YINNET immediately if you discover unauthorised access, unusual payments, or exposed credentials, and take necessary steps such as changing passwords and revoking keys.

Responsibility will be determined according to the cause of the incident, each party’s conduct, and applicable law.

3.5 Prices, Payments, and Renewals

Product prices, billing currency, billing cycles, applicable taxes, and renewal prices are governed by the order details and applicable arrangements disclosed at purchase. Subsequent price changes are governed by Section 14.

Where automatic renewal or automatic charging is supported, it will be performed only after the relevant authorisation has been obtained. Applicable cancellation methods and charging arrangements will be provided.

You must complete renewal payments before expiry. Creation of an invoice or delivery of a renewal reminder does not mean that payment has been completed.

3.6 USDT Payment Verification

When paying with USDT, check the amount, blockchain network, recipient address, and payment expiry shown on the payment page.

If the amount is incorrect, the wrong network is used, payment is late, or funds are not credited automatically, provide the order and transaction records for investigation. Whether funds can be confirmed, recovered, or credited depends on the actual transaction circumstances.

Refunds and account-balance restrictions for USDT payments are governed by Section 7.

4. Service Activation and Delivery

4.1 Activation Arrangements

Activation may require payment confirmation, resource allocation, and necessary information or security verification. Estimated delivery times are governed by the product description or order agreement.

If we expect that delivery cannot be completed within the agreed time, we will explain the reason and subsequent arrangements.

4.2 Determining Activation Time

A service is activated when the agreed resources and necessary access details have been delivered and the service is capable of being used as agreed.

Payment completion, invoice creation, or order confirmation alone does not constitute activation.

Where delivery is delayed for reasons attributable to YINNET, the undelivered period must not be counted as part of the actual service period.

4.3 Failure to Deliver

If YINNET cannot deliver the agreed service for reasons attributable to us, or fails to complete delivery by the agreed final deadline, you may cancel the undelivered portion and request a return of funds under Section 7.7.

USDT-funded payments are handled under Sections 7.2 and 7.7, including their exceptions where applicable law requires another method of return.

Substitution of a product or postponement of delivery requires your agreement.

4.4 Non-Conforming Delivery

If the delivered service does not meet specifications expressly agreed in the order, please provide relevant information through a support ticket.

We will investigate and correct or replace the affected service. If this cannot be completed within the period required by law or a reasonable period agreed between the parties, funds for the affected, unperformed portion will be handled under Section 7.7, without affecting your other statutory rights.

5. Resource Use and Fair Use Policy

5.1 Product Limits

Available CPU, memory, storage, bandwidth, traffic, and other resources are governed by the product specifications and fair use policies disclosed at purchase.

If a product restricts sustained high-load usage, the relevant metrics, assessment period, limits, and possible measures must be explained before purchase.

5.2 Shared Resources

A shared-resource product does not provide exclusive use of the physical host, storage equipment, or network uplink.

An advertised port speed does not guarantee identical sustained throughput to every region, network operator, or destination.

5.3 Resource Abuse

You must not use services for mining without permission, malicious computation, unauthorised large-scale scanning, or workloads expressly prohibited by the product policy.

Where usage exceeds published limits, or specific evidence shows material harm to the platform or other users, YINNET may throttle resources, restrict features, or suspend the affected service.

We will normally notify you and provide a reasonable opportunity to adjust your usage. Emergencies are handled under Section 8.

5.4 Normal Use

Usage that complies with published product specifications and limits will not be retrospectively classified as abuse solely because resource utilisation is high or platform costs have increased.

6. Traffic, Traffic Packages, and Billing

6.1 Traffic Measurement

Traffic measurement directions, units, plan allowances, and reset cycles are governed by the product description.

For products using bidirectional measurement, both inbound and outbound traffic count towards the allowance. Whether backup, internal, or mitigation traffic is counted depends on the published measurement rules for the product.

Unless expressly stated otherwise for a product, traffic cycles and reset times are calculated using Singapore Time.

6.2 Exceeding the Allowance

When traffic exceeds the plan allowance, the service may be throttled or suspended, or you may purchase additional traffic, according to the rules disclosed before purchase.

Any additional charges must have their prices, calculation methods, and triggering conditions disclosed in advance, with necessary authorisation obtained. We will not arbitrarily introduce charges that were not agreed.

6.3 Traffic Package Activation and Refunds

A traffic package becomes effective once payment is completed and the package is successfully allocated to the designated service.

Once effective, a traffic package is not eligible for a standard refund, whether to the original payment method, to your account balance, or as cash, regardless of whether any of its allowance has been used.

Failure to allocate a package, duplicate or incorrect charges, and circumstances where applicable law requires a return of funds are handled under Section 7.7.

Where a USDT-funded traffic package qualifies for one of these exceptions, Sections 7.2 and 7.7 continue to apply.

6.4 Traffic Package Validity and Reset

A traffic package follows the existing traffic cycle of the server to which it is assigned and expires at that server’s next originally scheduled traffic reset.

Any unused package allowance is cleared at that reset. It is not retained, accumulated, or carried forward to the next traffic cycle.

Purchasing a traffic package does not change the server’s existing traffic reset date or create a separate one-month validity period starting from the purchase date.

A one-time traffic package is not automatically reissued in the following cycle. Before purchasing, check the server’s traffic reset time and the remaining duration of the current cycle.

6.5 Measurement Disputes

YINNET’s system records may be used as the basis for traffic measurement and billing.

If you dispute the figures, you may provide the relevant time range, monitoring data, or records and request an investigation. Confirmed measurement or billing errors will be corrected.

7. Cancellation and Refund Policy

7.1 Standard Refund Conditions

In these Terms, a “standard refund” means the voluntary refund arrangement provided by YINNET in addition to rights granted by applicable law.

The standard refund deadline, traffic limit, processing fee, and monthly limit do not apply to the exceptional returns of funds listed in Section 7.7. They do not restrict cancellation, refund, or other remedies that cannot lawfully be excluded.

You may submit a standard refund request within 24 hours of initial service activation, provided all of the following conditions are met:

• No more than 24 hours have elapsed since initial activation when the request is submitted.

• Traffic usage at the time of submission does not exceed 10% of the plan’s base traffic allowance for the current cycle.

• The product is eligible for standard refunds and none of the exclusions in Section 7.3 applies.

• There is no verified serious violation, fraud, or refund abuse related to the relevant service or transaction.

• A standard refund allowance remains available for the month to which the request belongs, calculated under Section 7.4.

The 10% threshold is calculated using the plan’s base traffic allowance for the current cycle, excluding separately purchased traffic packages. Buying a traffic package does not increase the traffic usage threshold for standard refunds.

Whether a request is on time is determined by the submission time specified in Section 7.6, not by when the review is completed.

Funds are returned according to their original payment source and the applicable provisions of this section.

7.2 USDT Payments: Refunds to Account Balance Only

For orders funded with USDT, any approved refundable amount will be credited only to your own YINNET account balance. Refunds will not be sent back as USDT, transferred to external wallets, or made available for withdrawal.

This applies to:

• Orders paid directly with USDT.

• Portions of orders paid using an account balance topped up with USDT.

• Portions of subsequent orders paid using account credit refunded from those sources.

USDT top-up balances and account credit refunded from such orders may be used only to purchase or renew YINNET services. They cannot be exchanged for cash, USDT, or other digital assets, or withdrawn through bank transfer or another payment method.

Crediting a refund to your account balance does not make that balance withdrawable or eligible for a further refund outside YINNET.

The refundable amount is calculated from the original order and actual credited payment records, less any applicable fees expressly provided for in these Terms.

Where an order uses multiple payment sources, each portion is handled according to its verifiable original source. The return method for the USDT-funded portion does not change because it is combined with another payment method, converted into account credit, or used to buy another service.

Where applicable law requires funds to be returned by another method, that legal requirement applies.

7.3 Exclusions from Standard Refunds

Standard refunds are not available in the following circumstances:

• More than 24 hours have elapsed since initial activation when the request is submitted.

• Traffic usage at the time of submission exceeds the 10% threshold in Section 7.1.

• The renewal period to which the refund request relates has already begun.

• Custom resources or special configurations have been delivered, or the product was expressly identified before purchase as ineligible for standard refunds.

• A traffic package has become effective, whether or not its allowance has been used.

• The assigned IP address is blocked or restricted by the Great Firewall of mainland China as a result of your use, and the conditions in Section 11.4 are met.

• A request is submitted more than 24 hours after initial activation solely because of Google’s or another third-party platform’s regional classification, IP geolocation, or changes to those determinations—including Google identifying a connection as originating from mainland China—or resulting content or feature restrictions, and the conditions in Section 11.7 are met.

• An additional service has been used, or has incurred costs that cannot reasonably be recovered, and the relevant restrictions were disclosed before purchase.

• A promotional product was expressly identified before purchase as ineligible for standard refunds.

• There is a verified serious violation, fraud, or refund abuse related to the transaction.

• The standard refund limit for the month to which the request belongs has been reached.

A regional classification or IP geolocation issue involving Google or another third-party platform does not, by itself, exclude a standard refund request submitted within 24 hours of initial activation. Requests meeting Section 7.1 and the other applicable conditions remain eligible.

A complaint, risk flag, or incomplete information verification alone does not automatically justify refusing a refund.

This section does not affect rights to a return of funds under Section 7.7 or applicable law.

7.4 Processing Fee and Monthly Refund Limit

For eligible standard refunds, a processing fee equal to 10% of the amount actually paid for the refundable service applies only where disclosed before purchase and permitted by applicable law. The remaining amount is returned using the applicable method.

The same standard refund processing fee applies when a USDT-funded payment is refunded to your account balance. This is a standard refund processing fee and does not represent a claim that a payment provider necessarily charges the same percentage.

Each user may receive a maximum of 3 standard refunds per calendar month. Refunds to an account balance also count towards this limit.

The following counting rules apply:

• A calendar month runs from 00:00 on the first day of the month until immediately before 00:00 on the first day of the following month, using Singapore Time.

• Only approved standard refunds count. Each is assigned to the month in which the refund request was submitted.

• Review or crediting in a later month does not change the month to which the refund belongs.

• Refunds are counted per independent service, such as each VPS or dedicated server. An approved standard refund for each service counts as one refund.

• If one order, invoice, or ticket covers refunds for multiple services, each service receiving an approved refund is counted separately.

• A single refund for the same service is not counted more than once because mixed payment sources or instalments require separate processing.

• Eligible requests receive the available monthly allowance in submission order.

• Rejected requests and requests withdrawn before approval do not count.

• Unused monthly allowances do not carry forward.

Where multiple accounts belong to the same actual user, refund counts are combined. You must not circumvent the limit through additional registrations, impersonation, or other methods.

Once the monthly limit is reached, further standard refund requests assigned to that month will not be approved. A new month’s allowance does not extend an existing service’s 24-hour refund request deadline.

Exceptional returns of funds under Section 7.7 are not charged this standard refund processing fee and do not count towards the monthly limit of 3.

7.5 Service Cancellation and Refund Requests

Cancelling, shutting down, deleting, releasing, reinstalling, or ceasing to use a service does not constitute a refund request.

To request a refund, submit a separate request under Section 7.6.

Cancellation takes effect according to the arrangement displayed when cancelling or the time confirmed between the parties. Immediate cancellation may stop the service and result in data deletion, but does not automatically extinguish refund rights already established under these Terms or applicable law.

7.6 Submission and Processing

Submit refund requests through a support ticket, including the order number, payment details, and reason for the request. If you cannot access your account, you may apply using the email address in Section 1.4 and cooperate with necessary account verification.

The submission time is the time of the first ticket submission that clearly requests a refund and enables the relevant service to be identified. For requests made by the email method described above, the submission time is when YINNET first receives that email.

Subsequent submission of verification information or processing does not, by itself, change the original submission time. You must still cooperate with reasonable and necessary verification.

After receiving all necessary information, we will complete the review within a reasonable time and notify you of the result and expected processing time. If additional information or more time is needed, we will explain the reason and next steps.

Refund methods are as follows:

• USDT payments: Credited only to your own YINNET account balance under Section 7.2.

• Other payment methods: Normally returned to the original payment method. If this is not possible, a lawful and feasible alternative will be agreed with you.

• Payments from an account balance: Returned to the original account balance, retaining the funds’ original usage and withdrawal restrictions.

Mixed payments are handled according to each portion’s verifiable original source.

Paying through an account balance does not make otherwise non-withdrawable top-ups, refund credits, or commissions already converted to account credit eligible for an external refund.

The time taken for refunds processed through payment providers to reach you may depend on those providers’ procedures. Where applicable law requires another refund method or processing deadline, that requirement applies.

7.7 Exceptional Returns of Funds

The following circumstances are not subject to the standard refund policy’s 24-hour deadline, 10% traffic limit, 10% processing fee, or monthly limit of 3 refunds:

• Failure attributable to YINNET to deliver a paid service or additional resource.

• Non-conforming delivery that is not corrected under Section 4.4.

• Duplicate charges, incorrect charges, or other confirmed billing errors.

• Returns due under Section 14.3 following a material adverse change to a prepaid service.

• Other circumstances where applicable law requires a return of funds.

The amount returned is calculated according to the unperformed portion, actual overcharge, or applicable legal requirements.

USDT-funded payments normally remain subject to return as YINNET account credit under Section 7.2. If applicable law requires another method, that requirement applies.

7.8 Payment Disputes

These Terms do not restrict your right to raise a payment dispute under applicable law or payment provider rules.

If a support-ticket refund and a payment dispute are being processed at the same time, both parties should cooperate in checking their progress to avoid duplicate returns.

You must not use falsified information, or conceal that funds have already been refunded or credited to your account, to obtain a duplicate return of the same payment.

8. Service Suspension, Termination, and Data Deletion

8.1 Ordinary Procedures

For correctable information issues, breaches of product limits, or other ordinary breaches, YINNET will generally notify you of the affected service, the reason, and the action needed to resolve the issue.

A reasonable correction period will be set according to the nature and impact of the issue and the work required. Measures should be proportionate to the actual risk and minimise disruption to unaffected services where possible.

Non-renewal at expiry is handled under Section 8.4.

8.2 Emergency Measures

Where there is an ongoing attack, fraud, a serious security risk, or a legal requirement to act immediately, YINNET may first take necessary restriction, isolation, or suspension measures.

Where lawful and practicable, we will explain the reason and subsequent arrangements.

8.3 Scope and Review

Measures will generally be limited to affected services. They will be extended to other services or the entire account only where specific evidence shows that the risk extends further.

You may request a manual review through a support ticket. We will respond within a reasonable time or explain the investigation’s progress and any further information needed.

8.4 Expiry, Data Retention, and Deletion

If a service expires without renewal, YINNET may suspend or terminate it under the product rules applicable at purchase.

Each product’s suspension timing after expiry, data retention period, and deletion arrangements must be disclosed before purchase through the product description, checkout page, or a clearly linked service policy, and implemented accordingly.

Subsequent expiry or deletion notices must not retrospectively shorten an already promised retention period.

Suspension does not necessarily mean immediate data deletion. However, any retention period after suspension must not be treated as a backup service.

Renew the service or export the data you need before expiry. You should not rely on continued access after expiry. Recovery cannot be guaranteed once data has been deleted according to the applicable arrangements.

8.5 Data Retrieval and Exceptions

Except where you expressly request deletion, the law requires it, or a serious security incident or comparable circumstance prevents it, YINNET will reasonably assist you in exporting data during the applicable retention period where lawful, safe, and technically feasible.

Specific arrangements follow the product rules or a method confirmed between the parties. Recovery cannot be guaranteed if data has already been deleted or the storage medium is unreadable.

8.6 Fees Following Suspension or Termination

Fees following suspension or termination are determined according to actual performance, Section 7, and applicable law.

Termination does not automatically extinguish an established right to a return of funds.

9. Risk Reviews and Personal Data

9.1 Risk Reviews

To deliver services, protect account and payment security, prevent fraud, resolve disputes, and comply with the law, YINNET may process necessary registration details, login records, IP addresses, device information, orders, payments, and referral records.

Processing must comply with applicable law and the privacy information provided when the data is collected.

9.2 Assessment and Explanation

Risk assessments should consider multiple relevant factors. A shared IP address alone will not establish that different accounts belong to the same user or are involved in a violation.

To protect security and third-party privacy, we are not required to disclose complete risk-detection algorithms or other persons’ information. Where safe and legally permitted, we will explain the type of issue, required verification, and review process.

9.3 Data Protection

YINNET will use reasonable technical and organisational measures to protect the personal data it processes.

You may request access, correction, deletion, or exercise other data rights under applicable law by contacting us through the methods in Section 1.4.

These Terms do not replace a separate privacy policy or data-processing agreement required by law.

9.4 Your Processing of Third-Party Data

If you use the services to collect, store, or process another person’s personal data, you must ensure a lawful basis for that processing and fulfil applicable notification, security, and other obligations.

Where applicable law requires a separate data-processing agreement, it must be completed before the relevant processing begins.

10. Data Security, Backups, and Incident Assistance

10.1 Your Backup Responsibilities

Unless the product description or a written agreement expressly includes the relevant services, you are responsible for backing up and preserving your data and for system configuration, application security, and account security.

Create backups independent of the original service at intervals appropriate to the importance of the data, and verify that they can be read and restored.

Important data should not be stored only on a single server, disk, or storage environment.

Before reinstalling, deleting, releasing, cancelling, or performing other operations that may affect data, complete any necessary exports and backups.

10.2 Scope of Backup Services

Where a purchased product expressly includes backups, their frequency, retention period, coverage, and restoration method are governed by the agreement at purchase.

RAID, mirroring, snapshots, or internal redundancy do not automatically mean that YINNET has promised an independent backup service or backups available for user-initiated restoration.

Internal backups created for operational purposes do not mean that all data or every point in time can be restored.

These explanations do not affect YINNET’s obligations to provide any expressly promised backup service.

10.3 Hardware Failures and Data Loss

Servers, disks, storage equipment, and other hardware may fail, causing data corruption, loss, or unavailability.

Where YINNET has fulfilled its reasonable maintenance, security, and agreed backup obligations, and a hardware failure could not reasonably have been avoided and was not caused by YINNET’s negligence or breach, YINNET will not be liable for resulting data-loss compensation to the extent permitted by applicable law. We will nevertheless provide reasonable assistance under Section 10.5.

Responsibility for data loss is determined by the cause, the parties’ agreement, and applicable law. Describing an event as a “hardware failure” does not, by itself, establish an exemption from liability.

10.4 Force Majeure

If a natural disaster, war, or another event beyond reasonable control that legally qualifies as force majeure causes a service interruption, equipment damage, or data loss, YINNET may be relieved of corresponding liability according to the event’s actual effects and to the extent permitted by applicable law.

Whether an event qualifies, and the extent of any relief, depend on its cause, foreseeability, avoidability, and applicable law. Hardware failures or upstream service disruptions do not automatically constitute force majeure.

Where practicable, YINNET will notify affected users and take reasonable measures to mitigate loss and restore services.

10.5 Troubleshooting and Recovery Assistance

When data is corrupted, lost, or inaccessible, YINNET will make reasonable efforts to assist where lawful, safe, and technically feasible, including:

• Investigating affected hardware and storage environments.

• Checking for available data copies or applicable backups.

• Coordinating with the data centre, hardware suppliers, or upstream providers.

• Attempting data recovery, service repair, or redeployment where feasible.

This assistance does not guarantee complete recovery, a particular success rate, or completion within a specified time.

If specialist third-party recovery outside the purchased service is needed, its scope and additional charges must be explained and agreed with you in advance. Costs that YINNET must bear by law or contract will not be transferred to you through this provision.

10.6 Responsibility and Other Rights

This section does not exempt YINNET from liability imposed by law for its own intentional acts, negligence, failure to fulfil promised backup obligations, or other breach. Such liability is governed by Section 12 and applicable law.

Determining responsibility for data loss does not affect other rights under an applicable SLA, return-of-funds provision, or the law.

11. Network, IP Blocking, Regional Classification, and Service Availability

11.1 Network Scope

Unless expressly promised for a product, YINNET does not guarantee:

• Continuous connectivity from every country, region, and network operator.

• Permanently unchanged routing, latency, packet loss, or transfer speeds.

• Continuous availability of a particular website, game, application, social platform, or streaming service.

• Permanently unchanged IP geolocation, classification, reputation, or third-party database labels.

These explanations do not affect expressly promised delivery specifications or service obligations, and do not, by themselves, exclude refund requests that qualify under Section 7.

11.2 International Connectivity

International connection quality may be affected by your location, local network operator, international gateways, cross-border routing, and destination network.

Unless expressly promised for a product, we do not guarantee a particular latency, transfer speed, or connectivity outcome from mainland China.

11.3 IP Attributes and Delivery

Where a product specifies an IP region or particular attributes, compliance is assessed using the verification method and delivery standard disclosed before purchase.

Non-conformity at delivery is handled under Section 4.4. Later changes to third-party databases, platform policies, or the network environment are handled within the scope of any product guarantees expressly provided.

11.4 IP Blocking Resulting from Your Use

If, after delivery, a reasonable investigation supported by specific technical records or other reliable information establishes that the assigned IP address has been blocked or restricted by the Great Firewall of mainland China (GFW) as a result of your deployed applications, published content, traffic activity, or other use of the service, the affected service is not eligible for a standard refund, including a refund to your account balance.

This exclusion applies even if the request is submitted within 24 hours of initial activation or traffic usage remains below the limit specified in Section 7.1.

A single failed ping, inability to connect from an individual network, or one test result will not, by itself, establish GFW blocking or that the blocking was caused by your use.

You may request investigation and review through a support ticket. Whether an IP replacement is available, and the applicable conditions, depend on the product policy or an arrangement confirmed between the parties through the ticket. YINNET does not guarantee that a block can be removed or that a replacement IP address will not subsequently be blocked.

This provision does not exclude refund rights arising from a failure to meet expressly promised product specifications at delivery, YINNET’s failure to perform its agreed obligations where a return of funds is due, or other rights that cannot lawfully be excluded. Such circumstances are governed by Sections 4.4 and 7.7 and applicable law.

11.5 Maintenance Notices

For maintenance that can be planned in advance, YINNET will provide affected users with reasonable advance notice of the expected timing and scope of impact.

Emergency security work or incident repairs may be performed first, with notices and progress updates provided when practicable.

11.6 Service Level Agreements

Where a product expressly includes a Service Level Agreement (SLA), its availability calculation, exclusions, claim deadlines, and compensation arrangements apply.

A service status page, monitoring data, or historical availability record does not, by itself, create an additional availability or compensation commitment.

11.7 Third-Party Regional Classification and IP Geolocation

Google and other third-party platforms independently determine the geographic location associated with IP addresses and users through their own databases, location-detection mechanisms, and other information. YINNET cannot directly modify or control these determinations.

Unless expressly promised in the product description, order, or a written agreement between the parties, YINNET does not guarantee that a third-party platform will associate an assigned IP address or a connection using that IP address with any particular country or region, or that its classification will remain unchanged.

This includes Google identifying a connection as originating from mainland China, sometimes referred to in Chinese as “Google 送中,” or from another country or region that differs from the server’s actual location. Such a classification does not, by itself, indicate a change in the server’s physical location or network routing, and is not equivalent to GFW blocking under Section 11.4.

If you suspect an error in Google’s IP geolocation, you may submit a support ticket containing the relevant IP address and details of the issue. YINNET will assist in submitting an IP geolocation correction request to Google. Whether Google accepts the request, changes the location, how long it takes, and whether any correction remains effective are determined by Google. YINNET does not guarantee any of these outcomes.

Within 24 hours of initial service activation, you may still request a standard refund for the circumstances described above. YINNET will process requests that meet the other standard refund conditions in Section 7 in accordance with that section.

The applicable traffic usage limit, monthly refund limit, processing fee, and refund method remain governed by Section 7. Eligible refunds for USDT-funded payments will be credited only to your own YINNET account balance, subject to the statutory exceptions described in Section 7.2.

Compliance with the 24-hour deadline is determined by the submission time specified in Section 7.6. Subsequent investigation or processing by YINNET or Google does not affect a refund request submitted on time. Merely submitting a geolocation correction request or waiting for its outcome does not extend the standard refund request period.

After 24 hours from initial service activation, refund requests based solely on such third-party regional classifications, changes to those classifications, or resulting content or feature restrictions are not eligible under the standard refund policy, including refunds to your account balance.

This provision does not exclude refund rights arising from YINNET’s delivery of a service that does not conform to the agreement, failure to fulfil an express commitment, or other rights that cannot lawfully be excluded. Such circumstances are governed by Sections 4.4 and 7.7 and applicable law.

12. Limitation of Liability

12.1 Indirect Losses

To the extent permitted by applicable law, YINNET is not liable for indirect or consequential losses, including resulting loss of profit, goodwill, or business opportunities.

Whether a loss falls within a category that may lawfully be excluded depends on the circumstances and applicable law.

12.2 Liability Cap

Subject to Section 12.3, and only to the extent permitted by applicable law and where enforceable, YINNET’s aggregate liability arising from the same incident is capped at the service fees actually paid for the affected service’s most recent billing period as of the time of the incident.

Where the law requires a higher level of liability or does not permit this limitation, the law applies.

12.3 Liabilities Not Excluded or Limited

These Terms do not exclude or limit liability that cannot lawfully be excluded or limited, including liability for fraud, intentional misconduct, gross negligence, personal injury, or other matters to the extent that applicable law prohibits such a limitation.

The liability cap does not extinguish YINNET’s established obligation to return funds under these Terms or applicable law.

12.4 Critical Uses

If you intend to use the services for applications directly involving life safety, medical control, nuclear operations, aviation, or other uses capable of causing serious personal harm, you must first separately confirm appropriate conditions and safeguards with YINNET.

Until corresponding service standards and safety measures have been separately agreed, ordinary cloud services should not be used as the sole supporting system for those purposes.

You should establish reasonable redundancy and business-continuity arrangements appropriate to your operations.

13. Referral Programme and Affiliate Commissions

13.1 Commission Rules

Commission rates, calculation bases, eligible products, whether initial payments or renewals earn commission, and referral attribution are governed by the programme rules published when you participate.

13.2 Valid Referrals

Valid referrals must come from genuine, independent new users and meet applicable tracking, registration, ordering, payment, and activation requirements.

Refunds, chargebacks, fictitious orders, and other transactions that do not meet programme conditions do not generate valid commissions.

A refund to an account balance also permits adjustment of the related commission. Partial refunds are handled according to the affected amount and programme rules.

13.3 Holding Period

Commissions are subject to a 30-day holding period from the date they are generated. Commissions within this period are not available for withdrawal.

Where a specific transaction is subject to a concrete payment dispute or fraud concern, confirmation of that commission may be delayed. Where feasible, we will explain the reason and review process.

13.4 Withdrawal Threshold and Processing Time

Once eligible withdrawable commissions reach USD 50, you may request withdrawal using the method provided in the client area.

Under normal circumstances, YINNET will complete review and submit payment within 7 to 15 business days after receiving all necessary information. Payment provider settlement time may be additional.

Available withdrawal methods, currencies, and applicable charges are as displayed when the request is made.

This section applies only to eligible withdrawable affiliate commissions. It does not apply to top-ups, service refund credits, or other non-withdrawable account balances. The USDT service-refund restrictions in Section 7.2 do not, by themselves, remove eligibility to withdraw affiliate commissions that qualify under this section.

13.5 Converting Commissions to Account Credit

Before choosing to convert commissions into account credit, you should confirm the applicable restrictions.

Once converted at your request, the credit may be used only to purchase or renew YINNET services. It cannot be withdrawn again, transferred to another account, or exchanged for cash, except where applicable law requires otherwise.

If a service purchased using that credit qualifies for a refund, the funds are returned to the account balance and do not become withdrawable commissions again.

13.6 Prohibited Referral Activities

You must not obtain commissions through:

• Self-referrals or orders placed through other accounts you control.

• Arrangements involving relatives, controlled accounts, or other transactions that are not substantively independent.

• Registering, ordering, paying, or controlling accounts on behalf of referred users to manufacture a referral relationship.

• Fictitious transactions, fabricated orders, or exploitation of system vulnerabilities.

• Impersonating YINNET or making unauthorised promises.

• Spam, misleading redirects, or other deceptive promotion.

• Cookie stuffing, hidden frames, forced clicks, or referral tracking without users’ knowledge.

• Unauthorised cashback, commission sharing, or other incentives contrary to programme rules.

A shared IP address alone is not sufficient to establish referral fraud.

13.7 Invalid Commissions and Review

Where an order is refunded, charged back, or verified as breaching programme rules, YINNET may reverse or adjust the corresponding commission.

Any recovery or offset of commissions already paid must identify the basis and affected amount and comply with applicable law. Unrelated, legitimately earned commissions will not be arbitrarily forfeited.

You may provide relevant information and request a manual review.

13.8 Charges and Programme Changes

Participants are responsible for handling taxes on their commission income as required by law.

Payment and currency-conversion charges borne by participants must be clearly disclosed in advance.

Programme changes are governed by Section 14 and will not retrospectively remove commissions legitimately earned under the previous rules.

14. Changes to Terms and Services

14.1 Versions and Notices

When YINNET updates these Terms, we will publish the update date and applicable arrangements.

For material adverse changes affecting prices, refunds, resource limits, data processing, or other important rights, we will give affected users reasonable advance notice explaining the effective date, scope, and available options.

Wording corrections or clarifications that do not affect substantive rights may take effect upon publication.

14.2 Application of Changes

Changes generally apply to new orders or renewals after they take effect.

Merely updating a webpage will not retrospectively reduce the core service for an already paid period or remove established refund or commission rights.

Changes to prices for the next billing period should be accompanied by reasonable notice and an opportunity to cancel renewal.

14.3 Material Changes to Prepaid Services

If legal, security, or other necessary reasons require a material adverse change to a prepaid service, you may terminate the affected portion within the reasonable period specified in the notice and request a proportionate return for the unused period, unless the law provides otherwise or the change results from your breach.

The notice should explain the calculation and application process. Returns are handled under Section 7.7. USDT-funded payments are returned as account credit under Section 7.2 unless applicable law requires another method.

14.4 Emergency Measures and Consent

Measures required immediately by law, or necessary to address serious security risks, may be implemented first, with notice provided when practicable.

Where applicable law requires separate consent, a website announcement or continued use of the service will not be treated as a substitute for that consent.

15. Applicable Law and Other Provisions

15.1 Applicable Law and Disputes

These Terms are applied and interpreted according to the laws binding on the relevant transaction.

If a dispute arises, the parties may first seek resolution through a support ticket or the contact method in Section 1.4. If it cannot be resolved, either party may seek relief before a court with jurisdiction under applicable law.

These Terms do not remove consumer protections or remedies that cannot lawfully be excluded.

15.2 Notices

YINNET may send notices through the client area, your registered email address, or another method agreed between the parties.

For material service changes, important charging arrangements, or data deletion, direct notice will be provided to affected users to the extent required by applicable law and these Terms.

You must keep your contact details accurate and valid.

15.3 Language Versions

The Chinese and English versions of these Terms are intended to express the same rights and obligations.

Any ambiguity will be interpreted in light of the order details, transaction context, and applicable law. You may request clarification through a support ticket. No language discrepancy excludes rights that cannot lawfully be excluded.

15.4 Time Standard and Business Days

Unless the order or applicable product policy expressly states otherwise, dates, times, and deadlines in these Terms are calculated using Singapore Time (SGT, UTC+8).

Business days are Monday to Friday in Singapore Time, excluding Singapore public holidays.

Periods expressed in hours run continuously and are not paused by weekends or public holidays.

The standard refund limit in Section 7.4 is calculated by calendar month in Singapore Time.

15.5 Severability and Non-Waiver

If part of these Terms is found invalid or unenforceable, the remaining provisions remain effective to the extent permitted by law.

A party’s failure to exercise a right immediately does not constitute a permanent waiver of that right.