What gets deployed
Deployed with the configuration agreed for your organization.
Configured on the data types identified in the Diagnostic — client identification, sensitive data from your activity.
Tests with real or representative data, demonstrating that sensitive data does not leave where it should not.
A minimal handoff so your team understands what was deployed and why.
What is out of scope
The Deployment scope is defined from day one. Anything outside that scope is budgeted separately, not a silent expansion of the project — so you always know what you are paying for and why.
- Integrations with proprietary systems beyond the already identified workflow
- Extensive team training beyond one handoff session
- Detection rules for data types not previously identified
- Any requirement that appears after signing and was not agreed
The limit we do not blur
What anonymization solves — and what it does not
Anonymizing data solves the data protection problem: if no one can identify the person from what leaves, that data stops posing the same risk. But it does not solve professional privilege or data sovereignty. Privilege protects by category of information, not by whether that information identifies someone — an anonymized document can still be covered by privilege if its content belongs to that protected category.
For that different problem, the answer is not better anonymization — it is that the data never leaves your infrastructure at all. That is Privedge's edge mode, and it is why we offer two levels of guarantee instead of one that overpromises.
Learn more about edge inference →And after
With Privedge already deployed and running, the natural next step is keeping it alive: support, updates and adjustments as your workflows change. That is discussed once the system is already live, not before.
Frequently asked questions
Do I need to have contracted the Diagnostic first?
It is not mandatory, but it is the recommended starting point — the Deployment is configured better once the relevant workflows and data types are already known.
How long does the project take?
It is a fixed-scope project with a predictable duration. We confirm the exact timeline based on your organization's specific scope.
What if we need something outside the initial scope?
It is budgeted separately, transparently, before that additional work starts — never as a surprise cost.
Does this replace our legal counsel's judgment?
No. Privedge provides a technical capability. Regulatory compliance is determined by your organization together with your legal counsel.
Why does the re-identification map stay in our infrastructure?
Because that is the difference between pseudonymising and pseudonymising in a way that holds up. The <a href="https://www.edpb.europa.eu/our-work-tools/our-documents/recommendations/recommendations-012020-measures-supplement-transfer_en" target="_blank" rel="noopener">EDPB recommendations</a> on supplementary measures name pseudonymisation as effective when the information needed to re-identify is held exclusively by the exporter, kept separately and in an adequate jurisdiction. If that map travels with the data, or the provider holds it, the measure loses its point. With Privedge it never leaves your infrastructure.
Is this available outside Spain?
The Deployment is currently delivered in Spain, in Spanish.
Currently delivered in Spain, in Spanish.