Adobe Fonts
How to configure Adobe Fonts 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 Adobe Fonts web projects and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- 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. Adobe Fonts (formerly Typekit) web projects served from Adobe's servers. Adobe Inc. is a US company.
What the service does in this scope. Adobe does not set or use cookies to serve fonts for websites. For each request Adobe collects the fonts served, Web Project ID, JavaScript version, project type, embed type (JavaScript or CSS), account ID, serving service and server, and the hostname of the page; the IP address is received to deliver the font but not stored. Adobe uses this to provide the service, diagnose problems and pay foundries, and shares only aggregate reports with foundries. The JavaScript embed loads a p.gif image from typekit.net; Adobe describes it as an image, not a cookie.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | CSS embed code (no JavaScript); fonts loaded after Consenter consent. |
| Configuration B — Medium risk | JavaScript embed code (dynamic subsetting, p.gif); fonts loaded after consent. |
⚠ Recommendation — loading fonts before consent. Adobe sets no cookies, so § 25 TDDDG consent is not triggered by cookies. However, each font request transmits the visitor's IP address to a US provider. LG München I (judgment of 20 January 2022, 3 O 17493/20) held that transmitting the IP address to Google Fonts without consent breached the GDPR where self-hosting was possible. Adobe Fonts web projects are served by Adobe; have your DPO or independent counsel decide whether the same reasoning applies, and otherwise load the fonts after consent with a fallback font.
Step 1 — Configure Adobe Fonts
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Medium risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Unlock additional website features | Unlock additional website features |
| 2 | Embed type | Web Project embed code | CSS | JavaScript |
| 3 | Loading | Consenter (see ⚠) | After consent / per DPO | After consent / per DPO |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Adobe is a US enterprise subject to the US CLOUD Act; list the United States.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Medium risk |
|---|---|---|
| Processing purposes | Unlock additional website features | Unlock additional website features |
| Tracking method | No tracking | No tracking |
| Identifier | IP address | IP address |
| Data categories | IP address, Device characteristics | IP address, Device characteristics, Aggregated site statistics |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | IP not stored | IP not stored |
| Processing location | United States | 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