Los artículos de ayuda existen en alemán e inglés. Aquí los lees en inglés.
Protección de datos y seguridad
Which data is stored?
Pseudonymous identifiers, event data with timestamps, campaign and click identifiers, and conversion values. No raw IP addresses; event fields are not meant to hold plain-text names or contact details. Detected email addresses and phone numbers cause rejection; the automatic check does not detect every kind of personal data, though.
What exactly does Metrunio hold about my website’s visitors?
| Category | Implementation |
|---|---|
| IP addresses | not stored, neither raw nor as a checksum; processed only in transit and for rate limiting |
| User identifiers | user_id and user_id_hash are pseudonymised on receipt through a tenant-specific HMAC, including the SHA-256 of the email address from the Shopify app and the Shopware plugin |
| Plaintext PII | email addresses and phone numbers cause rejection (PII_DETECTED); we only store which field was affected, never the value |
| Metadata | at most 50 fields, 8 KB; HTML and executable content are rejected |
| Answers to the post-purchase question | only with consent to analytics; a key from a fixed list with the order number, linked to the order and journey, so not an anonymous survey |
| Fingerprinting | not implemented and not planned |
| Linking across websites | no linking across tenant boundaries. Within your tenant, Metrunio links contacts across websites as far as the consents and your instruction cover it: for example an ad seen on another site with the later visit to your shop (post-view), or visits to several of your websites through the same customer number |
In the browser
| Name | Where | What for | Needs |
|---|---|---|---|
| metrunio_anonymous_id | localStorage | visitor identifier | consent to analytics |
| metrunio_session | sessionStorage | the session, its origin and the lead ID of a form | consent to analytics |
| metrunio_queue | localStorage | events that have not arrived yet | a decision in the banner |
| metrunio_consent_pending | localStorage | a decision whose report has not arrived yet | a decision in the banner |
| metrunio_view | cookie of the measurement address, 30 days | view identifier for post-view | consent to marketing |
| metrunio_aid | cookie on your domain, 13 months (seven days in Safari), only through your own measurement domain | the same visitor identifier on all subdomains of your domain, even after the site’s storage was cleared | consent to analytics |
Before a decision in the banner, the SDK reads and writes none of these. Withdrawing consent removes the identifier, session and queue, and the collector deletes the cookie whose consent has gone. Safari shortens metrunio_aid to seven days.
Name the cookies and storage entries in your consent management and your privacy notice, with purpose and duration, before anyone decides. For metrunio_aid that includes its reach: it applies on all subdomains of your domain.
The underlying principle is simple: what is not collected cannot be lost, passed on or misused. That is why the limits are drawn technically rather than merely promised contractually.
Legal note
Which legal basis applies to which signal and purpose is for you as the controller to decide and to document with your data protection adviser.
Revisado por última vez el 13 oct 2026
También se pregunta
- Which personal data?
- Do you store IP addresses?
- What is in the database?
- Do you store rejected events?
- Which cookies does Metrunio set?
- What is stored in localStorage?
- What do I have to state about Metrunio in the cookie banner?
Artículos relacionados
- Are IP addresses stored?
How does Metrunio handle IP addresses and customer numbers?
IP addresses are not stored, neither raw nor as a checksum. Metrunio processes them only in transit and to limit requests. Since 14 October 2026 Metrunio no longer forms the truncated checksum that used to sit on measurement events; existing values have been deleted. Customer numbers and email checksums you pass are likewise pseudonymised on receipt, per account.
- Which attributes are linked?
How does Metrunio know that two signals belong together?
Only through unambiguous identifiers: session ID, pseudonymous first-party ID, click ID, impression ID, view identifier, pseudonymised customer identifier, and order or lead number. Nothing else.
- 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.
- How do I measure over my own domain?
How do I set up a custom measurement domain so ad blockers cost me less data?
In “Setup” you enter a name such as gauge.your-domain.com, and Metrunio gives you three DNS records at once (two CNAME and one TXT). Once they are in place and a certificate has been issued for your name, the address goes live; with the snippet or Tag Manager you then switch your setup, while the Shopify app and the plugins for Shopware and WordPress switch themselves. Measurement then runs first-party and is cut less often by ad blockers and browser tracking protection.