Privacy and confidentiality policy for retail staff

Write your employee privacy policy around real staff records, monitoring and access to shopper chats, with confidentiality clauses and workplace rights.

A privacy and confidentiality policy explains how you handle worker information and how your team protects the information it sees at work. For a retail employer, that includes staff records and customer chats, with different access rules for each.

Start with the systems your store uses. Name the person responsible for the policy, describe any monitoring and turn the examples below into instructions your team can follow.

Separate staff privacy from confidentiality duties

Staff privacy covers the information you collect about workers. Confidentiality duties govern how workers use customer information, colleague records and restricted business information they encounter through their jobs.

For example, a support worker’s bank details belong in their employment records. A shopper’s order history belongs to the customer record, even when that worker opens it during a support conversation.

State which parts of your employee privacy policy apply to each group:

  • Current employees receive the staff-information clauses and the confidentiality rules for their role.
  • Former employees receive information about retained records and the request route. Explain any continuing confidentiality duties separately from their removed system access.
  • Applicants receive recruitment-information details, including how unsuccessful applications are handled.
  • Contractors receive information about their own details and task-specific confidentiality and access rules.
  • Agency staff receive your workplace access rules. Identify the agency that employs them and explain which records each organisation handles.

Apply the same distinction to volunteers if your store uses them. Giving someone a staff account does not establish an employment relationship.

Keep the shopper-facing notice separate. The privacy policy template covers customer disclosures that this staff document supports.

Map employee data and the exemption’s limits

Map each record to its source, purpose, authorised readers and storage system before drafting promises about it. The following worksheet is illustrative. Replace the system descriptions and roles with those in your store.

Example staff-record worksheet

RecordCollection sourceWork purposeAuthorised readersStorage system
RecruitmentApplicant, referee and recruitment agencyAssess an applicationHiring manager and recruitment officerRecruitment folder with restricted access
Emergency contactWorkerContact someone during an emergencyPeople manager and designated emergency responderStaff register
PayrollWorker and approved time recordsCalculate pay and meet reporting dutiesPayroll officer and approved payroll providerPayroll system
RostersAvailability supplied by workers and manager allocationsArrange shiftsScheduling manager and affected workersRoster system with limited team visibility
LeaveWorker request and necessary supporting documentsApprove leave and maintain balancesLeave approver and payroll officerLeave system and restricted document folder
PerformanceManager reviews and relevant work evidenceManage performance and trainingPeople manager and authorised supervisorRestricted personnel folder
Support activityNamed account actions and support-system logsInvestigate access and support qualitySupport lead and authorised security administratorSupport platform audit log

The private-sector employee-record exemption is conditional. Under Privacy Act section 7B(3), both the employment relationship and the held record matter. The act or practice must directly relate to a current or former employment relationship and an employee record held by that employer.

A payroll record used by its employer to pay an employee can meet those conditions. The exemption does not automatically cover every detail about a worker or every collection step. Assess collection separately from later handling of a held record.

The Office of the Australian Information Commissioner’s employee-record guidance identifies boundaries that matter here. An unsuccessful applicant has no current or former employment relationship with the store. A contractor’s details and volunteer records do not gain the exemption through an employee relationship that does not exist.

An outsourced payroll provider cannot simply borrow the store’s exemption for records about the store’s employees. Agency arrangements also require you to identify the actual employer and record holder. Where the exemption does not apply, assess the organisation’s other privacy obligations. The Privacy Act Australia guide explains that wider applicability question.

Write the staff information clauses

Write the clauses from the completed worksheet so your employee data privacy policy describes actual handling. The following adaptable wording uses a fictional retailer, Example Retail Pty Ltd. Its named roles and systems are examples to replace before you issue your own policy.

Example clause: responsibility and coverage

Example Retail Pty Ltd handles worker information under this policy. Our People Manager is the policy owner and receives staff-information requests through the staff portal’s People request form. Workers without portal access can lodge a request through our business contact channel, addressed to the People Manager.

The staff-information provisions apply to records we handle about employees and former employees. Recruitment provisions apply to applicants. We explain our handling of contractor and agency-worker details when we collect them. Everyone granted access to our systems follows the confidentiality and access rules relevant to their duties.

Example clause: collection and use

We collect the information recorded in our staff-record worksheet for the purposes stated there. We obtain information from workers, their nominated contacts, authorised recruitment sources and our work systems. We explain a new collection or use before introducing it and meet applicable legal requirements.

We limit collection to information needed for our work purposes or required by law. Staff can ask the People Manager why information is requested and how it will be used.

Example clause: access and service providers

Access follows the approved role and record permissions in our worksheet. Managers receive information needed for their responsibilities. Payroll providers receive the records needed to process pay. Other providers receive only information authorised for their contracted task or another lawful purpose.

The People Manager records each provider’s service, information shared and access arrangements in a provider register. It records overseas handling locations and applicable safeguards. This includes countries where known and any legal requirements. Staff can request these details through the policy contact.

Do not promise Australian-only storage without checking storage, backups and overseas support access. A provider’s local office does not establish where its systems or support staff handle information.

Example clause: storage, retention and requests

We keep staff records in the approved systems listed in the worksheet. We restrict permissions and use named accounts, with stronger sign-in controls where available. Paper records remain in locked storage with controlled access.

Each record category has a retention rule based on applicable legal requirements and its documented business purpose. The record owner arranges secure disposal when retention ends, subject to any investigation or legal hold. Employment ending does not automatically trigger deletion.

Workers can ask the People Manager for access or correction. We identify the applicable access rights and explain the response. We protect other people’s information when providing records.

Policy-to-system checks

ClauseWhat to record before issuing itResponsible role in this example
Entity and contactLegal employer name, working contact route and alternate contactPeople Manager
Collection and purposeActual fields, collection sources and reasons for each record categoryRecord owner
AccessPermission groups and who approves or removes themSystem administrator and record owner
Providers and overseas handlingProvider register, handling locations and contract controlsOperations Manager
Storage and retentionApproved storage, safeguards, retention basis and disposal processRecord owner with legal or payroll advice where needed
Requests and concernsIntake route, secure identity check and escalation contactPeople Manager

The Fair Work Ombudsman’s workplace privacy guide explains what a staff policy can tell workers about their information. Keep your final wording consistent with the responsibilities your systems actually enforce.

Explain monitoring before it affects staff

Describe each monitoring activity separately, including what it captures and who can review it. Keep a technology out of your policy if your store does not use it.

Example monitoring register

ActivityPurposeInformation capturedAuthorised viewersRetention criterion
CCTVStore safety and investigation of incidentsImages in the stated camera areasDesignated safety managerApproved footage schedule, with relevant incident footage preserved
Support-session logsInvestigate access and service issuesAccount actions, conversation identifiers and timestampsSupport lead and security administratorDocumented investigation and audit needs
Shared-device access logsInvestigate use of store equipmentNamed sign-ins and session timesSecurity administratorDocumented security review period
Call recordingDefined service-quality or dispute purposesCall audio and relevant call detailsApproved quality reviewerApproved recording schedule and applicable legal requirements

A workplace privacy policy informs staff. Surveillance laws can impose additional requirements based on the jurisdiction, technology and circumstances. Check each workplace location, including arrangements for staff working remotely, before switching monitoring on.

New South Wales provides a bounded example. Sections 10 and 12 of the Workplace Surveillance Act address written advance notice and computer-surveillance policies. Computer surveillance must follow the employer’s policy, notified in advance so employees can reasonably be understood to know and understand it. These are separate requirements, as NSW’s Independent Commission Against Corruption explains in its public proceedings.

Use the NSW Act to assess the relevant notice rules and exceptions for that workplace. Do not turn the NSW example into an Australia-wide notice period. Check camera placement and audio-recording rules separately where those technologies are used.

Limit staff access to shopper chats and orders

Give a support worker access to the customer records needed for the assigned enquiry. Their employment records need a separate permission decision.

Consider this illustrative handover. A shopper enters an order number in the store’s shopping interface and asks about a delayed delivery. The conversation passes to a human support queue. An assigned worker opens the transcript and the necessary order details to answer.

That transcript remains a customer record. The worker’s sign-in and access log describe the worker’s activity. Their bank details remain in payroll. A single support interaction does not justify giving everyone access to all three.

Example access matrix

RolePermitted accessLimitApproval owner
Support workerAssigned conversation and necessary order detailsNo employee payroll files or unrelated customer exportsSupport lead
Payroll workerEmployee pay records needed for payroll dutiesNo shopper transcripts through the payroll rolePayroll manager
External contractorRecords needed for the agreed taskTime-limited account and approved dataset onlyContract owner

Use named accounts on shared devices and sign out before the next worker starts. Approve exports by purpose, recipient and storage location. Keep an export within the approved work system instead of copying it to personal email or an unrelated tool.

When a role changes, remove old permissions as you grant the new ones. At departure, revoke accounts and sessions and remove access to shared folders and provider systems. Preserve records that the business must retain.

If a transcript reaches the wrong worker, stop using it and report its location to the support lead through the incident channel. Give the conversation identifier and access details. Avoid forwarding the transcript into another inbox to demonstrate the mistake.

Protect confidential information without restricting workplace rights

Define confidentiality through permitted work duties and lawful disclosures. A rule that labels every workplace conversation confidential can obscure employees’ rights.

Example confidentiality clause

Use customer records, colleague records, credentials and restricted commercial information only for authorised work duties or a lawful disclosure. Access only the records your task requires. Share information through approved channels with authorised recipients and protect credentials from disclosure.

These rules preserve lawful disclosures to regulators, courts and other authorised recipients. They also preserve legally protected complaints or disclosures. They do not restrict applicable rights to discuss, or decline to discuss, your own pay and employment conditions needed to work it out. Another worker can decline to share their information.

Fair Work Act section 333B protects pay discussions and questions about relevant conditions where the rights apply. The Fair Work Ombudsman’s pay-secrecy guidance explains the transition rules for older, unchanged contracts containing pay-secrecy terms. Assess those conditions without writing a blanket ban into a new policy.

A worker discussing their own hourly rate is different from opening a colleague’s payroll file without authorisation. Preserve the discussion right while retaining access controls on payroll records.

Example acknowledgement

I have received this policy, know where to find it and understand the responsibilities explained for my role. I know how to raise a question or report a concern. This acknowledgement does not remove statutory rights or authorise monitoring beyond what the law permits.

Record training and questions alongside the acknowledgement. A signature alone does not establish that monitoring is lawful or that permissions match the policy.

Handle access requests and privacy concerns

Route staff requests to a named policy contact and identify the right that applies to the requested record. Employment-record access, privacy-law access and access your business voluntarily provides can have different rules.

Current and former employees have statutory rights to inspect and copy specified employment records under Fair Work requirements. Where the Australian Privacy Principles apply, their access and correction rules require a separate assessment. The employee-record exemption does not create a Privacy Act right to every exempt record.

Use this request procedure:

  1. Receive the request through the policy contact and record what the person wants to access or correct.
  2. Verify identity through a secure method suited to the request. Avoid collecting more identity information than needed.
  3. Locate records in the relevant systems and identify applicable rights, response requirements and any additional access the employer provides.
  4. Protect third-party information, provide records securely and explain any lawful limit on access. Correct inaccurate information through the responsible record owner and preserve required audit history.

For incidents, give workers a fast internal reporting route to the responsible manager. Include lost devices, mistaken permissions and disclosed customer information. Preserve logs and relevant evidence, restrict further exposure and escalate to the person responsible for privacy and security decisions.

Provide an alternate complaint contact when the concern involves the usual manager. Explain how the complainant receives a response and how unresolved concerns move to the next responsible person. Keep external complaint and lawful disclosure rights available.

Put the policy into onboarding and offboarding

Make the named policy owner responsible for putting the document into everyday work. Use this sequence before granting a new worker access:

  1. Complete the record, provider and monitoring worksheets with the people who own those systems.
  2. Adapt the clauses to the actual employer and work arrangements. Resolve the applicable privacy, surveillance and employment-record requirements.
  3. Communicate the policy to affected workers before the handling or monitoring begins, meeting any required notice and consultation obligations.
  4. Train each role on the records it can use, approved exports and the incident route. Record the acknowledgement and answer questions.
  5. Check permissions during onboarding, role changes and offboarding, then record who completed each check.

Test the policy with a new support account, a contractor handover and a departing worker’s account. The support account must reach its assigned conversation without exposing payroll. The contractor must receive only the agreed records, with an access end point. The departing account must lose access while required business records remain retained.

If a test fails, change the permissions or the policy before treating onboarding as complete. Revisit both when you add monitoring, change a payroll or support provider, introduce another data use or alter the access model.

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.

See it in actionFree trial · Simple setup