Among the most obvious problems related to shadow computing are wasted money and wasted resources. For example, in the end, a company may purchase a new subscription or license for a product it already owns. And when we talk about the average organization that runs hundreds of applications, that`s a lot of licenses to manage. The zylo data show that the average company maintains an inventory of 600 SaaS applications. Some experts argue that a SaaS “license” only means permission to use it and does not grant a copyright license. But why take the risk, given that a SaaS contract with the word “license” could harm the seller in at least four ways? Typically, this type of license does not apply to SaaS agreements because the customer does not install or download the software, but remotely connects to the vendor`s servers to use the software, usually online. The authorized vendor or provider hosts the software on their servers or in the cloud. In addition to termination rights, you should also tell some of the consequences of dismissal. The most important questions relate to customer data.
Can the customer download all their data from the platform? Is the service provider required to make the data available to the customer? If so, when and how? And how much should the service provider remove customer data from its live and backup databases? (If the database contains personal data and the service provider is a processor of that personal data, it must be removed once the services are completed in order to comply with the PDPP.) SaaS licenses are easy to acquire and provide. And while this is generally considered an advantage of SaaS, you should keep in mind that IT teams are not always aware of products purchased by employees without the consent of IT. This phenomenon is called shadow computing. Since there are no or no locally significant installed software components participating in a SaaS application, a software license is irrelevant. In this article, we will break down what goes into a SaaS license and why it is important to understand licensing agreements. Here is an example of a performance clause contained in Google Cloud`s SLA agreement: this means that a DEEE agreement is less appropriate, because the end result of using DEEE agreements is to grant the customer a copy of your software for use. Finally, the specifics of a SaaS licensing agreement are highlighted with regard to companies and end-users. You should make sure that the language you include with respect to user agreements is very clear. A judge may find that an agreement is not clear enough to be respected if you use too much legal or technical jargon for a user to reasonably understand. SaaS applications with multiple types of user licenses and authorization levels (z.B. Salesforce) represent a unique challenge for SaaS business management.