Skip to content
Back office: finance, HR, legalFor every industry

Answer data-protection requests on time

A person's data found in every connected system, the access report compiled and deletion or anonymization planned.

Today

Access and erasure requests come with a legal deadline. But the person's data is spread across ERP, CRM, e-mail, the file share and the HR system. Whoever handles the request searches by hand and easily misses a copy.

An example

A former applicant at Talwerk Antriebstechnik asks for his data to be erased. The agent finds his profile in the HR system, two e-mail threads and a folder with three documents on the file share. It proposes deleting everything except one record under a legal retention duty, and names the rule.
Fictional company, typical workflow.

Your data, wherever it lives

A person's data is spread out today: customer data in the CRM and ERP, applications and personnel files in the HR system, threads in mailboxes, contracts in the DMS and copies in folders on the drive. demi reads, understands and links it into one record per person, with your rights. In minutes the AI finds every copy in the connected systems with its retention rule, and the data protection officer decides what is deleted.

Where the data lives today

  • CRM
  • ERP
  • HR system
  • E-mails
  • DMS & archive
  • Folders & drives
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    The case needs data from ERP, CRM, HR system, e-mail and DMS. demi replaces nothing and keeps each person as one record across the sources of the case, with your retention rules per data type. After approval demi deletes or anonymizes the data; it writes back only after approval.

  2. 2 · PermitPermission Layer

    Only the person responsible for data protection can run the search, and only they see the results. The data protection officer reviews and approves the disclosure and the deletion plan, and every deletion is recorded.

  3. 3 · ActIntelligence Layer

    The agent collects every record about the person with its source and purpose and checks retention periods exactly against your documented rules. Where no duty applies, it proposes deletion or anonymization; the legal assessment stays with your experts.

How it runs

  1. 1

    The request comes in and is matched to the right person.

  2. 2

    The agent collects every record with its source and purpose.

  3. 3

    It checks the retention rule for each record.

  4. 4

    The data protection officer reviews the report and deletion plan, then approves.

  5. 5

    demi deletes or anonymizes in the systems and documents every step.

What changes

  • The deadline of every request in view

  • Copies found in every connected system

  • Every step documented and traceable

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+77 hfreed per year

Assumptions and calculation

demi finds the person's data in every connected system and drafts the response; you approve.

4 h → 2.4 h per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

4 data subject requests × 4 h × 40% × 1.0 (manual) × 12 months = 77 h

Value per year, before demi costs

Freed per year+77 h

Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.

= Value per year, before demi costs

+$5,005

gained per year

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

How does demi find a person's data across all sources of the case?

The Data Layer already keeps each person as one entity, with links to their records across the sources of the case. The agent also searches by name, e-mail address and customer number to catch records that are not linked, such as old e-mails. Uncertain matches are marked as such.

Who sees the search results?

Only the person handling the request, usually the data protection officer. The results are locked for everyone else. Every access is recorded.

How does demi handle legal retention periods?

Retention periods come from your documented rules per data type. Where one applies, the agent proposes restricting the record instead of deleting it and names the rule. The legal assessment of each case stays with your data protection experts.

Does demi delete data on its own?

Only after approval. The agent prepares a deletion plan. demi writes back only once the responsible person approves it. The log records what was deleted where, without keeping the deleted content.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases