Protección de datos y seguridad

• Which data is stored?

  What exactly does Metrunio hold about my website’s visitors?

  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.

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

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

• Does a deletion take lasting effect?

  Does a deleted person’s data come back on their next visit?

  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.

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

• Where is the data processed?

  Is there a data processing agreement, and where are the servers?

  Application, database and analytics storage are planned for the europe-west3 region (Frankfurt); what goes beyond that, such as logs and support access at the cloud provider, is listed in the sub-processor list under “Documents”. You conclude the data processing agreement with us in the portal under “Privacy” or in the Shopify app; nothing is measured before that. We have our own agreements with our sub-processors.

• How do I conclude the data processing agreement?

  How do I conclude the DPA with Metrunio, and why is nothing measured before?

  For every account, measurement starts only once the data processing agreement (DPA) is concluded; until then Metrunio accepts nothing and stores nothing. You conclude it in the portal under “Privacy” or in the setup step “Conclude the DPA”, and for a Shopify store also right in the app: enter the company, its address and the person concluding it, confirm they are authorised, done. Data arrives a few seconds later, without any change to your installation.

• Additional instruction for revenue reconciliation

  When do orders count after a refusal in the cookie banner?

  Orders your shop reports server-side after a refusal in the banner only count if the additional instruction for revenue reconciliation is activated for your account. You fill it in and sign it, and then we activate it; without it Metrunio rejects such orders. Orders with no decision in the banner at all count even without the instruction.

• Privacy policy text block: revenue reconciliation

  What does my privacy policy need to say about revenue reconciliation?

  Your privacy policy must name revenue reconciliation as a purpose of its own alongside tracking, with the legal basis (legitimate interest under Art. 6(1)(f) GDPR), the data, Metrunio as processor, the retention period and how to object. Metrunio’s privacy policy does not inform your buyers. The block below is a draft for you to adapt.

• Attributing orders via the checkout

  How does Metrunio attribute orders without a consent decision?

  Not at all, as long as you have not switched on order attribution via the checkout. With it, we attribute such an order to the visit when the same checkout was completed in the browser with consent and that consent already existed at the time of purchase.

• What security properties does Metrunio have?

  How is separation between customers enforced?

  Tenant separation is enforced in the database as well (row-level security), not only in application code. Tracking elements are signed, there is no open redirect, and signed requests are protected against replay.

• Do I need a cookie banner for Metrunio?

  Do I need consent and an entry in the cookie banner for Metrunio?

  Yes: Metrunio measures visits and ad contacts only with consent, so it belongs in your cookie banner and your privacy policy together with its storage entries. Without consent it accepts at most purchases and refunds for revenue reconciliation, without browser, customer or advertising identifiers. The legal framework is Section 25 TDDDG: storing and reading information on a device generally requires consent.

• Which legal documents exist, and where are they?

  Where do I find the terms, the data processing agreement, the TOMs and the list of service providers?

  All of them are published openly, with no form and no sign-in: the general terms at /en/terms, the privacy notice at /en/privacy, and the data processing agreement, the technical and organisational measures, the annex listing the further processors and the deletion policy at /en/documents. The same page carries the overview “Service providers and recipients”: it names every recipient with its role, including those that act as their own controller and therefore do not belong in a contractual annex. Further evidence (record of processing activities, retention periods in detail, the breach notification process) is available on request.

Al centro de ayuda