In the current implementation, Nexelorant stores the Telegram ID, the Telegram username where one exists, linked wallet addresses, deal history and related system data, correspondence with support, data needed to operate Nexelorant's internal analytics features, and internal records linking the Telegram account, wallets, and operations and ensuring that state is correctly displayed in the interface and the database.
In the current implementation, Nexelorant does not collect or store, as separate categories, IP addresses, device or browser fingerprints or similar device identifiers, email addresses, phone numbers, or KYC data. Separate cookie-based web analytics, advertising trackers, and third-party behavioral analytics are not used. Nexelorant's internal analytics features are not third-party, cookie-based web analytics.
Some data is stored on Nexelorant's own server-side infrastructure: interaction through Telegram and the server database requires retaining information to identify the user, link their account, wallets, and operations, and correctly display state. This information may constitute personal data under applicable law; the user's anonymity is not guaranteed.