The Brute Attack Protection

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. 

Data synced: Failed login attempts contain the user’s IP address, attempted username or email address, and user agent information.

The Contact Form 

Captures contacts, leads, and questions from posts and pages.

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. 

The Gravatar Hovercards

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

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. 

The Stats feature 

Tracks website visits and insights to enhance the website users’ experience

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.

Likes

 Allows visitors to show their appreciation for our 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

Sharing

Helps our readers spread our 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.

Subscriptions (Newsletter)

Transforms our blog posts into newsletters to easily reach our 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.

Go back to our Privacy Policy