Alex is a co-founder of Sprintlaw. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.
- Who Is Legally Treated As Holding The Information?
- When The Breach Must Be Notified
- When The Customer Business Notifies, And When Both May Need To
- Can One Party Send The Notice On Behalf Of Both?
- What A Coordinated Working Record Should Capture
- What Needs To Be In The Notice
- What To Check In Your Contract After The Incident Starts
- Key Takeaways
When a privacy incident involves both a New Zealand business and an outsourced service provider, the first legal question is not simply who discovered the problem or whose system was affected.
The more useful question is: who is legally treated as holding each affected set of personal information at the time of the incident? Under the Privacy Act 2020, that answer can change depending on whether the provider was handling the information only for the business, or was also using or disclosing it for its own purposes.
That distinction determines which organisation must notify the Privacy Commissioner and affected people if the breach is notifiable. Here, we explain how New Zealand businesses can allocate that responsibility, coordinate notices and keep the right evidence. This is general information, not advice on a particular incident.
Who Is Legally Treated As Holding The Information?
Privacy Act 2020 section 11 is the starting point. If agency A holds personal information for or on behalf of agency B, the information is treated as being held by B, not A. A common example is a service provider storing, hosting, processing or handling personal information as part of a service it delivers to its customer.
But section 11 does not stop there. If that provider also uses or discloses the same personal information for its own purposes, the information is treated as being held by both A and B.
In practice, ask:
- What exact personal information was affected?
- Why was the provider actually handling that information?
- Was the provider acting only for the customer business in relation to that information?
- Or was the provider also using or disclosing that information for a separately identified purpose of its own?
The legal position turns on actual handling and purpose, not just ownership language, permissions in a contract, or a broad statement that the provider is independent. A provider is not automatically treated as holding every dataset for its own purposes simply because it is a separate company. Equally, a contract describing the provider as a processor or service provider does not settle the issue if the facts show own-purpose use.
When The Breach Must Be Notified
Not every privacy breach must be notified. The serious harm and notification duties arise for a notifiable privacy breach, which is a breach that it is reasonable to believe has caused serious harm to affected individuals or is likely to do so.
When assessing likely serious harm, the Privacy Act requires consideration of matters including any action taken to reduce risk, whether the information is sensitive, the nature of the harm that may be caused, who has obtained or may obtain the information if known, whether the information was protected by a security measure, and any other relevant matters.
If the threshold is met, the agency must notify the Privacy Commissioner as soon as practicable after becoming aware that a notifiable privacy breach has occurred. Affected individuals must also be notified as soon as practicable, subject to the Act's exceptions, permitted delays and individual-notice rules. If individual notification is not reasonably practicable, section 115 requires public notice instead, subject to the Act's qualifications; it is not permission to say nothing.
There is no fixed statutory 72-hour deadline in New Zealand. The test is as soon as practicable.
That assessment should be done promptly. You do not need a perfect forensic report before deciding whether a notifiable breach may exist, and you should not let uncertainty about final facts stop the organisations from identifying who is responsible for the next step.
When The Customer Business Notifies, And When Both May Need To
The Office of the Privacy Commissioner's breach-management guidance applies this distinction to shared-provider incidents.
If a service provider processes information on behalf of another organisation and does not use the information for its own purposes, the notification obligation rests with the customer organisation. In that scenario, the provider may still be central operationally, because it may hold the logs, security facts and technical details, but the legal notification duty for that information sits with the customer agency.
If the provider uses the information for its own purposes, both the provider and the customer organisation may have notification obligations.
This is where businesses often go wrong. They either assume the provider must notify because the incident happened in the provider's environment, or they assume the provider's contract wording removes the customer's legal duty. Neither assumption is safe.
The practical recommendation from the Privacy Commissioner is that the organisation with the closest relationship to affected individuals will generally be the best one to notify them. That is sensible from a communications point of view, but it is not an exemption from legal responsibility. If both parties have duties, both still need to ensure those duties are actually fulfilled, even if one notice is sent on behalf of both.
Can One Party Send The Notice On Behalf Of Both?
Yes, often that is the most practical approach. The business and provider can agree that one party will notify on behalf of both organisations.
But that is an operational arrangement, not a transfer of statutory accountability. Each party that has a legal duty must still ensure the notice is actually sent, contains the required information available at the time, and is clear about which organisations it covers.
That means a contractual approval right, silence from the provider, or an assumption that the other side is handling it does not remove statutory responsibility. If your organisation has a duty, it should not treat a draft sitting in someone else's inbox as the same thing as completed notification.
In a coordinated notification, it helps to settle these points early:
- Who is sending notice to the Privacy Commissioner.
- Who is contacting affected individuals.
- Whether the notice is being sent on behalf of one or multiple organisations.
- Who is responsible for supplying technical facts, customer-facing language and follow-up updates.
- Who keeps evidence that notification was completed.
What A Coordinated Working Record Should Capture
There is no single prescribed statutory form for allocating roles between a business and a provider after a shared incident. Still, a short working record is a very useful coordination aid within a privacy incident response plan.
For each affected information group, record:
- What information is involved, described at a category level only.
- The provider's actual handling purpose for that information.
- The preliminary holder assessment under section 11.
- The serious-harm assessment and current reasoning.
- The notice sender and which agencies are represented in the notice.
- The recipients, such as the Privacy Commissioner and affected individuals.
- Known facts, unknown facts and what is still being confirmed.
- The next update point and what evidence will confirm follow-up action.
This is not a statutory checklist and it is not exhaustive. It is simply a practical way to stop key decisions being lost across email chains, incident calls and draft notices.
Keep the record at an organisational level. In an internal example, say things like customer contact details and booking history, rather than listing an individual's name or account number.
What Needs To Be In The Notice
Section 117 sets different content requirements for the Commissioner and affected individuals. A coordinated process should prepare the appropriate information for each audience.
A notice to the Privacy Commissioner must describe the notifiable privacy breach, including the number of affected individuals if known and the identity of any person or body suspected to be in possession of the information if known. It must also explain the steps taken or intended in response, including whether affected individuals have been or will be contacted. If the agency is relying on public notice because individual notice is not reasonably practicable, that reason must be set out. If an exception or delay is being relied on, identify the exception and reasons, or explain the need for delay and its expected period. It must also identify other agencies contacted about the breach and why, and give a contact person within the agency.
A notice to an affected individual must describe the breach and say whether the agency has identified any person or body suspected to be in possession of that person's information, without identifying that person or body, unless the agency believes on reasonable grounds that identification is necessary to prevent or lessen a serious threat to someone's life or health. It must explain the steps taken or intended in response, and where practicable set out steps the individual may wish to take to reduce loss or harm. It must confirm that the Privacy Commissioner has been notified, state that the individual has the right to complain to the Commissioner, and include a contact person.
An individual notice must not include particulars about other affected individuals. The Act also allows information to be provided incrementally. That is helpful in a fast-moving incident. But it does not mean waiting until every technical question is resolved. Any information available at a point in time should be provided as soon as practicable after that point.
Equally, a bare placeholder or acknowledgment should not be treated as completing the legal obligation if required content is already available and could have been provided.
Two Fictional Examples
Example 1: Appointment Platform Acting Solely On Behalf
In this fictional example, a bicycle-repair business uses a booking platform for customer appointment details and reminders. Unauthorised access affects those booking records. Assume the provider handles that information solely to deliver the booking service for the repair business, without using or disclosing it for its own purposes.
For that affected information, section 11 points toward the business being treated as holding the information, not the provider. If the serious-harm threshold is met, the notification duty for that dataset would rest with the business. The provider would still be expected to notify the business promptly, provide usable facts, and help manage the incident. The business may ask the provider to prepare technical wording, but the business should not assume the provider's silence removes its own responsibility.
That does not decide whether the breach is in fact notifiable on these limited facts. It only shows how the holder analysis can work when the provider acts solely for the customer.
Example 2: Storage On Behalf, Plus A Separate Own Purpose
A software provider hosts customer account records for a retailer. It also uses the same personal information for its own separately identified analytics product to improve and market services to other business clients. A breach affects the hosted account records and analytics environment.
Under section 11, information stored solely on the retailer's behalf is treated as held by the retailer. On the assumed facts here, the provider also uses that same personal information for its own purposes, so it is treated as held by both. If the breach meets the notifiable-breach threshold for that information, both have notification duties.
At the same time, not every dataset in the incident must be treated the same way. Internal provider staff access logs or provider-only billing contact records may require their own separate analysis. The mixed-purpose point is about keeping information groups and actual purposes distinct, not making a single label do all the work.
Again, this example does not decide liability, serious harm, lawful secondary use, or whether notification was ultimately compliant. It only illustrates the allocation issue in a mixed-purpose incident.
What To Check In Your Contract After The Incident Starts
A data processing agreement can require timely information and cooperation from a provider. Those terms support the incident response; they do not replace statutory duties.
Useful contract points for this incident-specific task include:
- Prompt notice from the provider when an incident affects the customer's data.
- Ongoing factual updates in a usable form, not just a one-line alert.
- Named operational and decision-making contacts on both sides.
- A process for coordinating external notifications and public statements.
- Evidence of completed notices and follow-up communications.
Those clauses help the customer agency make its own legal assessment quickly and help both sides coordinate if both have duties. But no clause should be treated as a substitute for working out who legally holds the affected information and whether the breach is notifiable.
FAQs
Does The Provider Always Notify Because The Incident Happened In Its System?
No. The location of the incident does not by itself decide the legal duty. Start with section 11 and ask whether the provider was holding the affected information only for the business or was also using or disclosing it for its own purposes.
Can Our Contract Say The Provider Takes Full Responsibility For Notification?
The parties can agree who will send notices in practice, including sending on behalf of both. But a contract does not remove a statutory duty from an organisation that legally has one. Each organisation with a duty still needs to ensure it is fulfilled.
Do We Need Separate Notices For The Privacy Commissioner And Affected People?
Often yes, because section 117 requires different content for each audience. A coordinated process can still be used, but do not assume one identical message will meet both sets of requirements.
Should We Wait Until Every Fact Is Confirmed?
No. Notification must be made as soon as practicable, and the Act allows information to be given incrementally. Provide what is available when it becomes available, rather than waiting for a complete forensic picture.
Key Takeaways
- In a shared-provider incident, work out who legally holds each affected information group under section 11 before deciding who must notify.
- If the provider acts only for the customer business, the notification duty for that information generally rests with the customer agency.
- If the provider also uses or discloses the same information for its own purposes, both organisations may have notification duties.
- Not every privacy breach is notifiable, but if the serious-harm threshold is met, notification to the Privacy Commissioner and affected individuals is required as soon as practicable, subject to the Act's qualifications.
- One party can send notice on behalf of both, but coordination does not remove statutory accountability.
- Keep a short working record for each information group so holder assessment, serious-harm assessment, sender, recipients, known facts and follow-up actions stay clear.
- Commissioner and individual notices have different content requirements, and available information should be provided incrementally as soon as practicable.
Sprintlaw's New Zealand legal consultancy can help prepare or review data processing agreements, provider responsibility clauses and privacy incident response plans. Call 0800 002 184 or email team@sprintlaw.co.nz to discuss the documents your business needs. For advice on an active breach, seek appropriately qualified help promptly.
Drafted by Taylor, Sprintlaw's AI, and overseen by Alex Solo. How we write
Get your customer-facing terms right
What should your privacy and online terms cover?
If you collect customer data, sell online or run marketing campaigns, your public terms and privacy documents should match the real customer journey.








