Blog

A Privacy Policy Is Not Enough: How to Build an Effective Data Privacy Management Programme

Learn why a privacy policy alone cannot ensure data privacy compliance and how expert ISO 27701 consultants helps businesses build an effective privacy management system.

Neha Dvivedi · 16 Ogos 2026

A privacy policy tells people how an organisation says it handles their data. It doesn’t show that anyone follows it. A data privacy management programme turns those promises into routines that can be checked.

Why isn’t a privacy policy enough?

Almost every business has a privacy policy on its website. It says what personal information is collected, why, how it’s used and, in some cases, how people can use their rights. Publishing it is the easy part.

Take a company that promises to keep personal information only as long as necessary. Does anyone review stored records and delete what’s no longer needed? Could the team say which departments, systems and outside providers can reach that data? If those questions get blank looks, the company has a policy but no programme.

What closes the gap is rarely exciting: named owners, written procedures, staff who know their part, and regular checks.

What’s the difference between a policy and a privacy management programme?

A policy states an approach. A programme, or Privacy Information Management System (PIMS), makes it happen. A policy may say customer data is protected from unauthorised access. A working programme says who can open the records, who approves that access, how often it’s reviewed and what happens when something goes wrong.

In practice, a programme starts with a data inventory: what personal information the organisation holds, why, where it’s kept and who can reach it. Records of processing follow where the law asks for them. Then come procedures for requests to access, correct or delete data. A check on vendors that handle data on the organisation’s behalf follows, along with a retention schedule that ends in secure disposal.

Staff need training on what they may collect, share and store. Last, an incident process covers how a suspected breach is spotted, reported and investigated. Together these give a business something it can show and review.

Where does ISO/IEC 27701 fit?

ISO/IEC 27701:2025 gives requirements and guidance for establishing, implementing, maintaining and continually improving a PIMS. It’s written for organisations that act as controllers or processors of personally identifiable information (PII).

Source: https://www.iso.org/standard/85819.html 

It covers setting privacy policies, objectives and responsibilities, and assessing the privacy risks in processing. It also covers managing controller and processor obligations, controls for how personal information is collected, used, stored and shared, monitoring, fixing nonconformities and regular review.

The 2025 edition stands on its own. A company can implement it alone or fold it into an existing ISO/IEC 27001 system. One caution: certification doesn’t guarantee compliance with every privacy law. The business still has to find and meet the laws that apply to it.

What do the DPDP Act and GDPR add?

Privacy duties depend on where an organisation operates, whose data it handles and which laws apply.

In India, the Digital Personal Data Protection Act, 2023 sets the framework for digital personal data. The DPDP Rules, 2025 were notified in November 2025 and start in stages. Provisions on the Data Protection Board began at once, consent manager provisions follow a year after notification, and the main duties for businesses apply from May 2027. These include notice, security safeguards, breach reporting and data retention. Check that schedule against your own role.

For businesses handling data in the European Union, the General Data Protection Regulation (GDPR) covers lawful processing, transparency, individual rights, security and accountability. Article 30 requires some organisations to keep records of processing. Article 33 says a qualifying breach should go to the supervisory authority without undue delay and, where feasible, within 72 hours, unless it’s unlikely to put people’s rights at risk.

Source: https://eur-lex.europa.eu/eli/reg/2016/679/oj 

Source: https://www.meity.gov.in/ 

A PIMS helps an organisation arrange its duties and keep evidence. It doesn’t replace legal compliance, so build it around the laws that actually apply.

How can a business start?

It doesn’t need complicated paperwork on day one. Start by understanding how personal information moves through the organisation, then add controls step by step.

1. Review current practice. List the personal information collected from customers, employees and suppliers, why it’s collected, where it’s stored and who can access it.

2. Find the gaps. Compare existing policies and controls with the laws that apply and with ISO/IEC 27701. Note what’s missing.

3. Assign owners. Decide who runs privacy activities, approves processing, handles individual requests and coordinates incident reports.

4. Write practical procedures for access, retention, deletion, vendors, requests and breaches. They should describe what the business actually does.

5. Train by role. People who handle customer records, HR data or sensitive business information need to know the risks of their job.

6. Check and improve. Run internal reviews, test controls and update procedures when operations or laws change.

How can MSCi help with ISO 27701?

A reliable programme takes more than documents. The organisation has to understand its data processing, spot its privacy risks and set up controls that work in daily operations. We help businesses assess their current practice and prepare for ISO/IEC 27701. With more than 40 years of consultancy experience, we support gap assessments and implementation planning, privacy documentation and procedures, risk and control gap identification, staff awareness and internal audit preparation.

MSCi doesn’t issue ISO certificates. Organisations seeking certification need an independent assessment by an accredited certification body. To talk through your ISO/IEC 27701 plans, contact MSCi.

Frequently Asked Questions

Is a privacy policy enough for data privacy compliance?

No. A policy states what an organisation says it will do with personal information. Compliance means someone is responsible for doing it, procedures exist, controls work, and there’s a record to show people follow them.

What’s the difference between a privacy policy and a PIMS?

The policy is what customers and staff read. A PIMS, or privacy information management system, sits behind it. It covers how risks are assessed, who owns what, which controls apply and how the whole thing gets reviewed and improved.

How does ISO/IEC 27701 help businesses?

It gives a business a clear structure for building and running a PIMS. Handling personal data, assessing privacy risk, assigning responsibility and choosing controls all have a defined place, so teams aren’t working it out from scratch.

Does the DPDP Act apply to small businesses and startups?

Size alone doesn’t settle it. What matters is whether the business processes digital personal data and what role it plays in that processing. A small firm should check its own obligations rather than assume it’s exempt.

Can a company implement ISO/IEC 27701 without ISO/IEC 27001?

Yes. The 2025 edition works as a standalone management system standard. Companies that already run ISO/IEC 27001 often combine the two to avoid duplicating audits and records.

Why work with ISO 27701 consultants?

They review current practice, find the gaps, help write the documents and set up the controls, then prepare the team for internal and external assessments. They also spot problems that people close to the work have stopped noticing.

Does ISO/IEC 27701 certification guarantee GDPR or DPDP Act compliance?

No. A certificate shows the system conforms to the standard within the scope assessed. 

What this covers

See how this looks as a working system

Reading about a requirement and seeing the documentation that satisfies it are different things. In a short demo we open the actual manual, procedures and records set for ISO/IEC 27701, show you how each clause is answered and where your existing way of working already fits. You will know what implementation involves before you commit to it.

Ask us about this

Tell us what is being asked of you and by whom.

What are you looking for?

We reply within one working day. Your details stay with our consultants.

More reading

All articles