Noof Terms of Service (v1.0)
These Terms of Service set forth the rights, obligations, and responsibilities between Onboarders Co., Ltd. (the “Company”) and the using organization and its users in connection with the use of the Noof service provided by the Company.
Article 1 (Purpose)
These Terms aim to clearly define the conditions of use, nature of the service, scope of responsibility, and usage limitations of the Noof service provided by the Company, and to govern the legal relationship between the Company and the using organization.
Article 2 (Definitions)
- Service means the Noof managed operations service and related platform provided by the Company.
- Using Organization means a corporation or entity that agrees to these Terms and uses the Noof service.
- User means an individual who belongs to the using organization and uses the service.
- Workspace means a service usage space created per using organization.
- Operations Policy means a reference document that explains the actual operational methods, scope, and procedures of the service.
Article 3 (Nature and Scope of the Service)
- Noof is not merely a software provision service, but a managed operations service (MSP) in which the Company directly accesses customer infrastructure to perform operational tasks such as deployment, monitoring, backup, and incident response.
- While the Company performs operational tasks, it does not guarantee specific outcomes (including uninterrupted service, complete resolution of incidents, or business performance).
- The detailed operational methods and scope of the service shall be governed by these Terms and the Operations Policy.
Article 4 (Effectiveness and Amendment of the Terms)
- These Terms become effective upon the using organization’s registration for the service or upon consent by its authorized representative.
- The Company may amend these Terms to the extent permitted by applicable laws.
- In the event of an amendment, the Company shall notify users of the changes, effective date, and deadline for consent through in-service notices or individual notifications.
- If the using organization does not provide consent by the specified deadline, the Company may restrict or suspend the use of the service.
Article 5 (Organization-Level Consent and User Notice)
- The party providing consent to these Terms is the using organization, and consent must be given by its representative or a person with equivalent authority.
- Users may use the service only if their organization has agreed to these Terms.
- If new consent is required due to amendments to these Terms:
- The Company shall request consent from the owner of the using organization.
- Users shall be notified that “consent from the owner is required.”
- If consent is not provided within the specified period, access to and operation of the service may be restricted.
Article 6 (Status of the Operations Policy)
- The Operations Policy is an explanatory document regarding service operations and does not require separate consent.
- The Operations Policy is used as a reference for interpreting these Terms and for operating the service.
- The Company may amend the Operations Policy and shall notify such changes through in-service notices.
Article 7 (Access Rights and Duty of Cooperation)
- The Company may access customer systems, servers, and databases within the scope necessary to provide the service.
- The using organization shall cooperate by providing necessary information, granting access rights, and participating in decision-making to ensure smooth operation.
- If access is restricted or cooperation is not provided, service quality may deteriorate or operations may be suspended, and the Company shall not be liable for such consequences.
Article 8 (Restriction and Suspension of Service)
The Company may restrict or suspend the provision of the service in any of the following cases:
- Failure to obtain organization-level consent to amendments to the Terms
- Termination or expiration of the contract
- Material violation of these Terms
- Revocation of access rights or circumstances making operation impossible
- Requirements under laws or by relevant authorities
In such cases, the Company shall not be liable for the consequences of service suspension.
Article 9 (Limitation of Liability)
- While the Company performs operational tasks in good faith, it shall not be liable for the following:
- Revenue, user numbers, or business outcomes of the customer’s service
- Uninterrupted service operation or any guaranteed availability level
- Issues inherent in the customer’s code, configuration, or data
- Failures or policy changes of third-party services (e.g., AWS, Vercel)
- Damages arising from the customer’s internal decision-making
- Even if the Company’s liability for damages is recognized, the maximum amount of compensation shall not exceed the total fees paid by the using organization to the Company for the relevant service during the most recent three (3) months.
Article 10 (Handling Upon Contract Termination)
- Upon termination of the contract or suspension of the service, the Company does not guarantee the continuation of operations.
- The availability and method of data return or backup provision shall be governed by a separate agreement or the Operations Policy.
Article 11 (Governing Law and Jurisdiction)
- These Terms shall be governed by the laws of the Republic of Korea.
- Any dispute arising between the Company and the using organization in connection with the service shall be subject to the exclusive jurisdiction of the court having jurisdiction over the Company’s principal place of business.
Document Version: v1.0
Date: 2026-01-21
If you have any questions about these Terms of Service, please contact us.