I’m so glad you’re here at HISsparrowBlog! Let’s talk data protection so we’re all clear on what’s what.
When you visit HISsparrowBlog, there are several ways information can be received about you. I collect the minimal amount of information needed, and none of the information is used to personally identify you or sold to a third party.
Below are situations where HISsparrowBlog or the services I use receive information when you visit:
- Comments and Comment Likes
- Post Likes
- Contact forms
- Analytics and traffic logs
For the purposes of my site, each of these things is performed by a service. These services allow me to run my site and are listed below:
- WordPress: Blogging platform by Automattic
- Jetpack: Security Plugin for WordPress by Automattic
- Mad Mimi: Email marketing service by GoDaddy
Now I’d like to go into the specifics of what each service does for me, the information they collect, and your options.
What the Services Do and the Data They Collect
This is the service I use to bring HISsparrowBlog to you. However, WordPress uses other services to provide their service – like Jetpack.
I believe it’s a hardware/software kind of relationship.
See Jetpack (below) for those particular services.
For more information on the collection and use of data by Word press, visit the Automattic Privacy Notice for Visitors to Our Users’ Sites.
Jetpack is a security plugin for my WordPress site, but it really does a lot more than that. It gives me the ability to:
- Design and customize my site.
- Share my posts to social media (Facebook, Pinterest, and Twitter).
- Secure my site.
- Monetize my site with WordAds.
- Receive comments and comment likes from readers.
- Allow commenters to add a profile picture to their comment using Gravatar.
- And more.
What information does Jetpack receive about me?
For each service Jetpack provides, I’ve copied the text from their site that details the specific information they receive and why.
This feature only records 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 also include the actor’s IP address (login attempts, for example) 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 the modification of 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, which will include the actor’s IP address and user agent.
Data Used: The following information (made available from the visitor’s browser) is collected and sent to Automattic’s 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.
Activity Tracked: 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.
Data Used: Commenter’s name, email address, and 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. Learn more about these cookies.
Data Synced (?): All data and metadata (see above) associated with comments. This includes the status of the comment and, if Akismet is enabled on the site, whether or not it was classified as spam by Akismet.
This feature is only accessible to users logged in to WordPress.com.
Data Used: In order to process a comment like, 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 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, 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.
Activity Tracked: Comment likes.
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 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’s IP address, timestamp, name, email address, website, and message.
Data Synced (?): Post and post meta data 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 synced, as well, as they are stored in post meta.
Data used: This feature will send a hash of the user’s email address (if 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) in order to retrieve their profile image.
Data Used: A visitor’s preference on viewing the mobile version of a site.
Activity Tracked: A cookie (akm_mobile) 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.
This feature is only accessible to registered users of the site who are 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. 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.
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.
Data Used: In order to check login activity and potentially block fraudulent attempts, the following information is used: attempting user’s IP address, 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. 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.
Subscriptions (Mad Mimi is now my primary subscription/email marketing service. Keep reading for information on that.)
Data Used: To initiate and process subscriptions, the following information is used: 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 in order to access the page (REQUEST_URI and DOCUMENT_URI). This server data used for the exclusive purpose of monitoring and preventing abuse and spam.
Activity Tracked: Functionality cookies are set for a duration of 347 days to remember a visitor’s blog and post subscription choices if, in fact, they have an active subscription.
This feature is only available to sites on the 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, country code. If Google Analytics is enabled, video play events will be sent there, as well.
Activity Tracked: Video plays.
WordPress.com Secure Sign On
This feature is only accessible to registered users of the site with WordPress.com accounts.
Data Used: User ID (local site and WordPress.com), role (e.g. administrator), email address, username and display name. Additionally, 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, country code.
Activity Tracked: 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.
Data Synced (?): The user ID and role of any user who successfully signed in via this feature.
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, 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.
This feature is only accessible to registered users of the site who are also logged in to WordPress.com.
Data Used: Gravatar image URL of the logged-in user in order to display it in the toolbar and the WordPress.com user ID of the logged-in user. Additionally, for activity tracking (detailed 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, country code.
Activity Tracked: Click actions within the toolbar.
For more information on Jetpack’s collection and usage of data, visit the Automattic Privacy Notice.
Mad Mimi is an email marketing service by GoDaddy.
It allows me to:
- Send automatic responses when readers subscribe to HISsparrowBlog.
- Send bi-weekly newsletters to those subscribers when new posts are published.
- Understand what’s working and what isn’t by tracking emails received, bounced, marked as spam, opened, forwarded, and what links are clicked inside the email.
You have the right to know what information is stored about you and to delete it.
I’ve outlined above what services I use and the information they process, but the only information I personally ask for and store are email addresses provided to me when a reader subscribes to my bi-weekly newsletter via Mad Mimi.
Along with this, Mad Mimi tracks what emails are received and opened, what links are clicked, and what emails are forwarded and shared to social media. You can choose to opt out of this tracking if you like (info below).
Here’s what you can do:
- Unsubscribe from my Newsletters:
- Click ‘Unsubscribe’ at the bottom of any HISsparrowBlog email and follow instructions, OR
- I can do it for you when you contact me.
- Disable tracking within emails (but still receive the bi-weekly newsletters).
- Click ‘Preferences’ at the bottom of any HISsparrowBlog email, and Mad Mimi will send you an email with a link to follow. After following the link, check the box that says ‘Don’t collect data about my email views and clicks,’ OR
- I can do it for you when you contact me.
- Delete Post Comments and Post Likes.
- Contact me and I’ll submit a request to WordPress.
I hope this page and the links provided gave you all the information you needed.
If you have any questions, contact me and I’ll do my best to help.
And please contact me if you see something I’ve missed, so I can make the necessary changes to this page.
I’ll continue to add items here as I find them.
Some Quick Links: