ABTO

Terms of Service

Effective date: September 14, 2026

Article 1. Purpose

These Terms set out the rights, obligations, responsibilities, and other necessary matters between ABTO (the “Company”) and users of the ABTO service (the “Service”).

Article 2. Definitions

The following terms have these meanings:

  1. “Service” means the following functions provided through abto.app, docs.abto.app, api.abto.app, their subdomains, and SDKs distributed by the Company:
    • AI gateway: forwards large language model (LLM) requests from a user’s application to the model provider selected by the user, such as OpenAI, Anthropic, or Google, and returns the response.
    • Model A/B testing and routing: assigns a user’s end users to different models by feature and routes requests to models whose outcomes have been evaluated.
    • Event collection and conversion analysis: connects behavior events sent by the installed Client SDK with model calls to analyze costs, latency, and conversions and display them in the dashboard.
  2. “User” means an individual or legal entity that agrees to these Terms and enters into an agreement with the Company to use the Service.
  3. “Organization” means the unit that groups a user’s projects, API keys, billing, and plans within the Service. The user who creates an Organization becomes its owner.
  4. “End user” means a user’s customer who uses an application or website integrated with the Service.
  5. “User data” means data a user sends to the Company’s systems while using the Service, including LLM request and response bodies, events collected by the Client SDK, and settings and identifiers entered by the user.
  6. “API key” means a gateway calling key or event collection key issued to authenticate a user.
  7. “Model provider key” means an authentication key that a user obtains in their own name from an external model provider, such as OpenAI, Anthropic, or Google, and sends with gateway requests.

Article 3. Publication and Changes to the Terms

  1. The Company publishes these Terms in the Service and at abto.app/terms/ so users can easily access them.
  2. The Company may amend these Terms to the extent permitted by applicable laws, including the Act on the Regulation of Terms and Conditions, the Act on the Consumer Protection in Electronic Commerce, etc., 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 reasons for the change alongside the current Terms in the Service from seven days before the effective date until the preceding day. Changes that are material or unfavorable to users are announced 30 days in advance and also sent to the email address registered at signup.
  4. A user who continues using the Service without expressing disagreement by the effective date is deemed to have accepted the amended Terms. A user who does not agree may terminate the agreement.
  5. Matters not covered by these Terms follow applicable laws, the Company’s separate policies, and guidance displayed in the Service.

Article 4. Entering into an Agreement

  1. An agreement is formed when a person agrees to these Terms and the Privacy Policy, applies through the Company’s signup process, and the Company accepts the application.
  2. Users sign up with an email address and password or a Google account. Email signup requires verification using a code sent by the Company.
  3. The Service is intended for individuals and legal entities developing or operating software for business purposes. Children under 14 may not sign up.
  4. A person signing up on behalf of a legal entity or organization warrants that they are authorized to represent it. In that case, the legal entity or organization is the User under these Terms.
  5. The Company may reject an application or subsequently terminate an agreement if:
    • Another person’s email address or information is used without authorization.
    • False information is provided or required information is withheld.
    • A previous agreement was terminated for violating these Terms.
    • Capacity constraints or technical problems prevent normal service provision.
    • The application otherwise violates applicable laws or is intended to undermine public order or accepted standards of conduct.

Article 5. Accounts and API Keys

  1. Users are responsible for securely managing their accounts, passwords, and API keys and may not transfer or lend them to third parties.
  2. If an account or API key has been compromised or exposed, the user must immediately revoke the affected key in the dashboard and notify the Company. The Company is not responsible for use occurring before notification.
  3. The Company does not store raw API keys. A key is displayed only once when issued. A lost key must be replaced with a newly issued key.
  4. Model provider keys sent with gateway requests are used only while processing the request and are not stored after it ends. Users are responsible for obtaining and managing these keys and for the associated usage and charges.

Article 6. Service Provision and Changes

  1. The Company provides the functions in Article 2, paragraph 1. Details and usage instructions are available in the integration guides at docs.abto.app.
  2. The Service is generally provided 24 hours a day throughout the year. The Company may temporarily suspend all or part of it for maintenance, equipment replacement, incident response, or other operational needs, with advance notice through the dashboard or email. For urgent circumstances where advance notice is difficult, notice is provided afterward.
  3. To improve quality or meet operational needs, the Company may add or change functions, interfaces, supported providers, and model lists. Changes with a material impact on users are announced in advance.
  4. During a trial period before general release, functions, plans, and service scope may change without advance notice. The Company improves the Service based on user experience during this period and informs users of changes.
  5. The Company cannot control and does not guarantee external providers’ response content, speed, availability, or policy changes.

Article 7. Plans and Payments

  1. The Service offers a Free plan, a Pro plan with 30 days of access per one-time payment, and an Enterprise plan under a separate contract. Prices, VAT treatment, call allowances, event retention, and other plan limits follow the information published at abto.app and in the dashboard billing screen. The Company may change plan structures or add plans.
  2. The Free plan is available immediately after dashboard signup without a separate payment.
  3. If Free or Pro usage exceeds published allowances and affects service stability, the Company may limit an Organization’s request throughput or some analytics functions. This does not block the application’s requests to its model provider, and the Company notifies the user by email when applying a limit. The Company may adjust plan allowances and gives 30 days’ notice of unfavorable adjustments.
  4. A Pro payment provides access for 30 days from the payment date, ending at the end of the day 30 days after that date. There is no automatic renewal. Continued access requires another payment; otherwise, the Organization switches to the Free plan when access ends.
  5. Enterprise is provided after a quote consultation under a separate contract. That contract sets prices, payment methods, billing cycles, duration, scope, and support. It prevails where it differs from these Terms.
  6. Paid plans are paid by credit or debit card. Card details are entered in and processed by the payment provider’s (NICE Payments) payment window. The Company neither receives nor stores card details.
  7. Pro is not activated if payment fails, for example due to a card limit or expiration. The user may retry. Enterprise payment failures are handled under the separate contract.
  8. The Company may change prices. Increases are announced by email and through the dashboard 30 days before taking effect and do not apply to already-paid periods or ongoing Enterprise contract periods.
  9. Card receipts are issued through the payment provider’s process.

Article 8. Termination, Withdrawal, and Refunds

  1. Pro ends without a separate cancellation process when the paid period expires, and the Organization switches to Free. Stopping use during the period does not prevent access for the remainder; refunds follow paragraph 5.
  2. Enterprise termination dates, notice methods, and treatment of remaining contract periods follow the separate contract. Where it does not specify otherwise, users may notify contact@abto.app at any time, with termination taking effect at the end of the current billing cycle, followed by a switch to Free.
  3. Users may withdraw from a paid plan within seven days of payment, regardless of whether they have used the Service.
  4. When withdrawal is accepted, the Company refunds the full payment to the original payment method through the payment provider within three business days of confirming the request. Card issuers may take additional time to reflect it.
  5. After seven days, unused time is not refunded when a user stops using or terminates the Service mid-period unless the contract provides otherwise. If the Service was unavailable due to the Company’s fault, the Company refunds the corresponding charges or extends access.
  6. The Company may decline to refund charges already paid if the agreement is terminated for a violation of these Terms.
  7. Payment and refund inquiries are received at contact@abto.app and handled without delay. Detailed procedures are set out in the Payment and Refund Policy.

Article 9. User Obligations

  1. Users must not:
    • Register false information at signup or when changing account information.
    • Steal or misuse another person’s account, API key, or model provider key.
    • Place abnormal loads on the Service, servers, or networks, or interfere with normal operations.
    • Bypass security controls or reverse-engineer, copy, or redistribute the Service’s source code.
    • Infringe the Company’s or a third party’s intellectual property, privacy, or other rights.
    • Use the Service to generate or transmit content contrary to applicable laws, provider policies, or public order.
    • Copy, sell, or provide information obtained through the Service to third parties for profit without the Company’s prior approval.
  2. Users must comply with applicable laws, these Terms, usage policies, and integration guides when using the Service.
  3. Users must promptly update their registered email address and billing information in the dashboard when they change and bear the consequences of failing to do so.

Article 10. Responsibility for End Users

  1. Before integration, users must inform end users about data processing through the Service and fulfill the notice, consent, and disclosure obligations for outsourced processing required by applicable laws, including the Personal Information Protection Act.
  2. For end-user personal information, the user is the controller and the Company is the processor acting on the user’s instructions. The Company does not use end-user data outside those instructions, these Terms, or the Privacy Policy.
  3. By default, the Client SDK does not collect input field contents, on-screen text, or raw prompts and responses. Users are responsible for the necessary legal basis if they enable broader collection or provide identifying end-user values through the SDK’s identification function.
  4. Users must design their applications so LLM request and response bodies do not contain sensitive information such as resident registration numbers, payment information, or health information. If such information must be sent, users may turn off body storage in project settings.

Article 11. Processing and Rights in User Data

  1. Users retain rights in their data. The Company processes it only as necessary to provide, operate, and improve the Service and does not sell it or use it to train the Company’s AI models.
  2. The Company stores gateway LLM request and response bodies so users can view them in the dashboard. Bodies are automatically deleted 30 days after storage. Users may turn off body storage in project settings, in which case only metadata such as token counts, costs, latency, and models is recorded.
  3. User data is stored on cloud infrastructure in the Republic of Korea and encrypted at rest and in transit. Detailed safeguards are described in the Privacy Policy.
  4. On termination, the Company deletes user data without delay except information that must be retained by law. Users are responsible for downloading their data before deletion.
  5. The Company may create and use aggregated information that does not identify users for operational statistics, incident analysis, and billing calculations.

Article 12. Intellectual Property

  1. The Company owns intellectual property rights in its software, documentation, designs, and trademarks related to the Service.
  2. While the agreement remains in effect, the Company grants users a non-exclusive, non-transferable right to use the Service and distribute the SDK within their applications. SDKs distributed under separate open-source licenses follow those licenses.
  3. Rights in content generated or transmitted through the Service and resulting LLM responses follow the agreement between the user and the provider. The Company claims no rights in them.

Article 13. Company Obligations

  1. The Company does not engage in acts prohibited by law or these Terms or contrary to public order and strives to provide stable service.
  2. The Company publishes a Privacy Policy and maintains safeguards under it to protect personal information and user data.
  3. The Company promptly handles user feedback or complaints it considers justified. If handling requires time, it explains the reason and schedule by email.

Article 14. Termination and Usage Restrictions

  1. Users may terminate their agreement by requesting account deletion at contact@abto.app at any time. For Pro, remaining access ends with account deletion and refunds follow Article 8. Enterprise plan termination follows the separate contract.
  2. After prior notice, the Company may restrict access or terminate an agreement for violations of Article 9 or the following reasons. If urgent action is needed to protect the Service or other users, it may restrict access first and give notice afterward:
    • Automated abuse that imposes a serious load on service infrastructure.
    • Legal or provider-policy violations that could subject the Company to third-party sanctions.
    • Confirmed misuse of payment methods.
  3. If a user has not logged in for at least one year, the Company may make the account dormant or delete it after email notification.

Article 15. Limits of Liability

  1. The Company is not liable for inability to provide the Service due to circumstances beyond its control, including natural disasters, war, power outages, telecommunications or cloud-provider failures, or model-provider failures or policy changes.
  2. The Company is not liable for disruptions caused by a user’s fault or for failure to obtain expected revenue or outcomes from the Service.
  3. The Company does not guarantee the accuracy, legality, or suitability of LLM responses. Users are responsible for deciding whether to provide them to end users and for the consequences. Model comparisons and routing results are references that assist users’ decisions; users make the resulting business judgments.
  4. Unless the Company acted intentionally or with gross negligence, its liability for damages does not exceed the total fees the user paid during the three months before the damages occurred. For Free users, the Company is liable only for intentional acts or gross negligence.
  5. This Article does not limit liabilities that applicable law does not permit to be excluded.

Article 16. Notices

  1. The Company may send notices to the email address registered at signup.
  2. Notices to all users may be posted in the dashboard or at abto.app for at least seven days instead of individual notices. Matters materially affecting a user’s transactions are notified individually.

Article 17. Disputes

  1. The Company and the user seek to resolve disputes through mutual consultation.
  2. These Terms and use of the Service are governed by the laws of the Republic of Korea.
  3. Unresolved disputes may be brought before the court with jurisdiction under the Civil Procedure Act.

Supplementary Provisions

  1. These Terms take effect on September 14, 2026.
  2. Business information:
    • Business name: ABTO (앱토)
    • Representative: Donghyeok Kang
    • Business registration number: 252-28-02127
    • Ecommerce permit number: 2026-서울용산-0995
    • Address: Room 305, 201-17 Cheongpa-ro, Yongsan-gu, Seoul, Republic of Korea (Munbae-dong, G&P Yongsan Park)
    • Phone: 070-4571-7854
    • Email: contact@abto.app