Privacy Policy: Managing User Data Safely

Activity Log – Privacy

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 where the activity occurs, the site’s Jetpack version, and the activity’s timestamp. Some activities may include the actor’s IP address (e.g., login attempts) and the 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 various other site settings and options. The retention duration of activity data depends on the site’s plan and the activity type. See the complete list of currently recorded activities (along with retention information).

Data Synced (?): Successful and failed login attempts will include the actor’s IP address and user agent.

Booking Application

Exporting booking information to Google Calendar using the Booking & Appointment for WooCommerce plugin; customer data is being exported to a third-party application. – Privacy

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: When 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, event timestamp, browser language, and country code.

Activity Tracked: Image views.

Comment Likes

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

Data Used: To process a comment, 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 valid/false data point that tells us if the user liked a specific comment.

Suppose you perform a similar action from one of our mobile apps. Additional information is used to track activity: IP address, user agent, event timestamp, blog ID, browser language, country code, and device info.

Activity Tracked: Comment likes.

Contact Form

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 and emailed directly to the form owner (i.e., the site author who published the page hosting the contact form).

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.

Google Analytics

This feature is only available on sites with Premium and Professional plans.

Data Used: Please refer to the appropriate Google Analytics documentation for details on the specific types of data it collects. For sites running WooCommerce (also owned by Automattic) and this feature simultaneously, with 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 the site owner can enable.

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

Gravatar Hovercards

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.

Infinite Scroll

Data Used: 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, and country code.

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

Notifications

This feature is only accessible to registered site users 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, and country code.

This feature may send the site owner visitor-related information or activity data. This may include an email address, a WordPress.com username, a site URL, 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). Acting from within the notification panel. E.g., liking a comment, marking a comment as spam, or clicking any link within the notification panel/interface.

Protect

Data Used: To check login activity and potentially block fraudulent attempts, the following information is used. Attempting to retrieve the user’s IP address and the user’s email address/username.

i.e., according to the value they were attempting to use during the login process. All IP-related HTTP headers are associated with the user making the request.

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 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.

This feature is only available to sites on the Professional plan.

Data Used: Any of the visitor-chosen search filters and query data to process a search request on the WordPress.com servers.

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: the 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) for spam checking. 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.

Simple Payments

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

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

Activity: The PayPal payer ID, transaction ID, and HTTP referrer are sent. A payment completion tracking event is 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.

Because PayPal processes payments, we recommend reviewing its privacy policy.

Video Hosting

This feature is only available on sites with Premium and Professional plans.

Data Used: For video play tracking via WordPress.com Stats. Information 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, event timestamp, browser language, and country code. If Google Analytics is enabled, video play events will also be sent there.

Activity Tracked: Video plays.

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.

WordPress.com Secure Sign On

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

Data Used: User ID (local site and WordPress.com).Role (e.g., administrator), email address, username, and display name 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: 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 functional cookies are also set, explicitly detailed in our cookie documentation.

Data Synced (?): The user ID and role of any user who successfully signed in via this feature.

WordPress.com Stats

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.

Necessary: The site owner cannot access this information via this feature. For example, a site owner can see that a specific post has 285 views, but cannot see which specific users/accounts viewed it.

Stats logs — containing visitor IP addresses and WordPress.com usernames (if available) — are retained by Automattic for 28 days and are used to power this feature.

Activity Tracked: Post and page views, video plays (if WordPress.com hosts videos), outbound link clicks, referring URLs, search engine terms, and country. If this module is enabled,

Jetpack also tracks performance on each page load, including the JavaScript file that tracks stats. This is exclusively for aggregate performance tracking across

JP sites to ensure our plugin and code are not causing performance issues. This includes tracking page load times and resource load durations (e.g., image, JavaScript, and CSS files).

The site owner can force this feature to honor visitors’ DNT settings. By default, DNT is off.