HAXTER CORPORATION SUITES

Terms and Conditions

Effective Version:Protocol Version

Service Provider: Haxter Corporation and/or its applicable operating entity or affiliated service division (“Haxter”, “Haxter Corporation”, “we”, “us”, or “our”)

Client: The individual or entity contracting, using, requesting, accepting, receiving, or benefiting from Haxter Corporation Suites services (“Client”, “you”, or “your”)

By requesting, accepting, receiving, using, operating within, or continuing to benefit from any service, infrastructure, development work, environment, demonstration, storage allocation, database allocation, website deployment, domain management, application support, or related provision made available under Haxter Corporation Suites (“Suites” or the “Services”), the Client acknowledges and agrees to the present Terms and Conditions.

1. Nature of the Service

Haxter Corporation Suites is an integrated service environment under which Haxter may provide, coordinate, operate, or administer one or more of the following on behalf of the Client, as applicable:

• domain registration and management;
• infrastructure and hosting environments;
• websites and web applications;
• storage, collections, and databases;
• demos, previews, development instances, and operational deployments;
• service integrations;
• email-related operational components;
• AI-connected systems and auxiliary technical services; and
• related maintenance, administration, and continuity functions.

Suites is not limited to the mere pointing of DNS records to a static page or isolated IP address. Where the Client’s environment includes multi-component web applications, databases, email, AI-connected systems, proprietary frameworks, or other interdependent technical resources, the Services shall be understood as a broader managed operating environment.

2. Domain Titularity and Provider Role

Where a domain is registered, managed, renewed, or operated by Haxter within Suites:

• the ultimate ownership and titularity of the domain belongs to the Client, specifically the service holder or designated lawful holder of the account, as applicable;
• Haxter acts as provider, registrar-operator, manager, and custodian of the domain within the broader operating environment of the Services;
• Haxter’s management or administration of a domain does not alter, extinguish, or negate the Client’s underlying titularity; and
• the fact that a domain may appear under privacy protection, registrar masking, operational management records, or Haxter-branded technical handling does not by itself mean that Haxter becomes the substantive owner of the domain.

For clarity, the domain remains the Client’s domain, while being administered by Haxter as part of the service environment.

3. WHOIS, Registration Data, and Holder Updates

The Client acknowledges that domain registration records, WHOIS visibility, privacy protection layers, and related registry-facing data may, depending on registrar or processor configurations, appear as blocked, masked, privacy-protected, or associated with operational handling references.

Where the Client is the lawful holder of the service and domain, an update of titular or registration-facing data may be processed as a registration configuration update in accordance with operational feasibility and registry practices. Based on the service model reflected in the present Terms, such update is not, by itself, characterized as a distinct sale of the domain to the Client, nor as a separate transfer of ownership from Haxter to the Client, but as an administrative correction or update of registration data consistent with the underlying titularity already vested in the Client.

4. Managed Environment and Operational Control

The Client acknowledges that a domain operating under Suites may be part of a managed service environment involving infrastructure, continuity controls, maintenance logic, multiple components, and interdependent technical architecture.

Accordingly:

• the administration of such domain is not equivalent to the management of a simple static site;
• the use of third-party registrars, external domain managers, or external DNS control while continuing to rely on Haxter’s service environment may materially affect service quality, continuity, diagnostics, preventive maintenance, or accountability boundaries;
• Haxter may determine that preserving centralized management within the Suites environment is necessary for stability, operational integrity, and continuity of service; and
• any externalization of domain control may alter Haxter’s ability to maintain the same level of integrated operational assurance.

5. Service Level Context

Where applicable to the Client’s service tier, Suites may be operated under a stated Service Level Agreement (“SLA”), including, by example reflected in the communications underlying this draft, a 99.5% service level for the relevant account tier.

The Client understands and agrees that:

• the SLA is tied to the operational conditions under which Haxter can properly manage the service environment;
• fragmentation of control, including but not limited to external domain transfer combined with ongoing use of Haxter-operated infrastructure, may impair or eliminate Haxter’s ability to preserve the same service level assumptions; and
• Haxter may decline to extend, maintain, or guarantee the same service level commitments where the environment is no longer fully operated under Haxter’s managed control.

6. Fees, Payment, and Regularization of Account

The Client shall timely pay all fees, invoices, charges, accrued service amounts, and any other sums due in connection with the Services, including but not limited to:

• development work;
• deployed or prepared websites;
• demos or technical demonstrations;
• storage allocations;
• database allocations;
• collections, environments, or provisioned resources;
• domain-related services; and
• any other service already designed, created, provided, provisioned, made available, or placed online.

If services, demos, resources, infrastructure, websites, storage, databases, or related technical work have already been designed, created, deployed, placed online, demonstrated, provisioned, or otherwise made available, the corresponding financial obligation shall exist notwithstanding whether the Client has already made payment.

An account is considered not regularized where outstanding amounts remain unpaid.

7. Restriction on Transfers While Amounts Are Outstanding

So long as the Client’s account is not fully regularized and all outstanding sums remain unpaid, Haxter may refuse, defer, suspend, or decline any request involving:

• domain transfer to another provider;
• transfer of associated assets;
• disengagement of operational resources;
• export of controlled service elements; or
• other forms of technical or administrative release tied to an unpaid account.

Under such circumstances, Haxter shall have no obligation to process a transfer until the account is brought fully current.

For operational clarity, where a Client seeks to remove a domain or service component while substantial unpaid balances remain, Haxter may treat the unresolved debt as the controlling economic condition preventing release.

8. Transfer to Another Provider

Once the Client’s account has been fully regularized, Haxter may evaluate and, if operationally appropriate, support a transfer of the domain to another provider or registrar.

However:

• such transfer is not automatic;
• such transfer may be subject to an administrative transfer fee corresponding to the process;
• Haxter may establish reasonable procedural requirements for such transfer; and
• any such transfer applies to the domain itself and does not, by implication, include the transfer of infrastructure, application logic, source materials, databases, proprietary frameworks, or any other non-domain asset unless separately and expressly agreed.

A domain transfer is therefore strictly distinguishable from the migration or handover of the broader technical environment.

9. Disengagement, Separation, and Migration Fees

Where the Client seeks partial or total separation from the Suites environment, Haxter may impose fees, charges, or project-based costs associated with disengagement, service separation, migration, or technical decoupling.

Such work may include, without limitation:

• separation of databases;
• separation of APIs;
• separation of AI-connected services;
• separation of email-related components;
• preparation of technical documentation;
• infrastructure uncoupling;
• migration planning; and
• partial or total operational disentanglement.

The Client acknowledges that this work may be materially complex and expensive, and that corresponding charges may be substantial and justified by the nature of the process.

10. No Automatic Portability of the Technical Stack

Transfer of a domain away from Haxter does not imply, include, grant, or require transfer of:

• databases;
• database access;
• HTML, CSS, or JavaScript source materials;
• PHP code;
• backend logic;
• application frameworks;
• proprietary search-enabling components;
• infrastructure configurations;
• AI integrations;
• operational services; or
• any other software, system, or technical resource beyond the domain itself.

The Client acknowledges that a domain and a technical implementation are separate assets or layers, and that domain transfer does not carry the technical stack with it.

11. Proprietary Frameworks and Haxter Technology

Certain websites, applications, environments, or service components delivered within Suites may have been built, enabled, accelerated, or made operational through Haxter’s proprietary frameworks, tools, systems, methods, or internal technologies.

Where this is the case:

• such frameworks and proprietary enabling technologies remain under Haxter’s control unless expressly licensed otherwise;
• the Client receives the benefit of implementation within the Suites model, but not, by default, unrestricted extraction or external reimplementation rights;
• if the Client wishes to continue using technology built upon or dependent on proprietary Haxter frameworks outside the Suites environment, a separate commercial license of the appropriate grade may be required; and
• absent such license, the existence of code artifacts does not necessarily make them independently portable, usable, or implementable elsewhere.

12. Preferential Pricing Within Suites

The Client acknowledges that, under Suites, certain development work, websites, applications, or technical implementations may be offered at preferential or discounted pricing as part of the integrated service relationship.

Such pricing may reflect, among other things:

• the service relationship itself;
• bundled privileges;
• limited modifications;
• operational continuity assumptions; and
• the fact that the Client is paying for service work, implementation velocity, managed operation, or hours of work within the Suites ecosystem rather than full unrestricted externalized ownership of all implementation assets.

Accordingly, preferential Suites pricing does not imply that the Client has purchased unrestricted external reuse rights to all underlying technical materials.

13. Exit Economics and Market-Value Adjustment

If the Client elects to leave the Suites environment, separate, externalize, or seek independent use of assets originally built under preferential Suites conditions, Haxter may require payment based on the market value of the work performed, rather than solely the discounted amount previously charged within the service relationship.

The economic rationale reflected in the service model is that a Client who received reduced pricing within the Suites ecosystem may not automatically carry external-use rights, portability rights, or equivalent unrestricted benefit at the same reduced amount.

Accordingly, where applicable:

• prior discounted service pricing does not cap the valuation of the work for externalization purposes;
• Haxter may require settlement of market-value pricing for the relevant work before external release, reuse, or decoupling; and
• the need for a separate commercial license for proprietary framework-based implementations may also apply in addition to such market-value adjustment.

14. Maintenance, Preventive Maintenance, and Support Boundaries

Haxter’s ability to provide maintenance, preventive maintenance, troubleshooting, and higher-level operational support depends on maintaining coherent control over the service environment.

If the Client unbundles, externalizes, fragments, or reassigns essential components—especially the domain layer—while expecting continued reliance on Haxter’s broader operational environment, Haxter may determine that:

• support boundaries have materially changed;
• preventive maintenance can no longer be performed under the same assumptions;
• service diagnostics are impaired; and/or
• Haxter cannot reasonably be held responsible for issues arising from externally controlled elements.

15. Speed of Deployment and Internal Methods

The Client acknowledges that a distinguishing feature of Suites is Haxter’s ability to place services online at unusual speed through the use of proprietary frameworks, internal tooling, and integrated methods.

Such deployment speed is part of the service value proposition. It does not imply that the underlying technical methods, frameworks, structures, or implementation logic are thereby transferred, waived, or converted into unrestricted Client-owned deliverables merely because they were used to accelerate delivery.

16. No Obligation to Continue Under Externally Fragmented Conditions

Haxter shall not be obligated to continue providing the same integrated service, continuity commitments, or quality assurances where the Client seeks to separate control of the domain or other key service layers from the rest of the Haxter-operated environment while still expecting unchanged service conditions.

Haxter may, at its discretion, determine that such arrangement is operationally unsuitable and may refuse, limit, or reframe service accordingly.

17. Account Standing as a Condition to Optional Assistance

Any assistance by Haxter regarding domain transfer evaluation, migration support, or external provider coordination is conditioned upon the Client first bringing the account fully current.

Once the account is fully regularized, Haxter may, without prejudice to its rights, evaluate options, discuss transfer pathways, or provide administrative assistance subject to applicable fees and technical constraints.

18. Interpretation of Service Scope

The Client agrees that Haxter Corporation Suites is to be interpreted as an integrated managed service model, not merely as a domain forwarding arrangement or isolated hosting utility.

Therefore, no statement, expectation, or assumption by the Client shall be interpreted to require Haxter to:

• separate integrated components without proper settlement;
• transfer technical assets merely because a domain is Client-owned;
• preserve SLA conditions under fragmented control; or
• deliver external portability of proprietary frameworks absent proper licensing and payment.

19. Reservation of Operational Discretion

To the extent necessary to preserve stability, continuity, service integrity, or payment discipline, Haxter reserves the right to determine the operational conditions under which transfers, separations, migrations, or administrative releases may occur, provided such determination remains consistent with the service model described in these Terms.

20. Entire Service Understanding Within the Present Scope

These Terms and Conditions reflect the service logic evidenced in the operative communications underlying this draft, namely:

• Client ownership of the domain;
• Haxter’s role as operational provider and manager;
• the integrated nature of the service environment;
• the distinction between domain ownership and technical stack ownership or portability;
• the requirement that outstanding debts be paid before transfer;
• the possible application of administrative transfer fees;
• the existence of disengagement or migration costs;
• the non-automatic transfer of databases, code, frameworks, or infrastructure; and
• the possible requirement of commercial licensing and market-value settlement for externalized use of work built under Suites.

21. Acceptance

By using, requesting, accepting, continuing to use, or benefiting from Haxter Corporation Suites, the Client acknowledges having read, understood, and accepted these Terms and Conditions.