Choose by the work you do. The CIPT is for people who build and engineer privacy into systems — data flows, encryption, de-identification, privacy by design. The CIPM is for people who run the privacy programme — policies, governance, vendor management, metrics, incident response. If your hands are on architecture and code, start with CIPT; if your hands are on the programme and the org, start with CIPM. Many privacy professionals eventually hold both, because together they cover "how it's built" and "how it's managed".
CIPT and CIPM are both IAPP certifications and both sit on the operational side of privacy — neither is a pure law exam. But they answer different questions, and picking the one that matches your actual role is what makes the credential useful on your CV rather than decorative.
Side by side
| Factor | CIPT | CIPM |
|---|---|---|
| Full name | Certified Information Privacy Technologist | Certified Information Privacy Manager |
| Core question | How is privacy built into systems? | How is a privacy programme run and improved? |
| Orientation | Technical — engineering, architecture, PETs | Managerial — governance, operations, lifecycle |
| Body of Knowledge | v4.0.0 (Sep 2025), five domains | v4.2.0, six domains |
| Format | 90 questions, 2.5 hours, scaled pass 300/500 | 90 questions, 2.5 hours, scaled pass 300/500 |
| Best for | Privacy engineers, architects, security, developers | Privacy managers, DPOs, programme leads |
What each actually tests
CIPT
The CIPT asks how you embed privacy into technology: the data lifecycle (collection, use, dissemination, destruction), privacy risk management, privacy by design, and privacy engineering and governance. Expect privacy-enhancing technologies — encryption, de-identification, k-anonymity, differential privacy — and architectural decisions. It rewards people who think in systems and data flows. See the CIPT exam guide.
CIPM
The CIPM asks what a privacy manager should do, and in what order, to build and sustain a programme: framing and scope, governance models, data assessment, protection, metrics and audits, and responding to requests and incidents. It rewards judgement — what to do first or best — over technical detail. See the CIPM exam guide and the privacy operations framework.
Tell them apart with a single question
The cleanest way to feel the difference is to see the same situation asked two ways:
CIPT framing: "An app collects location data it doesn't need for its core function. Which technical control best reduces privacy risk while preserving the feature?" → the answer is about technique: data minimisation in the data pipeline, on-device processing, truncating precision, or aggregation.
CIPM framing: "An app team wants to collect location data a product manager says isn't needed. What should the privacy manager do first?" → the answer is about programme judgement: assess the purpose and lawful basis, run or update the impact assessment, and decide proportionately — not which encryption to use.
Same raw situation, two different exams. If your instinct on reading it is "which control?", you'll feel at home in the CIPT. If it's "what's the right process and who decides?", that's CIPM territory. Most people lean clearly one way, and that lean is the best guide to which to take first.
Which to take first
| Start with CIPT if... | Start with CIPM if... |
|---|---|
| You're a privacy engineer, architect, developer or security professional | You run or are moving into privacy programme management |
| Your work is building privacy into products and data systems | Your work is policies, vendors, governance and operations |
| You want to prove hands-on technical privacy skill | You want to prove you can lead a privacy function |
Do you need both?
For many people, yes — eventually. The two are complementary rather than competing: CIPT proves you can build privacy in, CIPM proves you can govern it. A privacy engineer who moves toward leadership often adds CIPM; a privacy manager who wants technical credibility adds CIPT. If you're weighing a broader stack, the full IAPP stack and the AIGP for AI governance are the natural next considerations.
Frequently asked questions
Is CIPT or CIPM harder?
Neither is objectively harder — they suit different people. CIPT feels harder to non-technical candidates because of its engineering content; CIPM feels harder to pure technologists because of its management-judgement scenarios.
Can I take CIPT and CIPM together?
Yes. There are no prerequisites linking them, and they share an IAPP membership and overlapping CPE requirements, which makes holding both cheaper to maintain than two unrelated certifications.
Which looks better to employers?
Whichever matches the job. For an engineering or architecture role, CIPT signals the right skills; for a programme or DPO role, CIPM does. The strongest signal for a hybrid role is holding both.
Do CIPT and CIPM overlap?
They overlap on privacy by design and governance, but from different angles — CIPT from implementation, CIPM from programme management. The overlap is why holding one makes the other a little faster to earn.
Sources
Last reviewed: November 2026.