Scope of this policy
This policy covers account registration, plan purchases, client use and user panel operations on vpnsj.com, as well as connecting to international routes through the service. It does not cover third-party sites and services that users reach through VPNSJ — those sites have their own privacy rules, and their data handling is not decided by this service.
The service provides subscriptions for cross-border access. The account system requires only a username and password, and registration does not ask for an email address. In normal use, VPNSJ does not hold users' email addresses, real names, home addresses or ID documents, and does not require them in order to activate a route.
What data we collect and why
By function, the data VPNSJ handles falls into the categories below. Each one has a specific purpose, and none is reused for anything else.
- Account data: username, password digest, registration date, account status. Used for login checks, account recovery and handling of abnormal accounts.
- Order and billing data: plan tier, order number, amount, payment channel marker, activation and expiry dates, data used. Used to activate routes, calculate remaining data, and handle mid-term upgrade price adjustments and refunds.
- Device and connection data: client type and version, technical identifier of the signed-in device, identifier of the route used, connection start and end times, and error codes when something fails. The same account can sign in on an unlimited number of devices; device identifiers are used only to spot unusual logins and to diagnose connection failures and speed problems.
- Visit statistics: aggregated data such as page views, referral channels and device types. Used to decide which documentation needs expanding and which pages load slowly.
Screenshots, text and contact details that users volunteer in a ticket are used only to resolve that issue. They are not folded into other purposes and are not used for marketing.
How we handle connection logs
VPNSJ does not record which websites users visit, does not store the contents of DNS queries and does not retain session content. On the route side, only the minimum technical data needed to keep the service running is kept: aggregate counters of route load and error records from outage windows. Aggregate counters are not linked to any specific account's browsing destinations.
Connection records (connect time, disconnect time, assigned route) are kept for the shortest period needed for billing reconciliation and troubleshooting, then cleared on a set cycle. These records are used to verify data usage and to resolve issues such as a connection failing right after activation; they are not used to reconstruct browsing behaviour.
If a lawful request for data is received, VPNSJ cooperates within the limits of legal process. Because no records of browsing destinations are kept, the only information that can be provided is at the account and order level.
Cookies and local storage
This site does not use third-party advertising trackers. It stores a small amount of data locally in the browser, for the purposes below.
- Language preference: remembers the last language selected, so you do not have to choose again when moving between pages.
- Login session: a session identifier written after signing in to the user panel, used to keep you signed in and cleared when you sign out.
- Interface state: temporary state such as the selected plan period or your position in a list, which may be lost once the page is closed.
You can view and clear this data in your browser settings. After clearing it you will need to sign in again, and the language will revert to your browser default. Disabling local storage does not affect reading the documentation pages, but the user panel cannot keep you signed in.
Payments and third-party processing
Payment is completed through Alipay, WeChat and USDT. With the first two, the page redirects to that payment channel's checkout; account balance, card details and verification are handled by the payment channel, and VPNSJ neither sees nor stores them. For USDT, only the confirmation result of the on-chain transfer and its link to the order are recorded.
Once payment completes, the order number, amount and payment status are passed back to VPNSJ to activate the plan and for later reconciliation. When a refund is requested, VPNSJ submits the order number and amount to the payment channel and nothing else — no account password, no connection records. The progress of a 30-day no-questions-asked refund can be tracked in the user panel.
Data retention, deletion and policy updates
Retention periods differ by purpose.
- Account data: kept while the account is active; deleted or anonymised on the cleanup cycle after closure.
- Order and billing records: kept as needed for refund disputes and bookkeeping; during that period they are used only for reconciliation.
- Incident and connection records: cleared on the troubleshooting cycle, not archived long term.
Deletion requests: open a ticket in the user panel and state what should be deleted (the account, the order records, or both). A deleted account cannot be restored, and any unused data packages in it are voided at the same time; if you plan to keep using the service, confirm before you submit. Once the request is received, account ownership is verified, and the result is handled and answered within a reasonable period.
Policy updates: this policy is updated as features change and compliance requirements evolve. When a material change occurs, the date at the top of the page is updated and the key points are listed in an announcement in the user panel. Continued use of the service means you accept the updated policy; if you do not agree, you can stop using it and request a refund under the 30-day no-questions-asked refund terms.
Other questions about accounts and data can also be submitted through the ticket entry in the user panel.