Scope and Data Categories
This policy applies to the LaoVPN website, user panel, clients, and features directly related to subscription services. When these features are used, the service handles only the data needed for account verification, order delivery, traffic accounting, troubleshooting, security protection, and service improvement.
No email address is required for registration; a username and password are sufficient. The service therefore does not collect a registration email as mandatory information. Account data mainly includes the username, authentication credentials, subscription status, used traffic, and remaining entitlements. Passwords are used for identity verification and are not displayed to staff as readable content.
Order data includes the selected plan or traffic package, amount due, payment status, transaction reference information, creation and completion times, and refund or dispute records. Analytics may include pages visited, referring pages, browser category, device category, language setting, access time, and network address. This data is used to identify page failures, abnormal requests, and whether content is clear and effective.
No-Logs Position and Connection Data
LaoVPN follows a no-logs policy. It does not record which websites users access or retain browsing content, communications, or historical records that could link an account to a specific access target. The service also does not create persistent connection logs for long-term tracking of individual network activity.
While a route is operating, temporary session state may be generated as needed to complete routing, verify subscription status, calculate plan traffic, and prevent abnormal usage. This state serves only the current connection and is not retained as searchable personal access history after the connection ends. The account side still stores aggregated plan traffic so remaining subscription allowances can be displayed and applicable billing rules enforced, but this summary does not include a list of visited websites.
When troubleshooting a connection issue, users may voluntarily submit client messages, system platform, selected region, and the time period when the issue occurred. Tickets should contain only information needed to resolve the issue and are managed according to the retention rules for tickets and account data after processing is complete.
Cookies and Local Storage
The website uses Cookies or browser local storage to retain login sessions, interface language, necessary security state, and functional preferences, so the current session remains recognized after navigation. The user panel also stores authentication state locally to support access to account overview, plans, clients, and ticket features.
Analytics runs through same-origin paths on this website and is used to aggregate page visits and conversion entry points. Results help improve page structure, identify loading failures, and assess whether help content is effective; they are not used to build cross-site advertising profiles. Disabling necessary storage may prevent the login state from being maintained, while clearing browser data removes sessions and preferences stored on the current device.
Payment Processing and Third-Party Services
LaoVPN supports Alipay, WeChat Pay, and USDT. Payment confirmation is handled by the relevant third-party payment service, and information submitted during payment is also subject to that service’s own privacy rules. The service receives the result information needed to complete orders, confirm receipt of funds, process refunds, and review disputes, such as the order amount, payment status, and transaction reference information.
Third-party services may process payment information independently according to their legal obligations, risk-control rules, and data policies. LaoVPN does not control their internal retention periods. Before choosing a payment method, users should read the terms and privacy information displayed by the relevant service.
Data Retention, Access, and Deletion
Account authentication data is retained while the account remains active. Order, refund, and payment confirmation records are retained for as long as needed to provide subscriptions, handle disputes, complete financial reconciliation, and meet applicable legal obligations. When personal identification is no longer needed, the relevant data is deleted or de-identified. Analytics is retained according to operational and security needs; expired data is deleted or converted into aggregated results that cannot be directly linked to an account.
Users can log in to the user panel and submit a ticket to request access to, correction of, or deletion of account-related data. Deletion requests are processed after identity verification. If some order records are still needed for refunds, dispute handling, or legal obligations, those records are restricted and retained only for the relevant purpose, then deleted or de-identified when that purpose ends. Residual copies in backups are overwritten according to the backup lifecycle and are not used for routine business access.
Policy Updates
This policy may change as service features, data-handling methods, or applicable rules change. Updated text will be published on this page, and the last-updated date at the top will be changed accordingly. If an update materially affects data categories, processing purposes, or user rights, the website or user panel will provide a prominent notice.
Users are encouraged to review this page regularly before continuing to use subscription services. For questions about this policy or data processing, log in to the user panel and submit a ticket; do not include sensitive information unrelated to the issue.