Fractional DPO and privacy programme

Privacy stops being a series of projects when someone senior owns it continuously. Most organizations reach that point before they can justify a full-time privacy lead, and spend the years between with privacy owned by whoever last had time.

The short version: a named privacy owner on a cadence

A fractional DPO is a named senior privacy lead who works for your organization on a defined cadence, owning the privacy programme without being a full-time hire. It is the privacy counterpart of the vCISO and security programme, and the two are often run together so that privacy findings and technical controls are decided in one conversation.

The value is continuity: a person who was in the last conversation, knows why a decision was taken, and is in the next one. One-off assessments cannot produce that.

What you get

A data map and records of processing

Built first, because everything else depends on it. See data mapping and records of processing.

A request routine that runs

Intake, identity checks, deadlines and a log, set up so requests are answered on time whoever is away. See data-subject request operations.

Impact assessments and vendor review

Assessments before launch rather than after, through privacy impact assessments, and a standing review of processors through the privacy risk register and vendor management.

Reporting management can act on

What changed since last time, the top privacy risks and who owns each, what is not being funded and what that means.

What the role runs

Four standing responsibilities sit under the named owner.

What a fractional DPO runs Four responsibilities, top to bottom: the data map and records of processing, the request routine, impact assessments and vendor review, and reporting to management. Data map and records The base for everything else. Request routine Intake, identity, deadlines, log. Assessments and vendors Before launch, and standing. Reporting What changed, top risks, owners.
The same four items are described under what you get above.

How the work runs

The programme is built in an order that each step depends on: map what is processed, rank the gaps against the laws that apply to you, put a named owner and a review date on each, then run the standing cadence of requests, assessments, vendor review and reporting.

How a privacy programme is built Four steps in order: map what is processed, rank the gaps, put an owner on each, then run the standing cadence of requests, assessments, vendor review and reporting. 1 Map what is processed Data map and records of processing. 2 Rank the gaps Against the laws that apply to you. 3 Put an owner on each A named person and a review date. 4 Run the cadence Requests, assessments, vendors, reporting.
Mapping comes first because ranking and ownership cannot be done without it.

Engagements run on a fixed cadence for a fixed term, with a written statement of what is included and how additional project work is handled. The scope names deliverables rather than describing availability, and it is quoted in writing before the engagement starts.

Who it is for

Organizations that process personal data under one or more privacy laws and have no full-time privacy lead: growing software companies, health and education providers, groups with operations in several countries, and organizations preparing for a customer or regulator question. Yes. The role is not tied to one country, and privacy-law specialists, including for the EU and UK GDPR, join the engagements that need them.

What the role is, and is not

Accountability for privacy compliance stays with the organization and its officers; the role supplies the judgement, the routines and the reporting. Where a law requires a data protection officer, the role is a formal designation with duties and independence, and whether you must designate one is a question for your counsel. For reference, the GDPR text is on EUR-Lex: The GDPR allows the data protection officer to fulfil the tasks on the basis of a service contract, so an outside appointment is permitted in principle.

Where a law requires a formal designation, the engagement scope records exactly what the designation does and does not cover, and the decision to designate sits with you and your counsel.

Under US law

In the United States, particular rules name a responsible role: for example, the FTC Safeguards Rule requires a designated qualified individual to oversee the security programme (16 CFR 314.4(a)). A fractional lead can sit alongside that person or in the privacy half of the work; the financial-sector page covers the security half.

Under EU law

The GDPR requires a data protection officer for public bodies and for controllers and processors whose core activities are large-scale regular and systematic monitoring, or large-scale processing of special categories of data (Article 37(1)). The officer is chosen on professional qualities and expert knowledge of data protection law and practice, and may be a staff member or work under a service contract (Article 37(5) and (6)); other tasks the officer holds must not create a conflict of interests (Article 38(6)). Whether an outside provider can be your designated officer, and how a conflict would be judged, are questions for your counsel. We build the programme the officer works from, and we do not act as an organization’s representative in the Union under Article 27. The wider picture is on the GDPR programme page.

How the work is bounded

The scope is agreed in writing before work starts, and the engagement is quoted in writing with it.

SecHB does not issue certifications, attestations or audit opinions: those come from accredited certification bodies, CPA firms and QSAs. The work here is what an organization does to be ready for them.

Nothing here is legal advice. Where a question turns on the law, the work is done alongside the client’s counsel, not instead of them.

Questions we are asked

What is a fractional DPO?

A fractional DPO is a named senior privacy lead who works for your organization on a defined cadence, owning the privacy programme without being a full-time hire.

Is a fractional DPO the same as the formal data protection officer?

Where a law requires a data protection officer, the role is a formal designation with duties and independence, and whether you must designate one is a question for your counsel.

Can the data protection officer be an outside provider?

The GDPR allows the data protection officer to fulfil the tasks on the basis of a service contract, so an outside appointment is permitted in principle.

Who is accountable for privacy compliance?

Accountability for privacy compliance stays with the organization and its officers; the role supplies the judgement, the routines and the reporting.

Do you work outside Canada?

Yes. The role is not tied to one country, and privacy-law specialists, including for the EU and UK GDPR, join the engagements that need them.

Give privacy a named owner and a cadence

Background reading: what a fractional DPO does in the first 90 days. Describe the organization, where it operates and who owns privacy today. The reply says what a cadence would look like. See also all privacy services.

Discuss a scope