For DPCOs · NDPC audit return

Evidence support for DPCOs in audit return season

Under the NDPC's framework, the annual Compliance Audit Return is filed through a licensed Data Protection Compliance Organisation (DPCO). This page is for DPCOs. It explains the one part of that work StackWeaver can support: dated, tamper-evident evidence of technical controls, taken from your client's own systems. Your judgement, the privacy documentation and the filing stay with you. For who files and when, read our audit return guide.

Last reviewed: 15 November 2026 · Written by StackWeaver. This is not legal advice, an audit opinion or a finding about any company's regulatory status.

What your client gets from StackWeaver

  • Daily read-only checks. Once a day, and on demand, StackWeaver reads settings from systems your client connects. 23 connectors are live in production, including GitHub, Okta, Microsoft Entra ID, Amazon Web Services and Google Workspace. All are read-only. See every connector.
  • Evidence that can be checked later. Each result is kept as an Evidence Object with a SHA-256 fingerprint, including results that fail. Anyone holding an evidence file can confirm it matches the record on the verify page, and nothing is uploaded to do so.
  • A decision trail. Reviews and sign-offs are written to a chained decision record, so you can show who accepted what, and when.

What stays with the DPCO

StackWeaver does not file audit returns, give legal advice, or give a verdict on a client's regulatory status. It does not issue certifications, audit opinions or regulator approvals. Mapping evidence to NDPA obligations, privacy documents (policies, records of processing, impact assessments), your assessment of the client and the return itself remain yours. Control mappings in StackWeaver are drafts until a named reviewer signs them off.

What is not available yet

  • Connectors differ in depth. Each connector page says exactly what it reads. The Youverify, Smile ID and Prembly connectors today only confirm that a key works. They do not yet evidence real identity verifications.
  • StackWeaver does not ask clients to upload their documents to the platform until its independent penetration test is complete. The test is planned and its date is not fixed. Until then, document evidence is handled in live sessions and from the client's own stores.
  • StackWeaver does not publish a standard time to readiness. Timelines depend on scope and are set in a Statement of Work.

How a DPCO can work with us

  1. See how it works for a partner: request a partner demonstration. Partner types are on the partners page.
  2. Offer a client a fixed-scope start with the Evidence Readiness Assessment, which lists the gaps, the evidence that would close each one, and an owner for each.
  3. Look at what evidence looks like before you commit, in the evidence library.

Frequently asked questions

Is StackWeaver a DPCO or a competitor to DPCOs?

No. StackWeaver prepares technical evidence from a client's systems. It does not file audit returns or act as a DPCO. A DPCO decides what to include in a client's return.

Do you give DPCOs access to a client's data?

Clients connect their own systems with read-only access and choose what to connect. StackWeaver stores results such as counts and settings, and the Okta connector stores counts and opaque ids, not names, logins or e-mail addresses. See the connector pages for what each one reads.

Can a DPCO use StackWeaver for several clients?

Yes. Partners manage a portfolio of their own clients' engagements: evidence requests, submissions, reviews and a traceable record. This is live today. Scoped client participation is on our build list and is not live yet. By default a partner does not see a referred company's evidence or security posture without that company's agreement. Request a partner demonstration to see it.

Will StackWeaver evidence be accepted by the NDPC?

We cannot say. Only the NDPC decides what it accepts. StackWeaver evidence shows what a system's settings were at a point in time, and your DPCO decides how to use it.