Data processing agreement: what to check
Read a data processing agreement against the customer data a supplier receives. Check instructions, subprocessors, security, transfers and deletion terms.
- Published
- Last updated
A data processing agreement sets the terms for a supplier handling personal data on your business’s behalf. Read it against the information the supplier actually receives, the work it can perform and what happens when that work ends.
For a retailer, that means tracing customer conversations and order lookups through every supplier involved. The applicable privacy law determines which contractual duties are required. A document labelled “DPA” does not establish compliance by itself.
What the agreement governs
The agreement governs processing done for the retailer, such as hosting customer conversations or retrieving an order for support. It defines the permitted work and the responsibilities of each party.
Under the European Union’s General Data Protection Regulation (GDPR), a controller decides why and how personal data is processed. A processor handles it on the controller’s behalf. The European Data Protection Board’s explanation of these roles makes the actual processing relationship the starting point.
A privacy notice tells people how their information is handled. A confidentiality agreement restricts disclosure of protected information. General service terms cover the commercial relationship. Processing terms can sit inside those service terms or in a separate schedule, but they must govern the relevant processing.
For example, a promise to keep information confidential leaves unanswered whether the supplier can retain chat transcripts after cancellation. Permission to store transcripts does not tell customers about that collection. Each document has a different job.
Identify the laws that apply before treating a processor checklist as mandatory. A supplier can also have different roles for different activities. Handling your support tickets under instructions and using information for its own separate purpose require separate analysis.
Map the retail data being processed
Follow one customer question through the storefront and record what crosses each system boundary. The following journey is hypothetical. Its fields are examples to investigate, not a claim about any particular product.
A customer asks whether a jacket will arrive before an event. They later supply an order number and ask for a person. A possible data map looks like this:
| Recipient | Information received in this example | Purpose to put in the processing schedule |
|---|---|---|
| Storefront host | Customer’s message, session identifier and network address | Deliver the storefront and pass the question to the agent |
| Agent supplier | Message, viewed product and delivery postcode if supplied | Answer from catalogue and delivery information |
| Model or hosting subprocessor | The message and selected context sent by the agent supplier | Run the processing needed to produce the answer |
| Order-system supplier | Order reference and the authorised lookup request | Retrieve the relevant order’s delivery status |
| Helpdesk supplier | Conversation, order reference and contact details supplied for follow-up | Let staff continue the support conversation |
Record the returned data too. An order lookup might return a delivery address even when the agent only needs shipment status. Restrict the response to the fields needed for the approved task.
For every recipient, note where information is stored, who can access it and how long each copy remains. Include diagnostic logs and backups, plus the staff who can access each copy. A helpdesk connected directly by the retailer is not automatically the agent supplier’s subprocessor. Trace who appoints whom.
Separate your instruction to answer a delivery question from any permission for the supplier to reuse transcripts. Product improvement, advertising and model training need their own purpose analysis. Ask whether each use is on your behalf or for the supplier’s own purposes. Under GDPR, determining purposes and means can change the supplier’s role for that processing.
Clauses that change the decision
Read each clause as an operational commitment. Identify what your team would receive or be able to do if it needed to enforce that commitment.
These are practical review questions. Their legal status depends on the applicable regime and processing relationship.
| Clause | What to establish | Evidence or action to request |
|---|---|---|
| Instructions and purpose | The permitted data, tasks and duration, including any exception for legally required processing | A completed processing schedule and a way to issue changed instructions |
| Access and security | Which staff can see conversations and how access is restricted | The relevant access controls, confidentiality duties and security measures |
| Breach assistance | How the retailer learns of an incident and obtains facts for its response | Notification route, contractual timing and assistance with investigation and containment |
| Customer requests | How the supplier helps locate, export, correct or delete relevant records | A request procedure that covers the systems holding those records |
| Subprocessors | Who receives the data and what happens when that list changes | Functions, locations, authorisation process and notice of additions or replacements |
| Overseas handling | Where storage and remote access occur, including onward handling | A location map and the applicable transfer or disclosure safeguards |
| Audit information | How the retailer can assess compliance with processing duties | Relevant reports, answers to follow-up questions and usable audit provisions |
| End of service | How data is returned or deleted, including remaining copies | Export format, deletion process, backup treatment and any lawful retention exception |
Where GDPR Article 28 applies, its contract duties include documented instructions, confidentiality and appropriate security. It also covers subprocessor conditions, assistance with individual rights and assistance with security obligations. The controller must receive compliance information and audit cooperation. The official Article 28 text sets the precise requirements and exceptions.
Make the subprocessor change process usable. With general written authorisation under GDPR, the processor must notify intended additions or replacements so the controller has an opportunity to object. Ask what happens operationally if you object and cannot resolve the concern.
For deletion, distinguish ending access from destroying retained copies. The OAIC’s Australian security guidance addresses reasonable steps to protect information and destroy or de-identify it when no longer needed. Retention duties can create exceptions. Ask which records remain, why they remain and when they will be removed.
Read an example without assuming compliance
A specific schedule makes the processing easier to assess, but it still needs legal and operational review. Consider these fictional descriptions of the same support-chat service.
A defined support-chat schedule
The fictional schedule permits answering delivery questions and passing conversations to the retailer’s staff. It lists chat text, contact details supplied for follow-up and the delivery-status fields returned by an authorised order lookup. It excludes payment-card details and prohibits using transcripts to train a general-purpose model.
The supplier retains active transcripts for an agreed 30-day support period. After termination, the retailer can export transcripts during a 14-day window. The schedule then requires deletion of active copies and expiry of backups within a further 60 days, subject to a stated legal retention duty.
These invented periods illustrate terms the parties would have to agree. Set retention against the store’s actual purposes and applicable legal duties.
The retailer still needs answers about who can retrieve backups, whether deleted data reappears after restoration and how downstream copies are removed. It also needs the subprocessor list, security commitments and breach procedure. The schedule’s detail helps locate those questions. The retailer must still assess whether the answers are adequate.
A broad permission with unanswered questions
Suppose the fictional terms instead allow the supplier to use all customer information to provide and improve any of its services. They give no retention limit or description of downstream recipients.
That wording leaves the retailer unable to determine which services receive transcripts, whether training is permitted or what happens to order details after cancellation. Request a bounded processing schedule and separate terms for independent uses. If the supplier cannot define the handling, restrict the data you send or choose a different arrangement.
GDPR terms and Australian obligations
GDPR Article 28 governs controller-processor arrangements where that law applies. It requires binding written terms that describe the processing and people affected. Electronic terms can meet the writing requirement. At the controller’s choice, personal data must be returned or deleted when processing services end, with existing copies deleted unless applicable EU or Member State law requires storage.
An Australian business can fall within GDPR through its European establishment, offering goods or services to people in the EU or monitoring their behaviour there. Apply the territorial conditions to your activity. The OAIC’s guide for Australian entities dealing with GDPR explains this alongside Australian obligations.
For Australia, first establish whether the Privacy Act covers your business. The OAIC’s small-business guidance explains the general exemption for businesses with annual turnover of $3 million or less and the exceptions. Size alone does not settle coverage.
For an entity covered by the Australian Privacy Principles (APPs), overseas disclosure brings APP 8 into the review. It generally requires reasonable steps to ensure the overseas recipient does not breach the APPs, other than APP 1. The disclosing entity can remain accountable for overseas mishandling, subject to statutory exceptions.
The OAIC’s APP 8 guidance generally expects an enforceable contractual arrangement. It also distinguishes disclosure from limited contractor arrangements where the retailer retains effective control. An Australian hosting location alone does not answer who can access the data overseas.
An Article 28 schedule does not settle Australian compliance or supply every safeguard needed for an international transfer. Match the terms to each applicable regime and the mapped data flow. Before granting access, resolve the processing purpose and the supplier’s handling commitments. Keep the wider supplier selection decision in your AI vendor risk assessment.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.