Privacy Policy

Who we are

Here at NerdOfLinux.com, we value your privacy as much as our own. We understand your privacy concerns, and we hope this privacy policy will help you better understand the information we collect, and the reasons for collecting such information.

The personal data we collect and why

Standard Information– We collect standard server logs, which include,but are not limited to, the following information:

  • IP address
  • Date and time of access
  • Method(i.e. “Get or Post”)
  • The URL you access
  • What protocol you use(i.e. “https”)
  • Your user agent
    Here’s an example of our server logs:
127.0.0.1 - - [17/May/2018:16:35:14 -0500] "GET /tech/internet/a-rant-about-the-gdpr/ HTTP/1.1" 200 16090 "https://www.nerdoflinux.com/" "Mozilla/5.0 (X11; CrOS x86_64 10452.85.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.158 Safari/537.36"

This information is used mainly for debugging purposes, and is not automatically transmitted by us to third parties.

Analytics– We also use a few analytics services that keep track of things such as, but not limited to:

  • IP address
  • Date and time of access
  • URL you visit
  • Referrer(if applicable)
  • User agent
  • Device information(i.e. “iPhone 6”)

We use these analytics to allow us to better understand how users interact with our site. This, in turn, allows us to create more of the content that readers actually read. However, if you would not like to be tracked, you can turn off the majority of the analytics tools we use by enabling Do Not Track in your browser. However, please keep in mind that not allowing us to track which pages visitors go to, we can not know which content is liked more. We do NOT sell this information to any third parties.

Information you provide– We also store and log any information your provide us with(along with additional metadata), such as, but not limited to, when you submit a comment, or use our contact form. To have this data removed, please contact us.

Comments

Whenever you leave a comment on this site, certain information, including what you provide(such as your name and email) is logged and stored. This includes, but is not limited to:

  • IP address
  • User agent

along with any information you provide. This is stored so we can display the comment on our website, and the metadata helps us fight spam.

Contact Forms

Any information you supply us with in contact forms will be stored to allow us to process your request. Additional information will also be logged, such as, but not limited to:

  • IP address
  • User agent

Cookies

Similar to most other sites on the internet, we make use of cookies to assist us in gathering analytics, and personalize your experience. Some cookies are automatically set, and others are set when you do actions such as, but not limited to:

  • Sign in
  • Leave a comment

Additionally, when you leave a comment, you have the option to opt-in to save your information(i.e. email, name, site), and the cookie should automatically be removed in one year. Cookies are also set when you log in, and will be kept for around two weeks if you select the “Remember Me” option. When logging in, a temporary cookie is also set to determine if your browser accepts cookies.

Embeds

Some posts on this site may use content embedded from other sites. This embedded content will be as if you visited the site where the content is embedded from, and may collect information as stated in their privacy policy.

Who we share your data with

Aside from analytics, we do not automatically share your information with any other third party.

How long we retain your data

The majority of information you enter, or we collect, will be stored indefinitely, such as comments and their metadata. This allows us to keep comments on our site, and do things such as understand how this site is used.

What rights you have on your data

If you have an account, or have left a comment on this site, you may request to receive an exported file of the personal data we have on you. You can also request the deletion of such data, although that will not include information we keep for administrative, legal, or security purposes.

How we protect your data

We take the information you provide us seriously, and we have measures in place to prevent the unauthorized access of information that you have provided us with. These measures include the use of HTTPS, strong administrator passwords, etc.

Data breaches

In the unlikely even of a data breach, we will attempt to notify you by releasing a blog post and/or emailing you, if we have your email.

Contact

If you have any questions or requests, you can contact us by use of our contact form, or by email. We will try to respond to your request as quickly as we can, but we can not, and do not provide a guarantee.

Jetpack

This site uses the Jetpack plugin:

Activity Log

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.


Comment Likes

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.


Gravatar Hovercards

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.


Jetpack Comments

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.


Likes

This feature is only accessible to users logged in to WordPress.com.

Data Used: In order 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 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.


Protect

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.


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 reCAPTCHA (by Google) is enabled by the site owner, the sharing party’s IP address will be shared with that service. You can find Google’s privacy policy here.


Subscriptions

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.


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.


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