PRIVACY POLICY

Who I am

My website address is: https://evalenastyf.com.

This privacy policy applies between You, the user of evalenastyf.com, henceforth interchangeably referred to as “my blog”, “the blog” and “The Blog Post” and Me, Evalena Styf, the owner of this website. I take the privacy of your information very seriously and I will never sell your details to anyone else.

In this privacy policy, I explain how I use the Data I collect, or you provide, when you visit my blog.

What I collect and why

Log Files:

Like most blogs and websites, I collect and use the data contained in my blog’s log files. This information includes your: IP (internet protocol) address; ISP (internet service provider); browser; as well as the time you visited and what pages you looked at. This gives me invaluable information about my readership and helps me plan my content to best suit you.

Comments:

When you leave comments on my blog, I collect the data shown in the comment form together with your visitor IP address and browser user agent string. This information helps my blog software detect and delete spam.

An anonymised string created from your email address (also called a hash) may be provided to the WordPress Gravatar service to see if you are using it. The Gravatar service Privacy Policy is available here: h6y ps://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment. If you don’t have a Gravatar, a random pattern image will appear next to your name instead.

Media

If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.

Email Address:

The content on my blog is provided free of charge, and there is no need for you to become a member to be able to read my posts. At the moment, there are only two instances where you are asked to provide your name and email address on The Blog Post, and that is when you leave a comment on a post and when you sign up to the newsletter. In both instances, your email address is only visible to me and my assistant. Your name will appear with your comment, but readers cannot see your email address.

I will only be sending you an e-mail in direct response to correspondence from you, or if you have signed up to join my e-mail list. Should you receive an email from me that was not prompted by a previous message from you, or despite not having signed up for my newsletter, please let me know as soon as possible so I can get to the bottom of the problem.

Contact forms:

The contact forms you may come across in relation to The Blog Post ask you to provide personal information. Generally speaking, I only ask for your chosen first name (which does not have to be your legal given name) and your email address. Some opt-in forms have fields that allow you to enter more personal information, but this is not required. The only time I will need more detailed information from you is if you have signed up for something that requires me to send it to you by post or courier. I will be saving the contact details you give me and use them solely for the purpose of sending you the information, or product, you have requested. Under no circumstance will I pass on your contact details to anyone third part.

Cookies and Web Beacons:

If you leave a comment on my blog you may opt in to saving your name, email address and website in cookies. This is done for your convenience and means that you will not have to fill in your details again when you leave another comment. These cookies will last for one year.

If I set up a members’ area in the future and you visit my login page, my blog will set a temporary cookie to determine if your browser accepts cookies. This particular cookie contains no personal data and is discarded when you close your browser.

Again, if I do set up a members’ area, my blog will set up several cookies when you log in. These cookies are there 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.

If you have been given an account to help with the running of my blog, or to edit and/or publish articles, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. This type of cookie expires after 1 day.

I use affiliate links and third-party advertisements to support my blog. Some of these companies may use cookies and web beacons to collect information including your: IP address, ISP, browser and, sometimes, whether you use Flash. They do this for geotargeting purposes, which helps them show you ads relevant to your country or local area; and to your areas of interest-based on the kind of websites you visit.

You can disable, or selectively turn off, our cookies or third-party cookies. You do this yourself in your browser settings, or using special software like Norton Internet Security. Please note, disabling cookies can affect how you interact with my blog and other websites. You may, for instance, find that you are unable to log in to accounts and forums etc.

Embedded content from other websites:

Posts on my blog may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves exactly the way it would have if you had visited that website.

Third-party websites may collect data about you. They do NOT have access to your name and contact details, but they can monitor your interaction with their embedded content. This includes being able to track your visits to this and other websites in order to provide you with targeted advertisements.

Google and the DoubleClick DART cookie:

Google is a third-party vendor that uses cookies to serve ads on my blog. Google’s use of the DART cookie enables them to serve ads to you based on your visit to my blog and other sites on the Internet.

You can opt-out of the use of the DART cookie by visiting Google’s Ad and Content Network Privacy Policy.

For more information on cookies click here.

Who I share your data with

Rest assured that I will never sell your contact information to any third parties. As previously stated, I share some of your information (but no personal data) with my advertisers. Other than that, I will only ever share your details with people who work with me and need to contact you on my behalf, or in case I am asked to share the information for legal reasons.

I will share your information with governmental or judicial authorities, law enforcement agencies and others in response to subpoenas, court orders, or any other legal process. I will also share personal data if needed to investigate, prevent, or take action regarding illegal activities or suspected fraud. Last, but not least, I will share personal data to enforce or apply the terms and conditions of this Privacy Policy.

How long I retain your data

If you leave a comment on any of my posts or pages, the comment and its metadata are retained indefinitely. This is so I can recognise and approve any follow-up comments automatically instead of holding them in a moderation queue.

For users that register as members of my blog, I 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 for their username). Website administrators on my team can also see and edit that information.

Your rights to your data

If you have an account on The Blog Post, or have left comments on my posts, 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 am obliged to keep for administrative, legal, or security purposes.

Where I send your data

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