Privacy Delivery
Share data without exposing individuals
Privacy Delivery pseudonymises texts and documents before they go to an AI or to third parties, and puts the original values back into the response. It creates protected exports and test data in a valid format – and records who received what. Privacy Delivery builds on Data Discovery.
Safely to the AI and back
- 1
Pseudonymise
Text or file – PDF, Word, text, RTF or ODT. Personal data is replaced with neutral placeholders.
- 2
Hand over
You pass the pseudonymised version to the AI and record the destination. Handoffs to prohibited AI systems are flagged.
- 3
Re-identify
The AI's response gets the original values back – as long as you keep the mapping.
More ways to share data safely
Exports
Export data from a source in pseudonymised form – for analytics and reporting.
Test data
Substitute values in a valid format – realistic, but without real people.
Final check
The result is checked for any remaining unprotected details.
Evidence
The date, type, destination and person of every transfer are recorded – and for exports, the purpose as well.
For your applications
Your applications use Privacy Delivery via an interface.
Interface
Pseudonymise, re-identify, export and generate test data, directly from your applications.
Dedicated keys
Each application receives its own key; sensitive permissions such as re-identification are granted individually – time-limited and revocable at any time.
Traceable
Every transfer and every re-identification is recorded; the original values stay in your environment.
Service
Implementation
Installation, connection of your applications to the interface and training – all the way to production.
Frequently asked questions about Privacy Delivery
How does this differ from anonymisation?
Pseudonymised data can be traced back to the individual using the mapping; this mapping stays with you and is kept only for as long as you specify. Anonymised data, by contrast, can no longer be attributed to any individual.
Do the original values leave our premises?
No. The original values remain protected in your environment. Only the pseudonymised version is shared.
Which file formats are supported?
PDF, Word, text, RTF and ODT, plus text entered directly in the user interface or sent via the interface.
How is the test data created?
Personal data is replaced with substitute values in a valid format. This way, validation checks in your test systems keep working.
Can our applications use this automatically?
Yes, via the interface, with a dedicated key for each application that has only the permissions granted.
How do we get started?
With a 30-minute demo. Afterwards, we will clarify whether an assessment, a proof of concept or going straight to implementation is the right next step.
See Espresso in 30 minutes
We will show you the cockpit with sample data – and discuss where you should start.
Request a demoor write directly to info@espressodataprivacy.com