Privacy Policy

Posted on by

At the DisneyCruiseLineBlog.com, the privacy of our visitors is extremely important. This Privacy Policy outlines the types of personal information that is received and collected and how it is used.

DisneyCruiseLineBlog.com does not claim to represent, is not affiliated with, endorsed by, employed by, authorized by, or officially connected with, Magical Cruise Company, Limited, dba Disney Cruise Line, or their parent company, The Walt Disney Company.

Content of DisneyCruiseLineBlog.com is ©2011-2018. Website content may not be reproduced in whole or in part without the prior written permission of DisneyCruiseLineBlog.com.

If you require any more information or have any questions about our privacy policy, please feel free to contact us.

This Privacy Policy is reviewed and revised from time to time. You will want to revisit it regularly. Your use of this site, in any and all forms, constitutes an acceptance of this Privacy Policy.

Last Updated: May 2018


What personal data we collect and why we collect it

From time to time we may ask you to include personal data, such as name, email address when submitting links, reviews, suggested updates, and personal navigators to the website. Email addresses submitted with reviews, updates and navigators are only used to contact you with regard to the submission. These submissions are different from our email list which is a separate sign up.

Newsletter

Users might be asked to subscribe to our newsletter by providing name and email address to receive communication from DisneyCruiseLineBlog.com. We use a secure op-in subscription system and we reserve the right to contact subscribers with information related to this website and blog. Subscribers may unsubscribe anytime and every email delivered will contain an “Unsubscribe” link.

Log Files – We use log files like many other websites. The information in the log files include:

  • Internet Protocol addresses (IP)
  • Types of browser
  • Internet Service Provider (ISP)
  • Date and time stamp
  • Referring and exit pages
  • Number of clicks
  • All of this information is not linked to anything that is personally identifiable.

Cookies

We use cookies to store information about visitor preferences and to record user-specific information on visits and pages the user views so as to provide a custom experience. In regard to third-party advertisers, DisneyCruiseLineBlog.com has no access or control over these cookies. You should review the respective privacy policies on any and all third-party ad servers for more information regarding their practices and how to opt-out.

If you leave a comment on our site 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 wish to disable cookies you may do so through your web browser options. Instructions for doing so and for other cookie-related management can be found on the specific web browsers’ websites.

DoubleClick DART Cookie

Google, a third party vendor, uses the DART cookie to serve ads on DisneyCruiseLineBlog.com. Users may opt out of the use of the DART cookie by visiting Google’s Content Network Privacy Policy.

Google Analytics Cookie

The Google Analytics Advertising cookie has been implemented on this site. I am not sure really what it does, but google suggested that we turn this feature on.

The retention period for data you send that is associated with cookies, user identifiers, or advertising identifiers is set at 26 months from the visitors last site visit.

According to Google, the Advertising Features includes Demographics and Interest reporting, Remarketing, GDN Impression Reporting, and the DoubleClick Campaign Manager integration. These Advertising Features, enable Google Analytics to collect data about our website traffic in addition to data collected through a standard Google Analytics implementation.

Google does provide the following option to opt-out for all website that may be utilizing the Google Anaytics Cookie across the web. For more on how Google uses data please visit their privacy page.

Amazon Affiliates Cookie

Amazon Affiliates, a third party system, uses cookies to serve advertisements and links to products on Amazon.com. You may read more about Amazon Affiliates and their Operating Agreement here.

Embedded content from other websites

Articles on this site 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.

DisneyCruiseLineBlog.com embeds maps provided by MarineTraffic.com, a third party vendor.  You can read more about MarineTraffic.com‘s terms of use here.  DisneyCruiseLineBlog.com does not control the ads included with the embedded ship tracking maps.

Weather data is provided by a third party, OpenWeatherMap. OpenWeatherMap offers detailed weather data and analytics for any city. This data is provided for your general information only, and should not be treated as an official forecast. Please consult your local and national weather reports for your weather making decisions.

Who we share your data with

In this section you should name and list all third party providers with whom you share site data, including partners, cloud-based services, payment processors, and third party service providers, and note what data you share with them and why. Link to their own privacy policies if possible.

How long we retain your data

If you leave a comment, submit a review, or link, the information 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. Additionally, the contact information is used if we need to follow up on the specific submission.

What rights you have over your data
If you have left comments, reviews, or links, 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.

Where we send your data

Visitor comments may be checked through an automated spam detection service.

Comment Likes

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.

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.

Jetpack Comments

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

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.

Sharing

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.

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

YouTube

YouTube uses cookies and we use YouTube to host our videos as well as other YouTube users’ videos on our website. For more on this please review the YouTube privacy policy.