Wistia
How to configure Wistia 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 Wistia media 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. The Wistia player (Aurora web component or iframe embed). Wistia, Inc. is a US company.
What the service does in this scope. With Privacy Mode, Wistia collects only anonymised data; it can be set as the account default or per visitor via W.consent; W.consent(false) removes temporary storage used for tracking, though some non-tracking cookies and local storage may remain. With registration turned off, no personal information is collected and only anonymous, aggregate analytics are provided in Privacy Mode. Loading the player and tracking the viewer are separate decisions; the tracking preference can be set once the embed script is present. Wistia recommends classifying *.wistia.com and *.wistia.net as functional or essential in the consent manager.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | Player loads; Privacy Mode on by default; registration (email gate) off. |
| Configuration B — Higher risk | Player after consent; Privacy Mode off via W.consent(true); heatmaps and Turnstile email gate. |
⚠ Recommendation — Configuration A without consent. Wistia describes Privacy Mode as minimising data, not as requiring no consent, and some non-tracking storage remains; the player also transmits the IP address to Wistia (US). Loading the player before consent is a legally uncertain setup; have your DPO or independent counsel review it, or use a click-to-load placeholder.
Step 1 — Configure Wistia
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Unlock additional website features | Unlock additional website features; Support marketing analytics |
| 2 | Privacy Mode default | Account settings | On | On |
| 3 | Per-visitor consent | W.consent(true/false) from Consenter | Not called (Privacy Mode) | W.consent(true) after consent |
| 4 | Registration / email gate | Media customisation | Off | On |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Wistia is a US enterprise subject to the US CLOUD Act; list the United States.
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Unlock additional website features | Unlock additional website features, Support marketing analytics |
| Tracking method | No tracking | Third party tracking (crosssession, cross-website) |
| Identifier | No identifier | Device identifiers, Direct identifier (email gate) |
| Data categories | Aggregated site statistics, IP address anonymised | Browsing and interaction data, Device characteristics, Device identifiers, IP address, User-provided data, direct identifier, Privacy choices |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | — | Per Wistia cookie documentation |
| 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