--- title: "Terms of Service" description: "AI GO Terms of Service: service provision and license, billing and payment, user responsibilities, intellectual property and data ownership, data export and source code retrieval between URFiT and enterprise customers." canonical: "https://www.ai-go.app/en-US/terms-of-service" locale: "en-US" source: "AI GO（https://www.ai-go.app）" --- # Terms of Service Last Updated: October 2026 Welcome to the AI GO Enterprise Resource System (hereinafter referred to as "the System" or "the Services"). These Terms of Service (hereinafter referred to as "these Terms") constitute a legally binding agreement between Urfit Technology Co., Ltd. (hereinafter referred to as "Party A" or "the Company") and the enterprise user (hereinafter referred to as "Party B" or "the User") who agrees to these Terms, regarding the use and licensing of the System. When Party B registers online, logs in, clicks to agree, or actually starts using the System, Party B shall be deemed to have fully read, understood, and agreed to accept all provisions of these Terms. ## Article 1: Provision of Services and License to Use ### 1.1 Scope of License Subject to Party B's strict compliance with these Terms and full payment of all relevant fees, Party A grants Party B a non-exclusive, non-transferable, and non-sublicensable right to access and use the System via the internet during the subscription period. ### 1.2 Account Security and Exclusivity Party A will provide Party B with a dedicated account and password for the System. The System operates on a "Named User" or "Enterprise License" model. Party B shall not lease, share, transfer, or resell the account to any third party. Party B shall exercise the due care of a good administrator to properly safeguard its account credentials. If Party B discovers that its account has been compromised or has security concerns, it shall immediately notify Party A. ### 1.3 Restrictions on Use Party B agrees and guarantees that it will not use the System to perform any of the following activities: - (1) Reverse engineer, decompile, disassemble, or attempt to derive the source code of the System. This restriction does not apply to Party B retrieving the source code of its applications (including the development kit files contained therein) under Article 12. - (2) Use automated programs (such as crawlers or robots) to maliciously extract system data or call the API excessively beyond reasonable limits. - (3) Use the System to develop competitive products or services, or perform stress tests and security vulnerability scans without Party A's prior written authorization. ### 1.4 Changes to Services and Beta Features Party A reserves the right to update, add, or remove functions of the System at any time to maintain its optimal state. Party A may from time to time release "Beta" features, which are provided on an "as-is" basis and are not subject to the regular Service Level Agreements (SLA). Party A reserves the right to terminate Beta services at any time. ## Article 2: Fees and Payment ### 2.1 Subscription Plans and Fees The System currently offers the following standard subscription plans with the fees and entitlements as listed below: | Billing Type | Fee (NTD, excl. tax) | Description | | --- | --- | --- | | Annual Plan | **NT$ 99,000 / year** | One-time annual payment | All fees stated in these Terms exclude tax, and a 5% business tax shall be added; late interest is not subject to this tax. Each plan includes the following monthly usage allowances: - (1) **AI Credit**: 30,000 / month — AI Coding Agent / Cowork Agent powered by frontier models such as Codex (usage from customer-integrated API keys is not counted against this allowance). - (2) **Read/Write Traffic**: 200,000 transactions / month — All enterprise data read/write authorization and computing traffic, with each transaction auditable. - (3) **Enterprise Storage**: 50 GB / month — Enterprise data storage space. ### 2.2 Overage Fees If Party B's usage in any billing cycle exceeds the base allowances specified above, the excess usage shall be billed at the following rates: | Item | Overage Rate (NTD) | | --- | --- | | AI Credit | **NT$ 10 per 100 Credits** | | Read/Write Traffic | **NT$ 10 per 1,000 transactions** | | Enterprise Storage | Billed at officially announced rates | ### 2.3 Payment Terms Effective October 2026, the Services are prepaid. Annual plans shall be paid in full before activation; monthly plans shall be paid before the start of each billing cycle. Party A shall activate or continue the Services only after confirming receipt of payment, and has no obligation to activate the Services before payment is made in full. Remittance fees shall be borne by the remitting party. Overage fees (Section 2.2) are settled monthly. Party A shall issue an invoice for them in the following month, and Party B shall pay within thirty days from the invoice date. ### 2.4 Handling of Late Payments If Party B fails to pay the fees on time, Party A may charge late interest at **10% per annum**. If Party B has overdue payments under the Services or under any other agreement separately signed by both parties, and still fails to pay within a reasonable period after being notified by Party A in writing or by email, Party A may suspend Party B's access to the System until all outstanding debts are settled. ### 2.5 Fee Adjustments Party A reserves the right to adjust subscription plan fees. In the event of any price increase, Party A shall notify Party B at least **sixty (60) days** before the new rates take effect, via system announcement or email. To protect Party B's interests, the effective date of any price adjustment shall depend on Party B's subscribed plan: - (1) **Monthly billing plans**: The new rates shall take effect in the next billing cycle following the expiration of the sixty-day notice period. - (2) **Annual plans**: If Party B has prepaid an annual subscription and the contract is still in effect, the current contract fees shall not be affected by any price adjustment. The new rates shall only take effect upon the next annual renewal after the current term expires. If Party B does not agree to the adjusted rates, Party B shall terminate the Services before the new rates take effect. If Party B continues to use the Services after the new rates take effect, Party B shall be deemed to have been fully informed of and to have agreed to the modified fees. ### 2.6 Fourteen-Day Unconditional Refund Guarantee Within **fourteen (14) calendar days** of Party B's **initial subscription** to the Services (calculated from the subscription activation date recorded in the system), if Party B determines for any reason that the Services do not meet their needs, Party B may request a full refund by sending an email to Party A at [us@urfit.com.tw](mailto:us@urfit.com.tw). Party A shall refund the full subscription fee paid by Party B within **sixty (60) days** of receiving the refund request, to Party B's original payment method or designated bank account, without any processing fees. Upon completion of the refund, Party B's account shall be immediately deactivated. Data within the system shall be retained for thirty days for Party B to export, after which Party A may delete it. This fourteen-day unconditional refund guarantee applies only to Party B's initial subscription to the Services and does not apply to renewals or plan upgrades. Any overage fees actually incurred (as described in Section 2.2) are not eligible for refund. ### 2.7 Service Term and Renewal The service term is one (1) year from the date Party A activates the Services (based on the subscription activation date recorded in the system), for both monthly and annual plans. Unless either party gives written notice of non-renewal at least thirty days before expiration, the Services shall automatically renew for one (1) year on the same terms. Fees for the renewal year shall be paid in full before expiration; if not, Party A may stop the Services upon expiration. For annual plans, Party A shall send a renewal notice sixty days before expiration. ### 2.8 Early Termination Party B may terminate the Services by written notice to Party A, effective fourteen (14) days after the notice. For monthly plans, fees already paid for the current period are not refunded upon termination; for annual plans, fees already paid are not refunded except as provided in Section 2.6. ## Article 3: User Responsibilities and Acceptable Use Policy (AUP) ### 3.1 Guarantee of Legality Party B shall ensure the legality of any products, texts, images, videos, and data (hereinafter referred to as "Customer Data") uploaded, processed, or transmitted through the System, and shall strictly comply with the Consumer Protection Act, the Personal Data Protection Act, and intellectual property laws. ### 3.2 Prohibited Behaviors (Anti-Spam & Abuse) Party B shall not use the System to engage in the following prohibited behaviors: - (1) Send unsolicited commercial emails (Spam), phishing emails, or engage in any form of online fraud. - (2) Store or distribute files containing computer viruses, Trojans, worms, or other malicious software. - (3) Process, upload, or transmit content that is defamatory, pornographic, violent, hateful, discriminatory, or infringes upon the privacy and intellectual property rights of third parties. ### 3.3 Defense and Indemnification Liability If Party A is subject to claims by third parties or administrative penalties due to Party B's violation of the aforementioned obligations, unlawful Customer Data, or defects in products sold by Party B, Party B shall resolve the issues and indemnify Party A for all damages, losses, and expenses incurred (including but not limited to reasonable attorney fees, litigation costs, and loss of business reputation). ## Article 4: Intellectual Property Rights and Data Ownership ### 4.1 System Intellectual Property (Vested in Party A) The ownership, underlying core architecture, source code, UI/UX design, machine learning algorithms, and related derivative intellectual property rights of the System are exclusively owned by Party A or its licensors. These Terms do not transfer any system intellectual property rights to Party B, whether express or implied. ### 4.2 Customer Data Ownership (Vested in Party B) The ownership and intellectual property rights of Customer Data and related business data inputted by Party B into the System belong to Party B. Party B authorizes Party A to process and use such data only to the extent necessary to provide, maintain, and improve the Services. ### 4.3 Joint Marketing License Party B agrees that during and after the term of the Services, Party A may, for the purposes of promotion, service marketing, and joint marketing, use Party B's name, trademark (LOGO), and the public service results of mutual cooperation, free of charge, as Party A's customer case studies, promotional materials, or marketing materials. Such use excludes Party B's trade secrets and any information not approved for disclosure by both parties in writing. By agreeing to these Terms, Party B is deemed to have consented to the use described in the preceding paragraph. ### 4.4 Rights in and License to Application Source Code Within the Custom Apps and Hosted Apps that Party B installs or develops on the System, rights in the code written by Party B, or added by Party B through modification, belong to Party B. Intellectual property rights in the portions of such applications provided by Party A, including Marketplace templates, software development kit (SDK) files, and system components (collectively, "Party A Code"), remain with Party A under Section 4.1. From the time Party B installs or creates the application, Party A grants Party B a **perpetual, royalty-free, non-exclusive, non-transferable, non-commercial license** to Party A Code, under which Party B may: - (1) Freely modify, develop, and use Party A Code, and combine it with code written by Party B. - (2) Retrieve it together with the application, during the subscription term and after termination of this Agreement, for continued use in any environment of Party B's choosing. "Non-commercial" in the preceding paragraph means that Party B may not sell, rent, license, or sublicense Party A Code, or any application containing Party A Code, to any third party. Use of the applications in Party B's own operations, including making them available to Party B's customers and suppliers, is not commercial use. Partners approved in writing by Party A are not subject to the restriction in this paragraph. The license under this Section survives termination of this Agreement. However, if Party B breaches the restriction in the preceding paragraph, Party A may terminate the license under this Section by written notice. ## Article 5: Third-Party Services and Data Privacy ### 5.1 Disclaimer for Third-Party Integration The System may integrate third-party services (such as communication software APIs, payment gateways, and third-party AI language models). If certain functions of the System cannot operate normally due to policy changes, fee adjustments, or unexpected service interruptions of such third parties, Party A will make commercially reasonable efforts to assist in troubleshooting, but Party A shall not bear any liability for breach of contract or damages. ### 5.2 Confidentiality Obligations and Survival Period Both parties shall maintain strict confidentiality regarding any trade secrets, technical data, pricing, and business information marked as confidential by the other party, except as required by laws or competent authorities. This confidentiality obligation shall survive for three years after the termination or expiration of this Agreement. ### 5.3 Personal Data Protection Compliance Both parties shall strictly comply with the Personal Data Protection Act when collecting, processing, or utilizing personal data. Party B shall ensure that it has obtained clear consent from data subjects or possesses other lawful bases before transmitting data to the System. ## Article 6: Disclaimers and Limitations of Liability ### 6.1 "As-Is" Provision The Services are provided on an "As-Is" and "As-Available" basis. Except as otherwise provided in Article 10 (Service Level Agreement), Party A does not guarantee that the System will be uninterrupted, error-free, or fully meet Party B's specific commercial requirements. ### 6.2 System Maintenance and Backup Party A will make commercially reasonable efforts to maintain the stable operation of the System and will perform data backups in accordance with Article 12. Temporary service interruptions caused by Party A's scheduled maintenance (notified in advance) or urgent security patches do not constitute a breach of contract. Backup retention periods, restoration methods and their limitations, and the channels through which Party B may retain its own copies of data, are governed by Article 12. ### 6.3 Force Majeure and Allocation of Liability for Security Incidents Party A shall not be liable for any damages caused by force majeure events beyond Party A's control, such as natural disasters, wars, strikes, network infrastructure failures, or abnormalities in telecommunications or cloud service providers, which lead to system unavailability or data loss. For damages arising from unlawful intrusion by third parties, ransomware, or other security attacks, the following provisions apply according to their cause: - (1) Where the cause is the theft or leakage of Party B's account credentials, or Party B's own equipment, personnel, or self-developed applications, Party A shall not be liable for damages. - (2) Where the cause is an intrusion into the systems operated by Party A, Party A shall be liable for damages subject to the limitation set out in Section 6.4. Regardless of cause, Party A's notification obligations under Article 11 are not waived by the exemptions in this Section. ### 6.4 Limitation of Liability Unless otherwise mandatory by law, the total liability of Party A for damages to Party B shall be limited to the total service fees actually paid by Party B to Party A for the specific service during the twelve months preceding the event causing the damage. ## Article 7: Amendments, Termination, and Data Retention ### 7.1 Amendments to Terms Except where these Terms contain specific provisions regarding fee adjustments (Article 2, Section 2.5), Party A may amend these Terms. The amended terms will be announced in the System or notified to Party B via email at least thirty (30) days before they take effect. If Party B does not raise any written objection within thirty (30) days after such notice and continues to use the Services, Party B shall be deemed to agree to the amendments. If Party B raises an objection, both parties shall negotiate in good faith. If negotiations fail, Party B may terminate the Services before the amendments take effect in accordance with the law. ### 7.2 Termination of Services If Party B violates these Terms, relevant laws, or public order and good morals, and fails to correct the violation within five days after receiving notice from Party A, Party A has the right to immediately suspend or terminate Party B's account and claim relevant damages. ### 7.3 Handling of Idle Accounts If Party B uses a free plan or has overdue payments, and has not logged into the System for more than 180 consecutive days, Party A has the right to terminate the account and delete all related data after sending an email notification. ### 7.4 Data Handling After Contract Termination Upon termination or expiration of this Agreement, Party B shall export its Customer Data independently using the system functions, or request a manual export under Section 12.8, before the termination date or expiration date. Party A has no obligation to retain Party B's data thirty days after the termination of the Agreement and has the right to permanently delete Party B's data from the System without bearing any liability for data loss. ## Article 8: General Provisions ### 8.1 Pure SaaS Mode Declaration and Exclusion of Customization Unless both parties sign a separate customized development or project implementation agreement (such as the FDE Frontline Deployment Engineer Service Agreement), the System is provided as a standardized Software-as-a-Service (SaaS). The scope of this license does not include any dedicated engineer, customized programming, dedicated system operation, or on-site deployment services. Except for automated features provided by the System itself and routine customer support, Party A has no obligation to provide additional human technical support. ### 8.2 Offboarding and Transfer Assistance Upon termination of this Agreement, Party B shall export its data independently; manual exports under Section 12.8 are not subject to this Section. If Party B requests Party A to assist in host migration, project database export, or system transition consultation as a dedicated project, such technical services are not within the scope of standard licensing. Party A has no obligation to provide such engineering assistance. If Party A agrees to assist after evaluation, Party A may provide a separate quotation based on the actual engineering hours incurred. ### 8.3 Restrictions on Assignment Neither party may assign or transfer its rights or obligations under these Terms to any third party without the prior written consent of the other party. However, this restriction shall not apply if Party A undergoes a merger, acquisition, restructuring, or business transfer. ### 8.4 Entire Agreement and Severability These Terms (including the pricing plans announced on the official website and the attached Privacy Policy) constitute the entire agreement between both parties regarding the Services, superseding all prior oral promises or written agreements. If any provision of these Terms is declared invalid or unenforceable by a court of competent jurisdiction, the remaining provisions shall continue in full force and effect, and both parties shall replace the invalid part with a valid provision that best reflects the original intent. ### 8.5 No Waiver of Rights Any delay or failure of either party to exercise any right or remedy under these Terms shall not be deemed a waiver of such right or remedy. Single or partial exercise of a right shall not preclude future exercise of that right. ### 8.6 Audit and Compliance Assistance If Party B, due to internal audit or competent authority review requirements, requests Party A to provide system security explanations or cooperate with audits, Party A will provide written assistance within a reasonable scope that does not involve the confidential information of other customers. If such requirements lead to extra customized reports or on-site audit costs, both parties shall negotiate the fees separately. ## Article 9: Governing Law and Jurisdiction The interpretation, validity, and performance of these Terms shall be governed by the laws of the Republic of China (Taiwan). If any dispute arises from the Services, both parties shall first resolve it in good faith based on the principle of honesty and sincerity. If negotiations fail, both parties agree to submit to the jurisdiction of the Taiwan Taipei District Court as the court of first instance. ## Article 10: Service Level Agreement (SLA) ### 10.1 Service Availability Commitment Provider commits that the System's Monthly Uptime Percentage shall not fall below **99.9%**. The Monthly Uptime Percentage is calculated as follows: **Monthly Uptime % = (Total Minutes in Month − Unexpected Downtime Minutes) ÷ Total Minutes in Month × 100%** ### 10.2 Exclusions The following downtime shall not be counted as "Unexpected Downtime Minutes": - (1) Scheduled maintenance notified by Provider at least **24 hours** in advance via system announcement or email. - (2) Downtime caused by force majeure events (as defined in Article 6, Section 6.3). - (3) Downtime caused by third-party service failures (e.g., cloud providers, CDN, DNS services). - (4) Downtime caused by Client's own actions (e.g., account suspension due to policy violations, Client-side network failures). - (5) Beta feature service interruptions. - (6) Data loss caused by Client's own operations (such as accidental deletion, erroneous import, or incorrect data written by applications Client has developed). Such cases are handled under Article 12 and are not eligible for the availability remedies set out in this Article. ### 10.3 Service Credits If Provider fails to meet the availability commitment in any calendar month, Client may apply for Service Credits within thirty (30) days after the end of the affected month. Service Credits are calculated as follows: | Monthly Uptime % | Service Credit | | --- | --- | | 99.0% to <99.9% | **10%** of monthly subscription fee | | 95.0% to <99.0% | **25%** of monthly subscription fee | | Below 95.0% | **50%** of monthly subscription fee | Service Credits are applied as billing deductions to the next invoice and are not redeemable for cash. The maximum Service Credit for any calendar month shall not exceed 50% of Client's monthly subscription fee. ### 10.4 Sole Remedy Service Credits constitute Client's sole and exclusive remedy for Provider's failure to meet the availability commitment. ### 10.5 Real-Time Service Status Client may visit the [System Status Page (/status)](https://www.ai-go.app/en-US/status) at any time to view real-time operational status, historical uptime data, and incident records. Information on the status page is provided for reference purposes and does not affect the availability calculations defined herein. ### 10.6 Incident Notification and Response Times Provider commits to the following response timeframes upon detection of incidents affecting system availability: - (1) **P1 (Complete Service Outage)**: Status update within 15 minutes; initial response within 1 hour. - (2) **P2 (Core Feature Degradation)**: Status update within 30 minutes; initial response within 4 hours. - (3) **P3 (Non-Core Feature Anomaly)**: Status update within 2 hours; resolution plan within 1 business day. All incident status updates are published in real time on the [System Status Page](https://www.ai-go.app/en-US/status). ### 10.7 Scope of Commitments Under This Article The commitments and remedies set out in this Article extend **only to service availability**. They do not include any commitment as to Recovery Time Objective (RTO) or Recovery Point Objective (RPO). Data backup and restoration are governed by Article 12. Once Provider has completed rehearsal of its restoration procedures and established an auditable basis for measurement, Provider will add data recovery objectives, and remedies for failing to meet them, to this Article. ## Article 11: Security Incident Notification and Response ### 11.1 Notification Obligation and Deadline Upon confirming a security incident sufficient to affect Party B's data, Party A shall notify Party B's designated contact by email within **seventy-two (72) hours**, and shall additionally post a notice within the System where the scope of impact warrants it. ### 11.2 Contents of the Notification The notification under the preceding Section shall state the following. Where any item has not yet been determined at the time of notification, Party A shall supplement the notification promptly upon determination: - (1) The known nature of the incident and when it occurred. - (2) The types and scope of data potentially affected. - (3) Measures Party A has taken, and measures Party A recommends Party B take. - (4) Party A's point of contact. ### 11.3 Assisting Party B with Statutory Notification The obligation to notify data subjects under Article 12 of the Personal Data Protection Act rests with Party B as the collector of personal data. Party A shall provide, within reasonable scope, the factual information Party B requires to discharge that obligation, and shall cooperate with Party B in responding to inquiries from competent authorities. ### 11.4 Assistance with Incidents Originating on Party B's Side Party B shall notify Party A immediately upon discovering that its accounts have been compromised or upon any other security concern. At Party B's request, Party A may provide the following assistance: suspending affected accounts, forcibly terminating their sessions, and providing relevant audit records for Party B's review. ### 11.5 Relationship to the Disclaimer Provisions The notification and assistance obligations under this Article are **not waived by the exemptions in Section 6.3**. That Section waives liability for damages; it does not extend to the notification obligations set out here. ## Article 12: Data Backup, Restoration, and Portability ### 12.1 Platform-Level Backup Party A performs daily automated backups of the System's primary database, with a retention period of **seven (7) days**, and retains continuous transaction logs enabling restoration to any point in time within that retention period. Versioning is enabled on the file storage to which Party B uploads. ### 12.2 Nature and Limitations of Restoration Restoration under the preceding Section is a **system-wide operation** returning the database to a specific point in time. It is not a restoration of an individual tenant or an individual record. Given this technical characteristic, Party A does not accept requests to restore individual data rows. ### 12.3 No Self-Service Restoration Deletion within the System is permanent. No recycle bin, soft deletion, or restoration interface is provided. Party B should confirm before performing deletion operations within the System. ### 12.4 Channels for Party B to Retain Its Own Copies Party B may at any time retrieve its data through the following channels and store it in an on-premises or cloud environment of Party B's choosing: - (1) **System export function**: applicable to sales orders, purchase orders, live inventory, leads, employees, accounting entries, and all tables Party B has created in the Data Center. - (2) **Open API**: applicable to tables Party B has created in the Data Center, supporting paginated reads, which Party B may schedule and automate. - (3) **Custom App source code**: the complete source code of Party B's Custom Apps, including front-end code, server-side action code, and the SDK files provided by Party A and contained therein, may be retrieved at any time via the Builder API by an account with development permissions. ### 12.5 Hosted App Source Code and Data Outside the Self-Service Channels Hosted App source code is uploaded and deployed by Party B itself, and Party B should retain its original files. Where Party A holds the source archive of Party B's most recent successful upload, Party B may request its retrieval under Section 12.8. File attachments and application deployment artifacts (such as built container images) currently fall outside the self-service channels. Where Party B requires their retrieval, Section 8.2 applies. ### 12.6 Recommended Retention Frequency In view of the limitations described in Sections 12.2 and 12.3, Party A recommends that Party B **regularly** export and retain its important operational data through the channels listed in Section 12.4. For data loss arising from operational error on Party B's side, such copies are the practicable route to recovery. ### 12.7 Boundary with Exit Assistance Use of the self-service channels listed in Section 12.4, and manual exports requested under Section 12.8, are not separately charged. Data extraction, host migration, system conversion, or other engineering assistance beyond that scope is governed by Section 8.2. ### 12.8 Manual Export Requests Party B may request a manual export at any time by email to Party A ([us@urfit.com.tw](mailto:us@urfit.com.tw)), and Party A shall assist. The scope of a request covers: - (1) The data and application source code listed in Section 12.4. - (2) Hosted App source archives retrievable under Section 12.5. Party A shall, within **ten (10) business days** of receiving the request, provide the requested data or source code to Party B by a secure method agreed by both parties. Where Party B submits a request within the data retention period under Section 2.6 or Section 7.4, Party A shall not delete the data within the scope of the request until the manual export is completed.