A SaaS product team reviewing an application release and service availability on modern workstations
Updated: 16/11/2026
ING Broker editorial team

SaaS insurance: software errors and service interruption

For a SaaS company in Moldova, a software service error, unauthorised access and a cloud supplier outage are different scenarios. SaaS means software supplied as a service, usually through a subscription. Before assessing insurance, describe what is delivered to customers and which obligations the company accepted in its contracts.

This article is for founders, managers and product leads. It does not confirm the existence of a policy accepting every penalty, refund or technical incident. Its purpose is to help prepare the information and questions for a risk assessment. It does not replace legal review of contracts or a security assessment of the application.

Define the service through the function customers use

Explain what the application enables: appointments, administration, communication, analysis or another specific function. Separate the standard product from commissioned development. If the same company provides consulting or data migration, describe those separately. A general label such as “IT platform” does not identify every activity that could result in a claim.

Identify customer categories and known important uses. Do not describe an application supporting a critical process as merely a presentation website. Categories and anonymous examples can be used for the initial assessment. Named client lists and sensitive contracts should be sent only when necessary, through the agreed channel.

Separate marketing promises from signed obligations

Compare the proposal, product page, contract and technical schedules. Which outcome is promised and which feature is described only as a possibility? An excessively broad marketing statement can cause misunderstanding. Have the wording reviewed before assuming a potential dispute can be transferred to an insurer.

Do not copy liability limits or clauses from foreign contracts without analysis. For a Moldovan company, the actual contract, chosen law and specified courts may matter. This article does not decide which clause is valid in a dispute. Present the actual documents to the specialist and assessor, not an idealised version.

Describe availability using a measurable criterion

If a service level agreement, often called an SLA, exists, explain what is measured and where. Distinguish user access, application operation and cloud infrastructure availability. A supplier's indicator does not automatically prove the complete service worked for the customer. Preserve the method and source of your own measurements.

Explain planned maintenance, supplier incidents and remediation. Any service credits or commercial refunds should be identified separately from a compensation claim. Do not assume a policy reimburses every amount the company elects to provide to maintain a customer relationship.

A release should be traceable

For internal organisation, retain the version, approval, relevant tests and release time. Who can modify production? Who checks a sensitive function? How can an earlier version be restored? Describing those processes does not require publication of source code or infrastructure access.

If an error occurs, a clear timeline helps separate the cause from observed consequences. Identify what was confirmed at the time and what was discovered later. Do not retrospectively rewrite a log to make the process appear perfect. Statements and documents used for insurance assessment should reflect reality.

Cloud services do not remove company dependencies

List external services without which the product cannot function: hosting, authentication, messaging, databases or payments. Record an owner and incident contact for each. Two differently branded services may share one dependency. Check that possibility with the technical team rather than relying on marketing descriptions.

Separate your supplier agreement from obligations accepted toward your customer. The supplier's liability cap does not automatically become your company's cap. Nor does that supplier's policy establish that your business is insured. Clarify the remaining risk, rather than simply confirming that infrastructure has been outsourced.

Check data and restoration at customer level

Describe the data categories handled by the product and who determines access. For a multi-customer platform, ask how information is separated and restoration checked. Do not use real data in public demonstrations. A test environment containing fictional information can demonstrate the function without disclosing user information.

Record what can be recovered and the work remaining after files are restored. Recovering a database does not itself establish that integrations and intervening operations are correct. These are technical questions for internal planning, not a promise that all rebuilding costs can be insured.

Professional liability and cyber are not synonyms

An error in a service delivered to a customer should be assessed separately from the company's own expenditure after a security incident. One event can raise several questions, but a policy name does not answer all of them. Request scenario-based analysis: what happened, who seeks payment and what cost is claimed?

Distinguish correcting your own product, the customer's alleged loss, technical consulting and possible defence costs. Do not combine them into one amount labelled “damage”. For each component, ask about limits, conditions and unresolved matters against the actual proposal's documents.

Build a file that can be reviewed

Prepare a product description, revenue split by activity, relevant countries, a sample contract and an explanation of existing controls. Include subcontractors and developing activities where requested. Do not declare that every release is independently tested if the actual process differs. Explain uncertainties rather than hiding them.

Before comparing prices, confirm the proposed activities and territories, period and claim notification mechanism. A premium is the amount paid for insurance, not a measure of the entire contract's quality. Read the premium together with the deductibles, exclusions and limits for each category of cost. A deductible is the part of a loss borne by the insured under the contract. Exclusions are situations or risks for which the contract provides no cover.

Check subscription billing errors separately

As an internal exercise, consider a new version changing billing rules. Which tests establish the correct amount? Who approves the release? How are affected subscriptions identified if an error occurs? Use fictional accounts and do not execute real charges for a demonstration. This exercise supports product organisation; it does not prove that a potential incident qualifies under a particular policy.

Separate the technical correction, invoice reconciliation and customer requests. Preserve transaction history so the version and its effects remain traceable. Do not delete records just to make the report appear clean. Involve competent people in legal and accounting treatment of amounts. An insurance condition does not replace those checks or justify a financial transaction whose basis is unclear.

Customer numbers alone do not explain concentration of risk

A service can have many users while much of its revenue depends on a few contracts. Evaluate that dependency using company documents without publishing customer identities. For an initial discussion, an anonymous summary of activities and revenue concentration may be more appropriate than a full list of contracts and personal details.

Check whether the same feature is used for different purposes. An appointment application in a workshop and one integrated into a customer's sensitive process may need different explanations of an error's impact. These examples do not automatically establish a rate or acceptance. Describe how the product is known to be used and ask what further information is needed to assess the company's actual risk profile.

A supplier exit plan deserves documentation

Ask the technical team what moving the service would require if an important supplier became unusable. Distinguish data export, application configuration and supplier-dependent features. Do not say migration is simple if it has not been checked. A realistic plan identifies elements that cannot move without development or interruption.

For insurance comparison, describe the existing plan and its status: documented, partially tested or only proposed. A future plan is not evidence of a current control. Before publishing technical details, check whether they disclose sensitive information. An assessor may need a functional summary rather than every secret of the product architecture.

Ask questions against the same proposal version

Prepare a questions document and keep response dates. When a modified proposal arrives, check that answers still match the schedules. A verbal explanation of one product must not automatically be applied to another. For each component, show what is confirmed, excluded or still under assessment, without replacing uncertainty with a commercial promise.

  • Declared software activities and additional services.
  • Relevant territories and contracts.
  • Professional errors separated from the company's own cyber incidents.
  • Limits and deductibles for proposed categories.
  • Notification procedure and approval of external expenditure.
  • Treatment of commercial amounts assumed through the SLA.

Update the file after a product change, major contract or significant infrastructure modification. An update does not mean every new risk has already been accepted. Request confirmation of conditions and their effective date. The broker can help clarify assessment options without promising acceptance of an activity or settlement of a claim.

Frequently asked questions for SaaS providers

Does a cloud subscription include insurance for our product?

Do not assume so. The cloud supplier contract and any insurance for your own company have different subjects. Check responsibilities, limits and insured parties separately.

Does a policy automatically pay SLA service credits?

There is no general confirmation. Present the clause and actual scenario. The nature of the amount, contract conditions and insurer acceptance must be checked.

Must we send source code for the first discussion?

Do not send code, passwords or keys on your own initiative. Start with activities and processes. Agree necessary documents and a confidential channel before transmitting sensitive material.

Next step

Request a discussion with ING Broker to check assessment and brokering possibilities. The broker explains options and acts as intermediary. Risk acceptance, conditions and claims decisions belong to the insurer under the contract. This guide does not confirm product availability or cover for an individual case.

Read also: Professional liability of an IT service provider.

Sources and information limits

The Romanian original records consultation of these sources on 9 November 2026. The translation revision date does not represent a new legal or product verification. Preparation lists are editorial recommendations, not policy conditions. Product examples from cited providers do not constitute an ING Broker offer. Legal obligations and individual circumstances require specialist review.

SaaSMoldova