
To maintain a stable, high-speed connection between your browser and our neural infrastructure, Aigenix utilizes local storage states, session tokens, and cookies. This protocol explains how and why we deploy them.
Cookies and session tokens are tiny, encrypted text files downloaded to your device when you access the Aigenix terminal or public site. They allow our edge nodes to recognize your hardware, maintain your secure authentication state, and remember your dashboard configurations without requiring you to repeatedly re-authorize.
We classify our active tracking protocols into three distinct categories based on their function within the matrix:
While the majority of our cookies are natively served (First-Party), we do deploy a limited number of vetted Third-Party cookies. These are strictly limited to authorized cloud infrastructure monitors (to verify uptime SLAs) and anonymous analytical aggregators that track global site interaction flows.
You maintain ultimate authority over your local storage. You can configure your browser to intercept, block, or purge these tokens at any time. However, disabling Core Essential Tokens will instantly terminate your session and revoke access to the Aigenix API Terminal.
To purge your session states manually, navigate to your browser's Security/Privacy settings and clear local storage for the `aigenix.com` domain.
As our neural architecture evolves, the tokens required to optimize it may change. We will reflect any new structural cookies or trackers in this document and notify active Operators of critical changes to authentication protocols.
If you require a detailed breakdown of specific encrypted token hashes or have questions regarding your local storage privacy, initiate a connection with our compliance team: