Privacy policy

About this policy

This policy describes how information is handled when you use VPNKA at vpnka.xyz and the customer portal at dash.vpnka.xyz
The VPNKA administration operates the service and handles customer requests

For data questions, contact VPNKA support
This document is available without an account; its current revision date appears above

Information we process

• Account information you provide through the portal, such as an identifier, username, contact details and settings
• Your selected plan, access period, devices, usage counters and payment status needed to administer the subscription
• Technical information received by the website and portal: IP address, browser, device, language, request time and error details
• Support messages and attachments you submit

Payment credentials are entered through the payment provider’s interface
To record a payment, the service needs the order details, amount, currency, transaction identifier and payment status

Do not send passwords, full card details, confirmation codes or private connection keys to support

Website analytics

The public website uses an analytics service to understand how visitors use the site
It records random browser and session identifiers, page paths, language, referral source, active time, plan selections and visits to the customer portal

The browser identifier is stored in localStorage; the session identifier and first or returning visit status are stored in sessionStorage
These identifiers do not contain your name or email, but combined with technical information they can distinguish visits from the same browser

The analytics server receives your IP address and browser information, and may derive an approximate country from the IP
Query parameters and URL fragments are removed from the referral address
This script does not transmit form contents, passwords or payment credentials

The team may receive operational notifications about website activity and interest in plans through Telegram
These notifications concern website visits, not the contents of VPN traffic

You can remove local identifiers using your browser’s site data settings
This does not automatically remove records already received by the server; contact support to request deletion

Why information is needed

• To create and administer accounts, provide paid connections and track subscription periods
• To confirm payments and handle renewals or refund requests
• To answer questions and investigate technical problems
• To protect accounts and infrastructure against abuse
• To understand and improve the website and subscription process

Processing is limited to what is needed to provide the service, meet applicable obligations or rely on another lawful basis
Where separate consent is required for a particular activity, that consent must be obtained separately

Service providers and disclosure

The service uses hosting, payment, analytics and operational notification providers
Information needed for each task may be shared with those providers; it may also be disclosed in response to a binding lawful requirement

Payment providers and other external services have their own data policies
The information they receive depends on the payment method and the fields you complete

Retention and protection

Information is retained for as long as needed to administer accounts, resolve requests, record payments and meet applicable requirements
Once there is no remaining basis for retention, it must be deleted or anonymised

Access to operational information should be limited to service administration tasks
The website and customer portal use HTTPS; account protection also depends on keeping your password and device secure

A VPN does not replace system updates, careful password handling or checking website addresses

Your requests and policy updates

Contact support to request information about processing, correction or deletion, or to withdraw consent where processing relies on it
We may need to verify account ownership to protect your information

Some records may be retained where a binding legal basis remains
Requests are handled within the time limits imposed by applicable requirements

Updates are published here with a revised date
Where a change requires new consent, publishing the policy does not replace that consent