Most VPNs need an email and a payment method. Both create durable links between you and your traffic, even before the first packet is encrypted. The provider can be subpoenaed, breached, sold. The card processor knows you bought a VPN and roughly when. Marketing affiliates know you clicked a specific ad. Your relationship with the service is a paper trail before you've used it once.
QPOL takes a different route. Identity is a voucher — a bearer code, redeemable, transferable. You acquire it through any channel that suits you (Telegram bot, partner store, gift), redeem it in the app, connect. The service has no profile to hand over, no card on file, no notification mailbox tied to your network behaviour.
The model has trade-offs. There's no "forgot my password" flow, because there's no password. Recovery is a property of the voucher itself: keep the voucher, you keep access. Lose it, and there's no support pathway to bind a new code to your former usage — by design.
For multi-device usage you redeem the voucher on each device or share an activation link. Concurrent device limits are tied to the voucher type; the cabinet shows the current count. The cabinet itself is a thin layer for managing balance and rate visibility, not a profile linking voucher to traffic.
Anonymity at the QPOL layer is not a complete privacy story. The traffic still leaves the tunnel somewhere; that exit is observable to whoever sits at the other end. End-to-end encryption, operational discipline, careful website choices — those don't go away. What the voucher model removes is the metadata layer at the VPN provider: the ledger that, in most VPN companies, is the largest single pool of user data they hold.
If you're comparing this to a conventional VPN's privacy story, the question to ask is not "do you keep logs?" — every provider says no — but "what is the smallest piece of identifying data you collect, and where does it live?" For QPOL the answer is the voucher. There's nothing else to find.