BackendX Terms of Use

Effective Date: April 25th, 2026 Last Updated: April 24th, 2026 Contact: team@email.backendx.ai

These Terms of Use ("Terms") govern the use of the BackendX service (the "Service") provided by BackendX Inc. (주식회사 백엔드엑스) (the "Company").

BackendX is a software-as-a-service (SaaS) platform that enables users to generate, deploy, and manage backend services online. The Service includes software features that process user-submitted requirements and configurations to generate outputs such as source code, infrastructure definitions, deployment-related artifacts, and related software-generated results.

By creating an account or using the Service, you ("User") agree to be bound by these Terms and related policies.

These Terms apply to users worldwide. Mandatory consumer protection rules of the User's country of residence may apply to the extent required by law.

1. Definitions

  1. "User" means any individual or legal entity using the Service.
  2. "Account" means a login identity created to access the Service.
  3. "Requirements" means any user-submitted descriptions, specifications, text, or configuration inputs.
  4. "Task" means a software-generated or software-processed unit of work requested through the Service, such as backend generation, modification, deployment-related execution, or related in-product workflows.
  5. "Credit" means a limited digital usage entitlement issued by the Company for use only within the Service. Credits may be granted as part of a Subscription, purchased separately as top-up Credits, or granted for promotional purposes.
  6. "Subscription" means a recurring paid plan that provides access to certain Service features and may include a recurring monthly Credit allotment.
  7. "Output" means any generated source code, configuration files, documents, scripts, or infrastructure definitions (IaC).
  8. "Access Token" means cloud API credentials provided by the User (e.g., AWS Access Key ID/Secret Access Key, STS session tokens, or equivalent credentials).
  9. "Credit Policy" means the separate policy governing issuance, validity, expiration, and refunds of Credits.

2. Service Phases and Deployment Modes

  1. The Service is currently operated in its Beta 2 phase. The Alpha phase has concluded. The Company may continue to operate the Service in successive phases (including subsequent beta phases and general availability) as the Service matures.
  2. The Service offers the following deployment modes:
    • Mode B — BackendX-Hosted (default). The Company hosts and operates the generated service on infrastructure managed by the Company. The Company acts as a controller or joint controller (together with the User) of end-user personal data processed through the generated service, as further described in the Privacy Policy and the Data Processing Agreement referenced in Section 11A.
    • Mode A — Customer-Cloud Deployment (planned). The Company will, in a future phase, offer the option for the User to deploy the generated service to the User's own cloud account. In that mode the User is the controller of end-user personal data and the Company's role is limited to the scope of a separate operational delegation arrangement. Mode A is not generally available during Beta 2.
  3. During Beta 2, the following scope limitations apply to all generated services hosted under Mode B:
    • End-user file uploads and file storage are not supported. The User must not enable or configure the generated service to accept, store, or serve files uploaded by end-users. Bring-your-own-S3 or equivalent customer-owned storage integrations will be offered in a later phase under a separate addendum.
    • Services in regulated verticals (including those enumerated in the Acceptable Use Policy in Section 8) are not supported and will be rejected at interview or deployment.
  4. The Company may add, modify, restrict, suspend, or discontinue any feature of the Service.

3. Accounts and User Responsibilities

  1. Users must provide accurate information and must not impersonate others.
  2. Users are responsible for safeguarding their Accounts and notifying the Company of any suspected unauthorized access.
  3. Users must not submit sensitive personal data or regulated information within Requirements except as expressly permitted by the Acceptable Use Policy in Section 8 and under a lawful basis applicable to the User. The Company applies the security measures described in the Privacy Policy but cannot guarantee against harm arising from submissions that violate these Terms or the Acceptable Use Policy.

4. Subscriptions, Credits, and Payments

  1. The Company may offer the Service on a subscription basis, on a pay-as-you-go basis, or through a combination of both.
  2. A Subscription may include a monthly Credit allotment. Unless otherwise expressly stated, monthly included Credits reset at the end of the applicable monthly billing period, do not roll over into the next billing period, and expire if unused.
  3. Users may also purchase additional Credits separately as top-up Credits. Unless otherwise expressly stated, purchased top-up Credits remain valid for twelve (12) months from the date of purchase and expire if unused after that period.
  4. Credits are used solely within the BackendX Service to access eligible software features and request or run eligible Tasks.
  5. Credits are not cash, electronic money, stored value, deposits, or payment instruments, and have no monetary exchange value outside the Service.
  6. Credits are non-transferable, non-resellable, and may not be assigned to or exchanged with any third party, except where required by applicable law or expressly permitted by the Company.
  7. Issuance, use, priority of use, validity, expiration, cancellation effects, and refunds (if any) are governed by the Credit Policy.
  8. During early Service phases (including the current Beta 2 phase), specific Subscription tiers, Credit purchase options, or payment methods may be unavailable, limited, or offered on a preview basis. The Company will disclose current availability through the Service.
  9. The Company may change Subscription tiers, included Credit amounts, Credit pricing, and feature access from time to time. Any such changes will be disclosed through the Service or by other reasonable means before they take effect for future billing periods, unless immediate changes are required by law, security, or abuse-prevention reasons.
  10. Unless otherwise expressly stated, the purchase of a Subscription or Credits does not include offline consulting, manual development services, or any physical goods.
  11. Automatic Renewal. Unless expressly stated otherwise at the time of purchase, Subscriptions automatically renew at the end of each billing period (monthly or annual, as applicable) for a successive period of the same length, and the Company (or its payment processor) will charge the User's designated payment method at the then-current price for the renewing period until the User cancels. By purchasing a Subscription, the User authorizes such recurring charges.
  12. Price-Change Notice. The Company will provide reasonable advance notice of any price increase that will apply at the next renewal, by email or through the Service, at least thirty (30) days before the increase takes effect (or such longer period as required by applicable law, including California Business & Professions Code §17602 and equivalent U.S. state automatic-renewal statutes). If the User does not wish to accept the new price, the User may cancel the Subscription before the renewal date; continued use after the effective date constitutes acceptance of the new price.
  13. Cancellation and "Easy Cancel." The User may cancel the Subscription at any time through the account settings within the Service or by contacting team@email.backendx.ai. Cancellation will take effect at the end of the then-current billing period, and the User will retain access to paid features until that date. The Company will not require the User to call, mail, or otherwise leave the online account-cancellation interface to cancel, consistent with the U.S. FTC "Click-to-Cancel" standard and California Automatic Renewal Law requirements for online cancellation.
  14. Renewal Reminder. Where required by applicable law (including, without limitation, Korea's Act on Consumer Protection in Electronic Commerce and U.S. state automatic-renewal statutes), the Company will send a renewal reminder before each automatic renewal, identifying the amount to be charged, the billing date, and cancellation instructions.
  15. Free Trials and Introductory Offers. Where a free trial or introductory-rate Subscription is offered, the Company will disclose in a clear and conspicuous manner before the User's acceptance: (a) the length of the trial or introductory period, (b) the price that will apply after the trial/introductory period ends, (c) the renewal cadence, and (d) how to cancel before being charged. For EU and EEA consumers, the Company will comply with the "button solution" in Article 8(2) of Directive 2011/83/EU by labeling the purchase button with an explicit obligation-to-pay indication (e.g., "Order with obligation to pay" / "Subscribe and pay").

5. EU and EEA Consumer Rights

  1. If you are a consumer residing in the European Union or European Economic Area, you benefit from any mandatory consumer protection rights granted to you by the laws of your country of residence. Nothing in these Terms limits or excludes those mandatory rights.
  2. Where the Service is supplied to an EU or EEA consumer as a digital service or digital content, the Company will provide the service in conformity with the contract and with mandatory applicable law, including any mandatory rights relating to remedies for failure to supply or lack of conformity.
  3. If you are an EU or EEA consumer purchasing a Subscription or other digital service at a distance, you may have a statutory 14-day right of withdrawal from the date of conclusion of the contract, except to the extent an exception or reduction applies under mandatory law.
  4. If you ask us to begin supplying a paid digital service during the withdrawal period, you expressly request immediate performance. Where mandatory law so requires, we will obtain the additional confirmations needed for immediate performance and will inform you of the consequences for your withdrawal right.
  5. If you validly withdraw from a contract after requesting immediate performance of a digital service during the withdrawal period, you may be required to pay a proportionate amount for the service supplied up to the time of withdrawal, to the extent permitted by applicable law.
  6. If mandatory law grants you a right to terminate due to a negative modification of the Service, lack of conformity, or failure to supply, you may exercise that right notwithstanding any other provision of these Terms.

6. Account Deletion

  1. Users may request account deletion at any time.
  2. Upon account deletion, the Account may be permanently removed and remaining Credits may be forfeited or expire in accordance with the Credit Policy.
  3. Account deletion does not automatically trigger a refund. Refund eligibility for Subscriptions and unused purchased Credits is governed by the Credit Policy and applicable laws.

7. Delivery of Outputs and GitHub Collaboration

  1. The Company may deliver Outputs through GitHub repositories under accounts or organizations owned or managed by the Company, including by inviting Users as collaborators.
  2. The Company may change the delivery method or repository structure at its discretion.
  3. The Company may not provide technical support for Outputs (e.g., debugging, operations, performance tuning, or security reviews), unless otherwise agreed in writing.

8. Acceptable Use Policy

8.1 General prohibitions

Users must not use the Service to:

8.2 Prohibited service categories (hard blocks)

The Service is not available for the generation, hosting, or operation of services in the following categories, and the Company may refuse generation or deployment for any service falling within them:

8.3 Soft-gate categories (allowed with additional terms)

The following categories are allowed subject to additional disclosures, warranties, and acceptance of the Data Processing Agreement referenced in Section 11A:

8.4 No end-user file uploads (Beta 2)

During Beta 2, Users must not enable, configure, or operate end-user file upload, file storage, or file serving features within a service hosted under Mode B. The Company does not provide and does not authorize such features in Beta 2. Customer-owned storage integrations (bring-your-own-S3 or equivalent) will be introduced in a later phase under a separate addendum.

8.5 User responsibility

Users are solely responsible for the legality, deployment, operation, and consequences of any service built using the Outputs, including the conduct of their end-users. The Company's acceptance or deployment of a generated service does not constitute legal advice, does not certify compliance with any law, and does not transfer to the Company any duty owed by the User to its end-users.

9. Automated Analysis and Illegal Use Detection

  1. To prevent unlawful use, abuse, violations of these Terms, and to reduce legal risk, the Company may analyze Requirements and related configuration inputs using automated methods.
  2. For this purpose, the Company may use third-party AI tools solely as auxiliary means to detect potential illegality or violations.
  3. Only the minimum information necessary is used, and such information is not provided for external model training, subject to provider constraints.
  4. Automated analysis results are supporting indicators only and do not constitute final legal determinations.

10. Monitoring Scope and Reactive Inspection

  1. The Company may review system metadata, configuration information, and traffic patterns to the minimum extent necessary for security, stability, and abuse prevention.
  2. The Company does not routinely access, scan, or inspect application-level end-user data (such as databases or application logs) stored within generated services. The Company does not perform proactive database-level scanning for illegal content.
  3. The Company may conduct a reactive inspection of a generated service — limited in scope to the minimum data necessary to verify the report or request — when triggered by any of the following:
    • a credible abuse report received through the Company's abuse-reporting channel or any other reasonable means;
    • a law-enforcement request, court order, or lawful request from a competent authority;
    • a payment-processor, cloud-provider, or trust-and-safety flag affecting the service;
    • a material inconsistency between interview or deployment-stage answers and the actual behavior or data of the deployed service;
    • a third-party complaint alleging infringement of intellectual property, privacy, or other legal rights.
  4. Where a reactive inspection touches end-user personal data, the Company acts under the Data Processing Agreement referenced in Section 11A and under applicable legal bases; the scope, timing, and actors involved are recorded in an internal audit log.
  5. Evidence preservation and law-enforcement cooperation. The Company may preserve evidence and disclose information to competent authorities as required or permitted by law. Disclosure will be limited to the minimum necessary to comply with the specific legal demand.
  6. User notification of law-enforcement requests. Where legally permitted, the Company will notify the User of a law-enforcement request, court order, or comparable legal demand concerning the User's Account or generated service before complying, to give the User an opportunity to seek a protective order or challenge the demand. Where notification is prohibited (such as under a lawful gag order or sealed subpoena), the Company will notify the User as soon as the legal restriction is lifted. The Company will publish its law-enforcement response policy at a stable URL on the Service and may publish periodic transparency reports regarding the volume and type of legal demands received.

11. Infrastructure Management Support and Access Tokens (Mode A)

  1. Where the Service is deployed in Mode A (to the User's own cloud account), and at the User's request, the Company may provide technical management or operational support within the User's cloud account (e.g., deployment, monitoring, scaling configuration, operational assistance). Such support may require a separate operational delegation agreement or addendum.
  2. The User may provide an Access Token to the Company for such support, and the Company may perform actions using that Access Token.
  3. The Company will act only within the scope of permissions granted by the User and will not exceed such permissions. The User should scope the Access Token narrowly to the tasks for which it is provided.
  4. The User is responsible for issuing, scoping, rotating, revoking, and securing the Access Token, and may revoke or deactivate the Access Token at any time.
  5. Final operational responsibility and decision-making authority remain with the User. The Company's support does not imply joint operation or joint liability, except as expressly set out in a separately signed Data Processing Agreement or operational delegation addendum.

11A. Deployment Acceptance, Data Processing Agreement, and End-User Privacy Notice (Mode B)

  1. DPA at deployment. Before a generated service may be deployed or begin operation under Mode B, the User must review and accept the Company's Data Processing Agreement (which, where applicable, includes a joint-controller arrangement under Article 26 of the GDPR and a consignment arrangement under Article 26 of PIPA). The Company will present the Data Processing Agreement for active acceptance at deployment time and will record the version hash, timestamp, and accepting user.
  2. Customer warranties. By deploying a generated service under Mode B, the User represents and warrants that:
    • the intended service is lawful in every jurisdiction in which its end-users are located;
    • the service does not fall within any of the prohibited categories in Section 8.2;
    • the categories of end-user personal data the service will collect have been accurately disclosed to the Company at interview and deployment;
    • the User has, or will have before the service becomes available to end-users, a lawful basis under applicable data-protection law for processing each category of end-user personal data;
    • the User has implemented, or will implement, age-verification and parental-consent mechanisms where required by applicable law;
    • the User will comply with the Acceptable Use Policy and will not introduce regulated-data categories (such as protected health information or payment-card data) into the service without the Company's prior written agreement.
  3. End-user privacy notice. The Company will generate an end-user privacy notice describing the data practices of the generated service and the Company's role as platform provider. The User must, before making the generated service available to end-users, either (a) use the generated end-user privacy notice verbatim and serve it at a stable URL of the generated service, or (b) incorporate the Company-supplied disclosure block verbatim into the User's own end-user privacy notice. The User warrants that the end-user notice delivered to end-users accurately reflects the service's actual data practices.
  4. Data-subject rights routing. The User will designate a privacy-contact email for rights requests from end-users. The Company will route end-user rights requests it receives to that email in the first instance, and the User will respond within the timeframes required by applicable law. Where the Company is a joint controller, the Company will cooperate in the handling of such requests as set out in the Data Processing Agreement.
  5. Breach notification flow. In the event of a personal-data breach, the Company will notify the User without undue delay (and in any case within twenty-four (24) hours of awareness) with the information required for the User to meet its own notification obligations to end-users and competent authorities. The User will notify affected end-users within the statutory timeframe (including, where applicable, the 72-hour window under GDPR Article 34 and equivalent PIPA requirements). The Company may notify end-users directly only where necessary to comply with a direct legal duty or where the User is unresponsive.
  6. Customer indemnity. To the maximum extent permitted by applicable law, the User will indemnify, hold harmless, and — where permitted under the applicable jurisdiction — defend the Company and its officers, directors, employees, and agents from and against any third-party claim, demand, proceeding, or governmental action arising out of or relating to: (a) the User's breach of the warranties in Section 11A.2; (b) the legality or operation of the service deployed by or on behalf of the User; (c) the content or conduct of the User's end-users; (d) the User's failure to deliver a compliant end-user privacy notice or to respond to end-user rights requests; or (e) the User's introduction of undisclosed regulated-data categories into the service. The User's obligation includes payment of damages, settlements, fines, and reasonable attorney fees and costs. The Company will (i) promptly notify the User of any such claim, (ii) cooperate reasonably with the User's handling of the claim at the User's expense, and (iii) have the right, but not the obligation, to control the defense of any claim subject to this indemnity with counsel of its choosing, at the User's expense, in which case the User may not settle the claim without the Company's consent. Nothing in this Section limits mandatory consumer rights where applicable.
  7. Reservation of rights. The Company may refuse, delay, or reverse deployment where, in its reasonable judgment, the User's answers at interview or deployment are inconsistent with the actual generated service, with the Acceptable Use Policy, or with applicable law. Refusal at deployment does not entitle the User to a refund of Credits consumed for generation, subject to the Credit Policy and applicable law.

12. Automated Deployment and Scaling

  1. Automated deployment (e.g., deploy on source code updates) and automated scaling (e.g., scale when load thresholds are reached) may be offered as optional features.
  2. Responsibility for enabling, configuring (thresholds, scope, targets), and outcomes of such features remains with the User.
  3. Where the Company executes automation under Mode A using an Access Token, it will do so only within the User-configured settings and permission scope granted by the User. Where the Company executes automation under Mode B, it will do so in accordance with the Data Processing Agreement referenced in Section 11A.

13. Suspension, Restriction, and Termination

  1. If the Company reasonably suspects a violation of these Terms, the Acceptable Use Policy, or applicable laws, or if a reactive inspection under Section 10 identifies a material concern, the Company may suspend, restrict, or terminate access to the Service without prior notice. Where circumstances permit, the Company will notify the User of the reason and provide an opportunity to respond.
  2. The Company may temporarily suspend the Service for security, maintenance, outages, or legal or regulatory reasons.
  3. The Company may retain logs and records as necessary for security, audit, dispute resolution, and compliance with applicable laws, in accordance with the retention periods in the Privacy Policy.
  4. Upon termination, the Company may cease hosting the User's generated service under Mode B. The Company will, where reasonably feasible and subject to applicable law, provide the User a reasonable opportunity to export the Outputs and data stored within the generated service.
  5. If you are an EU or EEA consumer and mandatory law grants you a remedy because the Service is not supplied, is not in conformity, or is modified in a way that negatively affects your access to or use of the Service beyond what mandatory law allows, those remedies remain available to you.

14. Intellectual Property

  1. User content. As between the Company and the User, the User retains all rights, title, and interest in and to Requirements, configurations, and other content submitted by the User.
  2. Assignment of Outputs. Subject to Section 14.3 (third-party licenses), the User's compliance with these Terms, and payment of applicable fees, the Company hereby assigns to the User all of the Company's rights, title, and interest in the Outputs delivered to the User, to the maximum extent such rights are assignable under applicable law. Where such rights are not assignable, the Company grants the User a worldwide, perpetual, irrevocable, royalty-free, sublicensable license to use, reproduce, modify, distribute, and create derivative works of the Outputs.
  3. Third-party components. Outputs may include third-party components, including open-source software. Such components remain subject to their respective license terms, and nothing in Section 14.2 purports to assign rights the Company does not hold.
  4. Back-license to the Company. The User grants the Company a worldwide, non-exclusive, royalty-free license to use Requirements, configurations, and Outputs solely as necessary to provide, secure, operate, and improve the Service, to comply with legal obligations, and to exercise the Company's rights under these Terms. This license does not authorize use of Requirements for training the Company's own AI models except where separate consent has been obtained.
  5. Company marks and platform. The BackendX name, logo, and platform software are and remain the Company's intellectual property. No right, title, or interest in Company marks or the underlying platform is transferred to the User.
  6. Feedback. Where the User voluntarily provides feedback or suggestions regarding the Service, the User grants the Company a perpetual, irrevocable, royalty-free license to use such feedback without restriction.
  7. No warranty on Outputs. The Company makes no warranties regarding the accuracy, completeness, security, legality, or fitness of Outputs for any purpose, except as expressly provided in these Terms or required by mandatory applicable law.

15. Third-Party Services

The Service may integrate with third-party services such as GitHub, AWS, and external AI tools. The Company is not responsible for third-party outages, policy changes, suspensions, or limitations, except to the extent caused by the Company's willful misconduct or gross negligence.

16. Disclaimer and Limitation of Liability

  1. Except as expressly required by mandatory applicable law (including, without limitation, mandatory conformity and remedy rights granted to consumers in the European Union, European Economic Area, and United Kingdom, and mandatory consumer-protection rights under the laws of the User's country or state of residence), the Service and Outputs are provided on an "AS IS" and "AS AVAILABLE" basis, and to the maximum extent permitted by law, the Company disclaims all warranties, whether express, implied, statutory, or otherwise, including warranties of merchantability, fitness for a particular purpose, non-infringement, and uninterrupted or error-free operation. Nothing in this Section limits any non-excludable statutory warranty or consumer right.
  2. Users are solely responsible for the legality and operation of services built using the Outputs.
  3. Subject to Section 16.5, and to the maximum extent permitted by applicable law, the Company's total aggregate liability arising out of or relating to these Terms or the Service is limited to the greater of (a) the fees actually paid by the User to the Company during the six (6) months immediately preceding the event giving rise to the claim, or (b) one hundred U.S. dollars (USD 100). Where the Service is provided free of charge (e.g., during beta phases, trials, or other no-charge offerings), the Company's liability is limited to the maximum extent permitted by applicable law.
  4. Subject to Section 16.5, and to the maximum extent permitted by applicable law, the Company shall not be liable for any indirect, special, incidental, consequential, exemplary, or punitive damages, including loss of profits, revenue, data, goodwill, or reputation, even if advised of the possibility of such damages.
  5. Carve-outs. Nothing in Sections 16.1, 16.3, or 16.4 shall exclude or limit the Company's liability for: (a) death or personal injury caused by the Company's negligence; (b) fraud or fraudulent misrepresentation; (c) willful misconduct or gross negligence; (d) any other liability that cannot be excluded or limited under applicable mandatory law (including mandatory EU, EEA, UK, U.S. state, or Republic of Korea consumer-protection rules).
  6. Some jurisdictions do not allow the exclusion or limitation of certain warranties or damages; in such jurisdictions, the exclusions and limitations in this Section apply only to the maximum extent permitted by law, and the User may have additional rights.

17. Amendments

The Company may amend these Terms due to changes in laws or Service operations. Material changes will be announced through the Service or by other reasonable means. Continued use after the effective date constitutes acceptance of the amended Terms, except to the extent mandatory law requires a different consequence or gives the User a right to terminate.

18. Governing Law and Jurisdiction

  1. These Terms are governed by the laws of the Republic of Korea, without regard to conflict-of-laws rules.
  2. Non-consumer disputes. If you are not a consumer, all disputes arising out of or in connection with the Service, these Terms, or the relationship between the parties shall be subject to the exclusive jurisdiction of the Seoul Central District Court of the Republic of Korea as the court of first instance.
  3. Consumer disputes — choice of law. If you are a consumer, the choice of Korean law in Section 18.1 does not deprive you of any mandatory protection afforded to you by the laws of your country or state of residence that cannot be derogated from by agreement, including (where applicable) mandatory consumer-protection rules under the laws of the European Union and its Member States, the European Economic Area, the United Kingdom, the Republic of Korea, and the individual states of the United States.
  4. Consumer disputes — forum. If you are a consumer residing in the European Union or the European Economic Area, you may bring proceedings against the Company in the courts of the Member State in which you are domiciled, and the Company may bring proceedings against you only in those courts, in accordance with Articles 17 to 19 of Regulation (EU) No 1215/2012 (Brussels Ia). Consumers residing in the United Kingdom retain equivalent rights under applicable United Kingdom law. Consumers residing in the United States retain the right to bring proceedings in their home forum to the extent that any exclusive forum clause would not be enforceable against them. The jurisdiction clause in Section 18.2 does not apply to, and is not intended to limit, any such consumer.
  5. Nothing in this Section prevents either party from seeking urgent injunctive or equitable relief from a court of competent jurisdiction where necessary to protect intellectual-property rights, prevent unauthorized access to the Service, or otherwise protect rights pending resolution of a dispute.

19. Force Majeure

Neither party will be liable for any failure or delay in performance caused by events beyond its reasonable control, including acts of God, natural disasters, epidemic or pandemic, war, civil unrest, terrorism, governmental action or regulation, labor disputes, power or telecommunications failures, denial-of-service or other cyberattacks, or the failure or interruption of third-party services (including upstream cloud or AI providers) on which the Service depends. The affected party will notify the other of the event and use reasonable efforts to mitigate its effects. This Section does not excuse payment obligations already accrued.

20. Assignment

  1. The User may not assign, transfer, or delegate these Terms or any rights or obligations under them without the Company's prior written consent. Any purported assignment in violation of this Section is void.
  2. The Company may assign, transfer, or delegate these Terms in connection with a merger, acquisition, corporate reorganization, or sale of all or substantially all of its assets, or to an affiliate. Where required by applicable law, the Company will provide affected Users with prior notice and, where applicable, an opportunity to terminate.

21. Severability

If any provision of these Terms is held invalid, illegal, or unenforceable by a court or regulator of competent jurisdiction, that provision will be modified to the minimum extent necessary to be enforceable (and if not modifiable, will be severed), and the remaining provisions will continue in full force and effect.

22. Entire Agreement and Order of Precedence

  1. These Terms, together with the Privacy Policy, the Credit Policy, the Acceptable Use Policy in Section 8, and any Data Processing Agreement or other written agreement executed by the parties, constitute the entire agreement between the User and the Company with respect to the Service and supersede all prior or contemporaneous understandings, communications, and agreements, whether written or oral.
  2. In the event of a conflict among these documents, the following order of precedence applies:
    • first, any written agreement separately signed by the parties (such as an enterprise agreement or a Data Processing Agreement);
    • second, these Terms of Use;
    • third, the Credit Policy (for matters relating to Credits, Subscriptions, and payments);
    • fourth, the Privacy Policy (for matters relating to the processing of personal data; provided that, for conflicts on data-protection terms, the Privacy Policy prevails over these Terms).

23. Notices

  1. The User may deliver legal notices to the Company by email to legal@backendx.ai, with a copy to team@email.backendx.ai, and, where required by applicable law, by mail to the Company's registered office address in the Republic of Korea.
  2. The Company may deliver notices to the User by email to the address associated with the User's Account, through an in-product notification, or by posting a notice on the Service. Notice is deemed received when sent by email or when posted prominently in the Service.
  3. It is the User's responsibility to keep the Account email address current. The Company is not responsible for notices that fail to reach the User due to an outdated or inaccurate Account email address.