**This site is intended for individuals over the age of eighteen (18) and/or the adult age in your country of origin, whichever is higher. By navigating throughout this website you are confirming that you are legally an adult.**

 

Privacy Policy

This Privacy Policy has been created to better serve those who are concerned with how their personal information, described in United States legal fields as either personally identifiable information (PII), or sensitive personal information (SPI), is being used online. Additionally, information is posted here in order to be in compliance with the EU with respect to their GDPR (General Data Protection Regulation) which takes effect on May 25, 2018. Please read our privacy policy carefully to get a clear understanding of how we collect, use, protect or otherwise handle your personal information in accordance with our website. Your privacy is critically important and this policy applies to all site visitors and newsletter subscribers.

WHO WE ARE
Jaime Reese is the author and owner of this website as well as the owner of the newsletter mailing list managed through the MailChimp service. My books are self-published through my private label, Romandeavor, Inc. Jaime Reese is the only author publishing through Romandeavor. Therefore, only Jaime Reese and Romandeavor, Inc. have access to the information submitted with each newsletter subscription.

DATA COLLECTION, SHARING, AND STORAGE
Information is collected in different ways. We collect information from you when you subscribe to a newsletter, fill out a form or enter information on our site. The information collected is the minimum required to fulfill the request outlined in the form or complete the task. At your request, or when the website or newsletter is closed, we will delete / destroy your personal data in all formats.

We do not sell, trade, or otherwise transfer to outside parties your information unless we provide users with advance notice. This does not include website hosting partners and other parties who assist us in operating our website, conducting our business, or serving our users, so long as those parties agree to keep this information confidential.

Information is also collected by several resources used on this site whose purpose is to improve and protect your site experience.

RESOURCES WE USE THAT COLLECT DATA
MailChimp: Newsletter subscriptions are managed via the MailChimp service. You will never be subscribed to a newsletter or group without your explicit consent. Information is not released or shared with anyone not associated with this site unless required by subpoena, court order, or other governmental request.
Automattic: the company responsible for WordPress and the additional add-ins/plug-ins we use in Jetpack products. Specifically, site statistics, Gravatar Hovercards, blog subscriptions, searching, notifications, and Akismet (spam blocking).
WordFence: for site security and scanning
Forms: When choosing to complete a contact form, all fields are clearly labeled and the data is transmitted via email directly to Jaime Reese.

COOKIE POLICY AND INFORMATION
A cookie is a string of information that a Site stores on a visitor’s computer, and that the visitor’s browser provides to the Site each time the visitor returns. Pixel tags (also called web beacons) are small blocks of code placed on Sites. These files are stored on your computer’s hard drive. Visitors who do not wish to have cookies placed on their computers may set their browsers to refuse cookies with the understanding that some site features may not function properly.

Automattic—WordPress and JetPack
Automattic is the company behind WordPress and more. Our website uses the WordPress content management system and uses cookies to deliver feature-specific functionality of Automattic’s products. Automattic uses cookies and other technologies like pixel tags to help identify and track visitors and Site usage. For more information about their use of cookies and other technologies for tracking, including how visitors can control the use of cookies, please see the Automattic’s Cookie Policy (listed below).

Our website uses the following Automattic products: Jetpack (we use this for site statistics, Gravatar Hovercards, subscriptions, searching, and notifications), Akismet (spam blocking). These products/services collect and process data in accordance with their Privacy Policy.
Below is the information listed regarding the specific JetPack features used on this site.
For full transparency, here are the Privacy Policies that include all products and options offered by the following third parties.
Automattic’s Privacy Policy is listed here for your review: https://automattic.com/privacy-notice/
JetPack’s feature-specific Privacy Policy can be reviewed here: https://jetpack.com/support/for-your-privacy-policy/


The below items are feature-specific to this site and information is copy/pasted directly from the above JetPack Privacy Policy containing their full feature list at the time this was published. “Additional notes” were added by the site owner for clarity. Any references to “we” in the following pasted section refers to “Automattic” and their group.

  • 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.
    (additional notes)
     Other visitors to the website will only see your name and your comment. If you provide a website address, it will be linked to your name so that people can visit your site if they wish. Comment notifications are received by the site owner via email and stored on the WordPress dashboard for this site (which can only be accessed via a password-protected administrator account).
  • 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.
  • WordPress site Subscriptions: 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 (“REQUEST and DOCUMENT” ) which was given in order to access the page. 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.
    (additional notes) Users may unsubscribe from WordPress Follow and WordPress Subscriber updates at any time via their WordPress account. The “follow” or WordPress subscription request is managed directly via WordPress and their service. Each “follow” request is processed via WordPress directly. They require confirmation of each follow and users can update “Subscription Options” for all WordPress follows by following the link in the confirmation email received.
  • 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.).

 

Wordfence
Defiant is the company behind Wordfence. Wordfence is used on this site for security. The plug-in currently sets three cookies. Details regarding which are applicable to a user’s visit are listed. The following is a copy/paste of information provided by Defiant regarding their Wordfence product cookies.

  • wfwaf-authcookie-(hash)
    What it does: This cookie is used by the Wordfence firewall to perform a capability check of the current user before WordPress has been loaded. Who gets this cookie: This is only set for users that are able to log into WordPress. How this cookie helps: This cookie allows the Wordfence firewall to detect logged in users and allow them increased access. It also allows Wordfence to detect non-logged in users and restrict their access to secure areas. The cookie also lets the firewall know what level of access a visitor has to help the firewall make smart decisions about who to allow and who to block.
  • wf_loginalerted_(hash)
    What it does: This cookie is used to notify the Wordfence admin when an administrator logs in from a new device or location. Who gets this cookie: This is only set for administrators. How this cookie helps: This cookie helps site owners know whether there has been an admin login from a new device or location.
  • wfCBLBypass
    What it does: Wordfence offers a feature for a site visitor to bypass country blocking by accessing a hidden URL. This cookie helps track who should be allowed to bypass country blocking. Who gets this cookie: When a hidden URL defined by the site admin is visited, this cookie is set to verify the user can access the site from a country restricted through country blocking. This will be set for anyone who knows the URL that allows bypass of standard country blocking. This cookie is not set for anyone who does not know the hidden URL to bypass country blocking. How this cookie helps: This cookie gives site owners a way to allow certain users from blocked countries, even though their country has been blocked.


HOW WE USE YOUR INFORMATION
We may use the information we collect in the following ways:
• To send periodic newsletters.
• To administer a contest, promotion, survey or other site feature or update.
• To follow up after initial correspondence (via email).
• To maintain site security
• To improve the services we provide and overall website traffic information

HOW DO WE PROTECT YOUR INFORMATION
Data collected by third parties is managed by their respective privacy policies (as listed above). For data we can access, your personal information is contained behind secured networks and is only accessible by a limited number of persons who have special access rights to such systems, and are required to keep the information confidential. When orders are placed (e.g. signed paperbacks), all transactions are processed through a gateway provider (PayPal) and are not stored or processed on our servers.

THIRD-PARTY LINKS (text links or graphic/badge links)
Occasionally, we may include links to other websites via a link or badge which the visitor clicks then leaves our site. These third-party sites have separate and independent privacy policies. We therefore have no responsibility or liability for the content and activities of these linked sites. You should exercise caution and look at the privacy statement applicable to the website in question. We seek to protect the integrity of our site and welcome any feedback about these sites and will promptly remove them should they pose a risk to our visitors.

NEWSLETTER
The Jaime Reese newsletter is sent using the MailChimp service and requires your explicit consent. By subscribing to the newsletter, you acknowledge that the information you provide will be transferred to MailChimp for processing in accordance with their Privacy Policy (https://mailchimp.com/legal/privacy/) and Terms (https://mailchimp.com/legal/terms/).

In addition to newsletters, similar data may be collected on other forms for giveaways, contests, book orders, opinion polls, etc. We will not ask for any data than is not required and/or relevant for the purpose stated on the form.

Double opt-in
The Jaime Reese newsletter subscription requires a Double Opt-in. Meaning, when you subscribe to the newsletter, you will be sent an email asking you to confirm your subscription request. By confirming your subscription to the newsletter, you are acknowledging that your personal data can be stored and used as listed within this Privacy Policy.

Unsubscribing from newsletters
In the footer of each newsletter, you will find an ‘unsubscribe’ link. Additionally, you can refer to any prior newsletter edition and choose to “update your preferences” by clicking the link also found in the footer of the email newsletter. Within your preferences setting, you can see all the data that is currently collected.

MailChimp does not permanently delete unsubscribe requests. They retain unsubscribe requests for record keeping purposes to ensure you do not receive additional mailers after your “unsubscribe” request. If you would like to have your personal data completely removed from our list, you will need to contact me so that I can manually remove your name and data.

YOUR RIGHTS
You have the right to access your personal data held by the site owner, to know how we use it, and to update or correct your personal data. This policy should help make that clear, but specific questions are always welcome. You also have the right to request that we delete all personal data.

CONTACT
All inquiries and requests relating to your personal data can be directed to Jaime Reese at contactme@jaimereese.com. We will make good faith efforts to resolve requests and respond to such messages in a timely manner.

PRIVACY POLICY UPDATES
We reserve the right to revise this Privacy Policy by updating it and posting the update on this same Privacy Policy Page with a notation regarding the change.


May 25, 2018
Follow

Get every new post delivered to your Inbox

Join other followers: