A SaaS (Software as a Service) agreement governs access to software operated and maintained by a provider, generally over the internet in return for subscription fees. Unlike purchasing a copy of software installed on the customer’s own systems, continued use depends on service availability, system maintenance and access to information stored in the platform. A SaaS agreement is therefore more than a licence to use software: it establishes what the provider must deliver over time, what the customer may do with the system, who is responsible for the information and what happens when the service stops.
What Is a SaaS Agreement and Why Is It Needed?
SaaS services are used for customer relationship management, accounting, human resources, marketing, customer support, software development and other business processes. A business customer may rely on the platform for day-to-day operations, while the provider manages the operating environment, deploys updates and selects infrastructure suppliers. This division of control creates mutual dependence: the customer needs continuity and access to its data, while the provider needs clear rules governing use, payment, responsibility and changes to the product.
The agreement should define the service and allocate risks in advance. For example, a company subscribing to an order management system needs more than a promise to receive a username and password. It needs to know which integrations are included, who responds to incidents, how much downtime is permitted, whether order history can be exported and what happens if the provider discontinues an essential feature. For the provider, the same provisions help price the service, distinguish contractual commitments from a product roadmap and avoid promises the system cannot support.
In business transactions, a SaaS agreement should be distinguished from a software development agreement. A development agreement principally concerns creating and specifying a deliverable, accepting it and allocating rights in it. A SaaS agreement governs continuing use of an existing system, even if some configuration or implementation is required initially. Where the provider develops a bespoke component alongside the ongoing service, the development milestones, acceptance tests and rights in that component should be addressed separately. SaaS agreements combine contract law with issues of Israeli computer and internet law, including software licensing, privacy and information security.
Contract Structure: Master Agreement and Schedules
Larger transactions often use a Master Services Agreement (MSA), an order form identifying services and prices, and operational and legal schedules. A Service Level Agreement (SLA) sets availability and support metrics; a Data Processing Agreement (DPA) regulates the processing of personal information where necessary; and an Acceptable Use Policy sets out activities the customer may not perform through the platform.
Not every transaction needs all these documents. A single agreement may contain the necessary provisions, while a service purchased through an online interface may be governed by online service terms and an electronic order form. The question is not how many documents were signed, but whether the complete contractual terms and the binding version of each document can be identified. An order of precedence should be established if the order form, MSA, SLA and use policy conflict. A specially agreed price in an order form, for example, should not be overridden inadvertently by a general provision in an attached document.
Providers serving many customers sometimes use standard terms that are not negotiated individually. Israel’s Standard Contracts Law, 5743-1982, may apply to business-to-business contracts as well, depending on the statutory requirements. Under Sections 3 and 4, courts may intervene in unfair terms, including in certain circumstances provisions that give a supplier unreasonable power to change material obligations or suspend service. Inclusion of a term in the signed contract does not ensure that it will be enforceable. Online contracts and standard-form terms are also examined in the book Internet Law in Commercial Law, by Yonatan Drori, Yotam Werzansky-Orland, Oria Yarkoni and Yehonatan Bar Sade (Perlstein-Ginosar, 2015), Chapter 3, pp. 146–148. See our books and publications.
Scope of Service and Software Use Rights
The agreement should identify the system, modules and features included in the service, the operating environment and the date on which service begins. If the provider is expected to migrate data from an earlier system, perform integrations or train employees, it should state whether those activities are included or separately charged, who supplies the required information and access permissions, and what constitutes completion of implementation. A general promise that a platform will be “adapted to the customer’s needs” may create a dispute if no specifications or defined deliverables are attached.
Use rights may be limited to named users, a number of concurrent users, a particular company or a corporate group. A customer intending to allow employees of affiliates, consultants or contractors to access the platform should confirm that the licence covers them. Conversely, the provider may restrict prohibited uses, such as sharing accounts beyond the agreed limits, bypassing security measures, conducting unauthorized penetration tests or imposing an unreasonable burden on other customers.
SaaS offerings may also include APIs, connections to other systems and automation tools. Call limits, storage capacity, export options, permissions and charges for use beyond the subscription should be specified. A cloud provider is entitled to develop and change its product during the agreement, but an ordinary software update differs from removing a feature that was material to the customer’s selection of the system. An orderly change mechanism can include advance notice, a reasonable alternative or a right to terminate if material functionality is lost.
Intellectual Property Rights and Rights in Customer Data
In most SaaS agreements, intellectual property rights in the software, source code, interfaces and documentation remain with the provider or the rights holders from whom it has obtained licences. The customer receives permission to use the service for the agreed term and within the defined scope. Access to the platform does not itself transfer software ownership. Where the customer pays for bespoke modifications, the parties should expressly establish whether rights in those modifications belong to the provider or customer, or are licensed, and how each party may use the resulting code and know-how.
The status of customer data must be addressed separately. Although the phrase “ownership of data” is common in commercial agreements, not every item of data constitutes property protected by an independent proprietary right. Contractual terms should therefore provide that the customer retains its rights in content and data it uploads or creates in the system, while the provider receives only the permissions needed to operate, host, back up and support the service, subject to applicable law and third-party rights. The same provisions should regulate the customer’s right to access and export its information during the subscription and when it ends.
Disputes arise when the provider seeks to use customer information for its own purposes. Technical usage data needed for operations and monitoring should be distinguished from genuinely non-identifiable aggregated information, information relating to specific individuals and the customer’s confidential business content. Consent to use information to improve the service does not necessarily authorize use of documents, conversations or personal information to train artificial intelligence systems or develop other products. The contract should identify the categories of information that may be used for additional purposes, the permitted purposes, safeguards and whether that use may continue after termination. These issues also arise in AI-related commercial agreements.
If the service includes third-party components or open-source software, the provider should confirm that its licences permit the services it offers. Incorporating an open-source component does not by itself require the provider to deliver all its source code to the customer; the outcome depends on the particular licence and how the component is used. The relevant licence conditions should be examined, while underlying rights in software are considered in our guide to software copyright in Israel.
Fees, Subscription Term and Renewal
A SaaS agreement should explain how fees are calculated: a fixed subscription, per-user pricing, charges based on usage volume, transactions, storage or a combination of these. It should specify whether the price includes implementation, integrations, support, backups, API services and paid add-ons. The customer needs predictability over total costs, while the provider needs to prevent usage beyond the assumptions on which its pricing was based. The contract should therefore define how excess use is measured, when it will be reported and whether overage charges may be imposed automatically.
For longer engagements, the commitment period and automatic renewal mechanism also require attention. If the agreement renews for another year unless advance notice is given, the notice deadline should be clear and consistent with the order form. Where the provider can revise prices upon renewal, the parties should consider advance notice, any cap on increases, and whether the customer may reduce user numbers or move to a smaller plan. Unilateral price changes during a fixed contractual term require particular scrutiny.
The consequences of a payment dispute should also be addressed: payment dates, default interest, handling disputed invoices and the possibility of suspending service for nonpayment. A customer relying on the system for essential operations may seek protection against suspension over an amount disputed in good faith, provided undisputed sums are paid. The provider, meanwhile, needs an effective collection mechanism and protection against continued use without payment. A workable provision distinguishes an isolated late payment from a material and continuing payment breach.
Service Availability, Maintenance and Support (SLA)
The Service Level Agreement is one of the most practical parts of a SaaS contract. A general promise of “continuous and reliable” service does not establish when a breach has occurred. The SLA should state how availability is measured, the measurement period, which hours and functions count and which exclusions apply. Where a particular percentage of monthly uptime is promised, the parties should clarify whether it is measured from the perspective of an end user, the provider’s servers or its internal monitoring system. Scheduled maintenance windows should also be defined rather than treated as an unlimited exclusion.
Availability commitments do not replace commitments to respond to faults. Initial response time, commencement of work, target resolution time and escalation procedures should be distinguished. For a system supporting commercial operations, an outage preventing all users from logging in is different from a localized problem generating a report. Incidents can be classified by severity, with corresponding response levels, support hours and communication channels. From the provider’s perspective, the metrics should be measurable and relate to components within its control.
Many SaaS agreements provide service credits when availability commitments are missed. The agreement should state how credits are calculated, whether the customer must claim them within a specified period and any cap. A small credit may offer little meaningful relief to a customer whose operations were disrupted for a prolonged period. The parties should therefore examine whether credits are the exclusive remedy and whether repeated or extended outages trigger termination and a proportionate refund. A graduated credit mechanism may, for the provider, provide a predictable and limited response to ordinary operational failures.
Protection against data loss requires express arrangements for backups and disaster recovery. The Recovery Time Objective (RTO) describes the target maximum period for restoring the system after an incident, while the Recovery Point Objective (RPO) describes potential data loss in time terms. They address different needs: a system restored within an hour from a backup taken two days earlier does not provide the same protection as one that also restores recent data. The agreement should identify who performs backups, how often restoration is tested, what is covered and which exclusions apply.
Privacy, Information Security and Subprocessors
A SaaS service may involve hosting or processing information relating to employees, customers or end users. The agreement should define each party’s role in relation to personal information. Under Israel’s Protection of Privacy Law, following Amendment No. 13, the database controller determines the purposes of processing, while a database holder is an external party processing information for the controller. A SaaS provider may act as a holder in relation to information uploaded by its customer and, in other circumstances, as a controller in relation to information it collects for its own purposes. Contractual labels alone do not determine the parties’ legal status.
Where an external supplier obtains access to a customer’s database, the application of Regulation 15 of the Protection of Privacy Regulations (Data Security), 5777-2017, should be examined. The Regulation and guidance of the Israeli Privacy Protection Authority address, among other matters, assessment of outsourcing risks and contractual arrangements covering the types of information, purposes of processing, systems accessed, security measures, confidentiality, security incident reporting and return or destruction of information when the engagement ends. A general undertaking to “comply with all applicable laws” is no substitute for defining practical responsibilities. See the Privacy Protection Authority’s English-language information on data security requirements. If the GDPR applies and the SaaS provider processes personal data on behalf of the customer, the processing must be governed by a DPA or another legally binding instrument meeting Article 28(3) of the GDPR.
Information security calls for a detailed allocation of responsibility. The provider may be responsible for infrastructure security, security patches, monitoring and segregation of customer environments. The customer may be responsible for managing its employees’ permissions, passwords and access settings under its control. Depending on the service’s risks, the agreement should address encryption, access controls, logging, security testing and cooperation during incident investigations. It should specify when and how the provider notifies the customer of a security incident, what information is provided and how the response is coordinated if reporting to a regulator or affected individuals becomes necessary. These duties are examined further in our guide to information security and cyber incidents in Israel.
The service may depend on additional hosting, infrastructure, monitoring or support providers. The contract should specify when the SaaS provider may engage a subprocessor, which obligations must be passed on and what happens if a supplier materially affecting the handling of information is replaced. Where data is transferred outside Israel, the legal rules governing transfers to databases abroad must also be examined. Privacy notices help explain permitted information uses and disclosure obligations, but do not replace the contractual arrangements between customer and provider.
Representations, Indemnification and Limitations of Liability
A SaaS provider may undertake that its service complies with an agreed specification, that it holds the rights needed to make the software available and that it will operate the system with reasonable skill and care. The customer may undertake to use the service lawfully, provide only information it is entitled to supply and refrain from uploading content that infringes third-party rights. These commitments should correspond to matters within each party’s control. A blanket provider warranty that the platform suits every business need is no substitute for specifications; a blanket customer responsibility for all account activity should not disregard a security failure attributable to the provider.
Limitation of liability clauses determine which losses may be claimed and the maximum amount payable for breach. It is common to link a liability cap to service fees paid over a defined period, but that measure may be problematic where the subscription is inexpensive relative to the potential consequences of data loss or interruption of an essential operation. Separate caps may be appropriate for confidentiality breaches, information security incidents, intellectual property infringement and indemnity obligations instead of a single limit for every type of breach.
Exclusions of indirect or consequential loss must be considered separately. In software contracts, a substantial part of the customer’s losses may arise from missed transactions, restoration costs, interrupted operations or demands by third parties. The heading used in a contract does not always determine whether a particular loss is direct or indirect under applicable law. Exclusions should be drafted precisely and should not render key contractual commitments meaningless. Under standard-form agreements, limitation clauses and unilateral rights to change the service may also be subject to scrutiny under Israel’s Standard Contracts Law.
Indemnification usually becomes relevant when a third party brings a claim relating to one party’s rights or conduct. For example, the provider may indemnify the customer against allegations that the software infringes third-party intellectual property rights, while the customer may indemnify the provider for unlawful content it uploaded, if the agreement allocates that risk to the customer. The contract should identify what triggers the indemnity, who controls the defense, whether consent to settlement is required and which expenses are covered. An indemnity without a workable procedure may create a further dispute just when a claim is filed.
Suspension, Termination and Return of Customer Data
A provider’s right to suspend service is different from its right to terminate the agreement. Temporary suspension may be justified by a security threat, unlawful use or material nonpayment, but its conditions, scope and any notice should be specified to the extent circumstances permit. If a threat is confined to a particular account, it may be possible to restrict that account rather than disable the entire platform. The customer needs a reasonable opportunity to cure non-urgent breaches, while the provider needs the ability to act immediately when there is a genuine threat to other customers or its infrastructure.
Common termination grounds include a material breach not remedied within an agreed period, insolvency, persistent nonpayment or repeated service failures. The parties may also agree on termination for convenience after a minimum period. The agreement should address prepaid subscription fees, implementation charges, SLA credits and amounts accrued up to termination. An unclear relationship between a one-year subscription commitment and a right to stop service immediately may leave the parties disputing the balance of the fees.
The most important issue at the end of a SaaS engagement is the customer’s ability to operate without the service. From the outset, the agreement should specify how the customer can export its data, in which format, whether exports include attachments, activity history, permissions and metadata, and the charges for migration assistance. A file containing only basic records may not be sufficient to operate a replacement system. For complex transitions, the parties may agree on a migration period in which service continues at an agreed level and the provider assists the replacement supplier.
Deletion of information after termination must be regulated separately. The agreement should provide a period during which the customer can retrieve its information, when working copies will be deleted, how backups will be handled and which statutory retention exceptions apply. Immediate technical deletion of every copy should not be promised if the backup architecture does not permit it, but access restrictions and defined deletion periods can be established. Where the system stores personal information, these provisions must be coordinated with applicable law and obligations toward data subjects.
For arrangements within its scope, the EU Data Act should also be considered. The Regulation’s provisions on switching between data processing services began applying on 12 September 2025. Under the prescribed timetable, the abolition of certain switching charges takes effect on 12 January 2027. This does not mean that every Israeli SaaS provider is subject to these rules or that they require the supplier to transfer its source code. Applicability must be assessed by reference to the service, market and provisions of the Regulation.
International businesses procuring cloud services from Israeli providers, SaaS companies negotiating contracts with overseas customers, and foreign law firms seeking Israeli counsel for SaaS agreements, data protection issues or related disputes may contact Drori Stav at office@dwo.co.il.
