Find, record, structure and expose.
System maps, identifier assumptions, retrieval coordination, source inventories, evidence manifests and exception notes.
For privacy firms
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
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.
System maps, identifier assumptions, retrieval coordination, source inventories, evidence manifests and exception notes.
Identity sufficiency, scope, disclosure, redaction, exemptions, retention, erasure, legal advice and final response wording.
Proposed division of work
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
Decision boundary
One-client starting point
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.
Start with a structured environment, a named decision owner and up to three agreed systems.
Record identifiers, source owners, retrieval paths, limitations and the points where judgement is required.
Test the operating sequence without using live request data or making a production-access claim.
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 SprintCompounding preparation
A maintained source map can preserve what the team learned:
Coverage and source-map maintenance are planned. They are not generally available today.
Operational boundary
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
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.
Partner principles under validation
These are intended design principles, not contractual guarantees. A real engagement would require written terms.
The partner retains the client relationship.
The partner retains legal judgement and final approval.
Trace does not present itself as the client’s external DPO.
Trace does not use client data for model training.
Source access must be scoped and revocable.
No direct commercial approach to a partner’s client without agreement.
Export and exit must remain possible.
The partner can review the full evidence trail.
Expected commercial model
Map up to three systems and rehearse one synthetic request.
Maintained source map, monitored readiness, periodic tests and reserved operational capacity.
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
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.