Set up your bannerConfigure Your ToolsContent Embeds

Yumpu

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

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Unlock additional website features

Overview

This guide explains how to implement different privacy configurations for Yumpu publications on a website and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. Yumpu flip-book publications (i-Magazine AG, Switzerland) linked or embedded.

What the service does in this scope. A website operator documents that the Yumpu embed sets a broad range of cookies, including Yumpu's own (ypsession, yumpu_slc) and cookies associated with Google Analytics and Ads, Meta, Microsoft Clarity and Bing, LinkedIn and others, with retention up to 2 years. Yumpu's privacy policy is written under the GDPR and the Swiss DSG.

Configurations included.

ConfigurationSummary
Configuration A — Lower riskLink to the publication on Yumpu; no embed.
Configuration B — Higher riskEmbedded Yumpu reader loaded after Consenter consent / click-to-load.

Step 1 — Configure Yumpu

#Configuration areaWhere to configure itConfiguration A — Lower riskConfiguration B — Higher risk
1Processing purposesOperator decision—Unlock additional website features
2IntegrationWebsite codeLinkYumpu embed code
3LoadingConsenter script blocking / click-to-load—After consent

Step 2 — Map the configuration in the Consenter Manager

Processing location. Switzerland (adequacy decision); the embed loads US advertising and analytics vendors, subject to the US CLOUD Act; list the United States.

Consenter Manager fieldConfiguration A — Lower riskConfiguration B — Higher risk
Entry neededNoYes
Processing purposes—Unlock additional website features
Tracking methodNo trackingThird party tracking (crosssession, cross-website)
IdentifierNo identifierDevice identifiers
Data categories—Browsing and interaction data, Device characteristics, Device identifiers, IP address, Users' profiles
Legal role of data recipient—Individual Controller
Personalisation model—Profile based (embedded ad vendors)
Maximum storage duration—Up to 2 years
Processing location—Switzerland; United States

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