Activity Log
This feature only records 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 also 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 the modification of other various site settings and options. 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.
Data Used: If
Akismet and the Jetpack Contact Form 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 the sole purpose of spam checking. The actual submission data is stored in the database of the site 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 meta data 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 synced, as well, as they are stored in post meta.
Gravatar Hovercards
Data Used: This feature will send a hash of the user's email address (if 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) in order to retrieve their profile image.
Data Used: In order to record page views via
WordPress.com 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, 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.
Likes
This feature is only accessible to users logged in to WordPress.com.
Data Used: In order 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.
Mobile Theme
Data Used: A visitor's preference on 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 visitor of the site wishes to view its mobile version.
Learn more about this cookie.
Notifications
This feature is only accessible to registered users of the site 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. Some visitor-related information or activity may be sent to the site owner via this feature. 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.
Protect
Data Used: In order to check login activity and potentially block fraudulent attempts, the following information is used: attempting user's IP address, 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, which contain the user's IP address, attempted username or email address, and user agent information.
Sharing
Data Used: 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
reCAPTCHA (by Google) is enabled by the site owner, the sharing party's IP address will be shared with that service. You can find Google's privacy policy
here.
Subscriptions
Data Used: To initiate and process subscriptions, the following information is used: 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 in order to access the page (
REQUEST_URI
and
DOCUMENT_URI
). This server data used for the exclusive purpose of monitoring and preventing abuse and spam.
Activity Tracked: Functionality cookies are set for a duration of
347 days to remember a visitor's blog and post subscription choices if, in fact, they have an active subscription.
WooCommerce Services
Data Used: For payments with PayPal or Stripe: purchase total, currency, billing information.
For taxes: the value of goods in the cart, value of shipping, 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's billing information to the respective payment processor. Please see the respective third party's privacy policy (
Stripe's Privacy Policy and
PayPal's Privacy Policy) for more details. 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
USPS or
Canada Post, 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.
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, 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. When this module is enabled, Jetpack also tracks performance on each page load that includes the Javascript file used for tracking stats. This is exclusively for aggregate performance tracking across Jetpack sites in order to make sure that our plugin and code is not causing performance issues. This includes the tracking of 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.