Pre-launch website
A demand-validation site that explains the thesis, presents pricing experiments and accepts qualification interest.
About Trace · Pre-launch
Privacy operations should feel controlled before they feel automated.
Trace is being shaped around a narrow thesis: modern product teams need a dependable way to turn a fragmented GDPR request into one evidence-backed case—without pretending software can make every legal decision.
Why this product thesis exists
The hard part is rarely finding the legal deadline.
The hard part is knowing which team received the request, which identity matches which records, which systems were actually checked, who can decide an exception and whether the final package leaves a reliable trail.
That coordination often cuts across support, legal, operations, security and engineering. A broad compliance dashboard does not necessarily perform the work; a consultancy may perform it without leaving a reusable operational path; internal teams often rebuild the path for every request.
Trace is testing a middle model: hands-on implementation and case preparation supported by a repeatable product workflow, with legal and factual judgement kept at an explicit human boundary.
Current reality
What exists, what is being tested and what is not ready.
A buyer should not have to reverse-engineer product maturity from polished screens. These labels are the shortest version of Trace’s present truth.
Case interface and pack format
Illustrative screens and files designed to test whether the proposed outcome is understandable and useful.
Source-mapping operating model
A proposed hands-on approach for early pilots. It is not a generally available or capacity-backed service claim.
Repeatable product workflow
Case orchestration, maintained source maps and controlled approvals are the long-term product direction.
Human review model
Reviewer role, qualifications, capacity, independence and responsibility must be confirmed for each accepted offer.
Legal and security assurance
DPA, pilot terms, retention, subprocessors, architecture evidence and formal security processes still require review.
Not claimed: live self-serve connectors, automated legal decisions, general reviewer capacity, completed certifications, production assurance or customer outcomes.
Operating principles
The rules should survive the roadmap.
These principles constrain both the proposed early pilot and any software that follows. If a feature breaks the review boundary or hides evidence quality, it weakens the product.
Sell an outcome, not an interface
A customer should receive something useful from one request before being asked to learn another compliance platform.
Connect as little as possible
A controlled export or narrow read path may be better than broad permanent access, especially during an early pilot.
Make uncertainty visible
Missing sources, ambiguous identity, third-party data and retention questions belong in the case—not under a green status.
Keep judgement human
Trace may organise and draft. An authorised person decides disclosure, correction, erasure, exceptions and final wording.
Prove the operating model before building breadth
One paid, well-run pilot says more than a large roadmap of connectors nobody has trusted with a real workflow.
Record every hand-off
The next person should understand what happened, which evidence was used and why a decision remains open.
Designed for a specific operating problem
For product teams with real user data and no appetite for another internal project.
The initial hypothesis is deliberately narrower than “every business with GDPR obligations.”
- EU-facing SaaS, apps or marketplaces with a meaningful end-user base
- Personal data spread across product, billing, support and storage systems
- Legal, operations and engineering sharing responsibility
- Requests currently coordinated through email, tickets or spreadsheets
- A named decision owner and willingness to scope one concrete case
- A very simple, well-owned workflow that rarely changes
- No budget or authority to improve privacy operations
- A need for legal representation rather than operational support
- An expectation of autonomous decisions or guaranteed compliance
- A requirement for certifications or controls Trace cannot yet evidence
Company and people
The operator deserves the same scrutiny as the workflow.
No founder biography, contracting-entity details or named reviewer credentials were available to verify for this public page. Trace will not fill that gap with invented authority signals.
Disclosure required before an accepted pilot
A commercial proposal should identify:
- The contracting legal entity and accountable service owner
- The privacy and security contact paths
- The person or organisation performing any promised review
- That reviewer’s role, qualifications, capacity and decision boundary
- Applicable subprocessors, hosting and data locations
- Signed terms, DPA where applicable, retention and deletion instructions
Until those facts are supplied and verified, the website should be read as a pre-launch proposition—not proof of an operating compliance provider.
Ask an operating questionWhere Trace is trying to sit
More operational than advice. More accountable than automation.
The pilot exists to learn whether this middle position creates enough value to support a real company and product.
A tool still needs an operator.
Trace does not expect a customer to configure a complex platform before seeing value. The first outcome should come from managed implementation and one case.
Managed work becomes a reusable path.
Proposed hands-on source mapping and case preparation should create an operational asset the next request can reuse, while every human decision remains visible.
Advice may not become infrastructure.
Trace is not a law firm or a substitute for counsel. Its product ambition is the structured evidence, hand-offs and maintained source map around the decision.
How this claim discipline worksRead the product and evidence methodology →
A controlled first request
The next proof should be a well-scoped pilot, not another claim.
If the operating problem is familiar, share the context behind it. Trace will assess fit before discussing data, access or payment.