Activity Log – Privacy

This 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) 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. 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 will include the actor’s IP address and user agent.

Booking Application – exporting booking information to the Google Calendar using Booking & Appointment for WooCommerce plugin,  customer data being exported to third party application. – Privacy

Carousel

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

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

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

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 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 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 (i.e., when you scroll down to the bottom of the page, 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.

Jetpack Comments

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. Suppose Akismet (also owned by Automattic) is enabled on the site. In that case, 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.

Likes

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.

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, country code. This feature may send the site owner some visitor-related information or activity. This may include email address, WordPress.com username, 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), 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: 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 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.

Search

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

Simple Payments

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

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

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

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, the following information is used: 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.

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 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 to power this feature.

Activity Tracked: Post and page views, video plays (if WordPress.com hosts videos), outbound link clicks, referring URLs and search engine terms, and country. Jetpack also tracks performance on each page load when this module is enabled, including the Javascript file used for tracking stats. This is exclusively for aggregate performance tracking across Jetpack sites to ensure 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 can force this feature to honor DNT settings of visitors. By default, DNT is currently not honored.