Finally someone challenges me! Ok it’s very simple, how is this avoiding keyloggers? Do you know? Kay briefly discussed it in the last radio interview. The closest I’ve ever heard him to being right on his products. It bypasses the main stream of data transfer if you will. I’m not using technical terms, I’m using everyday terms. So typically the data is sent right up stream, no interruptions, where keyloggers and dip in and take however much data they want. From the keyboard to the processor. GuardedID blocks this path, sends it through another path (where keyloggers aren’t meant to be looking) and that stream taps back into the main stream to get to the processor. At the same time this data is being encrypted, which is another chunk of code executing. So now you have created 3 things that have to execute for 1 thing to happen. Where as before it was a 1 to 1 thing. But the main stream always executed even if it isn’t being bypassed. With a filter that encrypts the key strokes. This uses up RAM. Each processor only has so much RAM. When your computer is slow, check the RAM, because it’s probably executing something in the background which isn’t allowing you to execute what you’re trying to do. Computers execute what it’s told to execute, and that’s typically a first on, first execute.
All in all, if you’ve spent thousands on a computer with super RAM, then you probably won’t notice it as much. But the typical computer these days still doesn’t like when too many things are open at once. Maybe 5 or 6 things before you see an effect. So if you have an email open, a webpage open, and a third obscure thing open, and GaurdedID loaded up, IT WILL slow down your computer’s ability to execute all programs in its normal timely manner.
Any questions?
News 
Market Data 
Discover 
