Typeform
How to configure Typeform 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, Support marketing analytics
Overview
This guide explains how to implement different privacy configurations for embedded Typeform forms 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. Typeform forms embedded via the Embed SDK or linked. Typeform S.L. is based in Barcelona.
What the service does in this scope. Typeform stores form responses in the US, or in the EU for EU data-hosting customers; infrastructure is provided by AWS. Embedded forms load analytics scripts (requests to api.segment.io), which Typeform states can only be stopped by blocking them. Typeform acts as processor with SCCs and participates in the EU-US Data Privacy Framework.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Link to the hosted form; EU data hosting. |
| Configuration B — Higher risk | Embedded form loaded after Consenter consent; US hosting; GTM / tracking in the form. |
Step 1 — Configure Typeform
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | — (external link) | Unlock additional website features; Support marketing analytics |
| 2 | Integration | Website code | Link to form.typeform.com/... | Embed SDK (embed.typeform.com) |
| 3 | Data hosting | Plan / account | EU | US |
| 4 | Form tracking (GTM, pixels) | Typeform form settings | Off | On |
| 5 | Loading | Consenter script blocking | — | After consent |
Step 2 — Map the configuration in the Consenter Manager
Processing location. AWS hosts all Typeform data; AWS is a US enterprise subject to the US CLOUD Act; list the United States in all configurations with an entry.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|
| Entry needed | No (mention in the privacy policy) | Yes |
| Processing purposes | — | Unlock additional website features, Support marketing analytics |
| Tracking method | No tracking | Third party tracking (crosssession, cross-website) |
| Identifier | No identifier | Device identifiers |
| Data categories | — | Browsing and interaction data, Device characteristics, Device identifiers, IP address, User-provided data |
| Legal role of data recipient | — | Processor |
| Personalisation model | — | No personalisation |
| Maximum storage duration | — | Per Typeform cookie policy |
| Processing location | — | 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