If your website has a contact form, a WhatsApp button, an online checkout or an AI chatbot, it handles personal data. That matters because key parts of the Personal Data Protection Act start on 1 January 2027, and PDPA Sri Lanka readiness is no longer something to leave for “later”. This guide explains the PDPA Sri Lanka dates in plain English and gives you a practical website and AI-tool checklist.
We build websites, not legal opinions. Treat this as a starting point for your own review, and ask a lawyer about your specific situation.
PDPA Sri Lanka: what changes on 1 January 2027
The Personal Data Protection Act, No. 9 of 2022 (PDPA) was passed in 2022, but its provisions are being switched on in stages. In Extraordinary Gazette No. 2498/16, dated 22 July 2026, the President appointed 1 January 2027 as the date when Section 2, Section 3, Part I (processing of personal data) and Part III (controllers and processors) come into operation. You can read the official gazette on the Data Protection Authority site.
In short, the PDPA Sri Lanka rules about how you collect, use, store and protect personal data, and the duties of the businesses and suppliers that handle it, begin on that date. The order names only those provisions, so check the Authority’s site for any later orders covering the rest of the Act.
Does PDPA Sri Lanka apply to a small business?
Section 2 of the Act focuses on where and by whom personal data is processed, not on how big the business is. It covers processing that takes place wholly or partly in Sri Lanka, and processing by controllers or processors that are based in Sri Lanka or that offer goods or services to people here. You can read the wording in the Act published by the Data Protection Authority.
So a Kurunegala boutique with an online order form should assume PDPA Sri Lanka is relevant. A “controller” is the business that decides why and how the data is used. A “processor” handles it on the controller’s behalf, such as a hosting or email-marketing provider.
What counts as personal data on a normal business website
The Act defines personal data as any information that can identify a person directly or indirectly. Its examples include a name, an identification number, financial data, location data and an online identifier.
On a typical small business website, that can include:
- names, phone numbers and email addresses typed into a contact or quote form
- delivery addresses and order details from an online shop
- newsletter sign-ups
- messages sent through a live chat or AI chatbot
- account logins for customers or students
Even a “simple” brochure site often collects some of this. List every place on your site where a visitor can type something in.
Seven website checks for PDPA Sri Lanka readiness
These PDPA Sri Lanka checks follow duties in Part I of the Act. They are practical habits, not a guarantee of compliance.
- Know what you collect. Write down each form, plugin and chat tool, and what data it receives.
- Ask only for what you need. The Act says data must be adequate, relevant and proportionate to its purpose (Section 7). If a quote form works without a NIC number or home address, remove those fields.
- Explain it in plain words. Section 11 requires controllers to give people specific information, set out in Schedule V, in a concise and easily accessible form. A privacy page that describes what your business really does is better than a copied template. See how we explain it on our own BK DevOps privacy policy.
- Protect it. Section 10 refers to appropriate technical and organisational measures such as encryption and access controls. For a WordPress site, that means updates, strong passwords, two-factor login and tested backups. Our WordPress maintenance checklist and guide to 2FA cover the basics.
- Do not keep data forever. Section 9 says identifiable data should be kept only as long as the purpose needs. Decide how long you keep old enquiries, then delete them.
- Know your suppliers. Where a processor handles data for you, Section 21 expects a contract covering the subject, duration, nature and purpose of the processing. Make a list of your hosting company, email service, payment provider and plugin vendors.
- Plan for a breach. Section 23 says a controller must notify the Authority of a personal data breach in the form, manner and time set by rules. Decide now who in your team spots a problem and who acts. Our guide to the signs of a hacked WordPress site is a good first read.
WordPress also includes built-in tools to export and erase a user’s personal data, which can make handling requests easier.
Using AI tools without a PDPA Sri Lanka headache
AI tools are useful, but they create new places for personal data to go. Three simple rules help.
First, do not paste customer details into a public AI tool. That includes names, phone numbers, addresses, NIC numbers, bank details and private chat screenshots. Use invented examples when you ask for a draft reply or a sales email. Our guide to free AI tools for Sri Lankan SMEs includes PDPA privacy tips for everyday prompts.
Second, treat a website chatbot as a supplier. Visitors may type personal details into it, so the chatbot company may be handling data for you. Read its terms, find out where messages are stored, and tell visitors what the chatbot does. Our article on whether your website needs an AI chatbot compares the options.
Third, be careful with anything that profiles people. Section 24 requires a data protection impact assessment before processing that involves a systematic and extensive evaluation of personal data, including profiling. A one-off caption draft is unlikely to fit that description, but an AI system that scores or tracks customers might, so check the wording of the Act.
What is still being decided
Some PDPA Sri Lanka details depend on rules the Authority has still to finalise. The Act leaves the scale at which a Data Protection Officer is required to be “prescribed”, and breach notification timing is set by rules too. The Authority’s guidelines page lists the Act, its amendment, gazettes and draft guidance for consultation. Check it before you finalise your policies, because it may change.
A simple 30-day PDPA Sri Lanka plan
- Week 1: List every form, plugin, chat tool and supplier that touches personal data.
- Week 2: Remove unnecessary form fields and update your privacy page.
- Week 3: Update WordPress, themes and plugins. Turn on two-factor login and check your backups.
- Week 4: Write a one-page breach plan and a simple rule for using AI tools.
None of this requires a big budget. It does require someone to own the job, so name that person.
Need a hand with your website?
If you would like a second pair of eyes, BK DevOps can review your forms, plugins, hosting and WordPress security from the website side. Start with our free website audit or contact the team in Kurunegala. We will not give legal advice, but we can help with the technical side of PDPA Sri Lanka readiness.
