Disclaimer and Privacy Policy

G.I. Joe Mainframe

Disclaimer:

This site is not sponsored or endorsed by Hasbro, Inc or Takara Ltd.

G.I. Joe, “A Real American Hero”, its associated logos, COBRA, M.A.S.K., all character, group, and vehicle names and their respective likenesses are registered trademarks of Hasbro, Inc. Transformers, Beast Wars, Beast Machines, Armada, Generation One, Energon, Alternators, Binaltech, and Microman are copyrights and trademarks of Hasbro Inc. and Takara Ltd. All other comic book material is a copyright of the copyright holders.

G.I. Joe, the logo, Cobra, all character, group, and vehicle names and their respective likenesses are trademarks of Hasbro. All other comic book material is a copyright of the copyright holders.

Copyrighted works that are part of this web site are being used under the “fair use” doctrine. Section 107 of the Copyright Act provides as follows:

[T]he fair use of a copyrighted work, including such use by reproduction in copies or phonorecords or by any other means specified by [Section 106 of the Copyright Act], for purposes such as criticism, comment, news reporting, teaching (including multiple copies for classroom use), scholarship, or research, is not an infringment of copyright.

Absolutely no images or text may be taken from this site without our express written permission.

 

Privacy Policy

JoeBattleLines is committed to protecting the privacy of our visitors.

This notice applies to all information collected on the JoeBattleLines Web site or submitted to JoeBattleLines at any time through any Service Pages.

Personally Identifiable Information – Every computer connected to the Internet is given a domain name and a set of numbers, that serve as that computer’s “Internet Protocol” IP address. When a visitor requests a page from any Web site within the JoeBattleLines Network, our Web servers automatically recognize that visitor’s domain name and IP address.

We use security measures to protect against the loss, misuse and alteration of data used by our system. We will never share, sell, or rent individual personal information with anyone without your advance permission or unless ordered by a court of law. Information submitted to us is only available to employees managing this information for purposes of contacting you or sending you emails based on your request for information and to contracted service providers for purposes of providing services relating to our communications with you.

From time to time, JoeBattleLines or its advertisers may send a “cookie” to your computer. A cookie is a small piece of data that is sent to your Internet browser from a Web server and stored on your computer’s hard drive. A cookie can’t read data off of your computer hard disk or read cookie files created by other Web sites. Cookies do not damage your system. We use cookies to identify which areas of the JoeBattleLines you have visited or customized, so the next time you visit, those pages may be readily accessible. Our advertisers may also use cookies to ascertain how many times you’ve seen an advertisement. Our advertisers and we may use this information to better personalize the content, banners, and promotions that you see on our site. You can choose whether to accept cookies by changing the settings of your Internet browser. You can reset your browser to refuse all cookies, or allow your browser to show you when a cookie is being sent. If you choose not to accept these cookies, your experience at our Site and other Web sites may be diminished and some features may not work as intended.

The JoeBattleLines Network contains many hyperlinks to third party Web sites. The JoeBattleLines Network also contains advertisements of third parties. JoeBattleLines is not responsible for the privacy practices or the content of such third party Web sites or advertisers. JoeBattleLines does not share any of the individual personal information you provide JoeBattleLines with the third parties to which JoeBattleLines links, except as stated elsewhere within this Privacy Policy, although JoeBattleLines may share general, aggregate data with such third parties (such as how many people use our site). Please check with those Web sites to determine their privacy policy.

Please keep in mind that whenever you voluntarily disclose personal information online – for example through e-mail, discussion lists, or elsewhere – that information can be collected and used by others. In short, if you post personal information online that is accessible to the public, you may receive unsolicited messages from other parties in return.

Ultimately, you are solely responsible for maintaining the secrecy of your personal information. Please be careful and responsible whenever you’re online.

By using the JoeBattleLines Network, you consent to the collection and use of information by JoeBattleLines as specified above. If we decide to change our privacy policy, we will post those changes on this page so that you are always aware of what information we collect, how we use it, and under what circumstances we disclose it.

Specific Functions:

In order for this website to function, there are certain modules and functions that need to be enabled.  In order to provide full transparency, we’ve included exactly what data is collected by each component and how it will be used.

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.

 

Ads

 

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.

 

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.

 

Contact Form

 

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.

 

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.

 

Infinite Scroll

 

Data Used: In order to record page views via WordPress.com Stats (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.

 

Activity Tracked: 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 to work with this feature, a page view event will also be sent to the appropriate Google Analytics account with each additional load.

 

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.

 

Mobile Theme

 

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.

 

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.

 

 

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. By default, DNT is currently not honored.

 

WordPress.com Toolbar

 

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.