§1 Toolbox™ is intellectual property of Cevican AB and may under no circumstances be copied, modified, distributed, “de-compiled” or disclosed to third parties. Toolbox™ is equipped with monitoring functions that will detect possible misuse.

§2 Only customers of Cevican AB, or their representatives, may implement and use Toolbox™.

§3 Toolbox™ may only be included into one web site to support one domain and one IP-number to support one company only.

§4 The customer understands that data sent through Toolbox™ is not encrypted.

§5 Toolbox™ may only be used as specified by Cevican AB. Toolbox library functions, classes or any objects derived from it, not specified in the public in the API, may under no circumstances be called directly. Nor may one call or modify functionality of objects created by Toolbox. One may not read data from variables or objects not specified as public API. One may not use Toolbox, or derivatives from it, as building blocks to create complementary functionality or widgets. Indirect addressing, using the DOM/Child/Parent addressing is considered misuse.

§6 Even if general programming guidelines are followed, it is not allowed to modify the experienced visual appearance or the functionality of Toolbox components. The visual area occupied by the component, or in direct connection, may not be visually or functionally altered. Nor is it allowed to add invisible layers on top of the component.

§7 Toolbox™ functionality may be removed or modified.

§8 Only the latest version of Toolbox™ may be used. By using the SolidComponents Toolbox URL, the use of the latest version will be ensured.

§9 Toolbox™ is provided without any warranties and is used on the customers own risk. Reasonable care has been taken and the software has been rigorously tested in order to minimize the risk for critical errors. Cevican AB takes no responsibility for any consequences, direct or indirect, by using Toolbox™.

§10 It is strictly forbidden to bypass the Toolbox™ communication manager to call SolidComponents servers directly. All communication with SolidComponents must be handled directly by the communication manager which is ensured by using the provided API.

§11 Toolbox™ utilizes existing well-known and accepted IT-technology to communicate between client and server. As the Internet is a constantly changing environment, it is though still not possible to completely guarantee exactly the same functionality in the future.

§12 Toolbox™ has built-in functionality to deal with load-balancing and fraud and therefore, some weighted limitations do apply. Standard use should not be affected by these limitations.

§13 Toolbox™ has been developed with future compatibility as a guiding rule. The customer understands that Cevican AB has the right to require the customer to implement modifications to their current implementation in order to continue using Toolbox™.

§14 The general conditions and terms of use for using Toolbox™ may be modified without prior notification.

§15 The customer understands that activity will be logged in order to provide statistics, error control and to provide support as well as to prevent fraud and possible misuse.

§16 Identification may be required through a digital security key that may be changed over time in order to certify that Toolbox™ is used properly.

§17 In the case of, but not limited to, security issues Cevican AB has the right to deactivate features of Toolbox™.

§18 Customers who are using SolidComponents Flatrate™ license model understand that the use of some features will deduct credits from the credit balance.

§19 The total number of downloads generated by Toolbox™ and other sources will be accumulated. The total number of downloads that may be invoked on a monthly basis is defined by the customers license agreement.

§20 Toolbox™ may only be used to support manual user interaction through mouse and keyboard activity and all attempts to programmatically access or utilize server resources is strictly prohibited. It is for example strictly forbidden to use Toolbox™ to create batch processes.

§21 SolidComponents has the non-negotiable right to decide whether anything should be considered as misuse. In those occasions, SolidComponents will inform about required actions. If those actions are not performed, SolidComponents has the right to immediately deactivate the use of Toolbox™.

§22 In order to prevent misuse, SolidComponents will, API functions excluded, modify source code, class names, variable names and function names regularly. If the program stops working when the Toolbox source code is modified, it is likely to be considered as misuse. If the implementation is properly done using only the public API, these implementations will have no effect on your current implementation.

§23 Any actions taken that could be considered workarounds to bypass terms of use to accomplish functionality that is not approved, is likely to be considered as misuse.

§24 Toolbox™ is standard software and will not be modified in any way to suit a certain customer’s implementation. It is the customers’ responsibility to adapt their own web page to work with Toolbox™.

§25 In the case that any bugs are detected, the customer understands that it is considered very high priority to correct but nevertheless, since the same implementation of Toolbox™ is used by all customers, quick fixes cannot be implemented and has to pass through the validation procedure at SolidComponents. It is therefore very important that the customer tests any implementation rigorously before making it publically accessible.

§26 SolidComponents™ has the right to validate the code and web page(s) that takes advantage of Toolbox™ before public activation. Only approved implementations will be possible to activate for all users.

§27 It is the customers’ responsibility that guidelines and conditions are followed by those who implements Toolbox.