Jetpack privacy policy helper

The Activity Log feature only records the activities of a site’s registered users, and the retention duration of activity data will depend on the site’s plan and activity type.

Data used: To deliver this functionality and record activities around site management, the following information is captured: user email address, user role, user login, user display name, WordPress.com and local user IDs, the activity to be recorded, the WordPress.com-connected site ID of the site on which the activity takes place, the site’s Jetpack version, and the timestamp of the activity. Some activities may include the actor’s IP address (login attempts, for example) and user agent.

Activity tracked: Login attempts/actions, post and page update and publish actions, comment/pingback submission and management actions, plugin and theme management actions, widget updates, user management actions, and modifying other various site settings and options. The retention duration of activity data depends on the site’s plan and activity type. See the complete list of currently recorded activities (along with retention information).

Data synced: Successful and failed login attempts, which will include the actor’s IP address and user agent. See more about what data Jetpack syncs.

The Ads feature is only available to sites on the Security and Complete plans.

Data used: The following information (made available from the visitor’s browser) is collected and sent to Automattic’s Demand Partners: IP address, geographical data (derived from the IP address), user agent, operating system, device type, unique user ID (randomly generated identifier), current URL, and IAB (Interactive Advertising Bureau) interest category. The advertising partners may use that information to display personalized ads to those visitors. Sharing this information with our advertising partners may be considered a “sale” of information under the CCPA. Log data (IP address, geographical data, user agent, operating system, device type) is stored for 30 days. The unique user ID is stored in cookies and is retained for 1 year.

Activity tracked: Ad impressions, video-related events (i.e. pause, mute, 100% plays, etc.) or errors, and ad click events. Various cookies are used to deliver targeted advertisements to specific visitors, store user identifiers, and collect anonymous ad platform stats

The Brute Force attack protection feature blocks unwanted login attempts from malicious botnets and distributed attacks.

Data used: To check login activity and potentially block fraudulent attempts, the following information is used: the attempting user’s IP address, the attempting user’s email address/username (i.e., according to the value they were attempting to use during the login process), and all IP-related HTTP headers attached to the attempting user.

Activity tracked: Failed login attempts (these include IP address and user agent). We also set a cookie (jpp_math_pass) for 1 day to remember if/when a user has successfully completed a math captcha to prove that they’re a real human. Learn more about this cookie.

Data synced: Failed login attempts contain the user’s IP address, attempted username or email address, and user agent information. See more about what data Jetpack syncs.

The Carousel feature creates a gorgeous full-screen photo-browsing gallery.

Image views are only recorded if the site owner, has explicitly enabled image view stats tracking for this feature via the jetpack_enable_carousel_stats filter.

Data used: If image view tracking is enabled, the following information is used: IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, country code.

Activity tracked: Image views.

The Comment Likes feature gives your users the power to show comments some love.

This feature is only accessible to users logged in to WordPress.com.

Data used: To process a comment like, the following information is used: WordPress.com user ID/username (you must be logged in to use this feature), the local site-specific user ID (if the user is signed in to the site on which the like occurred), and a true/false data point that tells us if the user liked a specific comment. If you perform a like action from one of our mobile apps, additional information is used to track the activity: IP address, user agent, timestamp of event, blog ID, browser language, country code, and device info.

Activity tracked: Comment likes.

The Contact Form feature captures contacts, leads, and questions from your posts and pages, with the power of Jetpack Forms.

Data used: If Akismet is enabled on the site, the contact form submission data — IP address, user agent, name, email address, website, and message — is submitted to the Akismet service (also owned by Automattic) for spam checking. The actual submission data is stored in the site’s database on which it was submitted and is emailed directly to the owner of the form (i.e. the site author who published the page on which the contact form resides). This email will include the submitter’s IP address, timestamp, name, email address, website, and message.

Data synced: Post and post metadata associated with a user’s contact form submission. If Akismet is enabled on the site, the IP address and user agent originally submitted with the comment are also synced, as they are stored in the post meta. See more about what data Jetpack syncs.

The Donations Block feature facilitate the accepting of credit and debit card payments for donations, tips, and other forms of contribution.

This feature is only available to sites on the Security and Complete plans.

Data used: To facilitate new signups and renewals, the following is sent to Stripe (governed by Stripe TOS): name, Credit Card number, CVV, and Expiry date. Note that the credit card details are not stored by us—this data is collected and stored by Stripe. WordPress.com systems are fully PCI compliant.

Activity tracked: We plan to store anonymized analytics about which step in the purchase process was reached to improve the user experience. Cookies may be stored to implement content blocking in the future.

Data synced: We create a new WordPress.com account for the user or use the account associated with the email the customer gives us. An explanation of WordPress.com data used can be found here. The history of signups and billing facilitated via this feature is stored on WordPress.com servers for accounting and subsequent renewal purposes. To renew a subscription, on our servers we store: the safely encrypted Stripe ID of the credit card connected to subscription, user ID that initiated the purchase, the details about the product, the payment history for the subscription, the last 4 digits of the credit card and the brand – what is known in the industry as “safe details”. Also, we connect the ID of the credit card to the WordPress.com user ID, which allows for one-click payments on other subscription products sold on the WordPress.com network. See more about what data Jetpack syncs.

The GIF Block feature embeds an animated GIF image into a post or page on your site

Data used: An iframe is inserted into the page using an HTTP connection. The iframe is governed by Giphy’s privacy policy.

Activity tracked: We don’t track any activity. For details of what Giphy tracks, refer to their privacy policy.

This feature has been deprecated.

Data used: Please refer to the appropriate Google Analytics documentation for the specific type of data it collects. For sites running WooCommerce (also owned by Automattic) and this feature simultaneously and having all purchase tracking explicitly enabled, purchase events will send Google Analytics the following information: order number, product ID and name, product category, total cost, and quantity of items purchased. Google Analytics does offer IP anonymization, which can be enabled by the site owner.

Activity tracked: This feature sends page view events (and potentially video play events) to Google Analytics for consumption. For sites running WooCommerce-powered stores, additional events are also sent to Google Analytics: shopping cart additions and removals, product listing views and clicks, product detail views, and purchases. Tracking for each specific WooCommerce event needs to be enabled by the site owner.

The Gravatar Hovercards feature makes your Gravatar information visible to others.

Data used: This feature will send a hash of the user’s email address (if they are logged in to the site or WordPress.com—or if they submitted a comment on the site using their email address that is attached to an active Gravatar profile) to the Gravatar service (also owned by Automattic) to retrieve their profile image.

The Infinite Scroll feature displays next posts to your readers, so they can keep browsing without having to click.

Data used: To record page views via Jetpack Stats (which must be enabled for page view tracking here to work) with additional loads, the following information is used: IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, and country code.

Activity tracked: Page views will be tracked with each additional load (i.e. when you scroll down to the bottom of the page and a new set of posts loads automatically). If the site owner has enabled Google Analytics to work with this feature, a page view event will also be sent to the appropriate Google Analytics account with each additional load.

The Jetpack Comments feature integrates social media login options into your comment form.

Data used: Commenter’s name, email address, site URL (if provided via the comment form), timestamp, and IP address. Additionally, a jetpack.wordpress.com IFrame receives the following data: WordPress.com blog ID attached to the site, ID of the post on which the comment is being submitted, commenter’s local user ID (if available), commenter’s local username (if available), commenter’s site URL (if available), MD5 hash of the commenter’s email address (if available), and the comment content. If Akismet (also owned by Automattic) is enabled on the site, the following information is sent to the service for the sole purpose of spam checking: commenter’s name, email address, site URL, IP address, and user agent.

Activity tracked: The comment author’s name, email address, and site URL (if provided during the comment submission) are stored in cookies. Learn more about these cookies.

Data synced: All data and metadata (see above) associated with comments. This includes the comment’s status and, if Akismet is enabled on the site, whether or not it was classified as spam by Akismet. See more about what data Jetpack syncs.

The Jetpack Stats feature tracks your site visits and other valuable insights, so you can drive more traffic to your website

Data used: IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, and country code. Important: the site owner does not have access to any of this information via this feature. For example, a site owner can see that a specific post has 285 views, but he/she cannot see which specific users/accounts viewed that post. Stats logs — containing visitor IP addresses and WordPress.com usernames (if available) — are retained by Automattic for 28 days and are used for the sole purpose of powering this feature.

Activity tracked: Post and page views, video plays (if videos are hosted by WordPress.com), outbound link clicks, referring URLs and search engine terms, and country. Jetpack also tracks performance on each page load when this feature is enabled, including the JavaScript file used for tracking stats. This is exclusively for aggregate performance tracking across Jetpack sites to make sure that our plugin and code are not causing performance issues. This includes tracking page load times and resource loading duration (image files, JavaScript files, CSS files, etc.). The site owner has the ability to force this feature to honor DNT settings of visitors. By default, DNT is currently not honored.

The Latest Instagram Post feature displays your most recent images from Instagram on your site.

Data used: The images are loaded into the post content with an API request in PHP.

The Likes feature allows visitors to show their appreciation for your posts.

This feature is only accessible to users logged in to WordPress.com.

Data used: To process a post-like action, the following information is used: IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID (on which the post was liked), post ID (of the post that was liked), user agent, timestamp of event, browser language, country code.

Activity tracked: Post likes.

The Map Block feature adds a map to any post or page on your site.

Activity tracked: We don’t track anything. Refer to the Mapbox privacy policy for details of any activity they track.

The Mobile Theme feature has been discontinued.

Data used: A visitor’s preference for viewing the mobile version of a site.

Activity tracked: A cookie (akm_mobile) is stored for 3.5 days to remember whether or not a site visitor wishes to view its mobile version. Learn more about this cookie.

The Notifications feature makes sure that you can receive notifications for new comments and Likes on your WordPress.com and Jetpack sites.

This feature is only accessible to registered site users who are logged in to WordPress.com.

Data used: IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code. This feature may send visitor-related information or activity to the site owner. This may include: email address, WordPress.com username, site URL, email address, comment content, follow actions, etc.

Activity tracked: Sending notifications (i.e. when we send a notification to a particular user), opening notifications (i.e. when a user opens a notification that they receive), performing an action from within the notification panel (e.g. liking a comment or marking a comment as spam), and clicking on any link from within the notification panel/interface.

The Payments Block feature adds a payment button, collect donations, or add paid content to any post or page

This feature is only available to sites on the Security and Complete plans.

Data used: To facilitate new signups and renewals, the following is sent to Stripe (governed by Stripe TOS): name, Credit Card number, CVV, and Expiry date. Note that the credit card details are not stored by us—this data is collected and stored by Stripe. WordPress.com systems are fully PCI compliant.

Activity tracked: We plan to store anonymized analytics about which step in the purchase process was reached to improve the user experience. Cookies may be stored to implement content blocking in the future.

Data synced: We create a new WordPress.com account for the user or use the account associated with the email the customer gives us. An explanation of WordPress.com data used can be found here. The history of signups and billing facilitated via this feature is stored on WordPress.com servers for accounting and subsequent renewal purposes. To renew a subscription, on our servers, we store the safely encrypted Stripe ID of the credit card connected to the subscription, the user ID that initiated the purchase, the details about the product, the payment history for the subscription, the last 4 digits of the credit card and the brand – what is known in the industry as “safe details”. Also, we connect the ID of the credit card to the WordPress.com user ID, which allows for one-click payments on other subscription products sold on the WordPress.com network. See more about what data Jetpack syncs.

The Pay with PayPal feature makes your site accept PayPal payments from any post or page.

This feature is only available to sites on the Security and Complete plans, and PayPal handles the actual payment processing.

Data used: Transaction amount, transaction currency code, product title, product price, product ID, order quantity, PayPal payer ID, and PayPal transaction ID.

Activity tracked: The PayPal payer ID, transaction ID, and HTTP referrer are sent with a payment completion tracking event attached to the site owner.

Data synced: PayPal transaction ID, PayPal transaction status, PayPal product ID, quantity, price, customer email address, currency, and payment button CTA text. See more about what data Jetpack syncs.

Because payments are processed by PayPal, we recommend reviewing its privacy policy.

The Pinterest Block feature has been included in the WordPress Core blocks.

Data used: A pin is embedded using JavaScript resources loaded from Pinterest directly.

Activity tracked: We don’t track any activity. For details of what Pinterest tracks, refer to their privacy policy.

The Repeat Visitor Block feature shows what’s inside the page or post depending on how many times a visitor has visited the page.

Data used: The Repeat Visitor block records page views by setting a cookie named `jp-visit-counter` in the visitor’s browser, which is incremented on each visit. This cookie is stored only in the browser and not recorded in our databases.

The Search feature delivers the most relevant results to your visitors.

This feature is only available to sites on the Complete or Search plan.

Data used: We use any of the visitor-chosen search filters and query data to process the search request on the WordPress.com servers. We also use aggregate data about page views and searches to adjust our search results.

Activity tracked: We anonymously track when and what visitors search for and click on. This data is used to improve our search algorithms and track how well the search is working. This tracking includes: IP address, URL, user agent, timestamp of event, browser language, country code, search query, and filters.

The Sharing feature helps your readers spread your message across the web.

Data used: When official sharing buttons are active on the site, each button loads content directly from its service to display the button, information, and tools for the sharing party. As a result, each service can, in turn, collect information about the sharing party.

When a non-official Facebook or Pinterest sharing button is active on the site, information such as the sharing party’s IP address and the page URL will be available for each service, so sharing counts can be displayed next to the button.

When sharing content via email (this option is only available if Akismet is active on the site), the following information is used: sharing party’s name and email address (if the user is logged in, this information will be pulled directly from their account), IP address (for spam checking), user agent (for spam checking), and email body/content. This content will be sent to Akismet (also owned by Automattic) so that a spam check can be performed. Additionally, if the site owner enables reCAPTCHA (by Google), the sharing party’s IP address will be shared with that service. You can find Google’s privacy policy here.

The Newsletter feature transforms your blog posts into newsletters to easily reach your subscribers.

Data used: To initiate and process subscriptions, the following information is used: the subscriber’s email address and the ID of the post or comment (depending on the specific subscription being processed). In the event of a new subscription being initiated, we also collect some basic server data, including all of the subscribing user’s HTTP request headers, the IP address from which the subscribing user is viewing the page, and the URI which was given to access the page (REQUEST_URI and DOCUMENT_URI). This server data is used to monitor and prevent abuse and spam.

Activity tracked: Functionality cookies are set for 347 days to remember a visitor’s blog and post subscription choices if, in fact, they have an active subscription.

The VideoPress feature loads videos more quickly, and say good-bye to third-party video players on your website.

This feature is only available to sites on a VideoPress or Complete plan.

Data used: For video play tracking via Jetpack Stats, the following information is used: the viewer’s IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, and country code. If Google Analytics is enabled, video play events will also be sent there.

Activity tracked: Video plays.

The WhatsApp Button Block feature allows your customers to send you a message to inquire about your product or services or to ask for support.

Activity tracked: We don’t track any activity. For details of what WhatsApp tracks, refer to WhatsApp’s privacy policy.

The WooCommerce Shipping & Tax feature gets your WooCommerce store “ready to sell” as quickly as possible by taking care of tax calculation, payment processing, and shipping label printing.

Data used: For payments with PayPal or Stripe: purchase total, currency, billing information. For taxes: the value of goods in the cart, the value of shipping, and destination address. For checkout rates: destination address, purchased product IDs, dimensions, weight, and quantities. For shipping labels: customer’s name, address as well as the dimensions, weight, and quantities of purchased products.

Data synced: For payments, we send the purchase total, currency, and customer billing information to the respective payment processor. For more details, please see the respective third party’s privacy policy (Stripe’s Privacy Policy and PayPal’s Privacy Policy). For automated taxes, we send the value of goods in the cart, the value of shipping, and the destination address to TaxJar. Please see TaxJar’s Privacy Policy for details about how they handle this information. For checkout rates, we send the destination ZIP/postal code and purchased product dimensions, weight and quantities to the carrier directly or via EasyPost, depending on the service used. For shipping labels, we send the customer’s name, address, as well as the dimensions, weight, and quantities of purchased products to EasyPost. We also store the purchased shipping labels on our server to make it easy to reprint them and handle support requests. See more about what data Jetpack syncs.

The WordPress.com Secure Sign On feature makes you register for and sign in to self-hosted WordPress.org sites quickly and securely.

This feature is only accessible to registered users of the site with WordPress.com accounts.

Data used: User ID (local site and WordPress.com), role (e.g., administrator), email address, username, and display name. Additionally, for activity tracking (see below): IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, and country code.

Activity tracked: The following usage events are recorded: starting the login process, completing the login process, failing the login process, successfully being redirected after login, and failing to be redirected after login. Several functionality cookies are also set, which are detailed explicitly in our cookie documentation.

Data synced: The user ID and role of any user who successfully signed in via this feature. See more about what data Jetpack syncs.

The WordPress.com Toolbar feature has been deprecated.

This feature is only accessible to registered users of the site who are also logged in to WordPress.com.

Data used: Gravatar image URL of the logged-in user to display it in the toolbar and the WordPress.com user ID of the logged-in user. Additionally, for activity tracking (detailed below): IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code.

Activity tracked: Click actions within the toolbar.