The over 400 member self-regulating industry body ratified a series of updates to their code of conduct to clarify requirements addressing securing their platforms against fraudulent attacks and the new steps required by the networks to protect consumers against unauthorised activity on their mobile devices.
“Waspa continually refines the code according to which all members are expected to conduct their business. The potential threat posed by malware is a growing one and one that needed to be addressed,” says Ilonka Badenhorst, general manager at Waspa.
Version 15.9 of the Waspa code of conduct was adopted by the Industry Representative Body's Management Committee (Mancom) following the recent Waspa general meeting held in May.
The Waspa code of conduct has been continuously revised since May 2014 to reflect new challenges within the wireless application service provider (WASP) industry that provides South Africa's cellular users with mobile content and applications. "Waspa's world-leading code of conduct sets the standard for responsible self-regulation," adds Badenhorst.
Waspa first introduced a code of conduct to regulate the then emerging mobile content and applications industry in 2004. From a collection of like-minded firms wanting to offer increased protection to the local mobile consumer in line with developments globally, the sector is today an important and responsible contributor to South Africa's vibrant cellular industry.
The code of conduct contains provisions relating to how mobile content and services may be advertised.
According to Waspa, the code is aligned with the Electronic Communications and Transactions Act (ECTA), the Consumer Protection Act (CPA) and the Protection of Personal Information Act (POPI).
This means that members who align their activities with the Waspa code are in full compliance with the applicable legislation, and now also with regulations recommended by international counterparts.
A PDF version of the code showing the changes from the previous version is available for download via the code archive page. A copy of the revised code can be found here.
