Platform / Govern
The evidence exists before anyone asks for it
You know where every piece of data came from and where it went, and every classification change is recorded with who and when. Before a review, the signed report already exists.
Audit reports
A signed report that fixes the state of your data
After each discovery you can generate a PDF report with the state of the source at that moment. While it is a draft it can be edited; once signed, it stands as immutable evidence.
- Who started the discovery and when
- Labels added, modified or removed, with who made the change
- Percentage of confirmed entities
- Editable draft or signed, immutable report
Data Lineage
The complete journey of the data, from source to destination
The audit answers who decided what. Lineage answers where every piece of data came from and where it went: for any field you see the rule applied to it, how it was transformed and which destination it is in.
- Tracing field by field, from the origin to the destination
- Rule and transformation applied to each field, with its last update
- Complete journey: tap, entity, rule and destination
- Filter by destination type and by transformed fields
Clientes QA
Cliente
- Str.fakeapellido1
- Str.fakeapellido2
- Str.fakecedula_identidad
- Str.fakedireccion
- Str.fakeemail
- Str.fakegenero
- Str.custom functionmunicipio
- Str.custom functionnombre
- Str.faketelefono_fijo
- Str.faketelefono_movil
←Cliente/Str.apellido1
- Field
- apellido1
- Entity
- Cliente
- Destination
- Clientes QA
- Destination Type
- DATASET
- Source Tap
- –
- Rule
- Anonimizar Clientes
- Transformation
- fake (person/name)
- Last Updated
- 28/9/2026, 20:20:19
Data Path
tap→Cliente→Anonimizar Clientes→Clientes QA
Control
Who can do what, and why they did it
Organizations, projects and models define who can view, edit or run rules over sensitive data. And every classification change requires a reason that is linked to its author.
- Hierarchy of organization, project and model
- Viewer, editor or administrator permissions
- Mandatory reason for every label change
- Dictionary exports to document the transformations
The four capabilities
Questions about the evidence
What does an audit report contain?
When the discovery ran and who started it, which labels were added, modified or removed and who made each change, and the percentage of confirmed entities. It is generated as a PDF after each discovery.
Can I modify a report that is already signed?
No. While it is a draft it can be edited or discarded; once signed it becomes immutable and cannot be modified or deleted. If the classification changes later, a new report is generated.
What is the difference between audit and lineage?
The audit documents decisions: who classified a field, when and for what reason. Lineage documents journeys: which source a piece of data comes from, which rule was applied to it and which environments it is in. Together they answer the two questions of any review.
What happens if the source schema changes?
Lineage links every dataset to its source and its rules, so when a schema changes you see which derived datasets and environments are affected before provisioning again.
Can I hand the evidence to an external auditor?
Yes. Reports are generated as PDFs, so your legal team or an external auditor can review them without accessing the platform.
Does it help answer a GDPR audit?
It provides evidence of which personal data was identified, who made each classification decision and, through dictionary exports, which transformations were applied. The legal assessment is up to your legal team or your DPO.
Show the evidence, not the promise
We show you the lineage of a real field from your model, how a signed report is generated and exactly what an auditor receives.