Lesotho Data Protection Act compliance and requirements, so your data handling holds up when someone asks.

What it is

What is Lesotho's Data Protection Act and what is it used for?

The Data Protection Act, 2011 (Act No. 5 of 2012) is Lesotho's personal data protection law. It sets principles for processing personal information: lawful grounds including explicit consent, minimality, collection directly from the data subject, specified purposes, limited retention and destruction in a way that prevents reconstruction. Controllers must secure the integrity of personal information, bind agents by written contract, notify the Commission and affected people of security compromises as soon as reasonably possible, notify the Commission of their processing, give access and correction rights and restrict sensitive information.

The Data Protection Commission, established by section 6 of the Act, has a chairperson and five other members appointed by the Prime Minister on the advice of the Minister. The practical test: for any personal data you hold, could you show its purpose and basis, who was told, how it is protected and where it goes?

Current law. Printed in the Lesotho Government Gazette, Vol. 57, No. 19, of 22 February 2012 as Act No. 5 of 2012 under the short title Data Protection Act, 2011; section 1 says the Act comes into operation on the date of its publication in the Gazette; the Central Bank of Lesotho lists it among the legislation it publishes. Confirm current wording and the authority's guidance with your legal advisers.

Who it is for

Who needs to comply with Lesotho's Data Protection Act?

The Act reaches organisations of every size that handle personal data in Lesotho. Organisations usually come to Sterling for a structured programme from one of four directions:

• Every organisation that processes personal information. Section 53 asks a controller to notify the Commission of its processing, and section 25 says a controller processes personal information only upon notification.
• Employers, schools, clinics and retailers. They hold staff, student, patient and customer records, including health and other sensitive information that section 29 restricts.
• Processors, payroll, hosting and software providers. Section 22 requires a written contract with security and confidentiality duties between a controller and its agent.
• Banks, insurers, lenders and credit providers. They hold large volumes of customer information and answer to the Central Bank, which publishes the Credit Reporting Act, 2011.

The aim is handling of personal information that you control and can evidence. Compliance depends on how the rules are applied every day, not on a policy document alone.

Requirements

What are the main Lesotho Data Protection Act requirements?

Strip away the vocabulary and Lesotho's Data Protection Act requires a business to do six things whenever it handles personal information. The list below puts each one in business terms; the Act and the regulator's guidance give the full wording and exceptions.

• Notify the Commission before you process: a controller tells the Data Protection Commission what it processes, why, for whom, where data may travel and how it is secured, and processes only after notification.
• Collect only what you need, lawfully: personal information needs a lawful ground such as explicit consent, must be adequate and not excessive, is collected from the person where possible, and is used only for stated purposes.
• Tell people, and honour their rights: people are told who collects their data and why, can ask what is held and have errors corrected or deleted, and can stop direct marketing.
• Secure records and destroy them properly: controllers identify risks, keep safeguards current, retain records no longer than allowed, and destroy or de-identify them so they cannot be reconstructed.
• Control agents and transfers abroad: anyone processing on your behalf works under a written contract with security duties, and data leaves Lesotho only where the recipient gives similar protection, or consent or necessity applies.
• Report security compromises promptly: if personal information may have been accessed by an unauthorised person, the controller tells the Commission and affected people as soon as reasonably possible, with enough detail to act.

Compliance route

How do you achieve Lesotho Data Protection Act compliance?

There is no certificate at the end of this route. Compliance is something your organisation demonstrates, to the Data Protection Commission if a complaint or incident arises, and to customers who ask. Sterling helps you build and run the programme; interpretation of the law in contested cases remains with your legal advisers and, ultimately, the regulator and the courts.

1. 01
   Map the personal information you handle.Customers, staff, users and suppliers: what is collected, for which purpose, on which basis, where it is stored, who processes it for you and whether it leaves Lesotho.
2. 02
   Gap analysis: compare current practice with the Act.Each area of the Act reviewed against what actually happens, with actions, owners and dates agreed.
3. 03
   Put the controls and routines in place.Complete the formalities the Act requires, rewrite notices and consent wording, put security measures and processor contracts in place, name who is responsible and agree a breach procedure.
4. 04
   Test the programme and review the results.Internal review of samples, a simulated incident or data-subject request, and a management review that closes findings with evidence.
5. 05
   Operate, demonstrate and keep it current.Answer requests, record incidents and report them as the Act requires, keep formalities current, review transfers, refresh training and follow the Data Protection Commission's guidance as it is issued.

Check the route before you sign. The Act creates no certificate of compliance, so treat any offer of a "Lesotho Data Protection Act certificate" with suspicion. If a customer wants independent assurance, ISO/IEC 27701 or ISO/IEC 27001 is certifiable by an accredited certification body; confirm the body's accreditation scope directly with the accreditation body concerned.

Cost

How much does Lesotho Data Protection Act compliance cost?

The cost of a Lesotho Data Protection Act programme is driven by how much personal information you hold, how many systems and suppliers touch it, and how much already works. Your proposal shows each component, with what is included and what remains for your legal advisers.

Timeline

How long does Lesotho Data Protection Act compliance take?

Timing depends on how scattered your personal information is, how quickly system owners respond and how much has to change. Your proposal sets out the phases for your scope, long enough to map the information, fix the gaps and show that requests and incidents are handled the way the procedures say.

If a customer or contract has set a date, tell us at the outset and we will say plainly what can be in place by then and what should follow.

Your engagement

What your Lesotho Data Protection Act engagement includes

Your scope covers the full programme, from the information map to evidence that runs. Sterling does not certify, attest or validate compliance with the Act, and the Act creates no certificate of compliance; the Data Protection Commission supervises it, and we work alongside your legal advisers.

• Information map, gap analysis and plan

  Sources, systems, suppliers and overseas flows, with actions and owners agreed.

• Policies, notices and procedures

  Notices, consent wording, request, security and breach procedures, processor contract terms and transfer documents, drafted from Sterling's own templates with your teams.

• Effivity ISO & GRC software

  Registers, requests and incidents managed in Effivity, included with the engagement at no additional cost.

• Training for everyone

  Internal auditor training for your review team, as applicable to your standard, and preferential Sterling Academy access, including complimentary awareness training for your people as part of the engagement.

• Internal review and management review

  Sample testing, an incident exercise and findings closed with evidence.

• Formalities support

  Help preparing the formalities the Act requires and the responsible person's role, with findings closed with evidence.

Sterling OS™ sets how we deliver. Design™ is guided support, where your team builds the programme with our consultants' direction; Drive™ is managed support, where our consultants do most of the work with your input. You choose one of the two, not both in sequence. Once the programme is operating, Sustain™ keeps reviews, training and updates on schedule, and Automate™ is Effivity, where the records live.

The Data Protection Commission, established by section 6 of the Act, has a chairperson and five other members appointed by the Prime Minister on the advice of the Minister.

Often combined with

Standards organisations pair with Data Protection Act (Lesotho)

• ADGM Data Protection Regulations 2021ADGM data protection compliance for entities under the 2021 Regulations: lawful bases, DPO, impact assessments, 72-hour breach notice and transfers, all-inclusive proposal.
• APEC CBPRAPEC CBPR certification and requirements explained: Global CBPR and PRP, Accountability Agent review, annual renewal and how Sterling prepares your team.
• APPI (Japan)APPI compliance for Japan's Act on the Protection of Personal Information: the requirements, PPC breach reporting, cross-border rules and an all-inclusive programme.
• Bahrain PDPLBahrain PDPL compliance and requirements explained: consent, notification to the Authority, transfers abroad, 72-hour breach reporting, rights, cost and timing.
• CCPA / CPRACCPA compliance and requirements under the CPRA: notices, consumer rights, opt-outs, risk assessments, cybersecurity audits and ADMT, in an all-inclusive programme.
• Cyber and Data Protection Act (Zimbabwe)Zimbabwe's Cyber and Data Protection Act [Chapter 12:07]: POTRAZ licensing, lawful processing, security and transfers, built into a programme.