Privacy Policy

Privacy Policy

BACKGROUND:

MummyTravels understands that your privacy is important to you and that you care about how your personal data is used. I respect and value the privacy of everyone who visits this website, www.mummytravels.com and will only collect and use personal data in ways that are described here, and in a way that is consistent with my obligations and your rights under the law.

Please read this Privacy Policy carefully and ensure that you understand it. Your acceptance of this Privacy Policy is deemed to occur upon your first use of my site. If you do not accept and agree with this Privacy Policy, you must stop using My Site immediately.

  1. Definitions and Interpretation

In this Policy the following terms shall have the following meanings:

 

“Account” means an account required to access and/or use certain areas and features of My Site;
“Cookie” means a small text file placed on your computer or device by My Site when you visit certain parts of My Site and/or when you use certain features of My Site. Details of the Cookies used by My Site are set out in Part 14, below; and
“Cookie Law” means the relevant parts of the Privacy and Electronic Communications (EC Directive) Regulations 2003;

Information About Me

My Site is [owned and] operated by Cathy Winston, sole trader

Registered address: Unit 16935, PO Box 6945, London, W1A 6US

Data Protection Officer: Cathy Winston

Email address: hq@mummytravels.com

  1. What Does This Policy Cover?

This Privacy Policy applies only to your use of My Site. My Site may contain links to other websites. Please note that I have no control over how your data is collected, stored, or used by other websites and I advise you to check the privacy policies of any such websites before providing any data to them.

  1. What is Personal Data?

Personal data is defined by the General Data Protection Regulation (EU Regulation 2016/679) (the “GDPR”) as ‘any information relating to an identifiable person who can be directly or indirectly identified in particular by reference to an identifier’.

Personal data is, in simpler terms, any information about you that enables you to be identified. Personal data covers obvious information such as your name and contact details, but it also covers less obvious information such as identification numbers, electronic location data, and other online identifiers.

  1. What Are My Rights?

Under the GDPR, you have the following rights, which I will always work to uphold:

  1. The right to be informed about My collection and use of your personal data. This Privacy Policy should tell you everything you need to know, but you can always contact me to find out more or to ask any questions using the details in Part 15.
  2. The right to access the personal data I hold about you. Part 13 will tell you how to do this.
  3. The right to have your personal data rectified if any of your personal data held by me is inaccurate or incomplete. Please contact me using the details in Part 15 to find out more.
  4. The right to be forgotten, i.e. the right to ask me to delete or otherwise dispose of any of your personal data that I have. Please contact me using the details in Part 15 to find out more.
  5. The right to restrict (i.e. prevent) the processing of your personal data.
  6. The right to object to me using your personal data for a particular purpose or purposes.
  7. The right to data portability. This means that, if you have provided personal data to me directly, I am using it with your consent or for the performance of a contract, and that data is processed using automated means, you can ask me for a copy of that personal data to re-use with another service or business in many cases.
  8. Rights relating to automated decision-making and profiling. I do not use your personal data in this way.

For more information about My use of your personal data or exercising your rights as outlined above, please contact me using the details provided in Part 15.

Further information about your rights can also be obtained from the Information Commissioner’s Office or your local Citizens Advice Bureau.

If you have any cause for complaint about My use of your personal data, you have the right to lodge a complaint with the Information Commissioner’s Office.

  1. What Data Do We Collect?

Depending upon your use of My Site, I may collect some or all of the following personal data (please also see Part 14 on My use of Cookies and similar technologies and My Cookie Policy https://jetpack.com/support/cookies:

  • Name;
  • Email address;
  • IP address;
  • Web browser type and version;
  • Operating system;
  • A list of URLs starting with a referring site, your activity on My Site, and the site you exit to;
  1. How Do You Use My Personal Data?

Under the GDPR, I must always have a lawful basis for using personal data. This may be because the data is necessary for My performance of a contract with you, because you have consented to My use of your personal data, or because it is in My legitimate business interests to use it. Your personal data may be used for the following purposes:

  • Communicating with you. This may include responding to comments from you.
  • Supplying you with information by email that you have opted-in to (you may unsubscribe or opt-out at any time by contacting me
  • Analysing your use of My Site [and gathering feedback] to enable me to continually improve My Site and your user experience.
  • Adverts through third-party networks, including Google AdSense and Affiliate Window. Please see their privacy policy for further details.

 With your permission and/or where permitted by law, I may also use your personal data for marketing purposes, which may include contacting you by email with information. You will not be sent any unlawful marketing or spam. I will always work to fully protect your rights and comply with My obligations under the GDPR and the Privacy and Electronic Communications (EC Directive) Regulations 2003, and you will always have the opportunity to opt-out.

  1. How Long Will You Keep My Personal Data?

I will not keep your personal data for any longer than is necessary in light of the reason(s) for which it was first collected. Your personal data will therefore be kept for the following periods (or, where there is no fixed period, the following factors will be used to determine how long it is kept):

  • The life of this website
  1. How and Where Do You Store or Transfer My Personal Data?

I will only store or transfer your personal data in the UK. This means that it will be fully protected under the GDPR.

  1. Do You Share My Personal Data?

I will not share any of your personal data with any third parties for any purposes, subject to one important exception.

In some limited circumstances, I may be legally required to share certain personal data, which might include yours, if I am involved in legal proceedings or complying with legal obligations, a court order, or the instructions of a government authority.

  1. How Can I Control My Personal Data?
    • In addition to your rights under the GDPR, set out in Part 5, when you submit personal data via My Site, you may be given options to restrict My use of your personal data. In particular, I aim to give you strong controls on My use of your data for direct marketing purposes (including the ability to opt-out of receiving emails from me which you may do by unsubscribing using the links provided in My
    • You may also wish to sign up to one or more of the preference services operating in the UK: The Telephone Preference Service (“the TPS”), the Corporate Telephone Preference Service (“the CTPS”), and the Mailing Preference Service (“the MPS”). These may help to prevent you receiving unsolicited marketing. Please note, however, that these services will not prevent you from receiving marketing communications that you have consented to receiving.
  2. Can I Withhold Information?

You may access My Site without providing any personal data at all. You may restrict My use of Cookies. For more information, see Part 14.

  1. How Can I Access My Personal Data?

If you want to know what personal data I have about you, you can ask me for details of that personal data and for a copy of it (where any such personal data is held). This is known as a “subject access request”.

All subject access requests should be made in writing and sent to the email or postal addresses shown in Part 15.

There is not normally any charge for a subject access request. If your request is ‘manifestly unfounded or excessive’ (for example, if you make repetitive requests) a fee may be charged to cover My administrative costs in responding.

I will respond to your subject access request within one month and, in any case, not more than one month of receiving it. Normally, I aim to provide a complete response, including a copy of your personal data within that time. In some cases, however, particularly if your request is more complex, more time may be required up to a maximum of three months from the date I receive your request. You will be kept fully informed of My progress.

  1. How Do You Use Cookies?

My Site uses analytics services provided by Jetpack, which useS Cookies. Website analytics refers to a set of tools used to collect and analyse usage statistics, enabling me to better understand how people use My Site. For more details, please refer to My Cookie Policy https://jetpack.com/support/cookies

  1. How Do I Contact You?

To contact me about anything to do with your personal data and data protection, including to make a subject access request, please use the following details:

Email address: hq@mummytravels.com

Postal Address: Unit 16935, PO Box 6945, London, W1A 6US

  1. Changes to this Privacy Policy

I may change this Privacy Notice from time to time. This may be necessary, for example, if the law changes, or if I change My business in a way that affects personal data protection.

Any changes will be immediately posted on My Site and you will be deemed to have accepted the terms of the Privacy Policy on your first use of My Site following the alterations. I recommend that you check this page regularly to keep up-to-date.

 

Additional details regarding data use in relation to Jetpack functionality on www.mummytravels.com

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.

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.

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.

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

 

%d bloggers like this: