Subscriptions · DPO
Privacy360™ · Named role · Quarterly
Subscription·Detail + book a call

DPO as-a-service.

Privacy law made the Data Protection Officer a standing role, not a project — a named person, reachable by regulators and data subjects, keeping the record of processing honest. This subscription runs that role: a rebuild of your privacy baseline, then a permanent rhythm in Privacy360™.

Privacy360™ · Signify Hive· GDPR · Saudi PDPL · US state law aligned· Named role · published rhythm
What actually breaks

The role is assigned. The capacity is not.

The data protection officer role gets given to someone who already has a full job — a general counsel, a head of compliance, occasionally an IT manager. They accept it because somebody must, and they carry the accountability personally, in some jurisdictions with their name on a filing.

What they do not get is time. So the register drifts, subject requests are handled heroically rather than systematically, and the first genuine breach becomes the moment everyone discovers the role existed on an org chart and nowhere else.

The comparison

Bought as a project. Delivered as a product.

Neither column is a caricature. The left is how this work is bought almost everywhere, including by people who dislike it.

How this is normally bought
A named individual with no capacity behind the name
Advice by email, retrievable only by searching an inbox
A register updated when somebody remembers
The same firm advising and assuring
How it works here
A named role with a printed rhythm — the work happens on a calendar, not on goodwill
Decisions recorded where the evidence lives, in Privacy360
Kept current as part of the quarterly loop, with what is unevidenced named
Hard stop, published — while we hold the role we cannot audit the framework
The schedule

Onboarding, then a standing rhythm.

The shape is the same as every subscription here: a bounded start, then a loop that does not stop.

Onboarding
The role stood up

Processing inventory verified, obligations mapped, escalation path and response clocks agreed.

Partner gate
Continuous
The role, held

Subject requests, breach triage, vendor and transfer reviews — on defined response windows.

Every quarter
Refresh and readout

What changed in the regulatory landscape, what it now obliges, what is unevidenced.

Partner gate
On exit
Handover

The register, the decisions and the evidence trail leave with you, in full.

Why it repeats

A role, with a rhythm behind it.

The price for this one is not published yet, because its box is not printed yet — and this site publishes a price only when the box that earns it is final.

1
named role, with capacity behind it
4
readouts a year
0
prices published until the box is printed
1
hard stop — we cannot also audit it

Methodology 2026.2 — bumps when a box, a gate or a testing standard changes — never for a copy edit. Read it at working depth on the method page.

The shape of the box

A rebuild, then a standing role.

Final scope quantities are in calibration — the shape below is what the box holds. Full pricing publishes the day the box locks.

Normalization · ~5 weeksFixed fee
  • 01Privacy baseline — where the program actually stands
  • 02Record of processing rebuilt in Privacy360™
  • 03Obligations map — the laws that bind you, and to what
  • 04DPIA backlog triaged — what needed assessing and never was
  • 05DPO of record appointed — named, notified where required
The artefact: a living privacy programNot a binder
The standing rhythmQuarterly
  • 01Named DPO of record — regulator & data-subject contact point
  • 02RoPA kept current in Privacy360™ — changes captured as they happen
  • 03DPIA gate — new processing assessed before it ships
  • 04One quarterly privacy pack + readout for leadership
  • 05Breach-window availability — the clock-driven hours, covered
  • 06Scope-change log — remediation programs are Solution work, quoted as such
The role the law made permanentRun as a subscription

Subscriptions · DPO

Why this one opens with a conversation.

A DPO appointment is a regulatory exposure, not a subscription checkout — jurisdiction, sector and supervisory relationships genuinely change the box. We publish the full price and self-serve configurator when the scope quantities are locked; until then, the honest first step is thirty minutes with the people who’d hold the role.

The pattern and its economics mirror the pattern: one fixed-fee rebuild, one recurring price, renewal without a second rebuild. Nothing about this subscription is “contact us” coyness — it’s sequencing.

Subscriptions · DPO

What buying this forecloses.

While we hold your outsourced DPO role, we cannot audit your privacy framework — we would be auditing our own privacy operation. That is a hard stop, not a preference, and it is the sharpest example of a boundary we publish everywhere on this site.

If your Audit Committee wants independent assurance over privacy, either that opinion comes from someone else or the DPO role does. You choose which, we print the consequence before you buy, and where an Audit Committee relationship already exists we protect it.

The next step

Thirty minutes with the people who’d hold the role.

Bring your jurisdiction map and your current RoPA state — or bring neither, and we’ll start from where you actually are.

Book a call See the risk register instead