1. Who this policy covers
Klyrix VPN is a business-to-business (B2B) whitelabel platform. We provide encrypted WireGuard infrastructure, billing and delivery to business partners ("Partners" or "tenants"), who resell access to their own end customers under their own brand, bot and domains.
This policy explains how Mentoforce Information Technology L.L.C ("Klyrix", "we") processes data when operating the platform. It is written for the Partners who contract with us and for the end users those Partners serve.
For the personal data of an end user, the Partner who onboarded that user is the data controller and Klyrix acts as a data processor on the Partner's instructions. For a Partner's own account data, Klyrix is the controller.
2. Our zero-log commitment
Klyrix is built around a zero-log principle. We do not record the browsing activity of end users. In particular, we do NOT keep:
- Histories of the websites, domains or IP addresses a user visits;
- DNS queries tied to an identity, or per-site bandwidth breakdowns;
- The contents of any traffic passing through the tunnel;
- Mappings between a user's original IP address and the destinations they reach.
Because these records are never created, they cannot be sold, handed over, lost or subpoenaed. We do not sell or rent any data to third parties, and we do not run advertising or behavioural tracking on our network.
3. The limited data we do process
To run a paid, multi-tenant platform we process a minimal set of operational data:
- Partner account data — the partner bot identity, contact details and settings needed to operate the tenant;
- Billing records — crypto payment transactions and balances used to bill Partners and reconcile their customers' package purchases;
- Quota counters — aggregate byte totals per account, used only to meter usage against a plan. These are running totals, not per-destination logs;
- Connection key material — WireGuard public keys and assigned tunnel addresses needed to route a session;
- An end user's Telegram identifier (per tenant) — used to link a subscription to a chat;
- Operational telemetry from our own servers — health, capacity and uptime signals that contain no user traffic.
4. Traffic classification and DPI
The platform performs automated, real-time classification of traffic to enforce security filtering and the routing rules a Partner configures (for example, blocking malware and ad/tracker domains for everyone, and redirecting certain categories to a Partner's own destinations).
This classification — which may include deep packet inspection (DPI) techniques — happens in transit and in memory, at the moment a request is handled. We act on the category, then discard it. We do not store the result, attach it to a user identity, or build a browsing profile from it.
In other words: the system can decide "this request belongs to a blocked or redirected category" in real time, without ever writing down which user went where.
5. Controller and processor roles
Klyrix is a processor for end-user data and acts only on documented Partner instructions. The Partner, as controller, is responsible for the lawful basis of processing its customers' data, for the notices and consents it gives them, and for honouring their data-subject requests.
Klyrix is the controller for Partner account and billing data, which we process to provide and secure the platform and to meet our own legal and accounting obligations.
6. Where data is processed and transfers
Klyrix operates a global fleet of entry and exit servers so that traffic can be delivered close to end users. Operational and billing data may therefore be processed in more than one country.
Where data crosses borders, we rely on appropriate safeguards and limit what is transferred to the minimal operational set described above. No browsing logs are transferred, because none are kept.
7. Retention
We keep operational and billing data only for as long as needed to run the account and meet legal, tax and accounting duties, after which it is deleted or anonymised.
Quota counters reset on each billing cycle. Connection keys live only as long as a device is enrolled. There are no traffic logs to retain.
8. Security
Traffic is encrypted end to end with the WireGuard protocol. Administrative access to the platform is protected with mandatory two-factor authentication, encrypted secrets, and row-level database isolation between tenants.
No method of transmission or storage is perfectly secure, but we design the platform to hold as little sensitive data as possible — the strongest protection is the data we never collect.
9. Rights of end users
Because the Partner is the controller of its customers' data, end users should direct privacy requests — access, correction, deletion — to the Partner whose service they use. Partners may contact us to fulfil a verified request that depends on platform data.
10. Changes and contact
We may update this policy as the platform evolves. Material changes will be reflected here with a new "last updated" date.
Privacy questions: privacy@klyrix-vpn.com. Abuse reports: abuse@klyrix-vpn.com.