Privacy impact assessments for retail AI changes
Plan a privacy impact assessment for a retail AI change. Map data flows, identify affected people, choose controls and record residual risk and approval.
- Published
- Last updated
A privacy impact assessment (PIA) examines how a proposed change affects people’s privacy and records the controls needed before the change proceeds. For a retail AI workflow, map where customer information goes, assess the consequences and assign someone to verify each control.
Complete the assessment while you can still change the design. A catalogue assistant that starts receiving order references or customer photos needs a different assessment from one answering public product questions.
Decide what the assessment must establish
Define the proposed change, the people affected and the privacy decisions it requires. A PIA examines whether information handling is necessary and acceptable, as well as how it is protected. A security checklist alone cannot answer whether a retailer needs to collect a customer’s information. Completing a PIA does not certify compliance.
The OAIC’s PIA guide provides an adaptable assessment process. Begin with a short threshold assessment. Identify whether the change introduces personal information, a new purpose or a different recipient. Record why a fuller assessment is needed, or why existing controls adequately cover a limited change.
The Australian Government agency rule requires covered agencies to conduct PIAs for high privacy risk projects. That agency code does not impose the same blanket requirement on private retailers. The OAIC nevertheless encourages assessments across covered entities where a project has privacy implications.
For your retailer, first identify the applicable duties under the Privacy Act Australia framework. Record any additional state-law, contractual or overseas requirements separately. A European data protection impact assessment has its own legal triggers under the General Data Protection Regulation (GDPR). An Australian PIA does not automatically meet those requirements.
Before starting, appoint the assessment owner and the manager who can change or stop the project. Obtain the proposed design, provider terms and information-handling documents. Involve someone who understands the applicable law. A project timetable does not settle an unresolved privacy obligation.
Describe the change and map the data
Map each movement of information from collection through use and disposal, including provider systems and staff exports. Separate what the privacy policy says from what the proposed settings and contracts permit.
Consider a fictional retailer adding product questions and order support to its shopping assistant. A later option would let customers upload product photos. The intended benefit is help choosing products and checking an order without repeating the enquiry to staff. None of the arrangements below describes a particular provider or a tested system.
A fictional data-flow map
The proposed sequence is customer enquiry, retailer service, AI processing and reply. Order retrieval and staff handover create separate paths. This map records what the assessment must establish at each stage.
| Stage | Records | Movement | Purpose and access | Retention decision |
|---|---|---|---|---|
| Enquiry | Question, session reference and current product | Customer browser to retailer service | Answer the question. Customer and authorised service processes use the conversation. | Set a justified conversation period and expiry trigger. |
| AI request | Selected question, relevant catalogue text and conversation context | Retailer service to AI provider | Generate a reply. Determine whether provider support staff or subcontractors can access it. | Establish provider logging, training use and deletion terms. |
| Order support | Order reference and authenticated order result | Retailer service to order system, then back to the authorised session | Show permitted order details. Keep the full customer record out of the AI request unless needed and permitted. | Separate order-record duties from temporary lookup results. |
| Staff handover | Relevant conversation and contact details | Retailer service to restricted support workspace | Resolve the enquiry. Access belongs to the assigned support team. | Give support records their own justified schedule. |
| Photo option | Uploaded image, any embedded location data and generated output | Customer browser to image service and back | Identify a product. Assess people or private details visible in the image. | Decide storage, metadata removal and deletion before enabling uploads. |
Suppose the retailer’s notice describes order assistance, but the proposed provider terms also permit retained prompts for model training. The map exposes a second purpose requiring assessment. The statement “we use this to answer your enquiry” does not establish that training is authorised.
Record the countries of processing, storage and support access, including onward recipients. Identify who can export a conversation and where exports remain. Give every unknown an evidence owner. A sales statement about local hosting does not establish the location of every recipient or support team.
Identify impacts and choose controls
Assess privacy effects on people, then choose controls that change the proposed information handling. The Australian Privacy Principles provide the applicable federal duties for covered entities.
For a private organisation, APP 3 generally requires solicited personal information to be reasonably necessary for its functions or activities. Sensitive information generally adds a consent requirement unless an exception applies. Assess unsolicited information under APP 4 too, since customers can type private details into an unrestricted question box.
Explain collection under APP 5 and assess each proposed use or disclosure under APP 6. Document why any secondary purpose is permitted. Assess accuracy under APP 10 and the access and correction arrangements under APPs 12 and 13, including their exceptions. A general consent checkbox does not settle every duty.
For overseas handling, determine whether the arrangement is a use or disclosure. APP 8 generally requires reasonable steps before overseas disclosure, subject to exceptions. Accountability can remain with the retailer. The OAIC’s cross-border guidance explains that distinction.
Assess security and disposal under APP 11. The disposal duty has conditions, including exceptions for information that law requires you to retain. Avoid promising immediate deletion across backups without establishing what the systems can actually do.
Example control decisions
These are proposed decisions for the fictional workflow. Evidence remains a condition of approval, rather than a claim that any provider implements the controls.
| Impact on people | Proposed control | Responsible owner | Evidence needed | Residual concern |
|---|---|---|---|---|
| A customer discloses health details in a product question | Remove requests for unnecessary personal details. Establish handling for unsolicited sensitive information. | Privacy lead | Collection design and a sample handling exercise | Free text can still contain private information. |
| Another customer sees order details | Require identity checks and enforce access to the correct order at retrieval. | Engineering lead | Separate test customers cannot retrieve each other’s order | Shared devices need session-expiry controls. |
| A provider uses a private enquiry for another purpose | Select terms and settings that restrict use to the permitted purpose, or redesign the data sent. | Procurement owner | Agreed terms, configuration and onward-recipient assessment | Changed terms can reopen the decision. |
| A photo reveals another person or a home address | Limit uploads to necessary use cases and remove unnecessary metadata. Keep the option disabled until assessed. | Product owner | Sample-image handling and deletion results | Visible image content can still identify people. |
| An inaccurate AI inference affects a support decision | Keep uncertain inferences out of authoritative customer records and provide human correction. | Support manager | Sample disputed answer and correction path | Staff can copy an inaccurate answer into notes. |
| A transcript survives after its purpose ends | Apply a schedule to conversations, exports and provider copies, accounting for lawful retention. | Data owner | Retention settings and deletion evidence | Backup expiry can differ from active-record deletion. |
A privacy and ethics impact assessment can also examine exclusion or unfair treatment. For example, a customer unable to use the assistant still needs a workable support route. Keep that impact visible even where a security test passes.
Consult, approve and record the decision
Consult the people who can challenge the data-flow map before asking a manager to accept the remaining risk. Support staff know what customers actually send. Engineers identify hidden logs and retrieval paths. Procurement and the provider must explain contract terms and onward processing. Include privacy or legal advice for the duties the assessment identifies.
Obtain affected-person perspectives through a proportionate method, such as representative customer feedback using fictional scenarios. Ask whether the collection notice explains the proposed use and whether the non-AI support route is usable. Do not circulate real conversations to demonstrate the problem.
The OAIC’s AI guidance recommends privacy by design, including a PIA, when organisations consider AI products. It also calls for provider due diligence and ongoing review. Keep input data and AI-generated personal information within the assessment.
A fictional approval excerpt
The project owner proposes approving public-catalogue questions after verification, while keeping order support and photo uploads disabled. The engineering lead must supply the access-test results before order support is reconsidered. Procurement must resolve permitted provider uses and deletion terms before any customer information enters that service.
The manager records the remaining risk that customers will enter unnecessary personal information into free text. The proposed response combines collection guidance with restricted access and a handling procedure. If those measures cannot address the risk acceptably, the manager changes the design or declines the workflow.
Record the approved scope, evidence versions, outstanding conditions and the person authorised to accept residual risk. Explain which recommendations were accepted or rejected and why. Management acceptance cannot make unlawful information handling lawful. The OAIC does not approve private-sector PIAs through this process.
Verify controls and keep the assessment useful
Verify the proposed controls with non-production sample records before the changed workflow receives customer information. The expected result is a working system whose actual information movements match the approved map. A completed document without those checks leaves the control decisions unproven.
- Create two fictional customer accounts and distinct sample orders. Confirm that each session retrieves only its own permitted information. If an order reference alone exposes another account, block release and repair the authorisation check.
- Submit a distinctive fictional question. Check the reply, conversation history and staff view. Confirm that another session and any public page cannot retrieve the private exchange.
- Trace the sample request through the configured services. Compare the recipients and fields with the map. Investigate an unexpected analytics or support destination before accepting the flow.
- Apply the proposed retention and deletion process to the sample conversation, attachment and export. Check active records and establish how provider copies and backups expire. If a copy remains, identify its retention basis and restrict access.
- Exercise access and correction handling with a sample inaccurate record. Confirm that staff can locate the relevant copies and apply the permitted response without changing another customer’s records.
Keep evidence in a restricted location and record failures against their control owners. The fictional approval above becomes actionable only when its conditions have evidence.
Reopen the assessment when the provider, model, purpose or information types change. An incident, a new onward recipient or a failed deletion check also warrants review. Assign someone to monitor those triggers and record when the assessment must next be reviewed.
Use the separate privacy impact assessment template to record the project-specific findings and decisions. Before enabling the workflow, confirm that every release condition has evidence and that the approved scope matches what customers can actually use.
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.