However, it ultimately depends on what kind of SaaS application you're developing. You'll need different legal agreements depending on what exactly your SaaS app does.
Dropbox, for example, allows users to upload and share files such as text files, movie files, and image files. This means that Dropbox should have a legal agreement that covers user-generated content.
Mailchimp allows users to send email marketing messages through its app. This means that Mailchimp should have a legal agreement in place that places restrictions on what types of emailing its users can do (such as no spamming).
The following points should be addressed in clauses in your SaaS app's Terms and Conditions:
A good way to approach your Terms and Conditions agreement is to imagine a number of potentially rare but still possible situations that may arise between you and a customer, and include how such situations should be handled in the agreement.
For example, how will you handle a customer who misses payments for your SaaS app subscription? Will you revoke access immediately, or will there be a grace period? Will you allow customers to end the contract in the middle of a billing cycle and obtain a refund, or will there be a monetary penalty for interrupting the cycle?
Always be very clear in the language used in your Terms and Conditions. Using too much technical or legal jargon can be confusing to your users, and in the event of a legal case arising, a judge may find that your agreement is too unclear to be upheld.
The following clauses should be included in most SaaS app Privacy Policies:
Note that in some cases a Cookies Policy is required to comply with the the EU Cookies Directive.
Communications: Inform your app users that they may receive promotional emails from you, but that they can unsubscribe from communications.
There are legal requirements in place to let users unsubscribe from promotional emails, such as CAN-SPAM in the US and CASL in Canada.
If you collect personal information in different ways, such as both directly from users and through more automated means, disclose both.
Moz discloses what information it collects and how it does so in one concise, bullet-pointed clause:
Cookies are often used for advertising purposes such as personalized marketing. If you participate in personalized marketing or remarketing, let your users know that you do this and how they can opt out.
SurveyMonkey includes a separate Personalized Marketing clause that does this:
Along with personalized marketing, you should disclose if you participate in direct marketing or commercial communications. This can be sending emails, text message, mobile push notifications and other forms of direct communication.
Let users know how they can opt out of these communications if they want to, as Buffer does here:
Sometimes a SaaS app will be sold or merged. This can be concerning for your users, as they may not be ok with their personal information being transferred to someone else.
Check out the rest of the agreement to see how Startpage handles individual clauses.