Privacy Policy

Privacy policy

  1. Introduction

1.1 We are committed to safeguarding the privacy of our website [jorielovesastory.com] visitors.

1.2 This policy applies where we are acting as a data controller with respect to the personal data of our website visitors; in other words, where we determine the purposes and means of the processing of that personal data.

1.3 We use cookies on our website. Insofar as those cookies are not strictly necessary for the provision of our website, we will ask you to consent to our use of cookies when you first visit our website.

  1. Credit

2.1 This document was created using a template from SEQ Legal (https://seqlegal.com).

  1. How we use your personal data

3.1 In this Section 3 we have set out:

(a) the general categories of personal data that we may process;

(b) [in the case of personal data that we did not obtain directly from you, the source and specific categories of that data];

(c) the purposes for which we may process personal data; and

(d) the legal bases of the processing.

3.2 We may process data about your use of our website (“usage data“). The usage data may include [your IP address, geographical location, browser type and version, operating system, referral source, length of visit, page views and website navigation paths, as well as information about the timing, frequency and pattern of your service use]. The source of the usage data is [our analytics tracking system]. This usage data may be processed for the purposes of analysing the use of the website. The legal basis for this processing is [consent] OR [our legitimate interests, namely [monitoring and improving our website] OR [to better understand which parts of the blog’s content is being read the most].

3.3 We may process [your personal data] (“personal data“).[ The personal data may [include your name and email address].] [The source of the personal data is [you.] The personal data may be processed [for the purposes of communicating with you through the comment form, contact form, review request form, the betareading request form, the guest post or feature request form, the Classical Literature recommendation form or the newsletter opt-in form.] When you submit a request on this website [as outlined], your name, email, and the details of your request are saved on the server. They are stored to help view, manage, and process your submitted requests. The legal basis for this processing is [consent] OR [our legitimate interests, namely [the proper administration of our website] OR [interactive feedback and communication].

3.4 We may process [your information included in your personal profile on our website] (“profile data“). [The profile data may include [your name, email address, profile pictures, gender, interests and hobbies.] The profile data may be processed for [the purposes of enabling and monitoring your use of our website and services]. The legal basis for this processing is [consent] OR [our legitimate interests, namely [the proper administration of our website] OR [providing guest blogs on a regular or irregular basis].

3.5 We may process [information that you post for publication on our website or through our services] (“publication data“). The publication data may be processed [for the purposes of enabling such publication and administering our website and services]. The legal basis for this processing is [consent] OR [our legitimate interests, namely [the proper administration of our website] OR [interactive feedback and communication].

3.6 We may process [information contained in any enquiry you submit to us regarding the comment form, contact form, review request form, the betareading request form, the guest post or feature request form or the Classical Literature recommendation form] (“enquiry data“). The enquiry data may be processed [for the purposes of accepting enquires from publishers, publicists and authors in regards to honest reviews on behalf of books and stories] OR [betareading requests] OR [guest post or feature request] OR [general feedback and commentary]. When you submit a request on this website [as outlined], your name, email, and the details of your request are saved on the server. They are stored to help view, manage, and process your submitted requests. The legal basis for this processing is [consent] OR [interactive feedback and communication].

3.7 We may process [information that you provide to us for the purpose of subscribing to our email notifications and/or newsletters] (“notification data“). The notification data may be processed [for the purposes of sending you the relevant notifications and/or newsletters]. The legal basis for this processing is [consent] OR [the process of choosing to opt-in to receive the relevant notifications and/or newsletters for purpose of being updated about new content to this website].

3.8 We may process [information contained in or relating to any communication that you send to us] (“correspondence data“). The correspondence data may include [the communication content and metadata associated with the communication]. [Our website will generate the metadata associated with communications made using the website contact forms.] The correspondence data may be processed [for the purposes of communicating with you and record-keeping]. When you submit a request on this website [as outlined], your name, email, and the details of your communication are saved on the server. They are stored to help view, manage, and process your submitted correspondence. The legal basis for this processing is [our legitimate interests, namely [the proper administration of our website communications with users]] OR [interactive feedback and communication].

3.9 We may process [any of your personal data identified in this policy] where necessary for [the establishment, exercise or defence of legal claims, whether in court proceedings or in an administrative or out-of-court procedure]. The legal basis for this processing is our legitimate interests, namely [the protection and assertion of our legal rights, your legal rights and the legal rights of others].

3.15 In addition to the specific purposes for which we may process your personal data set out in this Section 3, we may also process [any of your personal data] where such processing is necessary [for compliance with a legal obligation to which we are subject, or] in order to protect your vital interests or the vital interests of another natural person.

3.16 Please do not supply any other person’s personal data to us, unless we prompt you to do so.

  1. Providing your personal data to others

4.1 We never disclose [your personal data] to [any third party] for the purpose of [enabling them to contact you so that they can offer, market and sell to you relevant goods and/or services].

4.2 This website uses Akismet in an effort to prevent spam whilst monitoring comments [OR] contact form submissions [by way of the the comment form, contact form, review request form, the betareading request form, the guest post or feature request form and the Classical Literature recommendation form]. You can review their privacy policy here: https://automattic.com/privacy.

We collect information about visitors who comment on Sites that use our Akismet anti-spam service. The information we collect depends on how the User sets up Akismet for the Site, but typically 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).

4.3 When you subscribe to receive email newsletters for updates on the latest posts on [jorielovesastory.com] you are consenting to having your personal information shared with WordPress.com via their JetPack plugin for self-hosted blogs via WordPress.org. You can review their privacy policy here: https://automattic.com/privacy [AND] here: https://jetpack.com/support/privacy.

4.4 This website is hosted by Nose Graze and some of your personal data might be stored on their server. You can read their privacy policy here: https://shop.nosegraze.com/privacy-policy.

4.5 In addition to the specific disclosures of personal data set out in this Section 4, we may disclose your personal data where such disclosure is necessary for compliance with a legal obligation to which we are subject, or in order to protect your vital interests or the vital interests of another natural person. [We may also disclose your personal data where such disclosure is necessary for the establishment, exercise or defence of legal claims, whether in court proceedings or in an administrative or out-of-court procedure.]

  1. International transfers of your personal data

5.1 In this Section 5, we provide information about the circumstances in which your personal data may be transferred to [countries outside the European Economic Area (EEA)].

5.2 The hosting facilities for our website are situated in the United States whilst our hosting company is located in [UK]. [The European Commission has made an “adequacy decision” with respect to [the data protection laws of each of these countries].] [Transfers to [each of these countries] will be protected by appropriate safeguards, namely [the use of standard data protection clauses adopted or approved by the European Commission, a copy of which you can obtain from nosegraze.com.

5.3 Sensitive and private data exchange between the website and its visitors happens over a SSL secured communication channel and is encrypted and protected with digital signatures.

5.4 You acknowledge that [personal data that you submit for publication through our website] may be available, via the internet, around the world. We cannot prevent the use (or misuse) of such personal data by others.

  1. Retaining and deleting personal data

6.1 This Section 6 sets out our data retention policies and procedure, which are designed to help ensure that we comply with our legal obligations in relation to the retention and deletion of personal data.

6.2 Personal data that we process for any purpose or purposes shall not be kept for longer than is necessary for that purpose or those purposes.

6.3 The personal data submitted through the contact forms on this website are never used for marketing purposes [OR] shared with third-parties.

6.4 We will retain your personal data as follows:

(a) Personal data submitted through the contact form [AND] the Classical Literature recommendation form will be retained for a maximum period of life of this blog following 6th August, 2013 [OR] until they request their information to be deleted.

The entirety of the form submitted through the contact form [OR] the Classical Literature recommendation form as well as a person’s IP address are stored whilst being emailed to the site administrator. This is done in order to ensure the contents of the form(s) are saved in case the emails are not delivered properly.

(b) Personal data submitted through the comment form will be retained for a maximum period of the life of this blog following 6th August, 2013 [OR] until they request their information to be deleted. Personal data attached to comments [OR] the metadata attached to comments is retained indefinitely in an effort to moderate future comments by the same person without holding future comments in a queue of moderation.

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.

Comments are moderated. Once your comment is approved for the first time, your comments thereafter will be recognised and automatically approved. All comments are reviewed and continue to be moderated after automated approval. By using the comment form you are consenting with the storage and handling of your personal data by this website. Once you use the comment form, if your comment receives a reply (this only applies to those who leave comments by email), there is a courtesy notification set to send you a reply ticket. It is at your discretion if you want to return to re-respond and/or to continue the conversation established. This is a courtesy for commenters to know when their comments have been replied by either the blog’s owner or a visitor to the blog who wanted to add to the conversation. Your email address is hidden and never shared.

(c) Personal data submitted through the review request form will be retained for a maximum period of the life of this blog following 6th August, 2013 [OR] until they request their information to be deleted. Personal data attached to the review request form is retained for purposes of record keeping requests [OR] for communication [OR] response on behalf of the requests being submitted.

(d) Personal data submitted through the betareading request form will be retained for a maximum period of the life of this blog following 6th August, 2013 [OR] until they request their information to be deleted. Personal data attached to the betareading request form is retrained for purposes of record keeping requests [OR] for communication [OR] response on behalf of the requests being submitted.

(e) Personal data submitted through the guest post [OR] feature request form will be retained for a maximum period of the life of this blog following 6th August, 2013 [OR] until they request their information to be deleted. Personal data attached to the guest post [OR] feature request form is retained for purposes of record keeping requests [OR] communication [OR] response on behalf of the requests being submitted.

6.5 In some cases it is not possible for us to specify in advance the periods for which your personal data will be retained. In such cases, we will determine the period of retention based on the following criteria:

(a) the period of retention of personal data submitted through the newsletter opt-in form will be determined based on the length of time a person chooses to remain active on the newsletter list before they elect to unsubscribe from receiving the newsletter [OR] during administration of the maintenance of this website for inactive accounts [which will be removed]. Persons can easily unsubscribe from being on the newsletter list with the link provided at the bottom of the newsletter.

(b) For users that register on our website (if any), 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.

When you subscribe to the newsletter your name (if provided) [OR] username (if using WordPress.com OR WordPress.org to follow this website) along with your IP address and email will be stored on the server. You can review their privacy policy here: https://automattic.com/privacy [AND] here: https://jetpack.com/support/privacy.

(b) Posts and pages on this website might include embedded content [which might include but will not be limited to videos, tweets, chapter samplers, audiobook samplers, etc]. This embedded content will interact with a visitor in the same way as if the visitor visited the other website.

The websites might collect data about the visitor, use cookies, use third-party tracking, monitor how a visitor interacts with the embedded content which might also include tracking your interaction with the embedded content if the visitor has an account and are actively logged into the website providing the content.

The privacy policies for these login assessed accounts are available via these links:

(a) https://vimeo.com/privacy (Vimeo)

(b) https://policies.google.com/privacy?hl=en (YouTube) a service provided by (Google)

(c) https://twitter.com/en/privacy#update (Twitter)

(d) https://soundcloud.com/pages/privacy/05-2018 (SoundCloud)

(e) https://support.scribd.com/hc/en-us/articles/210129366-Privacy-policy (Scribd)

6.6 Notwithstanding the other provisions of this Section 6, we may retain your personal data where such retention is necessary for compliance with a legal obligation to which we are subject, or in order to protect your vital interests or the vital interests of another natural person.

  1. Amendments

7.1 We may update this policy from time to time by publishing a new version on our website.

7.2 You should check this page occasionally to ensure you are happy with any changes to this policy.

  1. Your rights

8.1 In this Section 8, we have summarised the rights that you have under data protection law. Some of the rights are complex, and not all of the details have been included in our summaries. Accordingly, you should read the relevant laws and guidance from the regulatory authorities for a full explanation of these rights.

8.2 Your principal rights under data protection law are:

(a) the right to access;

(b) the right to rectification;

(c) the right to erasure;

(d) the right to restrict processing;

(e) the right to object to processing;

(f) the right to data portability;

(g) the right to complain to a supervisory authority; and

(h) the right to withdraw consent.

8.3 You have the right to confirmation as to whether or not we process your personal data and, where we do, access to the personal data, together with certain additional information. That additional information includes details of the purposes of the processing, the categories of personal data concerned and the recipients of the personal data. Providing the rights and freedoms of others are not affected, we will delete your personal data.

8.4 You have the right to have any inaccurate personal data about you rectified and, taking into account the purposes of the processing, to have any incomplete personal data about you completed.

8.5 In some circumstances you have the right to the erasure of your personal data without undue delay. Those circumstances include: [the personal data are no longer necessary in relation to the purposes for which they were collected or otherwise processed; you withdraw consent to consent-based processing; you object to the processing under certain rules of applicable data protection law; and the personal data have been unlawfully processed]. However, there are exclusions of the right to erasure. The general exclusions include where processing is necessary: [for exercising the right of freedom of expression and information; for compliance with a legal obligation; or for the establishment, exercise or defence of legal claims].

8.6 In some circumstances you have the right to restrict the processing of your personal data. Those circumstances are: you contest the accuracy of the personal data; processing is unlawful but you oppose erasure; we no longer need the personal data for the purposes of our processing, but you require personal data for the establishment, exercise or defence of legal claims; and you have objected to processing, pending the verification of that objection. Where processing has been restricted on this basis, we may continue to store your personal data. However, we will only otherwise process it: with your consent; for the establishment, exercise or defence of legal claims; for the protection of the rights of another natural or legal person; or for reasons of important public interest.

8.7 You have the right to object to our processing of your personal data on grounds relating to your particular situation, but only to the extent that the legal basis for the processing is that the processing is necessary for: the performance of a task carried out in the public interest or in the exercise of any official authority vested in us; or the purposes of the legitimate interests pursued by us or by a third party. If you make such an objection, we will cease to process the personal information unless we can demonstrate compelling legitimate grounds for the processing which override your interests, rights and freedoms, or the processing is for the establishment, exercise or defence of legal claims.

8.8 You have the right to object to our processing of your personal data for scientific or historical research purposes or statistical purposes on grounds relating to your particular situation, unless the processing is necessary for the performance of a task carried out for reasons of public interest.

8.9 To the extent that the legal basis for our processing of your personal data is:

(a) consent; or

(b) that the processing is necessary for the performance of the comment form, contact form, review request form, the betareading request form, the guest post or feature request form or the Classical Literature recommendation form in which which you are party or in order to take steps at your request prior to entering into direct contact and communication, and such processing is carried out by automated means, you have the right to receive your personal data from us in a structured, commonly used and machine-readable format. However, this right does not apply where it would adversely affect the rights and freedoms of others.

8.10 If you consider that our processing of your personal information infringes data protection laws, you have a legal right to lodge a complaint with a supervisory authority responsible for data protection. You may do so in the EU member state of your habitual residence, your place of work or the place of the alleged infringement.

8.11 To the extent that the legal basis for our processing of your personal information is consent, you have the right to withdraw that consent at any time. Withdrawal will not affect the lawfulness of processing before the withdrawal.

8.12 If you have an account on this site, or have left comments, 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 [by using our Data Access Request] OR [by using our Contact Form]. This does not include any data we are obliged to keep for administrative, legal, or security purposes.

  1. About cookies

9.1 A cookie is a file containing an identifier (a string of letters and numbers) that is sent by a web server to a web browser and is stored by the browser. The identifier is then sent back to the server each time the browser requests a page from the server.

9.2 Cookies may be either “persistent” cookies or “session” cookies: a persistent cookie will be stored by a web browser and will remain valid until its set expiry date, unless deleted by the user before the expiry date; a session cookie, on the other hand, will expire at the end of the user session, when the web browser is closed.

9.3 Cookies do not typically contain any information that personally identifies a user, but personal information that we store about you may be linked to the information stored in and obtained from cookies.

  1. Cookies that we use

10.1 We use cookies for the following purposes:

(a) [authentication – we use cookies [to identify you when you visit our website and as you navigate our website][ (cookies used for this purpose are: [identify cookies])]];

(b) [personalisation – we use cookies [to store information about your preferences and to personalise the website for you][ (cookies used for this purpose are: [identify cookies])]];

(c) [security – we use cookies [as an element of the security measures used to protect user accounts, including preventing fraudulent use of login credentials, and to protect our website and services generally][ (cookies used for this purpose are: [identify cookies])]];

(d) [analysis – we use cookies [to help us to analyse the use and performance of our website and services][ (cookies used for this purpose are: [identify cookies])]]; and

(e) [cookie consent – we use cookies [to store your preferences in relation to the use of cookies more generally][ (cookies used for this purpose are: [identify cookies])]].

10.2 Cookies used via the comment form on this website

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.

10.3 Cookies used via users who are logged in to make contributions to this website

If you have an account and you log in to this site, 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.

  1. Cookies used by our service providers

11.1 Our service providers use cookies and those cookies may be stored on your computer when you visit our website.

11.2 We use Google Analytics to analyse the use of our website. Google Analytics gathers information about website use by means of cookies. The information gathered relating to our website is used to create reports about the use of our website. Google’s privacy policy is available at: https://www.google.com/policies/privacy/. [The relevant cookies are: [identify cookies].]

11.3 We use social share options enabled by JetPack / WordPress which utilizes login cookies from a visitor’s Facebook, Twitter or Google+ account. The social share options on located on individual posts which require login cookies. [The relevant cookies are: [identify cookies].] The privacy policies for these login assessed accounts are available via these links:

(a) https://www.facebook.com/privacy/explanation (Facebook)

(b) https://twitter.com/en/privacy#update (Twitter)

(c) https://policies.google.com/privacy?hl=en-US (Google+)

11.4 Cookies are also set and used by WordPress.com [OR] WordPress.org – you can review their Cookie Policy at: https://automattic.com/cookies [OR] https://jetpack.com/support/cookies. This includes those who use their Gravatars attached to their comments.

  1. Managing cookies

12.1 Most browsers allow you to refuse to accept cookies and to delete cookies. The methods for doing so vary from browser to browser, and from version to version. You can however obtain up-to-date information about blocking and deleting cookies via these links:

(a) https://support.google.com/chrome/answer/95647?hl=en (Chrome);

(b) https://support.mozilla.org/en-US/kb/enable-and-disable-cookies-website-preferences (Firefox);

(c) http://www.opera.com/help/tutorials/security/cookies/ (Opera);

(d) https://support.microsoft.com/en-gb/help/17442/windows-internet-explorer-delete-manage-cookies (Internet Explorer);

(e) https://support.apple.com/kb/PH21411 (Safari); and

(f) https://privacy.microsoft.com/en-us/windows-10-microsoft-edge-and-privacy (Edge).

12.2 Blocking all cookies will have a negative impact upon the usability of many websites.

12.3 If you block cookies, you will not be able to use all the features on our website.

13. Children’s Online Privacy Protection Rule

13.1 Information shared by minors (those under 13) is not knowingly done without parental permission as in accordance with the Children’s Online Privacy Protection Rule. Visitors of my blog do add comments on book reviews I contribute for Children’s Literature, however, the only information that is on my blog is what was shared within the comment itself. I blog about Children’s Literature to help readers of all ages maintain a connection to the beauty of what is being written and published. If any information has inadvertently been gathered please use the Contact Form for it to be promptly removed or permission can be granted by the parents of the child in question.

14. Links to Third-Parties

14.1 This privacy policy applies only to [jorielovesastory.com] and is valid for visitors to this website and regarding information shared and/or collected here. This policy does not apply to any information collected offline or via channels other than this website. Please refer to third-party website privacy policies when you exit this website. No monetary compensation is received in return for providing the links on this website or any of the content posted on the website. If someone chooses to access a link, they do so at their own risk. We are not responsible for the content of the linked websites.

    15. Plugins used on jorielovesastory.com

15.1 We are a self-hosted WordPress.org. You can view the privacy policy of this service provider at https://automattic.com/privacy. This policy is also inclusive for the Aksimet Anti-Spam plugin which runs on this blog and JetPack for WordPress.com. There is a separate privacy policy for the “Like this Post” feature on this website which can be viewed here: https://jetpack.com/support/comment-likes/#privacy.

(a) 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.

(b) Carousel

Image views are only recorded if the site owner, has explicitly enabled image view stats tracking for this feature via the jetpack_enable_carousel_stats filter.

Data Used: If image view tracking is enabled, 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: Image views.

(c) 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.

(d) 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.

(e) 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.

(f) 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.

(h) 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.

(i) 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.

(j) 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.

(k) 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.

(l) 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.

(m) 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.

(n) 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.

(o) 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.

(p) Popular Posts Tabbed Widget for JetPack. You can view the information about this plugin on the information page https://wordpress.org/plugins/popular-posts-tab-widget-for-jetpack.

15.2 Plugins used on jorielovesastory.com which are not provided by WordPress.org [OR] WordPress.com [OR] Jetpack.

(a) Better Click to Tweet. You can view the information about this plugin on the information page https://wordpress.org/plugins/better-click-to-tweet.

(b) Comments Not Replied To. You can view the information about this plugin on the information page https://wordpress.org/plugins/comments-not-replied-to.

(c) Dave’s WordPress Live Search. You can view the information about this plugin on the information page https://wordpress.org/plugins/daves-wordpress-live-search.

(d) Disable XML-RPC. You can view the information about this plugin on the information page https://wordpress.org/plugins/disable-xml-rpc.

(e) Duplicate Post. You can view the information about this plugin on the information page https://wordpress.org/plugins/duplicate-post.

(f) Enable Media Replace. You can view the information about this plugin on the information page https://wordpress.org/plugins/enable-media-replace

(g) Image Widget. You can view the information about this plugin on the information page https://wordpress.org/plugins/image-widget.

(h) Public Post Preview. You can view the information about this plugin on the information page https://wordpress.org/plugins/public-post-preview.

(i) WordPress Importer. You can view the information about this plugin on the information page https://wordpress.org/plugins/wordpress-importer.

(j) WP Content Copy Protector. You can view the information about this plugin on the information page https://wordpress.org/plugins/wp-content-copy-protector.

(k) WP Edit. You can view the information about this plugin on the information page https://wordpress.org/plugins/wp-edit.

(l) WP Page Navi. You can view the information about this plugin on the information page https://wordpress.org/plugins/wp-pagenavi.

(m) WP-Polls. You can view the information about this plugin on the information page https://wordpress.org/plugins/wp-polls.

(n) WPTouch Mobile Plugin. You can view the information about this plugin on the information page https://wordpress.org/plugins/wptouch. For more information please visit the plugin website via https://www.wptouch.com.

(o) Yoast SEO. You can view the information about this plugin on the information page https://wordpress.org/plugins/wordpress-seo.

15.2 Plugins used created by Nose Graze [nosegraze.com]

The following plugins were created by [nosegraze.com] and are used regularly on [jorielovesastory.com]. In addition to these plugins, the following plugins have information pages attributed to explaining how the individual plugins work. Of all the plugins I am using by [nosegraze.com] there is only one plugin which will store information in my website’s database: [UBB Review Requests] if someone enters their name and email in a review request, that information is stored in the website database. You can review the privacy policy for Nose Graze via https://shop.nosegraze.com/privacy-policy.

(a) CW Twitter Card. You can view the information about this plugin on the information page https://www.nosegraze.com/install-twitter-cards-wordpress-blog.

(b) UBB Review Requests. You can view the information about this plugin on the information page https://shop.nosegraze.com/product/ubb-review-submissions-addon.

16. Our details

16.1 This website [jorielovesastory.com] is registered in [United States] and we are hosted by Nose Graze [UK] whilst our server is located in [United States].

16.2 You can contact us:

(a) [using our website contact form]

Fun Stuff for Your Blog via pureimaginationblog.com

By using this website, you hereby consent to my privacy policy and agree to its terms. This Privacy Policy was updated: 13th November, 2018. Should I update, amend or make any changes to my privacy policy, those changes will be posted here.