Some background: Ever since I had a problem with PayPal over something they said was in their end user agreement (which still isn't there even today) and it consumed so much of my time to resolve, I've become a stickler for reading EULAs of any software/service from top to bottom.
Fast forward to the latest update of Traffic Travis. I was about to install the latest patch and was greeted with a long EULA that I must accept before applying the patch.
With the PayPal fiasco still fresh in my mind, I dutifully read the agreement top to bottom.
The majority of it was just standard intellectual property stuff, liability disclaimer, etc. ... which is fine.
HOWEVER, CHECK THIS OUT !!!
3.2 Transfer of Data
The Software may from time to time transmit the data collected and generated through your use of the Software (including, without limitation, search results and keyword and other rankings) to TrafficTravis (and any of our affiliated companies). You grant TrafficTravis (and any of our affiliated companies) a perpetual, irrevocable, fully paid-up, non-exclusive licence to store and use such data for out business purposes.
NOTE: The bolding and underlining are mine, and the word "out" should be "our" (but I wanted to copy and paste the exact clause) for accuracy.
Translation: Without ANY limitation, Traffic Travis can transmit YOUR keyword research to be used by ANY of their affiliated companies for ANY purpose.
Just think about the "without limitation" possibilities:
You've uncovered through your hard effort some great buying keywords with high volume and insanely low competition. Traffic Travis detects the prime range and ratio and beams the data to home base who then passes it along to their affiliate team to build a competing site to exploit the market.
Anyway, just thought there might be some other Traffic Travis users who might want to know about this. As for me, I'm removing it from my computer. That clause is there for a reason and it sure isn't for the good of the customer.
EDIT: Here's a direct link to the vendor's reply where they agree to address these concerns in their EULA (in case you don't want to read the entire thread).