Skip to content
Convergo360

360 feedback and POPIA, what HR needs to know

POPIA applies to every 360 because ratings and comments are personal information. HR must state a purpose, sign operator contracts and limit retention.

· 9 min read · Convergo360 team

POPIA applies to every 360 feedback process run in South Africa, because the ratings and comments people give about a manager are personal information about that manager, and the raters' names and email addresses are personal information about them. The employer is the responsible party, so HR has to state a clear purpose, collect only what that purpose needs, put written contracts in place with any administrator or software provider, cover data that leaves the country, limit retention and secure the data. A properly anonymous 360 makes several of these duties easier to meet.

This article is general information about POPIA, not legal advice. Check your own setup with your Information Officer or a legal adviser.

Does POPIA apply to 360 feedback?

Yes. The Protection of Personal Information Act 4 of 2013 (POPIA) defines personal information to include "the views or opinions of another individual about the person". A 360 collects exactly that. It also holds the manager's own self-assessment and the names, email addresses and roles of everyone invited to rate.

Most of POPIA came into force on 1 July 2020 with a 12-month grace period. Organisations had until 30 June 2021 to comply, and the Information Regulator could enforce the Act from 1 July 2021.

In a 360 the roles usually split like this:

POPIA role Who it is in a 360
Responsible party The employer that decides to run the 360 and why
Data subject The manager being rated, and each rater
Operator An outside administrator or consultant, and the software provider
Information Officer The head of the business, or a person they authorise in writing

If you are new to running a 360, the South African guide to 360 feedback covers the process end to end.

What purpose should a 360 state under POPIA?

Section 13 requires personal information to be collected "for a specific, explicitly defined and lawful purpose". Section 18 requires you to tell people that purpose when you collect the information.

For a leadership 360 the cleanest purpose is development. Write it into the invitation and the survey introduction in plain words, for example "to help each manager understand how their leadership is experienced and plan their development". Then stick to it. If the same data later feeds pay, promotion or disciplinary decisions, that is further processing that has to be compatible with the original purpose under section 15. It also changes how people rate. Our article on 360 feedback versus performance reviews explains why mixing the two damages both.

The survey introduction should also tell raters:

  • who will see their answers and in what form
  • that results are shown only for groups of at least three people
  • that manager feedback is shown separately and is not anonymous
  • what happens to a comment that describes serious misconduct
  • how long raw answers are kept

How much personal information should a 360 collect?

Section 10 says personal information can be processed only if it is "adequate, relevant and not excessive" for the purpose. In a 360 the most common excess is demographic detail. Asking raters for age band, department, length of service or gender adds little to a development report and makes small groups easier to identify.

Collect the rater group (peer, direct report and so on), the ratings and the comments. Leave out anything you would not use in the report. Keep invitation and reminder emails thin as well. They need a link and a deadline, and they never need feedback content.

Who is an operator in a 360, and what must the contract cover?

An operator processes personal information for you under a contract, without coming under your direct authority. In a 360 that usually means two parties:

  1. An independent administrator or consultant who runs the cycle, reviews comments and releases reports.
  2. The software provider whose platform stores and processes the answers.

Section 20 requires an operator to process information only with your knowledge or authorisation and to treat it as confidential. Section 21 requires a written contract that makes the operator establish and maintain the security measures in section 19. The same section requires the operator to notify you immediately when there are reasonable grounds to believe the data has been accessed or acquired by someone unauthorised.

A sound operator agreement for a 360 covers:

  • the purpose and the data the operator will handle
  • who at the operator can access answers, by name or role
  • the security measures they keep
  • immediate breach notification to you
  • any subcontractors, including hosting and email providers
  • where the data is stored
  • deletion or return of data at the end of each cycle

Does using a cloud or email provider count as a cross-border transfer?

It can. Section 72 limits transfers of personal information to a third party in a foreign country. A transfer is allowed if one of these applies:

  • the recipient is bound by a law, binding corporate rules or a binding agreement that gives an adequate level of protection
  • the data subject consents
  • the transfer is necessary to perform a contract with the data subject
  • the transfer is necessary for a contract with a third party that is in the data subject's interest
  • the transfer benefits the data subject, consent is not reasonably practicable and they would likely consent

For a 360 this question comes up in two places. The first is where the platform hosts its database and backups. A provider hosted in Europe or the United States sends every rating outside South Africa. The second is email. Many transactional email services process addresses outside the country, even when the platform itself is hosted locally.

Ask every provider where data is stored and which subprocessors handle it. Where some processing happens abroad, check the provider's contract terms against section 72 and keep what crosses the border to a minimum. An invitation email that carries only a name, a link and a deadline sends far less abroad than one that names the manager being rated.

How long can you keep 360 feedback data?

Section 14 says records "must not be retained any longer than is necessary for achieving the purpose", unless a law, a contract or consent allows longer. When the period ends you must destroy, delete or de-identify the record in a way that prevents its reconstruction.

A 360 produces different kinds of data, and each one deserves its own period:

Data Why you hold it A defensible approach
Raw answers and comments To calculate and review the report Delete soon after the report is released, for example within 90 days
Rater lists and invitation records To manage the cycle Delete when the cycle closes, unless needed for a dispute
Released reports Development planning and coaching Keep for a set period, such as until the next cycle or a few years
Aggregated trend scores Tracking progress over time Keep only scores based on three or more responses

Write these periods into the privacy notice and the operator agreement, and check that the platform deletes on schedule.

Can a rater ask for their own 360 answers under POPIA?

Section 23 gives a data subject the right to ask whether you hold their personal information and to request a record of it. A rater can make that request. In a properly anonymous 360, the system holds no link between a rater and the answers they gave, so there is no record that identifies that rater's answers to return.

This is the design working as intended. If an administrator could find a rater's answers to satisfy an access request, anyone with that access could find them for any other reason. State in the privacy notice that individual answers cannot be traced back to the person who gave them, so they cannot be returned on request. The anonymity article explains how that separation works.

A manager being rated can ask for the personal information held about them, which includes the opinions in their report. Section 23(4) applies the refusal grounds in the Promotion of Access to Information Act (PAIA), which include protecting the privacy of third parties. Redacted comments and group averages protect raters here as well.

What security safeguards does POPIA expect for a 360?

Section 19 requires "appropriate, reasonable technical and organisational measures" to prevent loss of personal information and unlawful access to it. You must identify foreseeable risks, put safeguards in place, check them regularly and update them.

For 360 data the main risks are people inside the business reading individual answers, and someone linking a rater to their answers through IDs, timestamps or logs. Look for:

  • encryption that stops the platform provider and your own IT team reading individual answers
  • named access for the administrator, with multi-factor sign-in
  • no rater identity or submission time stored next to answers
  • reports downloaded through signed-in links rather than sent as email attachments
  • an audit log of who opened what, and when

The anonymity page sets out how these controls work in our product.

What does the Information Officer need to do for a 360?

In a private company the head of the business is the Information Officer by default. They can authorise someone in writing and designate deputies under section 56. Section 55 makes the Information Officer responsible for encouraging compliance, handling requests made under the Act and working with the Regulator on any investigation. Information Officers must be registered with the Information Regulator before they take up their duties.

Before a 360 launches, the Information Officer should review the privacy notice, the operator agreements, the cross-border position and the retention periods. They should also be the named contact for access requests and breaches.

What happens if 360 data is breached?

Section 22 requires you to notify the Information Regulator and the affected data subjects when there are reasonable grounds to believe their personal information has been accessed or acquired by an unauthorised person. Notification must happen "as soon as reasonably possible after the discovery of the compromise". The notice to data subjects must be in writing and give them enough information to protect themselves.

Since 1 April 2025 the Regulator has required security compromise reports to go through its eServices portal. Your operators must tell you immediately under section 21, so build that into the contract and agree who calls the Information Officer.

A 360 built so that nobody outside the administrator can read individual answers reduces what a breach exposes. Encrypted answers with no rater ID attached leak far less than a spreadsheet of names and comments.

POPIA checklist for running a 360

Area POPIA section What to check
Purpose 13, 18 Purpose stated in the invitation and survey introduction
Minimality 10 No demographics or fields you will not report on
Operator agreement 20, 21 Written contract with the administrator and software provider
Cross-border transfers 72 Hosting location and email provider checked, emails kept thin
Retention 14 Separate periods for raw answers, reports and trend scores
Access requests 23 Privacy notice explains raters' answers cannot be traced back
Security 19 Encryption, named access, no rater IDs or timestamps on answers
Information Officer 55, 56 Registered with the Regulator and briefed on the cycle
Breach notification 21, 22 Operator must report immediately, Regulator notified through eServices

Next step

Take the checklist to your Information Officer before you pick a provider, and ask each provider to answer it in writing. If you want to see how Convergo360 handles hosting, encryption and retention, read how it works or contact us with your Information Officer's questions.

Sources

Common questions

Does POPIA apply to 360 degree feedback?

Yes. POPIA defines personal information to include the views or opinions of another person about an individual, so every rating and comment about a manager is personal information. Rater names and email addresses are personal information too.

Is a third-party 360 administrator an operator under POPIA?

Usually yes. A consultant or software provider who processes 360 data on your behalf is an operator, and section 21 requires a written contract that makes them keep the security measures in section 19 and tell you immediately about any breach.

Can a rater ask for a copy of their own 360 answers?

They can ask, but a properly anonymous 360 holds no link between a rater and their answers, so there is no record to retrieve. Say this in the privacy notice before the survey opens.

How long can we keep 360 feedback data?

Section 14 says you keep records only as long as the purpose needs them. Set separate periods for raw answers, released reports and trend scores, and delete or de-identify each one when its period ends.

Do we have to report a 360 data breach?

Yes, if there are reasonable grounds to believe someone unauthorised accessed or acquired the data. Section 22 requires you to notify the Information Regulator and the affected people as soon as reasonably possible, and reports to the Regulator now go through its eServices portal.

See a sample report and how a cycle runs

A 30-minute walkthrough with someone who has run 360s before.

Book a demo