Los artículos de ayuda existen en alemán e inglés. Aquí los lees en inglés.
Protección de datos y seguridad
Does a deletion take lasting effect?
It lasts: a deleted person’s data does not come back on their next visit. Deletion and objection put the identifiers concerned on a suppression list; only a hash of them is stored, which is still pseudonymous personal data and is read for nothing but enforcing the suppression. The collector rejects events from suppressed persons before anything is stored.
Does a deleted person’s data come back on their next visit?
- What goes on the suppression list are the identifiers, not the person.
- Only a hash is stored. The list itself contains no readable identifiers.
- Rejected events appear in the collector response as blocked.
- A suppression can be lifted with a stated reason; that too is in the change log.
Why one deletion creates several rows
A person is known through several identifiers: pseudonymous browser ID, session, order number, pseudonymised customer ID. Each is suppressed in its own right, because each can come back on its own. That is why one deletion produces as many rows as the person had identifiers.
- The “Identifier” column names the kind of identifier, never its value and never its checksum.
- The “Reference” column carries a serial number so a row can be named.
- The “Request” column points to the case the suppression came from.
- Where one request holds several active suppressions, a bulk action lifts them together, with one reason for all of them and one log entry per row.
And if a backup is restored?
Backups are not searched to remove individual records from them. That would be more error-prone than the problem it solves. Restoring a backup therefore brings deleted data back at first, and the suppression list is back at the state of the backup: it lives in the same database. The way back is a journal outside the database, to which every deletion and objection is also written. Before the restored database takes in data again, the journal puts back the suppressions from the time in between, and a run checks the suppression list against the existing records and deletes again what is suppressed. The same run repeats regularly during operation; normally it finds nothing, which is exactly when it is right.
Note
The limit remains: if the same person visits later with a new pseudonymous identifier, after clearing browser storage for instance, a new, unlinked identity is created. What is suppressed are the known identifiers, not the human being.
Revisado por última vez el 15 oct 2026
En el portal del cliente
También se pregunta
- Suppression list
- Permanent opt-out
- Does deleted data come back?
- What happens to a deletion when a backup is restored?
- Why are there four entries in the suppression list?
- How do I lift every suppression for one person?
Artículos relacionados
- How do I handle access, deletion and objection?
A data subject exercises their rights. What do I do?
Privacy requests are handled in the portal under “Privacy”, not by ticket. Every request is recorded and logged in the change log; the data subject is located through a pseudonymous identifier.
- What happens when consent is withdrawn?
A visitor withdraws consent. What happens to the data?
From the moment of withdrawal nothing more is stored, and queued reports to advertising platforms no longer go out. Metrunio then automatically deletes what that browser reported under the withdrawn purpose, usually within a few minutes, and you do not need to create a request. Metrunio also deletes ad contacts from pixel, tag and click redirect that are linked to this browser; all other ad contacts stay.
- Why are my events rejected?
The collector does not accept events. How do I find the cause?
The collector response states a status per event and, on failure, the reason. Check that response first; “Data status” in the portal additionally summarises the reasons over the period.
- How long is data retained?
Which retention periods apply and can I change them?
Raw events are retained for 180 days by default, 90 days on the free Start plan; the period is configurable per tenant up to the plan’s limit and enforced automatically. Journeys, touchpoints and conversions share the period of the raw events they were derived from and are deleted with them, or earlier if a deletion is requested. If a change of plan lowers the limit below the configured period, we announce the reduction 30 days in advance.