# Security: data flows and the key in IT-InterMirror | IT-INTERDEV

> What leaves the house with IT-InterMirror and what does not: data flows, the mapping table, checks before sending, and why nothing is sent when in doubt.

Language: en · Source: https://it-interdev.de/en/security.html · Alternate (de): https://it-interdev.de/sicherheit.html · Updated: 2026-11-05

This page shows where your data goes with IT-InterMirror and where it does not. This is pseudonymisation, not anonymisation. The key makes the way back possible and stays with you.

## Data flows

| What | Does it leave the house? |
|---|---|
| Original documents | No. |
| Key (mapping table) | No. It stays with the customer. |
| Shadow copy | Yes, but only to the chosen cloud AI and only if the zone allows it. |
| Red and blue zones | Never. These zones never go to the cloud. |
| The AI’s answer | It comes back and is translated back on your side. |
| Log | It stays with you and contains no contents. |

## Where the mapping table lives

The key stays with the customer. In the relay server it exists in working memory only and has an expiry time.

We will describe the storage location and encryption of the mapping table here as soon as the details are released.

## When in doubt, nothing is sent

Before sending, IT-InterMirror runs three checks. If a document fails one, it goes into quarantine and nothing is sent.

1. **Hits from the key.** Is any name or identifier from the key still in the shadow copy?
2. **Amounts, dates and quantities.** Does every amount of the original appear unchanged in the result?
3. **The way back.** Does out and back produce exactly your text?

## Preview before sending

A preview in which you look at the shadow copy and approve it before it is sent: Status: in development.

## What this page is not

> **No legal advice.** This page describes technology. It is not legal advice and not a certificate. There is no third-party review.

