Avoiding Problems and Liability Issues for Creators of Remote Access Tools

Did you just launch a remote desktop application? Or are you planning to do so? Then you should be aware of these specific industry issues. rnThere are plenty of people that use Remote Desktop Software programs right now. And there are also plenty of developers making them, both large and small. If you are a small or independent software developer, then you will need to examine certain legal and public relations issues associated with this kind of software programs. rnThe main thing about remote control software is that it allows someone to completely take over another system, run applications, as well as open and copy any files from it. While this is the intended purpose of the software when used by an authorized person, if an unauthorized user manages to get access to a system remotely, it can cause huge issues for the owner of the compromised computer, as well as their network. rnThis is not to say that PC remote access software is unsafe. As a developer, you have probably put in many safeguards to prevent unauthorized access to a remote system. However, in order to avoid problems, it is recommended that you do the following: rn1. Include any security limitations in your documentation that is given to the user rnNot all PC remote access programs have very high security. For example, some of the most basic ones don’t use encrypted connections or have intrusion detection features. This, in itself is not a bad thing, as there are many users, especially home users, who don’t need high security but this must be mentioned in the documentation. You can also include a line saying that this program is not to be used in applications where security is paramount, such as military or government uses. rn2. Include security tips as part of your software’s help files and require the user to read them before installing the software rnJust put in the basic, common sense tips, such as using a secure password, not leaving a computer unattended around other people, not sharing the password with anybody else, etc. That way, the user cannot claim that they “weren’t aware that 12345 is not a secure password”, for example. While this may seem a bit “dumb” to anyone working in the IT industry, someone who isn’t too proficient with technology may not know these tips. rn3. Have a disclaimer in your terms of service rnIt is recommended that you consult with a legal professional regarding your rights in terms of limitation of liability. As a general rule, you can include a disclaimer that states the software comes with no guarantee of absolute security and that your maximum responsibility in case of any claim by a user would be refunding the cost of the software or any other services that they have received from your company.