Back to Hub

Terms of Engagement

LEGAL NOTICE: These Terms of Engagement constitute a binding sovereign agreement under the jurisdiction of the Russian Federation. Accessing Cyrillic Company infrastructure implies full and unconditional acceptance of all 50+ clauses detailed below.

01

Legal Acceptance

By accessing this digital node, you explicitly enter into a binding legal treaty with Cyrillic Company. Use of the system, infrastructure, or any cryptographic kernels constitutes a definitive digital signature and unconditional acceptance of these terms in their entirety. Any unauthorized access attempts will be logged and prosecuted under sovereign laws.

02

Russian Jurisdiction

All operations, data transmissions, and architectural engagements are governed exclusively by the laws of the Russian Federation. No foreign legal frameworks, including EU GDPR, US CCPA, or international trade regulations, shall supersede, override, or mitigate these provisions unless explicitly recognized by the Moscow City Court.

03

Sovereign Entity Status

Cyrillic Company is a registered sovereign engineering firm operating within the GKP-4 high-security zone. We maintain absolute operational independence from international regulatory bodies that do not align with Russian national security and technological standards.

04

Eligibility Criteria

Users must be at least 18 years of age and possess full legal capacity. Access is strictly prohibited to individuals or entities affiliated with organizations deemed hostile to Russian technological interests or those engaged in active industrial espionage against sovereign infrastructure.

05

Infrastructure Ownership

All physical hardware, logical substrates, cryptographic kernels, and networking protocols remain the absolute and perpetual property of Cyrillic Company. No license granted herein implies a transfer of ownership or equitable interest in the underlying technology.

06

Cryptographic Licensing

We grant a temporary, non-transferable, revocable license to utilize our proprietary encryption kernels for the specific duration of an approved mission. This license is subject to real-time revocation if security anomalies are detected within the user's connection node.

07

Account Security

Users are solely responsible for the physical security of their access terminals, biometric keys, and two-factor authentication devices. Any breach resulting from user-side negligence is the exclusive liability of the user. We recommend air-gapped terminal management for high-intensity missions.

08

Prohibited Acts: Espionage

Any attempt to map, probe, or reverse-engineer our internal networking architecture, load balancers, or kernel structures is classified as industrial espionage. Such actions will trigger immediate defensive countermeasures and notification to sovereign security authorities.

09

Prohibited Acts: Scraping

Automated extraction of data, architectural blueprints, or metadata (scraping) is strictly prohibited. Our AI-driven defensive nodes monitor all traffic for non-human patterns, and violating nodes will be permanently blacklisted at the hardware ID level.

10

Data Localization

All primary data processing, storage, and archival must occur within Russian territory as mandated by Federal Law No. 242-FZ. Users agree not to attempt to proxy or tunnel traffic in a manner that bypasses these sovereign data localization protocols.

11

Modification of Service

We reserve the absolute right to rotate cryptographic protocols, modify API endpoints, or relocate physical server nodes within the GKP-4 zone without prior notice. These changes are implemented to maintain the highest level of defensive integrity against emerging threats.

12

Commercial Terms

Mission fees are calculated based on computational intensity, bandwidth consumption, and the specific security tier requested (Standard, High-Intensity, or Sovereign). All quotes provided in mission briefs are final and inclusive of sovereign processing taxes.

13

Payment Default

Failure to settle mission credits within the defined timeframe results in the immediate cryptographic shredding of all active access links. Recovering data from shredded links is physically impossible due to our zero-knowledge architecture.

14

Confidentiality Brief

All technical dossiers, architectural diagrams, and communication logs shared by the Operator are classified as 'Top Secret' and are under strict non-disclosure obligations. Unauthorized disclosure constitutes a breach of national security protocols.

15

Indemnification

The User agrees to indemnify, defend, and hold the Operator harmless against any and all external legal actions, claims, or damages resulting from the User's mission objectives, data content, or violation of these sovereign terms.

16

Limitation of Liability

To the maximum extent permitted by Russian law, our liability is strictly limited to the direct computational cost of the specific service failure. We are not liable for any indirect, consequential, or speculative losses arising from mission outcomes.

17

Force Majeure: Network Isolation

We are not liable for outages caused by the physical cutting of intercontinental fiber cables, sovereign network shutdowns, or large-scale electromagnetic interference beyond our controlled environment.

18

Force Majeure: Kinetic Events

Kinetic damage to GKP-4 facilities, including acts of war, civil unrest, or catastrophic substrate failure, constitutes a force majeure event that suspends all Service Level Agreements indefinitely.

19

Audit Rights

The Operator reserves the right to perform real-time security audits on any terminal or node connecting to our hub. Failure to pass an automated security posture check will result in immediate connection termination.

20

User Representations

You represent and warrant that your mission data does not contain unauthorized post-quantum decryption tools, malware, or any algorithmic patterns designed to destabilize sovereign financial or technical systems.

21

Intellectual Property Hardening

Our source code utilizes advanced obfuscation, polymorphic structures, and self-destruct patterns. Any attempt to debug or inspect our binaries is a violation of this agreement and will be treated as an attack on our IP.

22

Open Source Components

While our core kernels are proprietary, specific utility modules may utilize open-source components. These are integrated under their respective licenses and are clearly documented within the mission's technical dossier.

23

Third Party Links

We provide bridges to external nodes for mission requirements but assume no responsibility for the cryptographic integrity or privacy practices of nodes operating outside our direct sovereign control.

24

Mission Termination

The Operator may unilaterally terminate any active mission if we detect ethical misalignment, unauthorized secondary objectives, or if the mission poses a threat to the stability of the Cyrillic ecosystem.

25

Data Shredding

Upon the conclusion or termination of a mission, all associated temporary data is overwritten 35 times using the Gutmann method across all physical platters to ensure absolute non-recoverability.

26

Arbitration

All disputes arising from this agreement that cannot be settled through direct negotiation must be submitted to the Russian Arbitration Court in Moscow for final and binding resolution.

27

Language of Treaty

This treaty is provided in English for convenience, but the Russian language version remains the only legally authoritative and binding text in any court of law or arbitration.

28

Waiver of Rights

Any failure by the Operator to enforce a specific clause at any time does not constitute a waiver of our right to enforce that clause or any other clause in the future.

29

Severability

If any provision of these terms is found to be invalid or unenforceable by a competent Russian court, that provision shall be limited or eliminated to the minimum extent necessary, and the remaining provisions shall remain in full effect.

30

Export Controls

Users must comply with all Russian Federation export control laws regarding high-security software and cryptographic technology. Re-exporting our kernels to restricted jurisdictions is strictly prohibited.

31

Biometric Data Consent

Enabling biometric authentication implies explicit consent for the Operator to process such data for the sole purpose of identity verification and terminal access control.

32

Zero Knowledge Protocol

We operate on a zero-knowledge basis. We do not store, manage, or have access to your private encryption keys. If you lose your keys, the data within your mission envelope is permanently and irretrievably lost.

33

Emergency Override

In the event of a detected global security threat, the Operator may initiate an emergency override, locking down all external nodes and isolating the GKP-4 hub from the global internet.

34

User Feedback

Any technical feedback, bug reports, or suggestions for infrastructure improvement provided by the User become the exclusive intellectual property of the Operator without compensation.

35

Non-Solicitation

During the term of engagement and for two years thereafter, the User shall not attempt to recruit, solicit, or hire any engineers or technical staff employed by Cyrillic Company.

36

Marketing Disclosure

The Operator may list the User's corporate logo as a 'Mission Partner' in internal reports and secure marketing materials unless an explicit non-disclosure request is filed during mission onboarding.

37

Compliance Audits

Partners on the 'High-Intensity' and 'Sovereign' tiers must undergo annual compliance audits conducted by our internal security board to ensure continued alignment with our technical standards.

38

Security Clearances

Accessing specific logical zones within the GKP-4 infrastructure requires personal security clearance vetting. We reserve the right to deny access based on our internal risk assessment protocols.

39

Hardware Standards

Connecting terminals must meet our minimum hardware requirements for TPM 2.0, secure boot, and encrypted RAM. Substandard hardware will be denied connection to the secure hub.

40

Network Latency

We optimize for maximum throughput within the Russian Eurasian network. We do not guarantee specific latency or packet loss metrics for nodes connecting from other continents.

41

Kernel Access

Direct access to our low-level kernels is strictly prohibited. All user-side operations must be performed through our authenticated API layers and secure sandboxes.

42

Data Sovereignty

While you retain legal ownership of your mission data, Cyrillic Company maintains absolute control over the cryptographic envelope and the physical substrate where it resides.

43

Sub-processing

We do not utilize third-party sub-processors for data handling. All processing is conducted 'in-house' by our own engineers and AI nodes within our own facilities.

44

Publicity

This engagement is classified by default. Any public disclosure, press release, or social media mention regarding your work with Cyrillic Company requires prior written approval from our Moscow headquarters.

45

Amendments

We update these terms periodically to reflect new security protocols. Amendments are pushed to your terminal interface; continued mission activity implies immediate acceptance of the updated terms.

46

Entire Agreement

These Terms of Engagement, along with the specific Mission Brief and technical dossiers, constitute the entire legal agreement between the User and Cyrillic Company, superseding all prior communications.

47

No Partnership

This agreement establishes a service-provider relationship only. It does not create a legal partnership, joint venture, agency, or employment relationship between the parties.

48

Survival

All clauses regarding confidentiality, intellectual property, indemnification, and limitation of liability shall survive the termination or conclusion of this agreement indefinitely.

49

Notices

All legal notices and official communications must be sent via our verified E2EE email node. Notices sent via traditional mail or unencrypted channels will not be considered legally received.

50

Effective Date

These terms are fully effective and enforceable as of January 17, 2026, and apply to all users, nodes, and missions currently interacting with the Cyrillic Company infrastructure.

End of Document | CYR-TOS-V4-2026