---
slug: betroffenenrechte
title: "How do I handle access, deletion and objection?"
category: datenschutz
locale: en
updated: 2026-10-16
keywords: ["data subject rights","access","deletion","objection","GDPR","Article 15"]
questions: ["A data subject exercises their rights. What do I do?","GDPR access request","Carry out a deletion request","Article 15 access","Article 21 objection","Deletion request from Shopify","customers/redact","Deadline for access requests from Shopify","Deletion by email checksum","Orders in a Shopify deletion request","orders_to_redact"]
url: https://bench.metrunio.com/en/help/betroffenenrechte
---

# 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.

## How the person is found

The search does not take names or addresses: event fields are not meant to hold them, and detected email addresses and phone numbers are rejected on receipt. Pseudonymous identifiers are accepted.

| Identifier | Origin |
| --- | --- |
| id_… | public identifier of an identity |
| jr_… | public identifier of a journey, found under “Customer Journeys” |
| anonymous_id | first-party identifier of the browser |
| customer number or user_id_hash | as your shop sends it, for example the SHA-256 of the email address from the Shopify app or the Shopware plugin |
| order number or lead ID | from the shop or CRM system |

A customer number is stored only after being combined with your account’s key. You still enter it the way your shop sent it: Metrunio does the combining itself during the search and finds both forms.

## Effect of each request type

| Type | Effect |
| --- | --- |
| Access (Art. 15) | produces a JSON file with identities, links, journeys, touchpoints, conversions and raw events, plus the stored consent decisions, the recipients of reported conversions and any suppression in place; changes nothing |
| Deletion (Art. 17) | deletes raw events, conversions and identities; attribution values already reported decrease retroactively |
| Objection (Art. 21) | removes identifiers, addresses and referrer and deletes the links; journeys, values and timestamps remain without them for aggregated reporting. Revenue reconciliation orders for the given order number are deleted, because they serve no other purpose |
| Rectification (Art. 16) | is not automated: a pseudonymous attribution can be wrong too, and it has to be corrected everywhere it could be rebuilt from. Write to privacy@metrunio.com with the request ID; the correction is made by hand following our documented procedure, including the recipients the data went to. Afterwards you close the request with “Close as done” and a record of what was done |
| Restriction (Art. 18) | is not a request type of its own in the portal, and a deletion does not replace it. Write to privacy@metrunio.com with the request ID: following our documented procedure, the affected data is preserved under protection and blocked from reports, AI queries, exports and reports to advertising platforms. Affected recipients are included |

> **Caution:** Before execution the identifier must be repeated for confirmation. A completed request cannot be run again. The Admin role is required (privacy.read and privacy.write).

- After a deletion or objection the message states how many records were affected and how many identifiers are suppressed. If an inventory check was shown above, it is run again; if that fails, it is marked as out of date.
- The access file is created from the data as it stands when you download it (generatedAt) and is not stored. If you download it after a later deletion, whatever was deleted is missing.
- It contains at most 5,000 rows per table; exportTruncated says whether there was more. If it is true, the access file is not yet complete: request the supplementary complete export via privacy@metrunio.com, quoting the request ID, before you answer the access request and close it.

> **Note:** The platform administration sees the request, its status and deadline, but not the data subject’s identifier. Handling stays with you.

## Requests from Shopify

If your store is connected through the Metrunio app, deletion and access requests from your customers arrive via Shopify. Metrunio carries out a deletion itself on receipt, with the same routine as “Carry out” in the portal, and puts the identifier on the suppression list; the request then shows as completed. An access request stays open and carries the deadline Shopify sets: 30 days from receipt. Open requests with a deadline are shown at the top of the privacy area.

A deletion from Shopify lists the customer’s order IDs alongside the email checksum. Metrunio deletes by those as well, so that revenue reconciliation orders stored under nothing but their order ID are covered, and suppresses the order IDs. If the email address is missing, the request shows the order IDs as its identifier in the portal.

> **Legal note:** The 30-day deadline is Shopify’s expectation. The one-month deadline under Art. 12(3) GDPR applies independently and can end sooner if the customer contacted you first.

## Also asked

- GDPR access request
- Carry out a deletion request
- Article 15 access
- Article 21 objection
- Deletion request from Shopify
- customers/redact
- Deadline for access requests from Shopify
- Deletion by email checksum
- Orders in a Shopify deletion request
- orders_to_redact

## Related

- https://bench.metrunio.com/en/help/sperrliste
- https://bench.metrunio.com/en/help/aufbewahrung
- https://bench.metrunio.com/en/help/journey-explorer
- https://bench.metrunio.com/en/help/shopify-app
- https://bench.metrunio.com/en/help/zusatzweisung-umsatzabstimmung