Gauteng e-Panic Button Alleged Data Breach: What to Ask

What has been reported about the Gauteng e-Panic Button data exposure, what is disputed, and eight questions to ask any panic button provider.

By The PanicGrid team6 min read
PanicGrid header graphic with the title Gauteng e-Panic Button Alleged Data Breach: What to Ask, beside a red alert dot with blue ripples

Quick answer: In September 2026, GroundUp reported that the database behind the Gauteng e-Panic Button was not secured and exposed user details, crime reports and location histories. The Gauteng government says no personal information was compromised. That is disputed, and an independent investigation has been demanded. Whatever the final findings, the story gives security companies, estates and trustees a clear list of questions to ask any panic button provider.

This article summarises what has been publicly reported, says who made each claim, and separates what is disputed from what is not. It is not legal advice, and the story is still developing. It reflects reports available on 6 November 2026.

What has been reported about the e-Panic Button

The Gauteng e-Panic Button is a provincial government app for reporting crime and calling for help. The department cites 288,307 active users.

On 23 September 2026, the investigative outlet GroundUp published its findings. It reported that the database used by the app was not secured, and that its records could be reached by anyone who analysed the app and the services it connects to. GroundUp said it broke no laws and did no hacking.

According to GroundUp, the exposed information included:

  • Names, gender, age, phone numbers, email addresses and vehicle registration numbers
  • Crime reports, including reports of domestic violence and assault, some naming alleged perpetrators
  • Photographs uploaded with crime reports
  • GPS coordinates, and location histories dating back to the app's 2024 launch
  • One-time login PINs

GroundUp says it alerted the department and the app's developer, Evolve Value Added Services, on 21 September. It reports that Evolve responded quickly and fixed the problems.

What the Gauteng government has said

On 29 September, the Gauteng Department of e-Government described the incident as an "attempted security breach". It said the vulnerability had been identified and corrected, that no citizens' personal information was compromised, and that it had asked for additional testing and verification.

GroundUp and others dispute that. The Gauteng Legislature's e-Government committee reportedly said it was deeply alarmed and would not accept assurances without evidence, and called for an independent investigation.

The Information Regulator and the notification question

On 30 September, the Information Regulator said it had not received a security compromise notification from the department under section 22 of the Protection of Personal Information Act (POPIA), and that it would engage the department. GroundUp later reported that the department notified the Regulator on 5 October. The DA has criticised the timing as a two-week delay.

GroundUp also reports that a police case was opened, and says it appears to target the researchers. The province has said opening a case after a security incident is standard procedure.

What is still unclear

From the reports we have seen:

  • Whether anyone other than the researchers accessed the data
  • How long the data was exposed
  • How many people were affected
  • Whether affected users have been told

At the time of writing, we had not found a published outcome of the independent investigation. If you quote this story, check the latest reports first.

Why this matters for every panic button service

A panic button app holds more sensitive information than most apps. It can know where a person is, where they have been, who they called for help and what happened to them. That is exactly the information that can put someone at risk if it reaches the wrong person.

This is not a reason to avoid panic buttons. It is a reason for security companies, estates, villages and trustees to ask better questions before they buy, and to keep asking after they have bought.

Eight questions to ask any panic button provider

  1. What personal information do you store, and why? Location history, photos and free-text notes deserve particular attention.
  2. How long do you keep it? Information you do not hold cannot be exposed.
  3. Has the system been independently security tested, and when? Ask for a summary, and ask what was fixed.
  4. How is access to the back end controlled? Who can see which client's data, and how is one client separated from another?
  5. What happens when someone reports a flaw to you? A clear, friendly route for reporting problems is a sign of a mature provider.
  6. What is your process if personal information is accessed without authorisation? Who tells the Information Regulator, who tells affected people, and how quickly?
  7. Do you keep access logs? Without them, nobody can say who accessed what, and when.
  8. Who is the responsible party, and who is the operator? Make sure a written agreement, such as an operator agreement, says who carries which duty.

What security companies and estates can do now

  • Put these questions to your current provider and ask for written answers.
  • Collect less. Only keep what your response procedure needs.
  • Write down your own plan for a security compromise: who is called first, who notifies the Regulator, and who tells residents.
  • Tell residents in plain language what is collected, who can see it and how long it is kept.
  • Make it easy for anyone to report a problem to you, and thank them when they do.

The exact duties depend on your role under POPIA, so take your own legal advice.

No provider can promise zero risk

No honest provider can promise that a system can never be breached, and we do not make that promise. A better test is how a provider prepares, tests, responds and communicates.

How PanicGrid fits

PanicGrid is white-label panic button software for security companies. You run it under your own brand, set each client up under your account and monitor alerts on a live console, working each one through to resolution. We welcome the questions above, and we will go through them with you in a demo: info@panicgrid.co.za or 061 939 0148. For a broader checklist, see our seven things to check before you choose panic button software.

Frequently asked questions

Was the Gauteng e-Panic Button hacked?

GroundUp says it analysed the app and did no hacking, and that the database was not secured. The department calls it an attempted security breach and says no personal information was compromised. Whether anyone else accessed the data has not been established in the reports we have seen.

Should I stop using panic button apps?

That is a question for each provider and each user. Follow the guidance of the Gauteng Department of e-Government and the Information Regulator on the e-Panic Button itself. For any other service, ask the questions above.

What is a section 22 notification under POPIA?

It is the duty to notify the Information Regulator and affected people when there are reasonable grounds to believe that personal information has been accessed or acquired by an unauthorised person. Whether it applies in a particular case depends on the facts.

Sources

  • How Gauteng's new panic app exposed your data, GroundUp: groundup.org.za
  • We found flaws in Gauteng's panic button app. The province set the cops on us, GroundUp: groundup.org.za
  • Gauteng e-Panic Button attempted security breach thwarted, SAnews: sanews.gov.za
  • Information Regulator to engage Gauteng over e-Panic Button data breach, Mail & Guardian: mg.co.za
  • E-Panic Button security flaw sparks legislature probe, ITWeb: itweb.co.za
  • Gauteng emergency app exposed users' private information, EWN: ewn.co.za
  • DA exposes two-week delay in reporting e-Panic data breach to Information Regulator, DA Gauteng: dagauteng.org.za

Keep reading