Privacy Policy

The following Privacy Policy has been modified and used according to a Creative Commons Sharealike license, and was originally provided by the fine folks at Automattic, Inc., via their website, WordPress.com.

It is the policy of critiQal.com (“critiQal“) to respect your privacy regarding any information we may collect while operating our website.

Who We Are

Our website address is: https://critiqal.com.

What Personal Data We Collect And Why

Website Visitors

Like most website operators, critiQal collects non-personally-identifying information of the sort that web browsers and servers typically make available, such as the browser type, language preference, referring site, and the date and time of each visitor request. critiQal‘s purpose in collecting non-personally identifying information is to better understand how critiQal’s visitors use its website. From time to time, critiQal may release non-personally-identifying information in the aggregate, e.g., by publishing a report on trends in the usage of its website.

critiQal also collects potentially personally-identifying information like Internet Protocol (IP) addresses. critiQal does not use such information to identify its visitors, however, and does not disclose such information, other than under the same circumstances that it uses and discloses personally-identifying information, as described below.

Comments

When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.

An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Cookies

If you leave a comment on critiQal you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.

If you have an account and you log in to critiQal, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.

When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.

Contact Form

critiQal currently keeps contact form submissions indefinitely for customer service purposes, but we do not use the information submitted through them for marketing purposes.

Ads

Third party vendors, including Google, use cookies to serve ads based on your prior visits to critiQal or other websites. Users may opt out of personalized advertising by visiting Ads Settings or www.aboutads.info.

Embedded Content

Articles on critiQal may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.

These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracing your interaction with the embedded content if you have an account and are logged in to that website.

Akismet

Akismet collects information about visitors who comment on critiQal for their anti-spam plugin. The information they collect includes the commenter’s IP address, user agent, referrer, and Site URL (along with other information directly provided by the commenter such as their name, username, email address, and the comment itself).

Jetpack Features

  • Activity Log: This feature only records activities of a site’s registered users.
  • Notifications: This feature is only accessible to registered users of the site who are logged in to WordPress.com.
  • WordPress.com Secure Sign-On: This feature is only accessible to registered users of the site with WordPress.com accounts.
  • WordPress.com Toolbar: This feature is only accessible to registered users of the site who are also logged in to WordPress.com.

Data Used:

  • Activity Log: 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.
  • Gravatar Hovercards 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.
  • Mobile Theme: A visitor’s preference on viewing the mobile version of a site.
  • Notifications: 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.
  • Subscriptions: 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.
  • WordPress.com Secure Sign-On: 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.
  • WordPress.com Stats: 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.
  • WordPress.com Toolbar: 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:

  • Activity Log: 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).
  • Mobile Theme: A cookie (akm_mobile) is stored for 3.5 days to remember whether or not a visitor of critiQal wishes to view its mobile version.
  • Notifications: 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.
  • Subscriptions: 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: 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.
  • WordPress.com Stats: 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. By default, DNT is currently not honored.
  • WordPress.com Toolbar: Click actions within the toolbar.

Data Synced:

  • Activity Log: Successful and failed login attempts, which will include the actor’s IP address and user agent.
  • WordPress.com Secure Sign-On: The user ID and role of any user who successfully signed in via this feature.

Aggregated Statistics

critiQal may collect statistics about the behavior of visitors to its websites. However, critiQal does not disclose personally-identifying information other than as described below.

Protection of Certain Personally-Identifying Information

critiQal discloses potentially personally-identifying and personally-identifying information only to those of its employees, contractors and affiliated organizations that (i) need to know that information in order to process it on critiQal’s behalf or to provide services available at critiQal’s websites, and (ii) that have agreed not to disclose it to others. Some of those employees, contractors and affiliated organizations may be located outside of your home country; by using critiQal’s website, you consent to the transfer of such information to them. critiQal will not rent or sell potentially personally-identifying and personally-identifying information to anyone. Other than to its employees, contractors and affiliated organizations, as described above, critiQal discloses potentially personally-identifying and personally-identifying information only when required to do so by law, or when critiQal believes in good faith that disclosure is reasonably necessary to protect the property or rights of critiQal, third parties or the public at large.

If you are a registered user of critiQal‘s website and have supplied your email address, critiQal will not send you e-mail unless you specifically request us to do so, or you sign up for a critiQal e-mail list. If you send us a communication (for example via a comment or the “Contact Us” form), we reserve the right to publish it in order to help us clarify or respond to your request or to help us support other users. critiQal takes all measures reasonably necessary to protect against the unauthorized access, use, alteration or destruction of potentially personally-identifying and personally-identifying information.

How Long We Retain Your Data

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.

For users that register on critiQal, 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.

Where We Send Your Data

critiQal is located in the United States. Visitor comments may be checked through an automated spam detection service.

Contact Information

If you have any privacy-specific concerns, please don’t hesitate to contact Reid at privacycritiqal.com.

Privacy Policy Changes

Although most changes are likely to be minor, critiQal may change its Privacy Policy from time to time, and at critiQal’s sole discretion. critiQal encourages visitors to frequently check this page for any changes to its Privacy Policy. Your continued use of this site after any change in this Privacy Policy will constitute your acceptance of such change.