Force Majeure Policy

Last updated: July 9, 2026

Scope of this document: This document governs the terminalstreet.com website and TerminalStreet's business (B2B) services only. TerminalStreet LLC also builds, hosts, owns, operates, and/or is credited on separate products, applications, and websites — including consumer applications and platforms operated by separate legal entities. Each such product is governed exclusively by its own legal terms published at its own domain. The policies on this site do not apply to users of those products except where a product document expressly incorporates them by name, and in any conflict the product document controls for that product. See Products & Scope.

This Force Majeure Policy ("Policy") outlines TerminalStreet LLC's ("TerminalStreet," "we," "us," or "our") approach to managing extraordinary events beyond our reasonable control that may affect our ability to fulfill our contractual obligations and service commitments. This Policy supplements our Terms of Service, Service Level Agreements (SLAs), and other contractual arrangements.

While TerminalStreet designs its systems for high resilience and implements robust business continuity measures, we recognize that certain exceptional events may impact our services despite our best efforts. This Policy explains how we define, respond to, and manage such events while minimizing disruption to our users.

1. Definition of Force Majeure

TerminalStreet defines a "Force Majeure Event" as an extraordinary circumstance beyond our reasonable control that materially prevents, hinders, or delays our performance of contractual obligations or service commitments, despite our implementation of reasonable business continuity and disaster recovery measures.

Such events may include, but are not limited to:

  • Natural Disasters: Earthquakes, floods, hurricanes, tsunamis, volcanic eruptions, wildfires, or other severe weather conditions or natural events of unusual magnitude
  • Public Health Emergencies: Pandemics, epidemics, or other public health crises as declared by relevant governmental or international health authorities
  • Armed Conflict and Civil Unrest: War (declared or undeclared), invasion, armed conflict, civil war, acts of terrorism, civil unrest, riots, or insurrection
  • Government Actions: Government requisition, order, legislation, regulation, or restriction that materially impairs our ability to perform, including trade sanctions, embargoes, or export controls
  • Critical Infrastructure Failures: Widespread or regional failures of critical infrastructure, including power grid failures, telecommunications network outages, or internet backbone disruptions beyond our reasonable control
  • Cyber Attacks: Extraordinary, severe, and widespread cyber attacks that overwhelm standard security measures, such as unprecedented distributed denial-of-service (DDoS) attacks or zero-day exploits affecting critical systems
  • Supply Chain Disruptions: Extraordinary disruptions in the technology supply chain affecting critical components or services necessary for our operations that cannot be reasonably mitigated
  • Third-Party Service Provider Failures: Catastrophic failure of critical third-party service providers (such as cloud infrastructure providers) due to Force Majeure Events affecting their operations

2. Events Not Considered Force Majeure

To provide clarity, the following events are generally NOT considered Force Majeure Events under this Policy, as they are either reasonably foreseeable or within our control to mitigate:

  • Routine maintenance (scheduled or unscheduled)
  • Individual server failures or limited hardware malfunctions
  • Software bugs or errors in our code that could have been detected through standard testing
  • Isolated or limited network outages that don't affect our entire infrastructure
  • Staff shortages due to normal employee turnover
  • Standard market fluctuations, economic conditions, or business cycle changes
  • Anticipated regulatory changes in the technology sector
  • Small-scale security incidents that can be addressed with standard security measures
  • Moderate increases in service usage or traffic within our scaling capabilities

3. Service Impact and Remedies

3.1 Service Impact

During a Force Majeure Event, the following impacts may occur to our services:

  • Temporary service unavailability or degraded performance
  • Delays in service delivery or reduced functionality
  • Limited customer support availability or extended response times
  • Postponement of planned releases, updates, or new feature deployments
  • Suspension of certain non-critical features to maintain core functionality
  • Temporary relocation of services to alternative infrastructure

3.2 SLA and Contractual Implications

When a Force Majeure Event occurs:

  • SLA Relief: Service Level Agreement (SLA) guarantees, including uptime commitments and response time obligations, may be suspended for the duration of the Force Majeure Event and a reasonable recovery period
  • SLA Credits: Service credits normally issued for SLA violations will not apply to service disruptions directly caused by the Force Majeure Event
  • Performance Metrics: Performance measurements affected by the Force Majeure Event may be excluded from periodic service reviews and reporting
  • Delivery Timelines: Contractual delivery timelines may be extended by a period equivalent to the duration of the Force Majeure Event plus a reasonable recovery period

While SLA commitments may be suspended, we remain committed to restoring services as quickly as possible and will make commercially reasonable efforts to maintain service continuity even during Force Majeure Events.

3.3 Financial Considerations

The following financial considerations apply during Force Majeure Events:

  • Subscription Services: For extended service outages (typically exceeding 7 consecutive days) caused solely by a Force Majeure Event, we may provide service credits or extend subscription periods at our discretion
  • Project-Based Services: For project-based work, timelines and deliverables may be renegotiated to account for delays caused by the Force Majeure Event
  • Payment Obligations: Customer payment obligations generally remain in effect during a Force Majeure Event, unless the event completely prevents access to all services for an extended period
  • Cost Increases: If a Force Majeure Event causes substantial increases in our operating costs, we reserve the right to renegotiate pricing for future service periods

4. Our Response to Force Majeure Events

4.1 Activation of Business Continuity Plan

When a Force Majeure Event occurs or is reasonably anticipated, we will:

  • Activate our Business Continuity Plan and/or Disaster Recovery procedures
  • Establish an incident management team to coordinate our response
  • Assess the potential impact on our services and customers
  • Implement available mitigation measures to minimize service disruption
  • Prioritize the protection of customer data and critical system security

4.2 Communication

During a Force Majeure Event, we commit to:

  • Notify affected customers as soon as reasonably practicable after identifying a Force Majeure Event
  • Provide regular status updates through our status page, email communications, and/or customer support channels
  • Offer estimates of expected impact and anticipated recovery timelines when reasonably possible
  • Designate specific communication channels for high-priority customer concerns
  • Provide post-incident reports for significant service disruptions

4.3 Recovery and Restoration

Our approach to service recovery includes:

  • Prioritizing the restoration of critical services and functions
  • Implementing a phased recovery approach based on service priorities
  • Conducting thorough testing before returning systems to full production
  • Performing data integrity checks to ensure no data loss or corruption
  • Coordinating with affected third-party providers as necessary
  • Documenting lessons learned to improve future resilience

5. Customer Responsibilities

We encourage our customers to take the following measures to minimize the impact of Force Majeure Events:

  • Business Continuity Planning: Develop and maintain your own business continuity plans that consider the potential unavailability of TerminalStreet services
  • Data Backups: Maintain regular backups of your data, even when using our services, in accordance with your own backup policy
  • Critical Dependency Assessment: Evaluate the criticality of TerminalStreet services to your operations and consider redundancy for mission-critical functions
  • Emergency Contacts: Ensure your emergency contact information is current in our systems
  • Prompt Notification: Inform us promptly if you become aware of potential Force Majeure Events that might affect our services
  • Reasonable Cooperation: Cooperate reasonably with our requests during the management of Force Majeure Events

6. Technology-Specific Considerations

6.1 AI and Machine Learning Services

For our AI and machine learning services, additional Force Majeure considerations include:

  • Model Performance: Force Majeure Events may impact model training schedules, performance tuning, or ongoing model improvements
  • Computing Resources: Resource-intensive AI operations may be temporarily scaled back during infrastructure challenges
  • Data Processing: Processing of new training data or model updates may be delayed
  • Recovery Priority: Critical inference services will typically be prioritized over training or optimization services

6.2 Blockchain and Crypto Services

For our blockchain and cryptocurrency services, specific considerations include:

  • Network Dependencies: Our services depend on the continued operation of underlying blockchain networks, which may themselves be affected by Force Majeure Events
  • Transaction Processing: Transaction submission, monitoring, or validation services may experience delays
  • Wallet Services: While core security of wallet services remains paramount, some functionality may be limited
  • Market Data: Cryptocurrency market data feeds or oracle services may be affected
  • Smart Contract Operations: Monitoring or automated interaction with smart contracts may be delayed

6.3 Financial Technology Services

For our financial technology services, special considerations include:

  • Regulatory Reporting: Force Majeure Events may impact regulatory reporting timelines, though we will make all reasonable efforts to maintain compliance
  • Transaction Processing: Processing of financial transactions may be prioritized over analytics or reporting functions
  • Market Data Services: Market data feeds or analysis may be delayed or temporarily limited in scope
  • Algorithmic Trading: Automated trading systems may be placed in a safe state or operate with modified parameters
  • Financial Institution Dependencies: Services that rely on external financial institutions may be affected by those institutions' own Force Majeure responses

7. Force Majeure Notification and Declaration

7.1 Declaration Process

TerminalStreet follows a structured process for declaring Force Majeure:

  1. Initial assessment of the event against our Force Majeure criteria
  2. Evaluation of the actual or potential impact on our services
  3. Formal determination by our executive leadership or designated incident commander
  4. Official notification to affected customers and partners
  5. Regular reassessment of the situation throughout the duration of the event

7.2 Documentation and Evidence

We maintain appropriate documentation regarding Force Majeure Events, including:

  • The nature, scope, and duration of the event
  • Evidence demonstrating the event was beyond our reasonable control
  • Actions taken to mitigate the impact
  • Service restoration efforts and timelines
  • Customer communications

This documentation may be provided to customers upon reasonable request, subject to confidentiality considerations.

8. Duration and Termination Rights

8.1 Extended Force Majeure

If a Force Majeure Event continues for an extended period:

  • For events lasting more than 30 consecutive days, either party may initiate discussions to determine appropriate accommodations or modifications to service agreements
  • For events lasting more than 60 consecutive days that substantially prevent delivery of critical services, either party may have the option to terminate affected service agreements without penalty, as specified in the relevant agreements
  • Termination rights, if exercised, do not eliminate payment obligations for services rendered prior to the Force Majeure Event

8.2 Partial Force Majeure

If a Force Majeure Event affects only certain services or components:

  • Unaffected services will continue to be provided according to normal terms
  • SLA suspensions will apply only to the affected services
  • Termination rights, if applicable, may be limited to the specifically affected services rather than the entire agreement

9. Policy Modifications

TerminalStreet reserves the right to modify this Force Majeure Policy from time to time. We will notify customers of material changes through our website or direct communication. Your continued use of our services following such notification constitutes acceptance of the updated Policy.

10. Governing Law

This Force Majeure Policy is governed by the laws specified in your service agreement with TerminalStreet. In the absence of a specific governing law provision, this Policy shall be governed by the laws of the State of Wyoming, USA, without regard to its conflict of law principles.

11. Contact Information

For questions about this Force Majeure Policy or to report potential Force Majeure Events affecting our services, please contact:

[email protected]

This Force Majeure Policy was last updated on July 9, 2026.