Set up your bannerConfigure Your ToolsMarketing Automation and CRM

Evalanche

How to configure Evalanche at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Receive marketing offers, Receive personalised marketing offers

Overview

This guide explains how to reflect Evalanche in the Consenter Manager. SC-Networks does not publish technical details of Evalanche's website tracking, so this guide uses a single fixed-behaviour table.

  1. Implement the service as described below.
  2. Map the implementation in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The mapping is an example, not a guarantee of legal compliance. Verify it against your implementation and current provider documentation.

At a glance

Scope. Evalanche marketing automation by SC-Networks GmbH, Starnberg, Germany: forms and, where used, website tracking.

What the service does in this scope. SC-Networks states that the use of tracking functionalities is configuration-dependent and must be controlled organisationally. Evalanche processes data as a processor under a data processing agreement.

⚠ Research gap. Cookie names, lifetimes and the exact behaviour of Evalanche's website tracking were not found in public documentation. Inspect the implementation in the browser and request the technical documentation from SC-Networks before finalising the mapping.

Step 1 — Implement Evalanche

Configuration areaFixed behaviour / required action
Processing purposesReceive marketing offers; Receive personalised marketing offers (if tracking and profiling are used)
Website trackingConfiguration-dependent; load after Consenter consent
ContractData processing agreement

Step 2 — Map the configuration in the Consenter Manager

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesReceive marketing offers, Receive personalised marketing offersMarketing automation
Tracking methodFirst party tracking (cross-session)Assumed for website tracking; verify
IdentifierDevice identifiers, Direct identifierTracking linked to contacts; verify
Data categoriesBrowsing and interaction data, Device identifiers, User-provided data, direct identifier, Users' profilesMarketing automation profiles
Legal role of data recipientProcessor—
Personalisation modelProfile basedMarketing automation
Maximum storage durationPer cookie inspectionNot documented
Processing locationGermanyGerman company; no CLOUD Act flag unless the DPA lists US sub-processors

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page