We do not intend to collect your personal data, however, WordPress plugins may collect your data. Jetpack is one such plugin, and it includes a free tool that can be used to explain exactly how data is obtained and used. <\/p>\n\n\n\n
This feature only records activities of a site\u2019s registered users, and the retention duration of activity data will depend on the site\u2019s plan and activity type.<\/em><\/strong><\/p>\n\n\n\n Data Used:<\/strong> 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\u2019s Jetpack version, and the timestamp of the activity. Some activities may also include the actor\u2019s IP address (login attempts, for example) and user agent.<\/p>\n\n\n\n Activity Tracked:<\/strong> 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\u2019s plan and activity type. See the complete list of currently-recorded activities (along with retention information)<\/a>.<\/p>\n\n\n\n Data Synced (?<\/a>):<\/strong> Successful and failed login attempts, which will include the actor\u2019s IP address and user agent.<\/p>\n\n\n\n Data Used:<\/strong> If Akismet<\/a> is enabled on the site, the contact form submission data \u2014 IP address, user agent, name, email address, website, and message \u2014 is submitted to the Akismet<\/a> service (also owned by Automattic<\/a>) 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\u2019s IP address, timestamp, name, email address, website, and message.<\/p>\n\n\n\n Data Synced (?<\/a>):<\/strong> Post and post meta data associated with a user\u2019s contact form submission. If Akismet<\/a> 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.<\/p>\n\n\n\n This feature is only available to sites on the Premium and Professional plans.<\/em><\/strong><\/p>\n\n\n\n Data Used:<\/strong> Please refer to the appropriate Google Analytics documentation<\/a> for the specific type of data it collects. For sites running WooCommerce<\/a> (also owned by Automattic<\/a>) 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<\/a>, which can be enabled by the site owner.<\/p>\n\n\n\n Activity Tracked:<\/strong> This feature sends page view events (and potentially video play events<\/a>) over 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. Tracking for each specific WooCommerce event needs to be enabled by the site owner.<\/p>\n\n\n\n Data Used:<\/strong> This feature will send a hash of the user\u2019s email address (if logged in to the site or WordPress.com \u2014 or if they submitted a comment on the site using their email address that is attached to an active Gravatar profile) to the Gravatar<\/a> service (also owned by Automattic<\/a>) in order to retrieve their profile image.<\/p>\n\n\n\n Data Used:<\/strong> In order to record page views via WordPress.com Stats<\/a> (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.<\/p>\n\n\n\n Activity Tracked:<\/strong> 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<\/a> to work with this feature, a page view event will also be sent to the appropriate Google Analytics account with each additional load.<\/p>\n\n\n\n This feature is only accessible to registered users of the site who are logged in to WordPress.com.<\/em><\/strong><\/p>\n\n\n\n Data Used:<\/strong> 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.<\/p>\n\n\n\n Activity Tracked:<\/strong> 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.<\/p>\n\n\n\n Data Used:<\/strong> In order to check login activity and potentially block fraudulent attempts, the following information is used: attempting user\u2019s IP address, attempting user\u2019s 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.<\/p>\n\n\n\n Activity Tracked:<\/strong> Failed login attempts (these include IP address and user agent). We also set a cookie ( Data Synced (?<\/a>):<\/strong> Failed login attempts, which contain the user\u2019s IP address, attempted username or email address, and user agent information.<\/p>\n\n\n\n Data Used:<\/strong> The Repeat Visitor block records page views by setting a cookie named `jp-visit-counter` in the visitor\u2019s browser, which is incremented on each visit. This cookie is stored only in the browser<\/strong> and not recorded in our databases.<\/p>\n\n\n\n This feature is only available to sites on the Professional plan.<\/em><\/strong><\/p>\n\n\n\n Data Used:<\/strong> Any of the visitor-chosen search filters and query data in order to process a search request on the WordPress.com servers.<\/p>\n\n\n\n Data Used:<\/strong> When official sharing buttons are active on the site, each button loads content directly from its service in order to display the button as well as 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 a Pinterest sharing button is active on the site, information such as the sharing party\u2019s IP address as well as 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<\/a> is active on the site), the following information is used: sharing party\u2019s 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<\/a> (also owned by Automattic<\/a>) so that a spam check can be performed. Additionally, if reCAPTCHA<\/a> (by Google) is enabled by the site owner, the sharing party\u2019s IP address will be shared with that service. You can find Google\u2019s privacy policy here<\/a>.<\/p>\n\n\n\n Data Used:<\/strong> To initiate and process subscriptions, the following information is used: subscriber\u2019s 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\u2019s 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 ( Activity Tracked:<\/strong> Functionality cookies<\/a> are set for a duration of 347 days<\/strong> to remember a visitor\u2019s blog and post subscription choices if, in fact, they have an active subscription.<\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" We do not intend to collect your personal data, however, WordPress plugins may collect your data. Jetpack is one such plugin, and it includes a free tool that can be used to explain exactly how data is obtained and used. Activity This feature only records activities of a site\u2019s registered users, and the retention duration… Continue reading Privacy Policy<\/span>
\n\n\n\nContact Form<\/h3>\n\n\n\n
\n\n\n\nGoogle Analytics<\/h3>\n\n\n\n
\n\n\n\nGravatar Hovercards<\/h3>\n\n\n\n
\n\n\n\nInfinite Scroll<\/h3>\n\n\n\n
Notifications<\/h3>\n\n\n\n
\n\n\n\nProtect<\/h3>\n\n\n\n
jpp_math_pass<\/code>) for 1 day to remember if\/when a user has successfully completed a math captcha to prove that they\u2019re a real human. Learn more about this cookie.<\/a><\/p>\n\n\n\n
\n\n\n\nRepeat Visitor Block<\/h3>\n\n\n\n
\n\n\n\nSearch<\/h3>\n\n\n\n
\n\n\n\nSharing<\/h3>\n\n\n\n
\n\n\n\nSubscriptions<\/h3>\n\n\n\n
REQUEST_URI<\/code> and DOCUMENT_URI<\/code>). This server data used for the exclusive purpose of monitoring and preventing abuse and spam.<\/p>\n\n\n\n
\n\n\n\n