Service Level Agreement

Article 1 (Purpose)

• 1. The purpose of this SLA is to define the standard service levels, support policies, scope of maintenance, incident response procedures, applicable conditions, and other necessary matters regarding the Services provided by Party A.
• 2. This SLA establishes operational standards aimed at improving the quality of the Service and clarifying its operations; unless Party A has expressly agreed otherwise in writing or by electronic means, it does not constitute a warranty, representation, obligation to achieve specific results, minimum performance obligation, quantifiable obligation enforceable upon demand, or strict deadline compliance obligation.

Article 2 (Scope of Application)

• 1. This SLA shall apply in conjunction with the User Agreement, Terms of Service, individual contracts, specific application terms, and other contractual terms relating to the Service (hereinafter collectively referred to as the “Superior Agreements, etc.”) entered into between Party A and Party B.
• 2. In the event of any inconsistency or conflict between this SLA and any higher-level agreement, the following documents shall apply in order of priority: individual application terms, the Service Agreement, the Terms of Service, this SLA, and any other specific provisions.
• 3. Matters not specified in this SLA shall be governed by the master agreement or other applicable agreements.
• 4. This SLA establishes service levels and maintenance policies; limitations of liability, disclaimers, maximum liability for damages, payment terms, refunds, termination, contract expiration, data deletion, and other legal rights and obligations shall be governed by the master agreement or other applicable agreements.

Article 3 (Basic Policy)

• 1. Party A shall endeavor, to the extent commercially reasonable, to maintain continuous availability, ensure stable operation, and provide incident response and maintenance support for this Service.
• 2. The service levels, response times, response policies, reporting policies, recovery policies, uptime targets, and all other figures, benchmarks, standards, or examples set forth in this SLA constitute Party A’s performance targets and operational guidelines and do not constitute a warranty, representation, enforceable obligation, minimum performance requirement, or obligation to achieve a specific result.
• 3. Even if Party B suffers any damage or disadvantage in connection with this SLA—including failure to meet this SLA, the occurrence of an outage, the time required to restore service, the necessity or timing of a permanent fix following a temporary restoration, delays in responding to inquiries, unknown causes, recurrences, or other matters—Party A shall not be automatically liable for any monetary obligations, including refunds, fee reductions, liquidated damages, service credits, compensation, or damages, unless Party A acted with intent or gross negligence.
• 4. Party B may not refuse to fulfill, set off, withhold, deduct, or reduce any payment obligations to Party A—including usage fees, paid maintenance fees, and all other payments—nor may Party B assert termination of the Agreement solely on the grounds of failure to meet this SLA, the occurrence of an outage, the length of recovery time, the handling of inquiries, investigation results, failure to implement permanent corrective measures, or any other circumstances related to this SLA.
• 5. If Party A has separately and explicitly stipulated any matters in individual contracts, individual application terms, quotations, purchase orders, written documents, or electronic communications, such stipulations shall take precedence.

Article 4 (Definitions)

The meanings of the terms used in this SLA shall be as defined in the parent agreement or other relevant documents, and as set forth in the following items.

• 1. “Service Outage” means a situation in which, due to a malfunction in the systems, networks, or applications under Party A’s control, the Service—in whole or in part—cannot be used as normally intended or becomes significantly difficult to use.
• 2. “Major Outage” means a disruption of the Service’s core functions, a significant decline in performance, a major impact on a large number of users, a major security impact, or any other disruption that Party A reasonably deems to be major.
• 3. “Downtime” means the period of time calculated from the point specified in Article 10 until Party A confirms that the service has been restored.
• 4. “Service Restoration” means the time when Party A, based on a reasonable determination, confirms that the relevant functions or systems related to the Service have been restored to a state in which they are normally available for use.
• 5. “Free Maintenance” refers to corrective actions taken by Party A to the extent deemed reasonably necessary by Party A when normal use of the Service is impeded due to malfunctions, defects, bugs, or failures attributable to Party A.
• 6. “Paid Maintenance” refers to maintenance, operational support, investigations, analysis, configuration changes, modifications, improvements, performance tuning, compliance support, preventive measures, data-related support, migration support, training support, audit support, submission of audit trails, after-hours support, support on non-business days, emergency response, and all other related services that exceed the scope of the free maintenance specified in the preceding paragraph.
• 7. “Provisional restoration” refers to a state in which the use of all or part of the Service has been resumed prior to the completion of a permanent solution, through workarounds, temporary measures, switching to an alternative configuration, limited resumption, or any other method deemed necessary by Party A.
• 8. “Permanent Resolution” means a permanent correction or improvement measure that Party A deems reasonably necessary to address the cause of a failure or malfunction.
• 9. “Official Receipt” means the point in time at which Party B notifies Party A of a malfunction or inquiry through the designated contact point and method specified by Party A, and Party A confirms receipt thereof.
• 10. “Third-Party Services” means cloud platforms, telecommunications carriers, authentication platforms, API providers, operating systems, browsers, external software, libraries, middleware, and any other services, products, or environments provided or managed by third parties other than Party A.

Article 5 (Scope)

• 1. The scope of this SLA shall be limited to those components of the Service that are managed by Party A, including the system infrastructure, applications, system APIs, and infrastructure network, as well as any associated components.
• 2. This SLA shall not apply to equipment, terminals, lines, communication environments, operating systems, browsers, third-party services, third-party software, Party B’s usage environment, Party B’s data, or any other incidents arising therefrom, unless expressly provided otherwise.
• 3. Even if Party A provides the Service via a third-party service, the availability, performance, continuity, modification, suspension, termination, or malfunction of such third-party service itself shall be excluded from the scope of this SLA.

Article 6 (Official Registration and Support Desk)

• 1. Party B shall submit any reports of service disruptions, inquiries, claims, objections, maintenance requests, or other communications related to this SLA through the support contact point, support email address, form, ticket system, or other methods designated separately by Party A.
• 2. Communications sent to sales representatives or individuals via email, chat, in person, by telephone, social media, or any other method not specified by Party A shall not be considered officially received unless Party A has expressly accepted them.
• 3. Party A shall reasonably determine whether action is necessary, the priority, the method, and the timing of implementation, taking into account the order in which the formal acceptance was completed, the importance, the scope of impact, the urgency, the adequacy of necessary information, reproducibility, duplication, and other relevant circumstances.

Article 7 (Party B’s Obligation to Cooperate)

• 1. In connection with any response to incidents, investigations, maintenance, paid maintenance, or any other matters related to this SLA, Party B shall promptly provide, at its own expense and responsibility, any information, materials, logs, screen captures, reproduction procedures, dates and times of occurrence, scope of impact, operating environment, configuration information, permissions, test environment, verification results, approvals, and any other necessary cooperation reasonably requested by Party A.
• 2. If Party B delays, refuses, or fails to provide the cooperation described in the preceding paragraph, Party A may postpone, withhold, suspend, or terminate all or part of the investigation, troubleshooting, restoration, permanent resolution, reporting, or other related activities.
• 3. Periods resulting from delays in cooperation by Party B, failure to provide necessary information, waiting for approval, waiting for confirmation, waiting for reproduction, waiting for third-party coordination, issues with Party B’s environment, waiting for instructions from Party B, or other circumstances attributable to Party B shall not be included in the calculation of outage time, response time, estimated time to restoration, reporting delays, or other evaluations under this SLA.

Article 8 (Determination of Disability)

• 1. Party A shall determine, based on reasonable criteria, all matters relating to the applicability of this SLA, including whether an incident has occurred, the time of occurrence, the scope of impact, the severity, the applicability of this SLA, whether an exclusion applies, whether a temporary resolution is applicable, and whether a permanent solution is required.
• 2. In making the determination described in the preceding paragraph, Party A’s monitoring records, access logs, system logs, measurement records, operational records, ticket records, alert records, and other records held by Party A shall be given priority as the basis for judgment.
• 3. The measurement results obtained by Party B, the results of third-party monitoring tools, perceived speed, screen displays, and other materials shall serve solely as reference materials for Party A’s judgment and shall not be binding on Party A.

Article 9 (Response Priority and Response Policy)

• 1. Party A shall determine the severity and response priority of any failure or malfunction by considering its scope of impact, severity, avoidability, availability of alternatives, reproducibility, impact on customers, security implications, and other relevant factors.
• 2. Party A shall endeavor to take prompt remedial, preventive, or alternative measures within reasonable limits with respect to any material disruption.
• 3. Party A does not guarantee the specific times for initiating response, providing an initial response, completing restoration, completing permanent resolution, reporting frequency, or any other completion times.
• 4.Examples of response priority levels are as follows.
  • (1) High: Example: When key functions are unavailable
  • (2) Medium: Example: When there is significant instability in the use of the feature
  • (3) Minor: Examples: Minor performance degradation or limited malfunctions
• 5. The preceding paragraph is merely illustrative; the final classification of importance shall be determined by Party A on a case-by-case basis based on reasonable judgment.

Article 10 (Downtime and Service Restoration)

• 1.The duration of the outage shall be calculated from the earlier of the dates listed below and shall continue until Party A confirms that the outage has been resolved.
  • (1) When Party B notifies Party A of the failure through the designated contact point and method, and Party A confirms the occurrence of the failure
  • (2) When Party A confirms the occurrence of the disability
• 2. Notwithstanding the preceding paragraph, any period attributable to circumstances on the part of Party B as specified in Article 7, Paragraph 3 shall not be included in the downtime.
• 3. If a provisional restoration is performed, Party A may deem the system to have been restored as of that point in time.
• 4. Party A may determine that, as an interim measure, imposing usage restrictions, functional limitations, workarounds, or proposing alternative methods following provisional restoration is sufficient.
• 5. If all or part of the Service becomes available as a result of a temporary restoration, Party B may not claim that the restoration is incomplete solely on the grounds that the permanent resolution has not yet been completed.

Article 11 (Permanent Measures)

• 1. The necessity, details, feasibility, timing, priority, method, and scope of permanent measures following a temporary restoration shall be determined by Party A based on a reasonable assessment of the cause of the failure, the scope of impact, the likelihood of recurrence, the availability of alternative measures, the required man-hours, dependencies on third parties, technical feasibility, priority relative to other projects, and other relevant circumstances.
• 2. Party A shall not be obligated to provide ongoing support, complete the work within a specific timeframe, make corrections in a specific manner, or adopt the correction method requested by Party B.
• 3. If Party A determines that a permanent resolution is not feasible, or if Party A proposes a workaround, alternative solution, operational change, functional limitation, or a switch to a different method in lieu of a permanent resolution, Party B may not claim that this constitutes a breach of this SLA or a failure to perform.

Article 12 (Free Maintenance)

• 1. The free maintenance included in the basic service fee shall be limited to corrective measures implemented to the extent deemed reasonably necessary by the Provider in cases where normal use of the Service is impeded due to malfunctions, defects, bugs, or failures attributable to the Provider.
• 2. Free maintenance may include investigation, root cause analysis, the proposal of workarounds, temporary fixes, interim measures, and permanent solutions to the extent deemed necessary by Party A; however, the specific content, scope, methods, sequence, timing, and feasibility of such measures shall be determined at Party A’s reasonable discretion.
• 3. The hours of operation for free maintenance support are from 9:30 a.m. to 6:30 p.m., Monday through Friday.
• 4. Saturdays, Sundays, national holidays, the year-end and New Year holidays, the Obon holidays, the Golden Week holidays, and any other holidays separately designated by Party A are excluded from the scope of free maintenance.
• 5. Party A may, at its discretion, respond outside of regular business hours; however, this does not imply that Party A is obligated to provide similar responses in the future.

Article 13 (Items Not Covered by Free Maintenance)

The services listed in the following items are not included in the free maintenance and are subject to paid maintenance.

• 1. Addition of new features, feature enhancements, specification changes, or specification additions
• 2. Configuration changes, parameter changes, design changes, display adjustments, or UI improvements
• 3. Performance improvements, tuning, optimization, or processing acceleration
• 4. Data correction, data reprocessing, data migration, data extraction, data conversion, individual data inquiries, data restoration, or data return
• 5. Measures to address changes in the external environment, connectivity, operating system, browser, middleware, libraries, APIs, authentication methods, certificates, network environment, and other factors
• 6. Modifications or adjustments to address changes in laws and regulations, system changes, tax reforms, changes in industry rules, and other external factors
• 7. Investigations or responses attributable to Party B’s or a third party’s equipment, lines, terminals, settings, operations, handling, usage methods, usage environment, Party B’s data, or integration partners
• 8. Overtime, Holidays, Late Nights, or Emergency Response
• 9. Educational support, operational support, migration support, manual creation, participation in meetings, individual consultations, and other similar services
• 10. Security enhancement, vulnerability response, audit support, submission of audit trails, and responses to third-party inquiries
• 11. Improvements to AI-related features, including output quality, accuracy, training tuning, model tuning, prompt tuning, and other AI-specific behavior enhancements
• 12. Other measures that Party A reasonably determines to exceed the scope of free maintenance

Article 14 (Paid Maintenance)

• 1. Any maintenance, operational support, investigation, analysis, modification, configuration changes, implementation support, preventive measures, performance improvements, data correction, data recovery, migration support, training support, incident response, audit support, submission of audit trails, after-hours support, support on non-business days, emergency response, or any other work beyond the scope of the free maintenance specified in Article 12 and the preceding article shall be subject to a fee.
• 2. The content, scope, method, timing, and cost of paid maintenance shall be determined in accordance with the quotation, terms of service, individual contract, or specific application terms provided by Party A.
• 3. Even if Party B makes a request or inquiry, Party A shall not be obligated to provide services beyond the scope of free maintenance unless Party A has provided a written estimate and Party B has agreed to it.
• 4. If Party B requests that Party A commence work on the same day or immediately, and Party A agrees to do so, and if such request is made by Party B’s representative or an authorizing officer separately designated by Party B via email, chat, an application form, or any other method capable of being recorded, the work performed pursuant to such request may be treated as having been agreed upon under paid terms.
• 5. In the case described in the preceding paragraph, Party A shall endeavor to notify Party B of such fact, as well as the estimated maximum cost (to the extent possible), the anticipated scope of work, and any other necessary details, either before the commencement of work or promptly after such commencement.
• 6. Party A may determine the fees and terms for emergency response, audit response, evidence collection, on-site response, third-party explanation, regulatory compliance, data recovery, data migration, and other advanced or specialized services on a case-by-case basis via individual quotations, regardless of the standard terms set forth in this SLA.

Article 15 (Service Level)

• 1. Party A shall endeavor to provide this Service in a stable and continuous manner, and shall set a target uptime rate of 99.0% or higher for the entire year.
• 2. The utilization rate referred to in the preceding paragraph is merely a target for Party A to strive toward and does not constitute a guaranteed value, a committed value, a minimum guaranteed value, or a numerical obligation that can be enforced under the contract.
• 3. Calculations of uptime, downtime, outage duration, instances of performance degradation, and other service level metrics shall be performed reasonably by Party A based on Party A’s monitoring records, logs, measurement records, and operational records.
• 4.When calculating the utilization rate, any stoppage, delay, performance degradation, or unavailability falling under the following items shall be excluded from the calculation.
  • (1) Scheduled or unscheduled maintenance, updates, migrations, patch applications, configuration changes, or other planned maintenance activities notified by Party A in advance
  • (2) Maintenance, vulnerability responses, security measures, measures to prevent system failures, disconnections, restrictions, or switchover that Party A deems urgently necessary
  • (3) Natural disasters, earthquakes, lightning strikes, fires, power outages, infectious diseases, war, terrorism, riots, changes in laws or regulations, administrative measures, and other acts of God
  • (4) DDoS attacks, unauthorized access, malware, ransomware, or other acts of interference or cyberattacks by third parties
  • (5) Causes attributable to Party B’s infrastructure environment, network, lines, terminals, settings, usage methods, operations, permission settings, Party B’s data, or third-party integration partners
  • (6) Failures, suspensions, delays, restrictions, specification changes, or termination of third-party services, cloud services, integration APIs, telecommunications carriers, authentication platforms, external communication networks, or other external environments
  • (7) Causes attributable to facilities, equipment, operating systems, browsers, middleware, libraries, or other external environments not managed by Party A
  • (8) Causes attributable to the acts, instructions, work, or omissions of the Party B or a third party
  • (9) The period attributable to circumstances on the part of Party B as specified in Article 7, Paragraph 3
  • (10) Other reasons beyond Party A’s reasonable control or other similar reasons
• 5. In the event of a major disruption to the Service, Party A shall notify Party B to the extent reasonably possible via an announcement on Party A’s website, email, a notification on the Service, or any other means Party A deems appropriate, and shall endeavor to take measures to restore the Service.
• 6. Following the occurrence of a failure, Party A shall endeavor to provide Party B, upon a reasonable request from Party B, with information regarding the scope of the impact, the cause, the measures taken, and measures to prevent recurrence, to the extent that Party A deems it appropriate to disclose such information.
• 7. The utilization rates, reporting, notification, and response obligations set forth in the preceding paragraphs are all targets to be met in good faith; Party A shall not be obligated to provide refunds, reduce fees, pay liquidated damages, issue service credits, provide compensation, or pay damages solely on the grounds that such targets were not met or there were delays. However, this shall not apply in cases where Party A acts with intent or gross negligence.

Article 16 (Scheduled Maintenance and Emergency Maintenance)

• 1. Party A may suspend, interrupt, restrict, or modify the specifications of all or part of the Service when necessary for maintenance, updates, improvements, migration, vulnerability response, security measures, adaptation to changes in third-party services, or other operational reasons.
• 2. When performing scheduled maintenance, Party A shall endeavor to notify Party B in advance to the extent reasonably possible.
• 3. In the event of emergency maintenance, the need to prevent a major system failure, urgent security measures, or any other situation that Party A deems an emergency, Party A may suspend, interrupt, restrict, or modify all or part of the Service without prior notice.
• 4. Any suspension, interruption, restriction, or modification pursuant to this Section shall not constitute a failure, non-performance, or breach under this SLA.

Article 17 (Exceptions)

This SLA does not apply to any suspension, delay, performance degradation, malfunction, unavailability, error, incorrect display, or other incidents resulting from the causes listed in the following items.

• 1. Scheduled maintenance or emergency maintenance as defined in Article 16
• 2. Natural disasters, epidemics, power outages, war, terrorism, riots, changes in laws or regulations, administrative measures, and other force majeure events
• 3. Interference by malicious third parties, unauthorized access, malware, ransomware, and other cyberattacks
• 4. DDoS attacks, acts of interference by third parties, and other attacks
• 5. Cases attributable to services, software, networks, lines, equipment, authentication infrastructure, or other environments provided by Party B or a third party
• 6. In the event of a failure in the fiber-optic line, telecommunications line, or external network used to connect to Party A’s network
• 7. In the event of a failure caused by equipment, devices, cloud services, operating systems, middleware, software, libraries, browsers, or other factors outside the control of Party A
• 8. Malfunctions in the operating system, middleware, or third-party software installed on servers, etc.
• 9. In the event that a disruption occurs due to a violation of the obligations set forth in the master agreement or similar documents
• 10. Cases attributable to Party B’s settings, operations, usage methods, operating environment, Party B’s data, or Party B’s subcontractors
• 11. Cases resulting from instability inherent to AI-related functions, model changes, or constraints or output characteristics of external AI platforms
• 12. Any other circumstances beyond Party A’s reasonable control, or similar circumstances, that Party A reasonably determines to be exempt from the scope of this SLA

Article 18 (No Refunds, Compensation, or Termination)

• 1. This SLA establishes Party A’s target objectives and response policies for maintaining service levels; except in cases of willful misconduct or gross negligence on the part of Party A, it does not automatically give rise to any obligation to provide refunds, fee reductions, service credits, liquidated damages, compensation, or other monetary benefits.
• 2. Party B may not refuse to fulfill, set off, withhold, reduce, or deduct any payment obligations to Party A—including usage fees or paid maintenance fees—nor may it assert termination of the Agreement solely on the grounds of failure to meet the terms of this SLA, the occurrence of an outage, delays in restoration, responses to inquiries, investigation results, failure to implement permanent corrective measures, or any other circumstances related to this SLA.
• 3. Notwithstanding the preceding paragraph, this shall not apply if Party A acts with intent or gross negligence, or if the master agreement or other relevant agreement expressly provides otherwise.
• 4. Party A’s liabilities under this SLA shall be subject to the limitations of liability, disclaimers, and maximum liability for damages set forth in the Master Agreement or other relevant agreements.

Article 19 (Backups, Data Preservation, and Restoration)

• 1. Party B shall, at its own responsibility and expense, create and maintain appropriate backups of Party B’s data, configuration information, output results, and any other necessary information.
• 2. Party A does not guarantee the integrity, continuity of storage, recoverability, ability to restore to a specific point in time, protection against accidental deletion, protection against logical corruption, or the acquisition of complete backups of Party B’s data.
• 3. Support for the extraction, restoration, correction, reprocessing, re-entry, return, conversion, or migration of individual data may be subject to paid maintenance or a separate contract.

Article 20 (Intellectual Property Rights)

• 1. All intellectual property rights in and to any programs, scripts, modules, configurations, specifications, designs, screens, forms, documents, manuals, research materials, know-how, operational methods, deliverables, derivatives, modifications, customizations, and all other tangible and intangible items created, provided, or implemented by Party A in connection with this SLA, the Service, paid maintenance, or any other matters related to the Service shall belong to Party A or the rightful owner.
• 2. Notwithstanding the preceding paragraph, all data, materials, trade names, trademarks, logos, and other rights specific to Party B that Party B has previously held shall remain with Party B, and this Article shall not transfer such rights to Party A.
• 3. Party B may use the deliverables described in the preceding two paragraphs only to the extent necessary for the use of the Service, unless Party A has expressly provided otherwise in a separate agreement or in the terms and conditions of a specific application.
• 4. Party B shall not, without Party A’s prior written or electronic consent, reproduce, modify, provide to third parties, sublicense, analyze, decompile, disassemble, or engage in any other acts regarding the deliverables described in the preceding paragraph that infringe or are likely to infringe upon Party A’s rights.
• 5. Payment for paid maintenance, modifications, configuration changes, investigations, analyses, data handling, or other services provided at the request or direction of Party B shall not constitute a transfer of the intellectual property rights specified in the preceding paragraphs.

Article 21 (Response to Security Incidents, etc.)

• 1. If Party A becomes aware of a security incident or similar event that could have a significant impact on the Service, Party A shall endeavor to notify Party B to the extent that such notification does not conflict with trade secrets, security maintenance, cooperation with law enforcement investigations, restrictions under subcontracting agreements, legal restrictions, or the protection of third-party rights.
• 2. The notice referred to in the preceding paragraph shall not be construed as an admission of Party A’s liability with respect to the relevant event, nor shall it automatically give rise to any specific obligation on the part of Party A to provide compensation, restore the property to its original condition, disclose information, or remedy the consequences.
• 3. Party A shall, with respect to the incident, take measures such as containment, isolation, isolation, restoration, enhanced monitoring, recurrence prevention, and any other actions deemed necessary, within commercially reasonable limits.
• 4. Party A shall not be obligated to disclose the specific details of the vulnerability, attack methods, impact on other customers, audit trails, log details, forensic information, or any other information that it reasonably determines would be inappropriate to disclose for security or business reasons.

Article 22 (Data Export and Migration Support)

• 1. If Party B requests data export, data return, data conversion, or migration support due to contract termination, cancellation, a change in services, or any other reason, Party A may treat such requests as paid maintenance services or as a separate agreement.
• 2. Party A shall reasonably determine the feasibility, scope, method, format, timing, and cost of the measures described in the preceding paragraph, taking into account the volume of data, storage format, technical constraints, security requirements, and other relevant circumstances.
• 3. Unless otherwise provided by law or a higher-level agreement, Party A does not guarantee the return of data in a specific format, full portability, full compatibility, or full connectivity with third-party services.

Article 23 (Suspension or Restriction of Use)

• 1.If Party A reasonably determines that any of the following applies, it may suspend or restrict the provision of all or part of the Service, or disable specific features, without prior notice to Party B.
  • (1) When necessary to ensure the stable operation, security, or protection of other customers of this Service or third-party services
  • (2) In cases where there is a risk of unauthorized access, unauthorized use, excessive load, abnormal communication, exploitation of vulnerabilities, or other risks
  • (3) If Party B violates or is likely to violate the master agreement or other relevant agreements
  • (4) Where the User’s use of the Service violates, or is likely to violate, the terms and conditions of third-party services, laws and regulations, or public order and morals
  • (5) In cases where there is non-payment, late payment, credit concerns, or other reasonable grounds for deeming continued use inappropriate
• 2. The measures described in the preceding paragraph shall not constitute a failure, non-performance, or breach under this SLA.

Article 24 (Amendments)

• 1. Party A may amend this SLA if there are amendments to laws or regulations, changes in operational practices, technical necessities, changes to the scope of services, changes to third-party services, changes in the external environment, security requirements, or other reasonable grounds.
• 2. Party A shall notify users of the contents and effective date of the amended SLA by posting them on Party A’s website, via email, through notifications on the Service, or by any other means Party A deems appropriate.
• 3. Except in cases of urgency, Party A shall, in principle, endeavor to provide the notice described in the preceding paragraph at least 30 days prior to the effective date.
• 4. The amended SLA shall take effect on the effective date separately specified by Party A.

Article 25 (Severability, etc.)

• 1. Even if any provision or part thereof of this SLA is deemed invalid or unenforceable under applicable laws or regulations, the remaining provisions shall remain in full force and effect.
• 2. Even if Party A does not exercise its rights under this SLA, such failure shall not be deemed a waiver of such rights.

Article 26 (Survival)

Articles 2, 3, 7, 8, 10, 11, 14, 18, 19, 20, 21, 22, 23, 24, 25, this Article, and any provisions that by their nature are intended to survive termination of the Agreement shall remain in full force and effect following the termination of this SLA.