Service documents and conditions
Last revised: 14 November 2026
NetLiberty Privacy Policy
This policy describes the information processed, its purposes, necessary disclosures and how to submit privacy requests.
1. Scope and purposes
This policy describes information needed for accounts, orders, payments, delivery, security and support. We seek information proportionate to those purposes. Telegram, payment networks and model services are independent services with their own conditions.
2. Account and order data
Numeric Telegram ID, optional username, language, registered email, verification state, orders, payments and wallet-ledger information may be retained to provide services. Telegram first/last-name fields are removed before bot messages are queued; free text may still contain information you enter. Identity documents are not requested in the ordinary flow.
3. Sign-in and device data
Sessions and relevant technical events are processed for access and security. The website may store theme preferences, necessary sign-in information and request-cart data in your browser. Technical logs may include IP addresses and request paths. Default settings do not use advertising cookies or third-party font CDNs; this does not imply an absence of all technical data.
4. Payments and blockchain
Necessary payment-request and transaction information is processed for matching. Public blockchain records are outside NetLiberty deletion control. Wallet passwords, private keys and recovery phrases are never required for payments or support.
5. AI conversations
In bot AI support, message text and limited conversation context, together with public knowledge and catalog information, are sent through OpenRouter to a model service to generate a reply. AI-enabled ticket support may also process message text and relevant public information. Email fields and private ticket links are excluded during AI-request preparation, but you should not put sensitive information in free text. AI output can be wrong and does not confirm payments or execute operations.
6. Private support
Tickets store email, subject, product, conversation text and timestamps for support. A private tracking link may grant access to a request; do not share it. An AI-chat message is not automatically a ticket or human notification.
7. Stock notifications
A notification request stores email, product identifier, language and consent time. Notifications activate after email verification and can be cancelled through the provided process. Cancelled requests leave the queue and are deleted within 30 days.
8. Access and protection
Administrative access should be limited to legitimate service purposes and authority. Encryption at rest is used for delivery information, license stock and bot-queue content in their respective systems. Security measures do not provide absolute immunity. One customer must not receive another customer’s data.
9. Retention
Current ticket policy deletes tickets 90 days after last activity. Necessary order, payment and credit records are retained for accounting, disputes and applicable requirements; no unconfirmed universal period is promised. Deletion from NetLiberty does not delete records held by Telegram, public blockchains or independent services.
10. Requests and contact
Use your account, tickets or contact@netliberty.space for access, correction, deletion or privacy questions. Authority may need verification to protect the account; applicable rights and legal retention constraints are reviewed. Do not send sign-in codes, passwords or private keys.
11. Updates
A new policy version is made available with its publication date. Significant processing changes should be explained appropriately. This policy alone is not a claim of security certification, comprehensive legal compliance or absolute anonymity.