change around some things

serviceagreement.txt

@@ -14,14 +14,16 @@ Section 1.1: Formation of Contractual Relationship
 This Spacebar Network Services Agreement (hereafter referred to explicitly as the "Agreement") represents a binding, formal legal contract executed between you, the individual end-user, and Spacebar Network (additionally referenced throughout these provisions as "us", "our", "the network", "Spacebar", "SPBR", or "SPFN"). By installing the required network environment configurations, creating an account, authenticating your physical hardware console with our dynamic directory nodes, transferring information packets, or accessing any service, game server, community forum, or code repository tied to Spacebar, you affirm that you possess the full legal maturity and mental capability necessary to form a binding contract within your home jurisdiction. If you are accepting these terms on behalf of a minor child, you assume full personal liability and financial responsibility for all activities, data transactions, and behavioral infractions occurring under that child's network account.
 
 Section 1.2: Implicit Scope and Unconditional Acceptance
-Your interaction with any structural node of the Spacebar Network establishes your unconditional agreement to be bound by the precise text of this document, our auxiliary rules, and our Code of Conduct. You explicitly acknowledge that this framework forms a social and technological contract designed to safeguard the stability, software equity, and individual dignity of the network ecosystem. You are fully bound by these clauses regardless of whether you have elected to inspect them in their entirety. Spacebar preserves the unrestricted right to unilaterally modify, suspend, or revoke your access privileges, database entries, or account status at any time, for any reason, without notice or right of appeal. If you disagree with any portion of these provisions, you must immediately terminate your network session, erase all configuration records, and sever your connection to our servers.
+Your interaction with any structural node of the Spacebar Network establishes your unconditional agreement to be bound by the precise text of this document, our auxiliary rules, and our Code of Conduct. You may view these in their non-shortened form on an electronic device at "https://git.spbr.net/spacebar/policy/". You explicitly acknowledge that this framework forms a social and technological contract designed to safeguard the stability, software equity, and individual dignity of the network ecosystem. You are fully bound by these clauses regardless of whether you have elected to inspect them in their entirety. Spacebar preserves the unrestricted right to unilaterally modify, suspend, or revoke your access privileges, database entries, or account status at any time, for any reason, without notice or right of appeal. If you disagree with any portion of these provisions, you must immediately terminate your network session, erase all configuration records, and sever your connection to our servers.
 
 ARTICLE 2: PRIVACY POLICY, VARIABLE MINIMIZATION, AND ARCHITECTURE
 
 Section 2.1: Philosophy of Data Minimization
+
 Spacebar Network adheres strictly to the principle of data minimization. We collect, process, and retain only the minimal operational metrics required to execute server handshakes, track game progression data, maintain network stability, and perform debugging analysis. We do not engage in commercial data profiling, nor do we sell, rent, lease, trade, or distribute user variables to marketing networks, commercial third parties, or analytical brokers. All logged parameters are stored securely and maintained only for the duration required to achieve technical infrastructure functionality.
 
-Section 2.2: Comprehensive Breakdown of Data Variables Processed
+Section 2.2: Data held used for communication
+
 To initialize and sustain an account profile within our network directory, the following technical data categories must be submitted, verified, and mapped within our database infrastructure:
 
 * Principal ID (PID): Upon user profile creation, our server node dynamically generates a distinct, non-identifiable numerical value designated as your Principal ID or PID. This index value is computed purely through a continuous arithmetic sequence and does not extract or incorporate real-world identity markers. It serves as your primary database lookup and authentication index.
@@ -31,11 +33,13 @@ To initialize and sustain an account profile within our network directory, the f
 * Country of Origin: Your localized country setting is extracted automatically from your console hardware setup and transmitted during your registration sequence. This string is mapped to your unique PID and returned to the console client upon application request. Because the underlying legacy game modules require this localized geographical data to route execution pathways, the network cannot achieve baseline functionality without processing this information.
 
 Section 2.3: Security
+
 We enforce multi-tiered defense protocols to insulate our network storage files from external exploitation, structural leaks, or unauthorized exfiltration.
 
 * Security Breach Disclaimer: While our servers do not manage raw, directly identifying real-world personal profiles, we pledge to execute exhaustive monitoring routines to maintain environmental safety. In the event that we confirm an unauthorized database intrusion or structural exploit, we commit to informing our active user base within 30 days of our official verification of the incident.
 
 Section 2.4: Handshake Dynamics and Matchmaking Telemetry
+
 Executing multiplayer sessions requires real-time coordination between different components of our network. When your game client makes an initial connection request to the Account (ACT) server to access an active NEX game server, a secure authentication handshake occurs. The encrypted token payload delivered back down to your client application contains your Principal ID (PID), an isolated NEX password (which exists as a distinct security string separate from your core account password and is known exclusively by the primary account server, the target game server, and your local client), a temporary session token generated exclusively for that unique connection instance, and the precise host address and network port of the target game server.
 
 Upon receiving this payload, your local game client immediately redirects its connection and makes a verification request directly to the specified NEX game server. To validate your identity, the client transmits the payload components to the game server, which concurrently opens a secure backend transmission line directly to the core account server to verify the legitimacy of your credentials. The variables shared back to the game server by the account server during this validation loop consist of your specific NEX password, your master Principal ID (PID), and your active session token. This complex loop is implemented strictly to achieve user authentication and absolute account validation.
@@ -43,15 +47,17 @@ Upon receiving this payload, your local game client immediately redirects its co
 Furthermore, our system infrastructure temporarily processes the internet protocol (IP) address provided dynamically by your console hardware. This network address is stored strictly within volatile system memory and is processed for the sole purpose of enabling peer-to-peer (P2P) networking arrays and population matchmaking routines with other active players on our network. Your IP address is shared with other active players during these matchmaking sequences so that individual player consoles can establish direct communication lines with one another.
 
 Section 2.5: Web Cookies and Tracking Elements
+
 Our external websites, administrative registration portals, and code storage environments may occasionally deploy text cookies to optimize site functionality, remember user display preferences, and review layout engagement. Cookies represent tiny data strings written directly to your browser application to recognize returning traffic. Spacebar Network does not harvest identifying real-world variables via cookies without your voluntary confirmation. These files are used for performance analytics, interface testing, and site layout adjustment, meaning deployment parameters may vary across the individual web domains inside our project. Typical implementations involve evaluating user traffic density, counting unique sessions, and recording site performance metrics. Users can customize their web browsers to block cookie tracking or signal incoming cookies, though certain interactive portions of our web portals may become unavailable as a result.
 
+
 ARTICLE 3: CODE OF CONDUCT, USER EXPECTATIONS, AND PROHIBITED ACTIONS
 
 Section 3.1: Commitment to Community Dignity and Safety
 Please note that we have rules to follow. These behavioral boundaries, restrictions, and expectations apply unconditionally across all aspects of the Spacebar network, our official Discord community, and our public or private Git repositories. The primary objective of our community framework is to build and protect a shared environment that respects and elevates the inherent human dignity, unique contributions, and individual safety of all participants. We are strictly dedicated to maintaining a collaborative culture that protects all members, extending equal participation privileges to all individuals regardless of their personal background, race, ethnicity, caste, skin color, physical age, structural body characteristics, neurodiversity, physical or cognitive disability, biological sex, gender expression, gender identity, romantic or sexual orientation, native language, personal philosophy, religious conviction, national origin, social background, socio-economic standing, or formal level of education. To preserve these essential values, you agree to consciously evaluate your actions, align your communications with our shared community principles, and completely refrain from the prohibited activities detailed below. Threats of executing these behaviors, or the open promotion of these actions, represent a material breach of this agreement.
 
-
 Section 3.2: Code of Conduct
+
 * Do not harass people: You are completely barred from executing harassment, which is defined as intentionally cross-communicating across multiple platforms against an individual's explicit desires, violating stated personal boundaries, tracking a user across digital nodes, or continuing unwanted communications or attention after a clear request to cease has been delivered.
 
 * Do not self-advertise on the network: You must not exploit our servers, text nodes, or communication channels to distribute commercial advertising materials, multi-level marketing pitches, unsolicited promotional text links, or self-advertise external services, products, or communities outside the pre-arranged, designated zones of our network ecosystem.
@@ -68,6 +74,7 @@ Section 3.2: Code of Conduct
 
 * Do not impersonate anyone, including staff members: You must not manufacture a false or misleading identity by adopting the name, title, profile, or avatar of another player, developer, or official moderator, nor may you utilize an assumed identityto mask your presence or evade a prior ban or network disciplinary action.
 
+Note that these may be changed, and you are held by our Network Rules as well.
 
 Section 3.3: Software Integrity, Fair Gameplay, and Modification Limitations