GDPR privacy policy for Australian retailers
Selling to EU shoppers? Check when GDPR applies, then match your privacy notice to lawful bases, customer rights, consent and international transfers.
- Published
- Last updated
A GDPR privacy policy explains how your Australian store handles customer data when its activities fall within the European Union’s General Data Protection Regulation (GDPR). Relevant EU establishment activities, deliberate offers to people in the Union or monitoring their behaviour there can bring processing within scope.
Start with your Australian customer notice, then map the European requirements to the data your store actually uses. The clauses below use a fictional retailer to show that mapping. They need adaptation to your business and do not establish compliance by themselves.
Check whether your store’s activities engage the GDPR
Assess the processing activity before adding European clauses to your notice. Under Article 3, processing in the context of an EU establishment’s activities can be covered even when the processing happens in Australia.
Without that establishment, examine whether processing relates to offering goods or services to people in the Union, or monitoring their behaviour there. The European Data Protection Board’s territorial-scope guidance explains how to assess those connections.
Consider two illustrative stores. An Australian retailer advertises delivery to France, runs French-market campaigns and accepts orders through that channel. Those facts support deliberate targeting. An Australian-only store receives an incidental visit from someone in France. Website accessibility alone does not establish targeting, although behavioural monitoring needs its own assessment.
A customer’s EU nationality alone does not decide scope. For the targeting test, their location during the relevant activity matters. Assess each purpose and channel instead of assuming the same result for every visitor.
The UK has a separate data protection regime. An EU assessment does not settle UK obligations. Australian duties can also coexist with GDPR duties, as the OAIC’s guidance for Australian entities explains.
Identify the controller and each customer data flow
The controller decides why personal data is processed and how that processing is organised. A processor handles personal data on the controller’s behalf. Determine each organisation’s role for each purpose. A payment provider could have its own controller responsibilities alongside services it supplies to your store.
Identify the retailer’s legal entity and privacy contact first. Then complete a data-flow worksheet before drafting. These are illustrative entries, not claims about a particular platform.
| Customer activity | Data and source | Purpose and recipient | Location to record |
|---|---|---|---|
| Account creation | Customer supplies name, email and login details | Store manages the account through its account provider | Account database, backups and support access countries |
| Checkout | Customer supplies delivery details and payment information | Store fulfils orders; payment provider and carrier receive relevant details | Each provider’s processing and access countries |
| Marketing signup | Customer supplies email and a recorded choice | Store and email provider send selected marketing | Mailing-list storage and delivery provider locations |
| Analytics | Browser supplies device identifiers and page events | Store and analytics provider measure browsing | Collection endpoint, processing and onward recipients |
| Shopping conversation | Customer supplies preferences and messages | Store and conversation provider answer questions | Conversation storage, logs and overseas access |
| Image upload | Customer supplies a product or room photo | Image provider processes the requested image task | Upload storage, processing and deletion locations |
| Human handover | Conversation provider passes transcript and relevant order reference | Authorised store staff or helpdesk provider resolve the request | Helpdesk storage and staff access countries |
Record retention and deletion treatment for every row too. Separate identifiable data from genuinely anonymous statistics.
An EU representative and a data protection officer are different roles. Article 27 generally requires a representative for a retailer without an EU establishment whose processing falls under Article 3(2). Its occasional-processing exception has further limits on large-scale sensitive or criminal-offence data and risks to people. Small business size alone does not establish that exception.
A data protection officer is required in specified circumstances under Article 37. Relevant triggers include core activities involving large-scale regular and systematic monitoring, or large-scale processing of special-category or criminal-offence data. Check applicable national requirements too. The Commission’s obligations guidance explains the role. Include contact details for either role where applicable.
Connect each purpose to a lawful basis
Select a lawful basis for each purpose before writing its notice clause. Necessary order processing and optional personalisation have different purposes, even when the same system performs both.
Use this purpose-and-basis worksheet to document the decision. Each suggested basis depends on the stated conditions.
| Purpose | Conditional basis | Decision to document |
|---|---|---|
| Deliver an order | Contract, where the data is necessary to fulfil the customer’s purchase | Why each requested field is needed to complete delivery |
| Answer an order-support request | Contract, where necessary to perform that contract; assess other support purposes separately | Which order details and messages the response needs |
| Prevent fraud | Legitimate interests where the purpose, necessity and balancing assessment supports it | Fraud risk, less intrusive alternatives and effects on customers |
| Optional saved personalisation | Consent where you choose and can satisfy that basis | What is saved, the specific purpose and how withdrawal stops the use |
| Send optional email offers | Consent where required by applicable marketing rules | The signup choice, proof of consent and unsubscribe mechanism |
| Retain statutory records | Legal obligation where qualifying EU or member-state law requires the processing | The actual law and required records; an Australian duty alone does not establish Article 6(1)(c) |
The EDPB’s lawful-processing guide distinguishes contractual necessity from business uses such as advertising. Adding optional tracking to sales terms does not make that tracking necessary for the contract.
For legitimate interests, identify the interest, assess necessity and balance the impact against the individual’s interests and rights. Keep that assessment and explain the relevant interest in the notice. Customers retain applicable objection rights.
Consent needs a freely given, specific, informed and unambiguous affirmative choice. Pre-ticked boxes do not supply that choice. Withdrawal must be as easy as giving consent and must stop future processing under that consent. Earlier lawful processing remains lawful.
A privacy notice supplies information. It does not require the customer to agree to every use of their data. Keep optional choices separate from necessary checkout processing. If you offer an online service directly to children and rely on consent, assess Article 8 and the relevant national age rules.
Draft the customer transparency clauses
Write clauses from your completed worksheet, then put collection-specific explanations where customers give you data. The Irish Data Protection Commission’s transparency checklist sets out the Article 13 and 14 information requirements.
The following adaptable examples describe fictional Wattle Home, an Australian homewares retailer. The assumed configuration includes optional saved preferences and a support transcript deleted after 90 days unless a documented dispute requires limited retention. None of these details describes your store automatically.
Controller and contacts
Wattle Home Pty Ltd is the controller for the customer processing described in this notice. Contact our privacy team through the store’s privacy enquiry form or the postal address shown in our contact details.
Replace that description with your legal entity and actual contact routes. Where required, add the EU representative’s identity and contact details and the data protection officer’s contact details. Do not give an ordinary customer-service employee a statutory title they do not hold.
Purposes, bases and interests
We use your delivery name, address and order details to fulfil your purchase under our contract with you. We use the details needed to answer an order query for that contractual purpose. With your consent, we save your shopping preferences to personalise later visits. You can withdraw that consent in preference settings.
This adaptable clause describes a separately assessed fraud-prevention use. We assess order-risk signals to protect customers and our store against fraudulent purchases. We rely on our legitimate interest in preventing fraud, subject to your rights. You can object through our privacy contact.
Name the actual signals and explain their use at a level customers can understand. Retain the clause only if the assessment supports that processing.
Recipients and retention
We share the information needed for each task with our payment provider, delivery carrier and customer-support provider. Authorised store staff can access your support conversation to resolve your request. Our international-recipients section explains overseas processing and applicable safeguards.
We delete ordinary support transcripts 90 days after the conversation closes. If a dispute requires a transcript, we retain the relevant material until that dispute and any applicable claims period end. Order records follow the separately stated record-retention requirements.
Adapt the recipient categories and periods to actual operations, including backups. Give the order-record period or usable criteria in the finished notice. A generic promise to retain everything for as long as necessary leaves the customer without that explanation.
Required fields and optional information
We need your delivery address to ship a physical order. Without it, we cannot complete delivery. Saving preferences and uploading a room photo are optional. You can browse and buy without either feature.
Identify separately any statutory requirement and its consequences. Add an international-transfer clause only after completing the transfer worksheet in the next section.
Rights and complaints
You can contact our privacy team to request access, correction, deletion or restriction of your personal data, subject to the applicable conditions. You can also request portability where it applies. You can object to relevant processing, including direct marketing. Withdraw consent through the same preference controls used to give it, or contact our privacy team. Withdrawal does not affect earlier processing that was lawful under your consent.
You have the right to complain to a competent supervisory authority, including in the member state of your habitual residence, workplace or the alleged infringement.
Collection sources and timing
For direct collection, provide the relevant information when you collect the data. A checkout notice can identify the order purpose and link to the detailed notice. The chat opening and upload control need information relevant to those activities too.
For indirect collection, identify the data categories and actual source, including whether it is publicly accessible. For example, explain that a carrier supplies delivery-status events and the order reference used to match them.
Under Article 14, supply the information within a reasonable period and at most one month. Bring that forward to the first communication or first disclosure where either happens sooner. Apply an exception only when its conditions are met. Give information about a new purpose before further processing starts.
Match chat, tracking and automated decisions to the notice
Describe a conversation by its separate uses of customer data. The following illustrative journey uses Wattle Home’s assumed configuration and unnamed service providers.
- A shopper asks for a washable rug for a small room. The conversation provider processes the message for the store to deliver the requested response.
- The shopper chooses to save room preferences for future visits. The store records the choice and the personalisation provider saves only the selected preferences under the stated consent.
- After buying, the shopper supplies an order reference to ask about delivery. The support provider retrieves the relevant order status using the store’s approved identity checks.
- The shopper requests a person. The retailer’s authorised support team receives the relevant transcript and order reference through its helpdesk provider. The handover notice identifies that recipient category and purpose.
An image upload adds another flow. State what the image provider receives, whether it retains the original and when deletion occurs. A photograph can reveal more than the product the customer intended to show.
Delivering a requested support answer does not establish permission for optional marketing or tracking. Cookie storage and device access also depend on applicable ePrivacy and national rules. The Irish regulator’s tracking guidance explains the distinction from GDPR processing. A privacy notice alone does not collect a required tracking consent.
Ordinary product suggestions do not automatically engage Article 22. Assess whether a decision is solely automated and produces legal or similarly significant effects. An automated credit refusal presents a different issue from suggesting a rug colour.
Where Article 22 applies, establish a permitted exception and the required safeguards before using the decision process. Explain its existence, meaningful information about the logic, its importance and expected consequences. Applicable safeguards include human intervention, expressing a view and contesting the decision. Human review must be meaningful. The Commission’s explanation of individual rights covers these protections.
Explain international recipients and transfer safeguards
Identify the parties and countries for every international flow, including remote access and onward recipients. Hosting the storefront in Australia does not settle where a support provider or subprocessor handles customer data.
Under the EDPB’s transfer guidance, direct submission by an individual differs from a transfer between organisations. A shopper in France entering delivery details directly into an Australian retailer’s form does not, by that act alone, create a Chapter V transfer. The retailer can still be subject to GDPR for that processing.
If that retailer then makes the details available to a separate Australian support processor, assess that disclosure as a transfer. The exporter can be outside Europe. A separate overseas company receiving access also needs assessment, even if the database stays in its original country.
Use a transfer worksheet for the actual vendor chain.
| Flow to investigate | Exporter and importer | Evidence needed before writing the clause |
|---|---|---|
| Store to support provider | Identify both legal entities and their controller or processor roles | Data categories, countries, access permissions and applicable transfer route |
| Support provider to subprocessor | Identify the onward recipient and its role | Authorised task, country, onward-transfer protection and retention |
| Store to overseas payment provider | Identify the payment entity and its role for this use | Data received, country and transfer instrument where required |
| Overseas remote access | Identify whether access is by a separate organisation | Access country, receiving entity and safeguards for that disclosure |
Adequacy, appropriate safeguards and derogations are different routes. An adequacy decision must cover the actual destination and recipient. Where appropriate safeguards are used, choose an instrument applicable to the parties and their GDPR status. Standard contractual clauses require the applicable assessment and any necessary supplementary measures. Limited derogations are not a routine substitute for safeguards in ongoing vendor arrangements.
The EDPB’s international-transfer guide explains these routes. A notice records the arrangement. It does not create it.
For an illustrative adequacy clause, assume Wattle Home uses a support processor in New Zealand. Its wording could read as follows.
We send support transcripts to our support processor in New Zealand. We rely on the European Commission’s adequacy decision for New Zealand for this transfer. Our privacy team can provide details of that decision.
Adapt the clause by naming your actual recipient category and country. State the actual adequacy decision or safeguard and explain how customers can obtain a copy. If using contractual safeguards, provide a working request route and identify the applicable clauses. Complete the underlying legal arrangement before presenting it as an existing protection.
Make the stated rights work across store systems
Give your privacy contact an operational path from a customer’s request to the systems holding their records. Rights have conditions. Access and correction differ from deletion, and portability applies to qualifying automated processing based on consent or contract.
Restriction can limit use while accuracy or an objection is assessed. An objection based on a person’s circumstances needs assessment under the applicable basis. A direct-marketing objection requires that marketing use to stop, including related profiling.
Use this request sequence, supported by the EDPB’s rights-handling guidance.
- Record receipt, the request and its response deadline. Route it to the responsible privacy team even if it first arrives in chat.
- Confirm identity proportionately. Seek extra information where there are reasonable doubts, without collecting unnecessary identification.
- Search account, checkout and conversation records, including uploaded images and relevant provider systems.
- Assess the requested right and any exception. Coordinate corrections, restrictions or deletion with recipients where required.
- Send a documented response without undue delay and within one month. A permitted extension adds up to two further months for complexity or request numbers. Explain the extension within the first month.
If refusing action, explain the reasons and the available complaint and judicial-remedy routes. Requests are generally free. A fee or refusal for a manifestly unfounded or excessive request requires justification.
Deleting a chat does not automatically justify deleting an order record that must lawfully be retained. Explain the retained category, purpose and period. Restrict its use accordingly. A legal-retention exception needs an applicable basis. It does not justify keeping the whole conversation indefinitely.
Send consent withdrawals and marketing objections to every system performing that use. A support agent marking a ticket complete does not stop an email campaign unless the mailing system receives the change.
Verify the notice against a complete shopper journey
Walk through checkout, tracking choices and support as one customer, then compare each collection point with the notice. The following is an illustrative acceptance check for Wattle Home, not a report of a tested store.
| Journey step | Expected observable result | Repair if it fails |
|---|---|---|
| New customer checks out | Order-purpose information is available before submission; optional fields are identified | Add the collection notice and remove unnecessary required fields |
| Customer declines optional tracking | Tracking that needs consent stays inactive; necessary checkout still works | Correct the consent controls and tracking configuration |
| Customer saves then withdraws preferences | Future consent-based personalisation stops and the affected provider receives the withdrawal | Repair propagation between settings and the personalisation system |
| Customer asks for human support | Authorised staff receive the relevant record under the stated notice and access rules | Reduce handover data or correct the recipient explanation |
| Customer requests deletion in chat | The privacy team receives the request; the response distinguishes deleted chats from any lawfully retained order records | Repair routing and document retention decisions |
| Transcript reaches its retention limit | Ordinary transcripts are deleted under the stated rule; any exception has a recorded reason and end criterion | Correct deletion jobs, provider settings or the notice’s inaccurate promise |
Repeat the relevant checks when you add an EU sales channel, change a purpose or vendor, alter an international flow or introduce a consequential automated decision. Update the notice and affected collection points before the changed use starts. Publish clauses only when the contacts and controls they describe work across the complete journey.
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.