Terms of Service

Article 1 (Purpose)

These Terms define the conditions and procedures for using the Service, the rights, obligations and responsibilities of the Company and users, and other necessary matters.

Article 2 (Definitions)

1. “Service” means the Company’s technology and product website, its inquiry form, and the developer portal for managing company workspaces, projects and API keys and for providing APIs and documentation.
2. “User” means any visitor or member who uses the Service under these Terms.
3. “Member” means a user who has signed in to the developer portal with a Google account and entered into a use agreement. The Service does not create separate IDs or passwords; Google account authentication is the only sign-in method.
4. “Company workspace” means a space in the developer portal that a member creates for, or is invited to join on behalf of, a company or organisation, with permissions divided into roles such as Owner, Admin, Developer and Viewer.
5. “API key” means the credential a member issues in the developer portal to call the Company’s APIs. Sandbox keys (tk_test_) receive simulated responses; live keys (tk_live_) receive real service responses.
6. “Content” means all documents, images, examples, software and other material the Company publishes on the Service.

Article 3 (Posting and Amendment of the Terms)

1. The Company posts these Terms at the link in the Service footer (tridot.io/terms).
2. The Company may amend these Terms to the extent this does not violate applicable laws such as the Act on the Regulation of Terms and Conditions and the Act on Promotion of Information and Communications Network Utilization and Information Protection.
3. When amending the Terms, the Company announces the effective date and the reasons at least 7 days before the effective date. Changes unfavourable to members are announced at least 30 days in advance and also sent to the member’s registered e-mail.
4. A member who continues to use the Service without objecting by the effective date is deemed to have agreed to the amended Terms. A member who does not agree may terminate the use agreement.
5. The Company may set operating policies or separate terms for specific services (for example paid services or API usage conditions); where they differ from these Terms, the specific policy or terms prevail.

Article 4 (Content of the Service)

1. The Company provides:
   • an introduction to its technology, products and use cases, and public documentation;
   • receipt of and replies to inquiries about collaboration, adoption, hiring and similar matters;
   • the developer portal: company workspace and team management, project and API key issuance and management, API documentation and sandbox responses, and usage views.
2. The portal’s APIs and documentation open in stages. Registration or the issuance of an API key does not by itself guarantee the availability of a particular API, any service level or any release date. Each service’s status (sandbox, live or coming soon) is shown in the portal.
3. If paid services (credits, subscriptions and the like) are introduced, the Company will publish the fees, payment and refund conditions separately and apply them only after obtaining the member’s consent.

Article 5 (Formation of the Use Agreement)

1. The use agreement is formed when a user agrees to these Terms and the Privacy Policy, signs in to the developer portal with a Google account to apply, and the Company accepts the application.
2. The Company may refuse acceptance or later terminate the agreement where the applicant:
   • uses another person’s Google account or submits false information;
   • is under 14 years of age;
   • was previously restricted for violating these Terms;
   • cannot be served for technical or operational reasons.
3. Members must keep their registration details current through their Google account or the portal settings; the member bears any disadvantage arising from failing to do so.

Article 6 (Member Accounts and Company Workspaces)

1. Members are responsible for the security of their own Google account (password, two-step verification and so on) and may not transfer or lend the account to a third party.
2. A member who creates a company workspace (the Owner) and its Admins warrant that they are authorised to represent the company or organisation in inviting members, assigning roles, setting allowed e-mail domains, and managing projects and API keys.
3. Workspace members may use the Service only within the role granted by the Owner or an Admin. The member and the workspace are jointly responsible for the consequences of a member’s actions.
4. Invitation links expire after 7 days and can be accepted only with the Google account matching the invited e-mail address.

Article 7 (API Keys and Developer Service Rules)

1. An API key is shown only once at issuance; the Company stores only its hash. Members must keep keys secure and must not embed live keys in software distributed to end users, such as game clients or mobile apps.
2. If a key is leaked or suspected to be, the member must revoke it in the portal immediately and issue a new one. Use of the key before revocation is treated as the member’s use.
3. Members must not:
   • circumvent or disable the Service’s authentication, rate limits or quotas;
   • resell responses obtained through the API without the Company’s consent, or systematically collect them to build a competing service;
   • reverse-engineer or decompile Service software or attempt to extract its source code;
   • process content through the API that violates the law or third-party rights.
4. Sandbox responses are simulated data for integration preparation and do not represent real processing results or service performance.
5. To keep the Service stable, the Company may apply per-key and per-project rate limits and monthly caps; the applicable limits are shown in the portal.

Article 8 (Obligations of the Company)

1. The Company complies with applicable laws and these Terms and strives to provide the Service reliably.
2. The Company protects users’ personal information in accordance with data-protection laws and its Privacy Policy (tridot.io/privacy).
3. Where a user’s opinion or complaint about the Service is found to be justified, the Company handles it promptly; where prompt handling is not possible, the Company informs the user by e-mail of the reason and the expected schedule.

Article 9 (Obligations of Users and Prohibited Conduct)

Users must not:

1. misappropriate another person’s information or register false information;
2. impersonate the Company’s officers, employees or affiliates;
3. interfere with the normal operation of the Service or place excessive load on its servers or network;
4. infringe the intellectual property, reputation or personal information of the Company or third parties;
5. misuse another member’s account or API key;
6. use the Service for criminal activity or in violation of applicable law;
7. violate these Terms, operating policies or the Company’s notices.

Article 10 (Provision, Change and Suspension of the Service)

1. The Service is in principle available 24 hours a day, every day. The Company may temporarily suspend all or part of the Service for maintenance, expansion or replacement, and announces scheduled suspensions in advance.
2. The Company may suspend the Service without prior notice, announcing the reason afterwards, in the following cases:
   • urgent system failures, security incidents or the response to them;
   • force majeure such as power outages, natural disasters or national emergencies;
   • outages at hosting, authentication, cloud or other infrastructure providers.
3. The Company may change the content and delivery of the Service, the portal’s features and API contracts. Changes with a material effect on members (API discontinuation or incompatible changes) are announced at least 30 days before they take effect, with a transition period.
4. If the Company discontinues the Service as a whole, it gives 30 days’ notice and takes reasonable steps to let members export their data.

Article 11 (Intellectual Property and Data)

1. Copyright and other intellectual property in the Service and Content belong to the Company or the rightful owner. Users may not reproduce, distribute, transmit or create derivative works from Content without the Company’s prior written consent, except that public documentation may be consulted for integration development.
2. Rights in data that members enter into or send through the developer portal (project information, API request data and the like) belong to the member or their company or organisation. The Company processes such data only as necessary to provide the Service, maintain security, measure usage and comply with the law, and does not use it to train the Company’s AI models without the member’s consent.
3. The Company’s trademarks, logos and product names may not be used without the Company’s consent.

Article 12 (Restriction of Use and Termination)

1. A member may terminate the use agreement at any time by requesting account deletion at hello@tridot.io. The sole Owner of a company workspace must transfer ownership to another member or delete the workspace as well.
2. Where a member violates these Terms or disrupts the normal operation of the Service, the Company may issue a warning, suspend the account, revoke API keys or terminate the agreement. In the case of an urgent security threat the Company may act without prior notice and inform the member afterwards.
3. When the Company restricts or terminates use, it informs the member by e-mail of the reason and how to object. The member may object within 30 days of the notice.
4. On termination, the member’s account information and data are destroyed in accordance with the Privacy Policy, except for information that must be retained by law for the required period.

Article 13 (Damages and Disclaimer)

1. A party that causes damage to the other by violating these Terms is liable to compensate that damage.
2. The developer portal’s preview features, sandbox responses and public documentation are provided as is; the Company does not warrant fitness for a particular purpose or freedom from errors.
3. Unless caused by the Company’s wilful misconduct or gross negligence, the Company is not liable for damage arising from:
   • force majeure such as natural disasters, power outages or infrastructure provider outages;
   • causes attributable to the user (poor account or API key management, violation of these Terms and so on);
   • actions taken in reliance on information or materials obtained through the Service;
   • disputes between users or between a user and a third party.
4. For services provided free of charge, the Company’s liability for damages is limited to the extent permitted by law. The scope of liability for paid services is set out in the separate terms for those services.

Article 14 (Protection of Personal Information)

The Company processes users’ personal information in accordance with its Privacy Policy (tridot.io/privacy) and applicable law. The Company does not collect or store the password of the Google account used to sign in.

Article 15 (Governing Law and Jurisdiction)

1. Disputes concerning these Terms and the use of the Service are governed by the laws of the Republic of Korea.
2. The Company and users seek to resolve disputes by consultation first; failing that, actions are brought before the court having jurisdiction under the Civil Procedure Act of Korea. For users abroad, consumer protections under the mandatory laws of their country of residence are not excluded.
3. The Company is located in Seoul, Republic of Korea. These Terms are written in Korean and provided with an English translation; where the two differ, the Korean version prevails.

Article 16 (Supplementary Provisions)

1. These Terms take effect on September 18, 2026 and replace the “Website terms” in effect since September 11, 2026.
2. Business information: Tridot Inc. / Suite 604, 217 Yeoksam-ro, Gangnam-gu, Seoul, Republic of Korea / Business registration no. 372-81-01941 / Mail-order business report no. 2024-Seoul Gangnam-06300 / Contact hello@tridot.io