For privacy firms

Make the evidence chase repeatable.

If every client request starts with finding system owners, asking for exports and reconciling identifiers, the preparation can consume senior time. Trace is testing a technical preparation service that would document those steps and organise evidence for your firm’s review.

The partner thesis

Trace is testing whether a documented evidence path can reduce repeated preparation across a privacy firm’s client requests. The proposed service would record sources, owners, retrieval steps and gaps while the firm keeps advice and final judgement.

Senior time and preparation

When each missing export creates another follow-up.

A request can stall while a consultant locates the right client owner, reconciles an identifier or checks why an export is incomplete. If those steps repeat across client matters, the evidence chase may consume time the firm needs for advice and review.

The proposed Trace service would record each agreed source, owner, retrieval step and limitation. The intended result is a case with visible evidence and open questions for the authorised privacy professional to review. Time savings and delivery capacity remain unproven.

Repeatable preparation

Find, record, structure and expose.

System maps, identifier assumptions, retrieval coordination, source inventories, evidence manifests and exception notes.

Professional judgement

Interpret, decide, advise and approve.

Identity sufficiency, scope, disclosure, redaction, exemptions, retention, erasure, legal advice and final response wording.

Proposed division of work

Trace prepares. Authorised privacy professionals decide.

The boundary is part of the model being tested. Exact roles, instructions and liabilities would need to be agreed for each paid engagement.

Proposed operating role

Trace is being designed to prepare

  • Intake and case structure
  • Source maps
  • Approved retrieval coordination
  • Source inventories
  • Evidence organisation
  • Draft response structure
  • Exception notes
  • Timestamped activity records
  • Closure evidence

Decision boundary

The partner retains

  • Identity sufficiency decisions
  • Interpretation of the request
  • Disclosure and redaction decisions
  • Retention and exemption decisions
  • Erasure or correction authorisation
  • Legal advice
  • Final response approval
  • The client and requester relationship

One-client starting point

Test the workflow on synthetic data first.

The proposed Readiness Sprint would map up to three systems for one suitable client workflow and rehearse one fictional request. Its three intended outputs are a source map, a synthetic evidence pack and a prioritised list of gaps.

  1. 01

    Choose one suitable client workflow

    Start with a structured environment, a named decision owner and up to three agreed systems.

  2. 02

    Map the evidence path

    Record identifiers, source owners, retrieval paths, limitations and the points where judgement is required.

  3. 03

    Rehearse a synthetic request

    Test the operating sequence without using live request data or making a production-access claim.

  4. 04

    Review the case pack together

    Inspect the fictional evidence manifest, exception notes, decision boundary and gaps before discussing coverage.

Target under validation: €2,500. Final scope, capacity, terms and data handling must be confirmed in writing.

Explore the Readiness Sprint

Compounding preparation

The next request should not start from zero.

A maintained source map can preserve what the team learned:

Systems
Which agreed sources may contain relevant records
Identifiers
How the same person is matched across those sources
Owners
Who can produce or approve each retrieval path
Limits
Where coverage ends or manual intervention remains
Decisions
Which questions must return to the authorised professional

Coverage and source-map maintenance are planned. They are not generally available today.

Operational boundary

What Trace will not do.

Replace your firm as external DPO

Provide autonomous legal decisions

Contact your client commercially without agreement

Accept request files through this website

Claim one-click connectors that do not exist

Promise production work before scope and capacity exist

Initial partner profile

Designed around a focused first environment.

The working hypothesis is a privacy firm with approximately 3–20 professionals, multiple retainer clients, recurring rights-request work and senior capacity constrained by retrieval and administration.

A suitable first client workflow

  • Structured customer data
  • Approximately three primary systems
  • Stable identifiers such as email or user ID
  • A named privacy decision owner
  • No active employee dispute or litigation
  • Willingness to rehearse with synthetic data

Partner principles under validation

The relationship should be legible before the technology.

These are intended design principles, not contractual guarantees. A real engagement would require written terms.

01

Client relationship

The partner retains the client relationship.

02

Professional judgement

The partner retains legal judgement and final approval.

03

Role clarity

Trace does not present itself as the client’s external DPO.

04

Data use

Trace does not use client data for model training.

05

Access

Source access must be scoped and revocable.

06

Non-circumvention

No direct commercial approach to a partner’s client without agreement.

07

Portability

Export and exit must remain possible.

08

Evidence

The partner can review the full evidence trail.

Expected commercial model

Start with evidence. Discuss coverage after.

01
Open for design-partner discussions

Readiness Sprint

Target €2,500 one-time

Map up to three systems and rehearse one synthetic request.

Explore the Readiness Sprint
02
Planned

Privacy Operations Coverage

Expected from €750 per month

Maintained source map, monitored readiness, periodic tests and reserved operational capacity.

03
Planned

Standard request preparation

Expected €750 per standard request

A mapped, structured request prepared for authorised review within an agreed scope.

These prices are being tested. They are not a checkout, binding offer or promise of production availability.

One useful first step

Bring one suitable client workflow

Start with a conversation about one suitable client workflow. If the fit is clear, we can discuss a proposed €2,500 Readiness Sprint using synthetic data. Scope, terms and capacity must be agreed before paid work. Do not send client or requester data.