{"id":2933,"date":"2018-05-22T17:24:23","date_gmt":"2018-05-23T00:24:23","guid":{"rendered":"http:\/\/www.gydlepublishing.com\/blog\/?page_id=2933"},"modified":"2018-05-23T17:12:34","modified_gmt":"2018-05-24T00:12:34","slug":"privacy-policy","status":"publish","type":"page","link":"http:\/\/www.gydlepublishing.com\/blog\/privacy-policy\/","title":{"rendered":"Privacy Policy"},"content":{"rendered":"

Who I am<\/strong><\/p>\n

This is a personal website and blog run by Mary Parlange, AKA Gydle. The website address is http:\/\/www.maryparlange.com\/blog, or http:\/\/www.gydlepublishing.com\/blog.<\/p>\n

Personal data I collect and why I collect it<\/b><\/p>\n

Subscriptions<\/b><\/p>\n

Data Used: To initiate and process subscriptions, the following information is used: subscriber\u2019s 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\u2019s 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.<\/p>\n

Activity Tracked: Functionality cookies<\/a> are set for a duration of 347 days to remember a visitor\u2019s blog and post subscription choices if, in fact, they have an active subscription.<\/p>\n

My e-mail subscription is a double agreement (you\u2019ll get an e-mail asking if you REALLY want to subscribe, and you\u2019ll have to click a link in that mail). Every e-mail that is sent to you includes an \u201cunsubscribe\u201d option so you can opt out at any time.<\/p>\n

Comments<\/strong><\/p>\n

Data Used: Commenter\u2019s 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\u2019s local user ID (if available), commenter\u2019s local username (if available), commenter\u2019s site URL (if available), MD5 hash of the commenter\u2019s email address (if available), and the comment content.\u00a0Akismet<\/a> (also owned by Automattic<\/a>) is enabled on the site, so the following information is sent to the service for the sole purpose of spam checking: commenter\u2019s name, email address, site URL, IP address, and user agent.<\/p>\n

Activity Tracked: The comment author\u2019s name, email address, and site URL (if provided during the comment submission) are stored in cookies.<\/p>\n

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.<\/p>\n

Contact forms and enquiries<\/b><\/p>\n

When people contact me through the contact form on the About page – or any of the other contact methods mentioned on my website, I may use the personal data you provide in order to respond to your enquiry.\u00a0\u00a0I use\u00a0Akismet, so\u00a0the contact form submission data \u2014 IP address, user agent, name, email address, website, and message \u2014 is submitted to the Akismet<\/a> service (also owned by Automattic<\/a>) 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\u2019s IP address, timestamp, name, email address, website, and message.<\/p>\n

Embedded content from other websites<\/b><\/p>\n

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.<\/p>\n

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.<\/p>\n

Analytics<\/b><\/p>\n

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: I do not have access to any of this information via this feature. E.G: I can see that a specific post has 285 views, but I cannot see which specific users\/accounts viewed that post. Stats logs \u2014 containing visitor IP addresses and WordPress.com usernames (if available) \u2014 are retained by Automattic<\/a> for 28 days and are used for the sole purpose of powering this feature.<\/p>\n

Activity Tracked: Post and page views, video plays<\/a> (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.).\u00a0<\/span><\/p>\n

I have \u201cinfinte scroll\u201d enabled, to help me with stats for the site. Data used: In order to record page views via WordPress.com Stats<\/a> (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.<\/p>\n

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).<\/p>\n

Cookies <\/b><\/p>\n

If you leave a comment on my 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.<\/p>\n

Site Protection <\/b><\/p>\n

I\u2019m the only registered user for the site. If someone tries to login as a user, I\u2019ll collect the following information in order to block them: attempting user\u2019s IP address, attempting user\u2019s 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.<\/p>\n

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\u2019re a real human.<\/p>\n

Who I share your data with<\/b><\/p>\n

By default, WordPress.com doesn\u2019t share any data with anyone. I\u2019m with them on that.<\/p>\n

How long I retain your data<\/b><\/p>\n

(See above). If you leave a comment, the comment and its metadata are retained indefinitely. This is so I can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.<\/p>\n

What rights you have over your data<\/b><\/p>\n

You can request to receive an exported file of the personal data I hold about you, including any data you have provided to me. You can also request that I erase any personal data I hold about you. This does not include any data I an obliged to keep for administrative, legal, or security purposes.<\/p>\n

Where I send your data<\/b><\/p>\n

Although I can\u2019t imagine any scenario in which this would happen, it\u2019s theoretically possible that I may need to transfer the personal data you provide to me to other countries which may be outside the European Economic Area (EEA). I will ensure that your personal data is handled as described in this Privacy Policy.<\/p>\n

My contact information<\/b><\/p>\n

If you have any questions about this Privacy Policy or how I use your data, send me a message at gydleblog@gmail.com and I will do my best to set your mind at ease.<\/p>\n","protected":false},"excerpt":{"rendered":"

Who I am This is a personal website and blog run by Mary Parlange, AKA Gydle. The website address is http:\/\/www.maryparlange.com\/blog, or http:\/\/www.gydlepublishing.com\/blog. Personal data I collect and why I collect it Subscriptions Data Used: To initiate and process subscriptions, … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"spay_email":""},"jetpack_shortlink":"https:\/\/wp.me\/P1R58n-Lj","jetpack_sharing_enabled":false,"_links":{"self":[{"href":"http:\/\/www.gydlepublishing.com\/blog\/wp-json\/wp\/v2\/pages\/2933"}],"collection":[{"href":"http:\/\/www.gydlepublishing.com\/blog\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/www.gydlepublishing.com\/blog\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/www.gydlepublishing.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.gydlepublishing.com\/blog\/wp-json\/wp\/v2\/comments?post=2933"}],"version-history":[{"count":7,"href":"http:\/\/www.gydlepublishing.com\/blog\/wp-json\/wp\/v2\/pages\/2933\/revisions"}],"predecessor-version":[{"id":2936,"href":"http:\/\/www.gydlepublishing.com\/blog\/wp-json\/wp\/v2\/pages\/2933\/revisions\/2936"}],"wp:attachment":[{"href":"http:\/\/www.gydlepublishing.com\/blog\/wp-json\/wp\/v2\/media?parent=2933"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}