Set up your bannerConfigure Your ToolsWebsite and Shop Platforms

Jetpack

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

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Improve the service

Overview

This guide explains how to implement different privacy configurations for Jetpack Stats (WordPress plugin by Automattic) and how to reflect them in the Consenter Manager. Security features (Protect, Scan, WAF) are out of scope; sharing buttons and embeds loaded by Jetpack need their own entries.

  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. Jetpack Stats on the public front end.

What the service does in this scope. Automattic owns and operates Jetpack; its Privacy Center links to the Automattic privacy notice and the Jetpack cookie list. Automattic's cookie policy lists tk_ni, tk_ai and tk_qs for its first-party analytics on user sites.

Configurations included.

ConfigurationSummary
Configuration A — No entry neededStats module deactivated.
Configuration B — Medium riskStats active; the Stats script is blocked until Consenter consent.

Step 1 — Configure Jetpack

#Configuration areaWhere to configure itConfiguration A — No entry neededConfiguration B — Medium risk
1Processing purposesOperator decision—Improve the service
2Stats moduleJetpack → Settings / ModulesOffOn
3LoadingTheme / tag management—After Consenter consent

Step 2 — Map the configuration in the Consenter Manager

Processing location. Automattic is a US enterprise; list the United States.

Consenter Manager fieldConfiguration A — No entry neededConfiguration B — Medium risk
Entry neededNoYes
Processing purposes—Improve the service
Tracking methodNo trackingFirst party tracking (cross-session)
Identifier—Device identifiers
Data categories—Aggregated site statistics, Browsing and interaction data, Device identifiers, Device characteristics
Legal role of data recipient—Processor
Personalisation model—No personalisation
Maximum storage duration—Per Jetpack cookie list
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

On this page