[ T-01 — SERVICE SCOPE ]
Operational Services
XCYB TECH provides enterprise cybersecurity infrastructure, strategic consultation, and autonomous defense operations to qualified organizations. Services are delivered within the scope of executed engagement agreements.
Strategic consultation and briefing. Structured operational briefings, infrastructure assessments, and security posture evaluations conducted for qualified enterprise organizations.
Enterprise cybersecurity services. Deployment of XCYB operational capabilities including threat monitoring, incident coordination, and infrastructure defense for contracted clients.
AEON operational infrastructure. Access to the AEON autonomous intelligence layer — persistent threat monitoring, behavioral analysis, and autonomous response infrastructure — available to organizations that have completed the deployment qualification process.
Deployment evaluation. Pre-engagement qualification processes to assess organizational fit, infrastructure requirements, and operational readiness for XCYB deployment.
Future operational ecosystem. XCYB is building additional operational divisions. Access to pre-release or restricted divisions is governed by separate qualification requirements and will be subject to these terms upon activation.
Services are subject to change as XCYB's operational ecosystem evolves. Engagement scope is defined in executed service agreements, which supersede these terms where applicable.
[ T-02 — ACCESS & ELIGIBILITY ]
Operational Access
XCYB does not provide open access to its infrastructure. Every engagement begins with an evaluation. Access is earned, not granted by default.
XCYB services are available to enterprise organizations and qualified individuals operating in environments where operational security is a critical concern. Access is not provided on demand and is subject to the following conditions:
Enterprise usage expectation. XCYB services are designed for organizations with active operational security requirements. Consumer use, academic research requests, or competitive intelligence gathering are not eligible use cases.
Operational review rights. XCYB reserves the right to evaluate, qualify, and approve organizations requesting access to its services. Submission of an intake request does not guarantee engagement.
Deployment qualification. Access to AEON and restricted operational infrastructure requires completion of XCYB's deployment qualification process, including technical and organizational assessment.
Revocation. XCYB may restrict or revoke access to any service, system, or intake channel at any stage of the evaluation or deployment process, with or without prior notice, where operational or security concerns warrant.
[ T-03 — ACCEPTABLE USE ]
Operational Use Standards
Access to XCYB systems, intake channels, and operational infrastructure is granted for lawful, operationally legitimate purposes only. The following uses are prohibited:
Infrastructure probing. Attempting to probe, scan, test, or compromise XCYB's operational infrastructure, intake systems, or any systems associated with XCYB engagements.
Competitive intelligence. Using XCYB intake channels, briefings, or consultation access to gather intelligence for a competing organization or to reconstruct XCYB's operational methodologies.
Unauthorized access. Accessing or attempting to access systems, data, or operational infrastructure beyond the scope explicitly authorized by XCYB.
Security misuse. Applying information or operational intelligence obtained through XCYB briefings, assessments, or engagements in ways that compromise third-party security, violate applicable law, or undermine infrastructure integrity.
Misrepresentation. Providing false or materially misleading information during the intake, qualification, or engagement process.
Violations of acceptable use standards may result in immediate access revocation and, where applicable, referral to relevant legal or regulatory authorities.
[ T-04 — INTELLECTUAL INFRASTRUCTURE ]
Proprietary Operational Architecture
XCYB TECH's systems, methodologies, intelligence frameworks, and operational architecture represent proprietary infrastructure developed through sustained investment in security research and operational engineering.
Brand and system identifiers. XCYB, AEON, and all operational division names and product identifiers are proprietary to XCYB TECH. Use requires explicit written authorization.
Operational methodology. XCYB's assessment frameworks, deployment methodologies, threat intelligence structures, and operational protocols are proprietary and confidential. They may not be reproduced, distributed, or adapted without written authorization.
Engagement deliverables. Briefing documents, assessment reports, infrastructure analyses, and consultation outputs produced by XCYB are confidential operational deliverables delivered under the terms of an executed engagement agreement.
AEON architecture. The AEON autonomous intelligence system — its detection logic, behavioral analysis architecture, response orchestration, and underlying intelligence substrate — is protected operational infrastructure. No access, reproduction, or reverse engineering is authorized beyond the scope of an executed deployment agreement.
[ T-05 — AVAILABILITY & CONTINUITY ]
Operational Continuity
XCYB maintains continuity across its service delivery infrastructure. Specific availability commitments are defined in executed service agreements and are not implied by access to intake channels or consultation services.
Infrastructure maintenance. XCYB systems may be subject to scheduled or unscheduled maintenance. Maintenance windows are communicated to active clients where operationally possible.
Operational security measures. XCYB may temporarily restrict access to systems or intake channels as a precautionary operational security measure. Such restrictions do not constitute a service failure.
Service evolution. XCYB reserves the right to modify, expand, restrict, or discontinue service offerings as its operational ecosystem evolves. Material changes to active engagements will be communicated under the terms of the applicable service agreement.
Pre-deployment access. Access to pre-release systems, restricted operational divisions, or future ecosystem components is provisional and subject to change without notice.
[ T-06 — LIABILITY ]
Operational Liability
XCYB provides services to support and strengthen client operational security posture. The scope of XCYB's obligations and liability is defined by executed service agreements. The following applies in the absence of, or as a floor beneath, any executed agreement:
Security outcomes. XCYB does not guarantee specific security outcomes beyond the operational scope defined in an executed engagement agreement. No general warranty of security is implied by the provision of consultation, assessment, or infrastructure services.
Limitation on consequential damages. To the extent permitted by applicable law, XCYB's liability for any claim arising from the use of its services is limited to the fees paid by the client under the relevant engagement agreement during the 90-day period preceding the claim.
Third-party systems. XCYB is not liable for vulnerabilities, failures, or security incidents in third-party systems, infrastructure, or services that fall outside the defined scope of an active engagement.
Pre-engagement interactions. Consultation, briefing, and intake interactions that precede an executed service agreement are provided as-is. No warranty of fitness, accuracy, or completeness is implied.
[ T-07 — OPERATIONAL CONFIDENTIALITY ]
Mutual Confidentiality Obligations
Information exchanged within a XCYB operational environment does not leave it. This applies to both parties.
XCYB treats all information exchanged during briefings, assessments, consultations, and active engagements as operationally confidential. Organizations engaging with XCYB are subject to equivalent obligations.
Client operational data. Infrastructure details, threat intelligence, organizational information, and operational context disclosed to XCYB during any phase of an engagement are treated as classified operational data. They are not shared, published, or used outside the scope of the relevant engagement.
XCYB operational intelligence. Methodologies, assessment findings, deployment architectures, and intelligence outputs produced by XCYB are confidential. They may not be disclosed to third parties, reproduced, or applied outside the authorized engagement scope.
Engagement existence. The existence, scope, and details of a XCYB engagement may constitute sensitive operational information. Disclosure of engagement details to third parties requires prior written authorization from XCYB.
Survival. Confidentiality obligations survive the conclusion of any intake process, evaluation, or engagement.
[ T-08 — GOVERNING FRAMEWORK ]
Legal Governing Structure
These terms are governed by applicable law in the jurisdiction of XCYB TECH's principal place of operation. Where an executed service agreement specifies a governing jurisdiction, that agreement governs.
Disputes arising from pre-engagement intake interactions or from these terms in the absence of an executed agreement will be addressed through direct communication with XCYB operational counsel before any external proceeding is initiated. XCYB is committed to resolving operational disputes through structured dialogue rather than adversarial process.
Any provision of these terms found to be unenforceable under applicable law will be limited to the minimum extent necessary to maintain the enforceability of the remaining provisions.
[ T-09 — FINAL TERMS ]