iAgent Terms of Service

1. Product and scope

iAgent is a local desktop app focused on workflow assistance in its current public scope. It helps users turn plain-language requests into reviewable workflows, but it does not replace professional judgment, business rules, legal advice, or internal approval controls.

These terms are provided by Shanghai Aijingte Artificial Intelligence Technology Co., Ltd (上海爱晶特人工智能技术有限公司), the legal entity that owns and operates iAgent.

Current public installers cover macOS and Windows. iOS is a mobile client for iAgent cloud chat, cloud workspace, file review, workflow actions, billing, and account access after the iOS app is made available through TestFlight or the App Store. Linux, Android, team collaboration, full organization management, and deep external-system integration belong to the public service scope only after the Download page, App Store listing, release notes, or official docs clearly say they are live.

Marketing copy is not a substitute for product facts. Functional scope follows backend behavior, public docs, release notes, and the actual application interface.

2. Account registration and AI interaction logs

By registering, signing in, purchasing, or using iAgent, users agree to these terms and the privacy policy. Users who do not agree should not register or continue using the product.

iAgent cloud AI features may send user prompts, document content placed into model context, table content, converted file text, tool call parameters, model responses, model name, token usage, cost, latency, status code, and error information to the iAgent cloud proxy, model providers, and necessary cloud service providers.

iAgent may use Cloudflare AI Gateway or similar cloud logging systems to store AI interaction logs for debugging, quality analysis, security review, abnormal request tracing, cost control, billing, and service operations. Users should avoid submitting data they are not allowed to process, secrets, payment information, identity numbers, complete sensitive contracts, or other content they do not want to enter the cloud model path.

3. User responsibilities

Users are responsible for making sure imported, processed, and exported data is legally sourced and that they have permission to process it. Users must not use iAgent to process data they are not allowed to access or to bypass internal controls.

Users must review output from models, rules, scripts, and workflows. High-risk actions such as external-system writes, regulated filing, audit support, statutory disclosure, system import, and file overwrite require human confirmation.

Users may not use iAgent for unauthorized access, data leakage, malicious automation, unlawful scraping, regulatory evasion, or other unlawful activity.

4. Cloud execution and sandbox boundary

iAgent Cloud Workspace is a cloud execution capability. User-started cloud tasks may run commands, browse websites, install runtime environments, execute code, or generate files inside a controlled sandbox. The cloud workspace is intended to feel like a temporary cloud server for task execution, but it is not a dedicated cloud account for the user and does not give the user direct control over the underlying infrastructure.

To keep automation smooth, production code-agent tasks enable broader tool permissions by default inside the sandbox, including the underlying command-line tool's --dangerously-skip-permissions mode. This default experience depends on the iAgent-controlled cloud sandbox boundary being enabled and verifiable. It does not let a task bypass iAgent's quota, audit, credential, network, file, browser, or high-risk action approval rules.

If the cloud sandbox, isolated runtime, credential resolution, browser resources, or another required security component is unavailable, iAgent must fail closed. The task will not be downgraded to unsandboxed execution, and users will not be asked to paste secrets, tokens, or sensitive credentials into a prompt to continue. Users may see the task fail, queue, retry, or require confirmation.

5. Generated content and accuracy

iAgent may generate classification suggestions, rule text, script text, report notes, anomaly warnings, or other assistive content. This content improves workflow speed but should not be treated as automatic business, legal, or audit conclusions.

For amount handling, precision rules, record balance, report scope, and file writes, the product should prefer deterministic code and reviewable rules. Users still need to confirm results against source material and business policy.

If generated content conflicts with original documents, company policy, accounting rules, tax requirements, or human review, those sources take priority.

6. Payments, access passes, and refunds

iAgent's current public paid plans for individual users are primarily one-time access passes. Users may buy 1 month of access or 1 year of access. After payment succeeds, iAgent grants the corresponding paid benefits based on the backend order and the payment provider webhook reconciliation result. Unless a checkout page clearly describes a plan as a subscription, these one-time access passes do not renew automatically and do not create automatic future charges.

iAgent will try to send renewal reminders before an access pass expires. A reminder is only a service notice. It does not mean that iAgent will renew the access pass or charge the user automatically. After an access pass expires, the user needs to purchase another pass to continue using the corresponding paid benefits.

For purchases processed through Paddle, Paddle acts as the authorized reseller and merchant of record. Refunds, cancellations, statutory withdrawal rights, and payment disputes for those transactions are handled under Paddle's Buyer Terms and Refund Policy. Users can request a refund through the "View receipt" link in their Paddle confirmation email, through the billing page, or through Paddle buyer support. If a future plan is clearly labeled as a subscription, users may also use the subscription management link in Paddle's email or buyer portal to cancel that subscription.

Unless required by applicable law or approved under Paddle's Refund Policy, transactions are non-refundable and non-exchangeable. Mandatory consumer rights in the user's country or region continue to apply. For example, Paddle's Refund Policy describes statutory withdrawal or cancellation rights that may apply in the EU, EEA, Switzerland, the United Kingdom, Turkey, Israel, South Korea, Brazil, China, Canada, Singapore, and other regions where local law provides non-waivable rights.

Users may request a refund within 14 days of payment. iAgent will help verify the order, account benefits, used credits, used services, and payment provider records. A partial refund may refund only part of the order amount. A full refund will normally end the paid benefits connected to that order. After a refund is approved, iAgent may revoke, shorten, or adjust the related access pass, account credits, managed model credits, or other paid benefits so that refunded access does not continue.

If a user experiences a persistent technical issue or a material product defect that prevents access to the features or benefits described, they should contact iAgent support first so we can try to resolve the issue. If the issue cannot be resolved, the user may contact Paddle buyer support and provide details of the issue and any response received from iAgent.

For purchases made through App Store, Google Play, PayPal, Alipay, WeChat Pay, or another non-Paddle payment channel, the refund entry point, eligibility review, and processing time may depend on that channel's rules and applicable law.

For purchases made through Apple's App Store, Apple processes the payment and may manage refunds, cancellations, billing issues, family sharing eligibility, taxes, storefront rules, and subscription management under Apple's rules. iAgent uses Apple signed transaction and renewal information to verify the purchase, reconcile billing, and update the user's Access Center entitlements. Users should use the App Store subscription management and refund flows for Apple-managed purchases.

Access to iOS cloud capabilities depends on the user's current entitlement snapshot. Some plans may show iOS cloud chat, workflow execution, file processing, MCP-backed capabilities, Python Runtime, QuickJS, or cloud workspace features as unavailable, locked, expired, refunded, revoked, or quota-limited.

iAgent and its payment providers may refuse refund requests or suspend related access where there is evidence of fraud, refund abuse, manipulative behavior, unlawful use, service abuse, payment disputes made in bad faith, or violation of these terms.

7. Updates, support, and changes

Desktop versions ship through the public update channel. Platform builds, signing, and upload steps may finish at different times, so public releases may not be synchronized across all platforms.

iOS versions are distributed through Apple's TestFlight or App Store channels when available. iOS release timing, app review results, build availability, and subscription product availability may depend on Apple review, App Store Connect configuration, and regional availability.

To keep core features such as document parsing, spreadsheet handling, OCR, and automated workflows working properly, the iAgent desktop app may automatically download, install, or update required local runtime components after installation, after first launch, or when a related feature is first used. These components may include the Python Runtime, document-processing components, and security update components. They are installed in the local app data directory and verified through version metadata, hashes, and signatures.

Launch-stage support boundaries follow the Download page, release notes, and public docs. Capabilities not listed there should not be understood as public commitments.

These terms may change as the product and release process evolve. Formal terms updates should be published on the official site with an effective date or applicable version.

8. Review notice

This page describes the current public service scope and does not replace professional judgment by counsel or a compliance owner. Liability limits, dispute resolution, governing law, and cross-border data language require separate confirmation.

Before public adoption, the product owner should verify product facts and a legal or compliance reviewer should verify whether the language fits the target market.

If these terms conflict with an order, invoice, privacy policy, or applicable law, the applicable law and more specific written agreement control.