For outsourced DPO and privacy firms · Pre-launch

Still chasing evidence across your clients’ systems?

Trace is developing a technical operations service for privacy firms whose consultants chase system owners, exports and missing records. The proposed service would organise that evidence for review while your firm keeps the client relationship and legal judgement.

No production access. Do not send request details, identities, exports or credentials through this website.

Prototype interface · Sample data
Case TR-0241 · Illustrative case

Access request · Synthetic rehearsal

Prepared for authorised review
01
Intake
02
Sources
03
Evidence
04
Review boundary
Sources in scope
PGPostgresMapped
STStripeMapped
INIntercomMapped
Latest events

Evidence manifest prepared

Retention exception recorded

Source inventory completed

Synthetic intake recorded

Evidence manifest
Case summaryPDF
Source inventoryCSV
Exception notes1 open
Activity recordJSON
Review boundary
ARAuthorised reviewerDecision remains with customer

One retention exception remains visible. Disclosure, redaction, erasure and final wording require an authorised decision.

Illustrative workflow · Synthetic data

The evidence chase

When evidence chasing consumes senior consultant time.

If a request starts with finding client system owners, matching identifiers and following up on incomplete exports, preparation can consume senior time before a case is ready for review. Trace is testing whether a documented evidence path can make that recurring work easier to repeat.

01

Find

Work out where the person appears across the client’s systems.

02

Structure

Record what was searched, what was found and what remains uncertain.

03

Prepare

Turn fragmented evidence into one case an authorised professional can decide.

The proposed workflow

From incoming request to a review-ready case.

The workflow ends at a visible decision boundary. Disclosure, redaction, retention, erasure and final wording remain with an authorised privacy professional and the controller.

  1. 01

    Intake recorded

  2. 02

    Scope and identity state confirmed

  3. 03

    Approved sources searched

  4. 04

    Evidence organised by source

  5. 05

    Exceptions made visible

  6. 06

    Case prepared for authorised review

See how the boundary works

Clear ownership

Trace prepares. Authorised privacy professionals decide.

This is the proposed operating boundary under validation. It is not yet a responsibility structure contractually operational for all customers.

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 authorised privacy professional 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

Proposed Readiness Sprint

Know where the next request would get stuck.

For one client workflow, the proposed Readiness Sprint would map up to three agreed systems, identify the owners and retrieval paths, and rehearse one fictional request. The intended output is a source map, a synthetic evidence pack and a prioritised list of gaps.

Target price under validation€2,500

  • Source map: systems, identifiers, owners and retrieval paths
  • Synthetic evidence pack: fictional records and decision boundaries
  • Prioritised gaps: missing ownership, coverage and next steps

No live personal data is required for the synthetic dry run. Payment can follow only after scope, delivery capacity and terms are confirmed in writing.

Explore the Readiness Sprint
01

Intake ownership

Who receives the request, records it and owns the next hand-off.

02

Identity matching

Which identifiers connect the same person across agreed systems.

03

Source coverage

Which sources are in scope, how they are checked and where gaps remain.

04

Decision boundary

Which questions require an authorised privacy professional.

05

Evidence trail

What records the search, exceptions, decisions and closure path.

Deliberately narrow

Start where the workflow can become repeatable.

Best initial fit
  • Outsourced DPO or privacy firms with multiple clients
  • Modern SaaS, marketplace and subscription companies
  • Structured customer data
  • Approximately three primary sources
  • Stable identifiers such as email address or user ID
  • A named privacy decision owner
  • A willingness to test the workflow on synthetic data
Not an initial fit
  • Employee disputes
  • Litigation or contested legal matters
  • Broad mailbox, Slack or file-share discovery
  • Health data or children’s data
  • Large volumes of unstructured documents
  • Autonomous legal decisions
  • Organisations requiring certifications Trace cannot yet evidence
  • Urgent live matters before scope and delivery capacity exist

See the output

Understand the proposed deliverable before the product exists.

The sample case uses fictional people, systems and records. It shows the intended structure of a review-ready case: what was searched, what was found, which questions remain open and where human judgement begins.

TRACE / SYNTHETIC CASE 001
  1. Case summary
  2. Source inventory
  3. Evidence manifest
  4. Exception register
  5. Decision boundary
  6. Activity record

Fictional records only

Commercial model under validation

Readiness first. Coverage after the workflow is proven.

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.

Founder note

A note from the founder

“I am building Trace to understand whether privacy teams need a dependable operations layer between advice and the actual work of finding, structuring and evidencing a request. I am looking for privacy professionals willing to walk through their last real workflow: where it became manual, where senior judgement was needed and what should become repeatable.”

Mees Tierolff · Founder, Trace

Email Mees about your workflow

Straight answers

Questions before a workflow conversation.

What is managed data-rights operations?
It is the operational work around a request: mapping sources, coordinating approved retrieval, structuring evidence, documenting exceptions and preparing a case for an authorised privacy professional to decide.
Is Trace a law firm or external DPO?
No. Trace is developing an operations layer for privacy professionals and internal teams. It does not provide legal advice or replace the controller, external DPO or authorised decision-maker.
Is Trace already live?
No. Trace is pre-launch and validating the operating model with prospective design partners. There is no production service or general availability today.
What is a Readiness Sprint?
A proposed fixed-scope engagement to map up to three agreed systems, define the evidence path and rehearse one request using synthetic data. The target price under validation is €2,500.
Who makes the final privacy decisions?
The authorised privacy professional and controller retain decisions about identity, interpretation, disclosure, redaction, retention, exemptions, erasure, correction and final wording.
Do I send request data through this website?
No. Do not send identities, request contents, exports, credentials or other personal data through this website. The first conversation is only about the workflow.
Which systems are in the initial scope?
The proposed starting point is up to three structured systems with stable identifiers and an agreed retrieval path. The actual systems and boundaries would be confirmed in writing.
Can a privacy firm use Trace behind its own client service?
That is the primary model under validation. The firm would keep the client relationship, advice and final judgement while Trace prepares the repeatable operational layer beneath it.
What happens after I join the waitlist?
Trace may invite a small number of relevant teams to a workflow conversation. Joining does not create a contract, reserve delivery capacity or authorise access to any system.
Why test readiness before a real request arrives?
A synthetic rehearsal can expose missing owners, identifiers, retrieval paths and decision boundaries without using live request data or discovering those gaps against a deadline.

Founding design partners

Show us where the last request became expensive.

Join the design partner list or describe the workflow in an email. Do not send names, request contents, exports or credentials. The first conversation is about the operating problem, not access to personal data.

A related problem under validation

Requests need evidence. Retention needs a recurring review.

We are also testing whether teams need help reviewing personal data scattered across email, shared folders and business systems. No retention software is generally available.

Explore data retention automation, with applications for recruitment, travel operators and visa and immigration agencies.

These are research directions. The proposed DSAR Readiness Sprint and its commercial terms remain separate.