Device Linkage & Multi-Account Restrictions: A Technical Deep-Dive
This page explains how our system securely links user accounts to devices and prevents unauthorized access.
This documentation provides an exhaustive technical analysis of the hardware-level metrics utilized by our Access Management systems to prevent account sharing and ensure precise resource allocation.
1.0 The Hardware Registration Protocol
Traditional, cookie-based session tokens are fundamentally insufficient for managing advanced local execution environments, as they can be easily transferred across unverified hardware. To resolve this inconsistency, our backend architecture relies on persistent, hardware-level device linkage via the Settings.Secure.ANDROID_ID.
Authentication Sequence
Initial Initialization & Retrieval
During the primary deployment event, the local client securely polls the operating system for its unique Secure Settings Identifier (SSAID). This string is safely processed locally before being transmitted to the main authorization servers.
Standard Ledger Assignment
The processed identifier is permanently bound to the user's active license record within the relational database. Any subsequent requests to download orchestration data will pause if the requesting device's record does not perfectly match the ledger.
2.0 Lifecycle Management & Multi-Instance Management
This strict 1:1 hardware tethering prevents "Account Polling"—a scenario where a single licensed account is distributed across a fleet of unverified endpoint devices. Anchoring the license to physical hardware ensures that backend system load balancing remains predictable.
> ❌ Notice: This device is already linked to an account.
This diagnostic notice is triggered if an authentication attempt is initiated from a hardware profile that does not align with the stamped ID in the registry.
Ref: DEVICE LINK
III. System Directive Checklist
01. Primary Device Validation
Ensure your initial login is executed on your designated primary operational device, as the binding occurs instantaneously upon first authentication.
02. Hardware Migration Protocols
In the event of hardware replacement, updating the SSAID record requires a standard support ticket to verify the transfer's authenticity.
03. System Resets
Executing a full factory reset on certain handsets may regenerate the OS-level SSAID, which will necessitate a standard infrastructure migration request.