When is a saaS agreement commonly used in Singapore?
A software as a service agreement, commonly referred to as a SaaS agreement, is used whenever a customer accesses software functionality hosted and maintained by the provider over the internet, rather than installing and running the software on the customer’s own infrastructure, covering everything from enterprise business systems to specialised industry applications.
SaaS arrangements are commonly used across virtually every business function today, including customer relationship management, accounting and finance systems, human resources platforms, and industry specific applications, reflecting the significant shift in recent years away from traditional on-premises software toward cloud-hosted subscription services.
Businesses commonly choose SaaS solutions for the reduced upfront infrastructure investment, automatic access to updates and new features maintained by the provider, and the flexibility to scale usage up or down compared with traditional software licensing models requiring significant upfront investment and ongoing internal maintenance.
Because SaaS arrangements involve ongoing dependency on the provider’s infrastructure and continued operation, and because the customer’s data is typically hosted on the provider’s systems rather than the customer’s own infrastructure, businesses entering into a significant SaaS agreement should have the terms carefully reviewed, particularly regarding data security, availability, and exit arrangements, before committing to the service.
Which parties should sign the agreement and who should have authority to bind them?
The SaaS provider, operating and hosting the software service, and the customer, subscribing to access and use the service, are the parties who sign a SaaS agreement, and each should ensure the signing party has proper authority to bind the entity concerned, particularly for enterprise-scale subscriptions involving significant ongoing fees.
Where the customer is part of a larger corporate group, the agreement should clearly specify which entities are permitted to access and use the service under the subscription, since SaaS agreements are commonly structured around a specific subscribing entity rather than automatically extending to affiliated companies.
Where the SaaS provider relies on underlying infrastructure from a third party cloud hosting provider, the customer should understand this dependency, since the provider’s ability to deliver the service reliably depends in part on this underlying infrastructure relationship, which is generally outside the customer’s direct visibility or control.
Because a SaaS relationship typically involves ongoing dependency rather than a one-time transaction, both parties should ensure the contracting entities and their respective authority are properly documented, and customers in particular should understand the provider’s own infrastructure dependencies as part of assessing the overall reliability of the service.
What essential commercial terms should be included?
The agreement should clearly specify the scope of the service, including which specific features and functionality are included, any usage limits such as data storage capacity or number of authorised users, and how the service may be modified or updated by the provider over the subscription term.
Service level commitments, including uptime or availability targets, should be clearly specified along with the remedies, typically service credits, available to the customer if the provider fails to meet these commitments, since the customer’s business operations may depend on the service being reliably available.
Data ownership and portability provisions are particularly important in SaaS agreements, confirming that the customer retains ownership of their own data input into the service, and specifying the customer’s right to export their data in a usable format both during the subscription and upon termination.
Because SaaS customers are often significantly dependent on the provider’s ongoing operation and cannot simply take possession of the underlying software in the way a traditional licensee might, these service scope, availability and data portability terms are particularly important, and customers should ensure they are adequately addressed before committing to a significant SaaS subscription.
How should payment, performance standards and timelines be addressed?
SaaS agreements are typically structured around recurring subscription fees, whether billed monthly or annually, often scaling based on factors such as the number of users or the volume of data or transactions processed, and the agreement should clearly specify how fees are calculated and any provisions for fee increases over the subscription term.
Service level agreements specifying uptime targets, typically expressed as a percentage of availability over a given period, and support response times for different severity levels of reported issues, should be clearly documented, along with the specific service credit remedies available if these targets are not met.
Where the customer requires implementation or onboarding assistance to properly configure and begin using the service, timelines and responsibilities for this implementation phase should be addressed, particularly for more complex enterprise SaaS deployments requiring data migration or integration with the customer’s existing systems.
Because SaaS pricing models can become complex, particularly where fees scale based on usage, and because service reliability is often central to why a customer selected a hosted solution in the first place, both parties should ensure payment and performance provisions are clearly documented, with customers paying particular attention to how usage-based fees might grow as their business scales.
How can liability, indemnities and limitations of liability be drafted?
SaaS providers typically seek to limit their liability, often capping it at a multiple of fees paid over a recent period, and customers should assess whether this cap is adequate given the potential business impact if the service experiences a significant outage or data loss affecting critical business operations.
Data security and breach notification provisions are particularly important in SaaS agreements given that customer data is hosted on the provider’s infrastructure, and the agreement should address the provider’s security obligations, breach notification commitments, and, where personal data is involved, compliance with the Personal Data Protection Act including the provider’s role as a data intermediary.
An indemnity from the provider addressing claims that the SaaS platform itself infringes third party intellectual property rights is commonly included, protecting the customer from exposure arising from the underlying technology rather than from the customer’s own use of the service.
Because the customer’s data security and business continuity depend significantly on the provider’s own infrastructure and practices, which the customer generally cannot directly control or verify, customers should carefully review liability caps, security commitments and breach notification provisions, and should consider requesting independent security certifications or audit rights for higher risk or higher value SaaS engagements.
What termination rights and consequences should be included?
The agreement should specify termination rights for both parties, including for material breach, non-payment, or, for term-based subscriptions, simply the natural expiry of the term if not renewed, along with any right for the customer to terminate for convenience, which may be subject to notice requirements or early termination fees depending on the specific agreement.
Data export and deletion provisions upon termination are particularly critical in SaaS agreements, specifying the customer’s right to export their data in a usable format within a reasonable period after termination, and the provider’s obligations regarding secure deletion of the customer’s data from their systems after this export period.
Where the customer has built significant business processes around the SaaS platform, transitional support, even if limited or provided at an additional fee, can be valuable to help the customer migrate to an alternative solution without significant business disruption upon termination.
Because losing access to a SaaS platform that has become embedded in daily business operations can be highly disruptive, customers should pay particular attention to data export rights and any transitional support available upon termination when negotiating a SaaS agreement, rather than focusing solely on the ongoing subscription terms.
How should confidentiality, personal data and intellectual property be handled?
SaaS agreements should include confidentiality provisions covering both parties’ confidential information, with particular attention to the customer’s business data processed through the service, which the provider will have significant access to given the hosted nature of the arrangement.
Where the service processes personal data, which is common for most business applications, the agreement should clearly address the provider’s role and obligations under the Personal Data Protection Act, typically as a data intermediary processing personal data on behalf of the customer, with appropriate contractual data protection commitments from the provider.
Intellectual property provisions should confirm the provider retains ownership of the underlying SaaS platform and technology, while the customer retains ownership of their own data and any content they input into the service, with the customer granted only a right to access and use the service rather than any ownership interest in the underlying platform.
Because SaaS providers have inherent and ongoing access to customer data as part of delivering the hosted service, unlike traditional on-premises software where the customer maintains direct physical control over their systems, customers should pay particular attention to data protection and confidentiality provisions when negotiating a SaaS agreement, especially where sensitive business or personal data will be processed through the platform.
What happens if a party breaches the agreement?
If a customer breaches the agreement, such as by failing to pay subscription fees or by exceeding permitted usage limits, the provider typically has the right to suspend or terminate access to the service, and given the customer’s likely dependency on the service, this can create significant immediate operational impact for the customer.
If a provider breaches the agreement, such as by failing to meet agreed service levels on a persistent basis or suffering a significant data breach due to inadequate security measures, the customer may have a claim for damages or service credits, and in serious cases, may be entitled to terminate the agreement and seek an alternative provider.
Both parties should properly document service issues as they arise, including outage incidents, support response times, and any other performance concerns, since these records become important both for enforcing service credit remedies and for supporting any broader claim if the provider’s performance persistently falls short of agreed standards.
Because a customer’s operational dependency on a SaaS provider means a breach by the provider can have immediate and significant business impact, customers experiencing persistent performance issues should engage with the provider promptly to address concerns, while also seeking legal advice on their contractual remedies if the issues are not properly resolved.
Should disputes be resolved through Singapore courts, arbitration or mediation?
Many SaaS disputes, particularly those involving service level or performance concerns, are resolved through direct engagement between the parties, often through the escalation processes typically built into the commercial relationship, given both parties’ general interest in the ongoing service relationship continuing successfully.
Mediation can be a useful option for SaaS disputes that cannot be resolved through direct engagement, particularly where the customer has significant switching costs and both parties therefore have an interest in preserving the relationship where the underlying issues can genuinely be addressed.
Where the SaaS agreement specifies arbitration, disputes not resolved through negotiation or mediation would proceed to arbitration rather than the courts, and parties should check their specific agreement terms, since SaaS agreements offered by larger international providers commonly specify a particular dispute resolution forum and governing law that may not always be Singapore.
Where no arbitration clause applies, or where the agreement specifies Singapore courts, disputes proceed through the Singapore court system, with the appropriate court depending on the value and complexity of the claim, and customers should confirm the applicable governing law and dispute resolution forum before entering into a significant SaaS agreement, particularly with an overseas based provider.
