Our website address is: somewhatnerdy.com<\/a>.<\/p>\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.<\/span><\/em><\/strong><\/p>\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<\/a> and local user IDs, the activity to be recorded, the WordPress.com<\/a>-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 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 Data Synced (?<\/a>):<\/strong> Successful and failed login attempts, which will include the actor\u2019s IP address and user agent.<\/p>\n Data Used:<\/strong> The following information (made available from the visitor\u2019s browser) is collected and sent to Automattic\u2019s Demand Partners: IP address, geographical data (derived from the IP address), user agent, operating system, device type, unique user ID (randomly generated identifier), current URL, and IAB (Interactive Advertising Bureau) interest category. Log data (IP address, geographical data, user agent, operating system, device type) is stored for 30 days. The unique user ID is stored in cookies and is retained for 1 year.<\/p>\n Activity Tracked:<\/strong> Ad impressions, video-related events (i.e. pause, mute, 100% plays, etc.) or errors, and ad click events. Various cookies are used for the following purposes: delivering targeted advertisements to specific visitors, storing user identifiers, and collecting anonymous ad platform stats.<\/p>\n Data Used:<\/strong> If image view tracking is enabled, the following information is used: IP address, WordPress.com<\/a> user ID (if logged in), WordPress.com<\/a> username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, country code.<\/p>\n Activity Tracked:<\/strong> Image views.<\/p>\n Data Used:<\/strong> In order to process a comment like, the following information is used: WordPress.com<\/a> 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 true\/false data point that tells us if the user liked a specific comment. If you perform a like action from one of our mobile apps<\/a>, some additional information is used to track the activity: IP address, user agent, timestamp of event, blog ID, browser language, country code, and device info.<\/p>\n Activity Tracked:<\/strong> Comment likes.<\/p>\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 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 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 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 Data Used:<\/strong> This feature will send a hash of the user\u2019s email address (if logged in to the site or WordPress.com<\/a> \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 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<\/a> user ID (if logged in), WordPress.com<\/a> username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, country code.<\/p>\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 This feature is only accessible to users logged in to WordPress.com<\/a>.<\/span><\/em><\/strong><\/p>\n Data Used:<\/strong> In order to process a post like action, the following information is used: IP address, WordPress.com<\/a> user ID, WordPress.com<\/a> username, WordPress.com<\/a>-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.<\/p>\n Activity Tracked:<\/strong> Post likes.<\/p>\n Data Used:<\/strong> A visitor\u2019s preference on viewing the mobile version of a site.<\/p>\n Activity Tracked:<\/strong> A cookie ( This feature is only accessible to registered users of the site who are logged in to WordPress.com<\/a>.<\/span><\/em><\/strong><\/p>\n Data Used:<\/strong> IP address, WordPress.com<\/a> user ID, WordPress.com<\/a> username, WordPress.com<\/a>-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<\/a> username, site URL, email address, comment content, follow actions, etc.<\/p>\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 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 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 Data Used:<\/strong> Any of the visitor-chosen search filters and query data in order to process a search request on the WordPress.com<\/a> servers.<\/p>\n Data Used:<\/strong> When sharing content via email, 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 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 This feature is only accessible to registered users of the site with WordPress.com<\/a> accounts.<\/span><\/em><\/strong><\/p>\n Data Used:<\/strong> User ID (local site and WordPress.com<\/a>), role (e.g. administrator), email address, username and display name. Additionally, for activity tracking (see below): IP address, WordPress.com<\/a> user ID, WordPress.com<\/a> username, WordPress.com<\/a>-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code.<\/p>\n Activity Tracked:<\/strong> The following usage 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 functionality cookies are also set, and these are detailed explicitly in our Cookie documentation<\/a>.<\/p>\n Data Synced (?<\/a>):<\/strong> The user ID and role of any user who successfully signed in via this feature.<\/p>\n Data Used:<\/strong> IP address, WordPress.com<\/a> user ID (if logged in), WordPress.com<\/a> username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, country code. Important:<\/em> The site owner does not<\/strong> 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 \u2014 containing visitor IP addresses and WordPress.com<\/a> usernames (if available) \u2014 are retained by Automattic<\/a> for 28 days and are used for the sole purpose of powering this feature.<\/p>\n Activity Tracked:<\/strong> Post and page views, video plays<\/a> (if videos are hosted by WordPress.com<\/a>), 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<\/a>. By default, DNT is currently not honored.<\/p>\n This feature is only accessible to registered users of the site who are also logged in to WordPress.com<\/a>.<\/span><\/em><\/strong><\/p>\n Data Used:<\/strong> Gravatar image URL of the logged-in user in order to display it in the toolbar and the WordPress.com<\/a> user ID of the logged-in user. Additionally, for activity tracking (detailed below): IP address, WordPress.com<\/a> user ID, WordPress.com<\/a> username, WordPress.com<\/a>-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code.<\/p>\n Activity Tracked:<\/strong> Click actions within the toolbar.<\/p>\n <\/p>\n If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.<\/p>\n For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.<\/p>\n If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":"What personal data we collect and why we collect it<\/h2>\n
<\/h3>\n
Activity Log<\/h3>\n
\nAds<\/h3>\n
\nCarousel<\/h3>\n
\nComment Likes<\/h3>\n
\nContact Form<\/h3>\n
\nGoogle Analytics<\/h3>\n
\nGravatar Hovercards<\/h3>\n
\nInfinite Scroll<\/h3>\n
\nLikes<\/h3>\n
\nMobile Theme<\/h3>\n
akm_mobile<\/code>) 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<\/a>.<\/p>\n
\nNotifications<\/h3>\n
\nProtect<\/h3>\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
\nSearch<\/h3>\n
\nSharing<\/h3>\n
\nSubscriptions<\/h3>\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
\nWordPress.com<\/a> Secure Sign On<\/h3>\n
\nWordPress.com<\/a> Stats<\/h3>\n
\nWordPress.com<\/a> Toolbar<\/h3>\n
How long we retain your data<\/h2>\n
What rights you have over your data<\/h2>\n