User Service Agreement.

1. Scope of application and method of acceptance of the agreement

1.1 This agreement is entered into between you and Jianxiu Tech (Hangzhou) Co., Ltd. (hereinafter referred to as "we") regarding the use of EasyOps, Asset Sonar and their supporting websites, documents, and update services (collectively, the "Services").

1.2 Before downloading, activating, launching for the first time, submitting an experience application or purchasing services, we will provide you with an entrance to view this Agreement and Privacy Policy. This agreement is established after you accept it by checking, clicking to confirm, or other explicit actions. Merely browsing public pages that do not require an account does not automatically constitute acceptance of payment, limitation of liability or dispute resolution terms.

1.3 If you use this service on behalf of a company or organization, you are deemed to have been fully authorized, and the organization will be responsible for the use.

1.4 Automatic renewal, security risks, liability limitations, service termination and dispute resolution terms that have a significant impact on you will be drawn to your attention in bold, prompt boxes or confirmation interfaces. If you have any questions, you can contact us for clarification before accepting.

2. Service content and license type

2.1 EasyOps (mobile version)

• provides network diagnosis, knowledge base query, on-site operation and maintenance tools and other functions.
• basic functions are free to use, and value-added capabilities may be provided through subscription.

2.2 Asset Sonar (enterprise desktop)

• Asset Sonar is commercial software. The licensed entity, term, approved media, service scope and fees are determined by the applicable order, contract, quotation or written authorization.
• A valid license permits the customer to run the software from an approved physical USB drive or other medium for internal asset auditing, export and synchronization to the customer's own Snipe-IT across Windows 7 SP1, Windows 10 and Windows 11 endpoints.
• The software may require connectivity for initial activation, periodic validation, renewal, status recovery, version checks and updates. Offline availability is determined by the applicable license configuration or written agreement.
• Updates may be delivered as full or delta packages and may fall back after validation or installation failure. Customers remain responsible for keeping necessary configuration, logs and business backups and for ensuring adequate power, disk space and connectivity.
• Data processed by licensing and operations services is described in the Privacy Policy. Endpoint inventory and Snipe-IT business data are not automatically uploaded to Jianxiu merely for license validation.

2.3 License restrictions

We grant you a non-exclusive, non-transferable, revocable license to use, which is limited to legal, authorized and compliant purposes, and may not be used beyond the scope.

3. Account, configuration and security responsibilities

• You should keep your account number properly.ApiKey、AssignPassword shall not be disclosed to unrelated persons.
• should ensure that the configuration file (e.g. Profiles, mapping fields, interface addresses) are accurate and valid to avoid mis-synchronization or mis-coverage.
• If abnormal access, credential leakage or data anomalies are found, the relevant credentials should be deactivated immediately and the administrator should be notified to handle it.

4. User Code of Conduct and Prohibited Matters

You promise to use the service only in legally authorized scenarios. Prohibitions include but are not limited to:

• Unauthorized scanning, detection, penetration, and attack on other people's networks and systems.
• uses this service to spread malicious code, perform blackmail, steal or destroy data.
• bypasses security mechanisms, cracks authorization, decompiles closed source parts, and abuses interfaces in batches.
• Forge, tamper with, delete logs and audit records, or circumvent compliance trace requirements.
• Use this service to engage in behavior that violates laws, regulations, industry norms or public order and good customs.

5. Open source terms and third-party components

5.1 First-party Asset Sonar applications, launchers, documentation, interfaces, update packages and related commercial components remain owned by Jianxiu Tech or their lawful owners. No source-code, copying, modification, redistribution or resale rights are granted except by written authorization or mandatory law.

5.2 The Services may include third-party open-source libraries, runtimes, fonts or commercial components. Each remains governed by its accompanying license and notices. A third-party license applies only to the relevant component and does not by itself change the commercial licensing of first-party Asset Sonar software.

5.3 Windows, Snipe-IT and other third-party names and trademarks belong to their respective owners. Where redistribution of a third-party component is permitted, the customer must preserve applicable licenses and attribution notices.

6. Subscription, automatic renewal and refund (EasyOps)

• Subscription price, service content, billing cycle, trial to payment conditions and estimated deduction time are subject to the application store or purchase page when you confirm your purchase.
• Automatic renewal must be chosen by you. We or the payment channel will clearly explain the renewal period, price and cancellation method before your confirmation, and will remind you in a prominent way before the renewal and deduction date; no automatic renewal will be performed without valid authorization.
• You can cancel automatic renewal on the subscription management page of the corresponding app store. After cancellation, the subscription will usually stop renewing at the end of the paid period and will not affect the remaining rights and interests of the current period.
• Refunds and order cancellations can be carried out through payment channels such as App Store and Google Play, but the channel rules do not exclude or limit your rights to returns, refunds, quality assurance, complaints and damages according to law.
• If there are major changes to the subscription price or core service content, we will notify you prominently before the next billing cycle and will not replace your choice with a default check.

7. Data and content responsibility boundaries

7.1 You are responsible for the legality, accuracy, and completeness of the data you enter, import, synchronize, and export.

​​7.2 You should ensure that you have legal access and write authorization to the target system (such as Snipe-IT).

7.3 For data deviations that are directly caused by your configuration errors, permission mismatches, unauthorized operations, target interface abnormalities or external network interruptions and for which we are not at fault, you shall bear the corresponding responsibility; liability caused by product defects, our failure to perform legal obligations or our fault will not be exempted by this article.

8. Service availability, updates and maintenance

• We can update, repair and optimize functions without materially damaging the core rights and interests of paid users. When the core payment capabilities are deactivated, reasonable notice will be given in advance and migration, continued performance, refund or other reasonable solutions will be provided in accordance with the law.
• Emergency security fixes may be released without prior notice.
• Short-term unavailability due to system maintenance, third-party failure, and network fluctuations will not be considered a breach of contract.
• If Asset Sonar licensing or update services are affected by maintenance or network failure, we will take reasonable recovery measures. Local capabilities may continue within a valid offline entitlement; reconnecting may be required after that entitlement ends or to restore license status.

9. Intellectual Property Statement

EasyOps and its related documents, interface design, trademarks and brand logos are owned by us or the legal rights holders. Except as expressly permitted by law or agreement, no reproduction, modification, dissemination or commercial reuse is allowed without written permission.

10. Risk notification list (listed item by item)

To avoid ambiguity in understanding, the following risks are clearly listed by clicking "Trigger Scenario → Possible Consequences → Recommended Measures". You should conduct a risk assessment and keep records before going online.

10.1 Configuration and mapping risks

• trigger scenario:CATEGORY_ID_MAP、COMPONENT_CATEGORY_ID_MAP、ACCESSORY_CATEGORY_ID_MAP Configuration error or missing.
  Possible consequences:Asset classification error, component/accessory association failure, batch retry amplification error.
  Recommended measures:first samples 10 units for verification in the test environment before entering into production batches.
• trigger scenario:ActiveProfile Incorrect selection (error in switching between test environment and production environment).
  Possible consequences:writes to the wrong target system, generates dirty data or duplicate assets.
  Recommended measures:goes online, two people review the Profile and API address, and the first batch of grayscale synchronization.
• trigger scenario:asset tag prefix (such as ASSET_TAG_PREFIX) Rule changes are not synchronized.
  Possible consequences:The old and new asset numbers conflict and the report statistics are distorted.
  Recommended measures:Freeze synchronization tasks before changes and publish new coding rules uniformly.

10.2 Permissions and Credentials Risks

• trigger scenario:API Key permissions are too large or have not been rotated for a long time.
  Possible consequences:Unauthorized writing, batch mistaken modification, and credential leakage lead to security incidents.
  Recommended measures:Minimum privilege authorization, periodic rotation, and immediate revocation if suspected leakage.
• trigger scenario:Accounts are shared and passwords are transmitted in clear text or stored on public devices.
  Possible consequences:The responsibility boundary cannot be audited and unauthorized operations occur.
  Recommended measures:Assign accounts per person, enable safe storage, and enable operation traces.
• trigger scenario:Administrator rights run permanently.
  Possible consequences:The impact of incorrect operation is expanded, and malicious programs take advantage of high privileges.
  Recommended measures:Only temporarily elevates privileges during necessary tasks, and degrades privileges after the task is completed.

10.3 Network and interface risks

• trigger scenario:The proxy, gateway, WAF, and certificate chain configurations are inconsistent.
  Possible consequences:401/403/404/5xx High-frequency error reporting and synchronization interruption.
  Recommended measures:Establish a connectivity list based on the environment, and perform regression verification after changes.
• trigger scenario:Third-party API current limit or version change.
  Possible consequences:The request failure rate increases, tasks are delayed, and some fields fail to be written.
  Recommended measures:Implement speed limit and retry strategies, and track upstream version announcements.
• trigger scenario:Internal network DNS abnormality or link flapping.
  Possible consequences:The scan results are unstable and the synchronization batch fails randomly.
  Recommended measures:Perform network health check first, and then execute batch tasks.

10.4 Data quality and consistency risks

• trigger scenario:The device serial number is empty, the model field has dirty data, and the MAC is repeated.
  Possible consequences:Asset deduplication failed, merged incorrectly, or was created repeatedly.
  Recommended measures:performs local verification and cleaning before allowing writing to the target system.
• trigger scenario:Multi-batch concurrent synchronization and lack of conflict strategy.
  Possible consequences:Data competition, version overwriting, and status rollback are difficult.
  Recommended measures:uses batch serial or partition locking strategy to retain batch snapshots.
• trigger scenario:The exported report is inconsistent with the online status time point.
  Possible consequences:Audit reconciliation deviation and distortion of management decision-making.
  Recommended measures:unified export time point, retaining "snapshot time + batch number".

10.5 Terminal and operating environment risks

• trigger scenario:The operating system component is missing (such as .NET Runtime) or the version is incompatible.
  Possible consequences:program crashes, functions are unavailable, and scanning is incomplete.
  Recommended measures:performs environment self-test before going online to lock the supported version range.
• trigger scenario:Security software blocks scanning or synchronization behavior.
  Possible consequences:The result is incomplete, the network request fails, and it is misjudged as a product failure.
  Recommended measures:Establish a whitelisting process with the security team and document approvals.
• trigger scenario:Insufficient disk space or restricted permissions.
  Possible consequences:Log writing failed, export was interrupted, and the configuration was damaged.
  Recommended measures:Set the minimum space threshold and abnormal alarm mechanism.

10.6 Compliance and legal risks

• trigger scenario:performs scanning, detection, and asset collection on unauthorized networks.
  Possible consequences:violates network security and data compliance requirements, triggering legal liability.
  Recommended measures:Ensure the scope of written authorization and retain approval records.
• trigger scenario:Cross-border transfer failed to fulfill internal review or legal obligations.
  Possible consequences:Regulatory penalties, business interruption, contract breach.
  Recommended measures:is evaluated by the organization's legal/compliance team and necessary processes completed.
• Trigger: removing third-party license or attribution notices, or distributing a third-party component beyond its license scope.
  Possible impact: open-source or commercial-component compliance disputes, takedown demands or claims.
  Recommended control: review third-party notices before distribution and preserve required notices.

10.7 Operation and maintenance process risks

• trigger scenario:is directly synchronized in full, without grayscale and rollback plans.
  Possible consequences:Batch errors spread rapidly and the recovery cost is high.
  Recommended measures:implements the process of "testing and verification → small batch grayscale → batch release".
• trigger scenario:fault handling, "Rerun with full volume" replaces "Retry with failed objects".
  Possible consequences:Repeated writing, surge in interface pressure, and mistaken overwriting of historical data.
  Recommended measures:Accurately retry according to the failure list and keep operation records.
• trigger scenario:There is no log archiving and review mechanism.
  Possible consequences:Difficulty defining responsibilities and recurring problems.
  Recommended measures:archives "scan snapshot + synchronization results + exception list + operation log".

10.8 Risk level and responsible party matrix (audit version)

11. Disclaimer and limitation of liability

• This service is provided "AS IS" and does not promise to adapt to all equipment, networks, privatized environments and customized processes.
• We do not guarantee that all third-party data sources, interfaces, and dictionaries will continue to be accurate, real-time, and complete.
• To the extent permitted by law and fair and reasonable, liability may be limited in accordance with the law for indirect losses that are not reasonably foreseeable and have no direct causal relationship with the breach of contract; this limitation does not affect your legal claims for direct losses and statutory relief.
• For general property losses caused by minor negligence, the cumulative compensation liability we bear is subject to twice the actual amount paid by you for relevant services in the twelve consecutive months before the liability event occurs. The reference cap is RMB 1,000 for free services. If the people's court, arbitration institution or legal provisions deem that adjustments should be made, such determination shall prevail.
• The above limitations do not apply to losses, personal injuries, infringement of personal information rights, infringement of intellectual property rights caused by our intentional or gross negligence, as well as liabilities that are expressly not limited or exempted by law.

12. Change, suspension and termination of agreement

12.1 We may update this agreement according to laws, regulations, product functions and risk control needs. Major changes involving price, core functions, liability limitations, automatic renewal or dispute resolution will be notified in a prominent manner before taking effect; if re-agreement is required according to law, re-confirmation will be obtained.

12.2 If you seriously violate this Agreement, commit illegal acts, or cause significant real security risks, we may take measures to restrict, suspend or terminate. Except for emergency safety incidents, we will explain the reasons in advance as much as possible and provide reasonable opportunities for appeal or rectification.

12.3 If we voluntarily stop core paid services and you do not breach the contract, refunds, relocation or other reasonable arrangements will be provided for the unfulfilled portion in accordance with the law. We will provide a reasonable data export window before termination if technically feasible.

12.4 After the agreement is terminated, the confidentiality, intellectual property, liability and dispute resolution provisions that by their nature should remain in effect will remain in effect.

13. Law application and dispute resolution

13.1 This agreement shall be governed by the laws of the People's Republic of China.

13.2 For disputes arising from this agreement, both parties shall first negotiate amicably, or may request mediation from consumer organizations, industry organizations or administrative agencies in accordance with the law. If negotiation or mediation fails, you may file a lawsuit with the people's court with jurisdiction over the place where Jianxiu Tech (Hangzhou) Co., Ltd. is domiciled; if the law has other mandatory provisions on consumer jurisdiction, exclusive jurisdiction or other relief channels, those provisions shall prevail. This article does not limit the right of any party to complain, report or apply for administrative processing in accordance with the law.

14. Contact and complaint channels

For service inquiries, infringement complaints, legal matters or compliance communications, please contact:

Jianxiu Tech (Hangzhou) Co., Ltd. · Service and Compliance Contact

Email:axuan@bigbabol.xyz