http://www.lavishsoft.com/account/policies is about it
I have too many people asking about CLS lately and having trouble, I want to recommend some changes. First off, since the MMO - Pro style was added to the Quick Setup Wizard, I have been recommending that people NOT use CLS because it is large (nearly impossible to share due to its size, therefore hard to help people fix issues with) and convoluted (having dozens and dozens of Key Maps that they will never use in their life) and doesn't really save much trouble over using MMO - Pro currently. Using the QSW automatically sets up ATGs, the virtual key maps, etc, leaving the user to set up their DPS Rotations (e.g. by having it press the buttons they would otherwise be pressing to play solo) and assign Hotkeys. If you've not done it, please go through with a configuration from the wizard and maybe even watch my video, so you know the difference between what you're providing and what is already available --
http://isboxer.com/wiki/Style:MMO_-_ProHere's a couple things I would do...
1. Drop all of the level-range Key Maps. People are unlikely to go in and correct the rotation for every single level range as they level; they would rather stick with one and adjust it as they level. I say this from experience with CLS. If the rotations were pre-built that might be different. But, as it stands, I would say the cost (configuration size, cost of time to fix each level range, etc) to benefit ratio of having separate key maps for every 5 levels is pretty bad. The cost to benefit ratio of using one Key Map per class is WAY better, and is much much easier for the user to manage and for the rest of us to support.
2. Make sure all targeted damage macros use something like /stopmacro [noexists,noharm,dead]. This is to prevent the game from automatically selecting a target for you when you use a /cast macro. (I'm not sure this occurs when using a normal ability key on your Action Bar, as opposed to a /cast macro where it does happen and confuses a lot of people.) Note that putting it in PreAttack and then using /click PreAttack would not be sufficient because that only stops the PreAttack macro and does not affect the macro doing the /clicking.