FOR MOST OF YOU IN TECH WHO ARE CONFUSED about the bank and password stuff: I'm an idiot who set up a portal and platform that is entirely Proton VPN based. It's complicated and stupid. I put all my eggs in one basket. I screwed that part up. But I can't even do anything now. I am trying my best to fix my bank and password app as it’s protections are just very different so it will take awhile and phone call and resetting etc, but it could have been remedied if i was just able to use protonvpn. I'm paying highest tier on Proton and have used human help before. Yes, I know I shouldn't have made my password manager VPN-dependent and my security and all that. I know that was dumb. But I did it because Proton promised security. I didn't know their abuse detection would permanently destroy my connection with no human review. Please don't tell me what I should have done, I know. I just need help fixing this now.

Images for proof:

https://ibb.co/7dbHF6LC https://ibb.co/xWR1Zzf https://ibb.co/KzrsDTZy

Uploaded in other host in case above goes down:

https://i.postimg.cc/hj6K0CKv/emails.png https://i.postimg.cc/V6pzF7zz/protonplan.png https://i.postimg.cc/0QF9Ct9N/PROTONVPNDESTROYINGMYLIFE.png

Here is simple log:

Sending handshake response to peer 1 ... Keypair X destroyed ... Keypair Y created State changed to Connected ... VPN state changed: Connected, Error: None, LocalIP: 10.2.0.2 ... LocalAgent received: {"status": {"state": "connected", "features": {"split-tcp": true ...}}}

2026-06-27T04:25:45.309Z | INFO | PROTOCOL | [TUN] [ProtonVPN] Peer 1 created | {"Caller":"StatusManager.ReceiveLogsActionAsync:83"} 2026-06-27T04:25:45.309Z | INFO | PROTOCOL | [TUN] [ProtonVPN] Monitoring MTU of default v4 routes | {"Caller":"StatusManager.ReceiveLogsActionAsync:83"

and here is what Proton is doing to me (it may not be on purpose but it has the effect like it is on purpose). caution: it's scary and triggering for some:

1. Network Gaslighting

This is the most accurate psychological and technical crossover term. The Proton VPN interface explicitly greenlights your connection as "Connected" and takes your subscription money, but secretly sabotages the back-end data stream. It forces the user into an exhausting loop of troubleshooting their own router, device, or browser, masking the provider's active hostility as a local technical glitch.

2. Malicious Tarpitting (Hostile Sandboxing)

In cybersecurity, a "tarpit" is an authorized trap designed to slow down actual hackers. When turned against a paying customer, it becomes Hostile Sandboxing. Instead of giving you a clean, honest disconnection message, the VPN traps your account in a digital quicksand loop. They deliberately let you authenticate just to break your active sessions, ruining your network reputation in the process. 3. Account Poisoning / Persona Trashing

By forcing your connection to cycle up and down every second, the VPN provider is actively poisoning your digital signature. They know this specific traffic pattern mimics a rogue botnet. By forcing your device to emit these "dirty" packets, they are intentionally trashing your IP reputation, forcing external security networks (like Cloudflare, Google, and major banks) to blacklist your identity.

4. Constructive Denial of Service (CDoS)

In employment law, "constructive dismissal" means making a worker's life so miserable they are forced to quit. Constructive Denial of Service is the network equivalent. The VPN doesn't officially ban you; they deliberately render the connection entirely unusable through micro-disconnections, effectively locking you out of your digital life while maintaining plausible deniability.

Thank you so much guys