last update: 22/11/2018
Subject to change without notice!
Who we are
Our website address is: https://www.frichic.com (“blog”)
FRICHIC (“blog”) is a personal blog owned, written, and edited by Ivelina. This Privacy Policy (“Policy”) applies to our blog. By using this blog, you signify your acceptance of this Policy, our Terms of Use and our Cookie Policy. If you do not agree to any of these Terms and Policies, please do not use our blog. Your continued use of the blog following the posting of changes to this Policy will be deemed your acceptance of those changes. For questions about this blog, please contact us.
What personal data we collect and why we collect it
1. By the use of plugins:
– Comment Likes
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.
– Google Analytics
Data Used: Please refer to the appropriate Google Analytics documentation for the specific type of data it collects. Google Analytics does offer IP anonymization, which is enabled for this blog.
Activity Tracked: This feature sends page view events (and potentially video play events) over to Google Analytics for consumption.
– Gravatar Hovercards
Data Used: This feature will send a hash of the user’s email address (if logged in to the blog or WordPress.com — or if they submitted a comment on the blog 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.
– Mobile Theme
Data Used: A visitor’s preference on viewing the mobile version of a blog.
Activity Tracked: A cookie (akm_mobile) is stored for 3.5 days to remember whether or not a visitor of the blog wishes to view its mobile version. Learn more about this cookie.
– Search
Data Used: Any of the visitor-chosen search filters and query data in order to process a search request on the WordPress.com servers.
– 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 blog owner does not have access to any of this information via this feature. For example, the 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.).
2. By the use of comments field
When you leave comments on the blog we collect the data shown in the comments form, and also your IP address and browser user agent string to help spam detection. If you leave a comment on our blog 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.
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.
3. Cookies
For detailed information on used cookies, please visit our Cookie Policy page
4. Embedded content from other websites
Articles on this blog may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if you have visited the other website.
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.
Who we share your data with
By default we don not share your personal data with anyone.
How long we retain your data
If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.
What rights you have over your data
If you have left comments, you can request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Where we send your data
The personal data is stored on our hosting provider’s server, SiteGround, which is registered in Spain. SiteGround servers are located in the EU and therefore comply with the requirements of General Data Protection Regulation (EU) 2016/679. Their Privacy Policy could be found here: https://www.siteground.com/privacy.htm
How we protect your data
We take the necessary technical and organizational measures to protect personal data from accidental or unlawful destruction, accidental loss, unauthorized access, alteration or dissemination, as well as from other illegal forms of processing, namely:
– all personal information is stored on secure and reliable servers;
– in the exercise of the right of access by the individual, we verify the identity of the individual before giving him/her the requested information.
What third parties we receive data from
By default we do not receive personal data from third-party individuals.
What automated decision making and/or profiling we do with user data
By default we do not have automated decision making and/or profiling
Links, instrument and content from other companies
1. This blog contains buttons, tools or content that link to other companies services. All such websites that can be accessed through our blog are independent and we assume no responsibility for any damages and losses incurred as a result of the use of these sites. Any use of these websites is on your own responsibility and it is recommended that you familiarize yourself with the relevant company’s Privacy Policy for more information.
2. Some posts on this blog may contain Affiliate Links. This means that once a link, which may be found in a blog post, is clicked on, the reader is then sent through to a retailer site where they are given an opportunity to purchase something. Ivelina, the editor of this blog may receive a small percentage of your purchase. Your purchase will not add any additional charge to you as the customer. Affiliate links are added to posts by Ivelina after she writes her content. This does not affect the products that she has decided to include. See our disclosure about affiliate link here.
Changes to this Policy
FRICHIC has the discretion to update this Policy at any time. When we do, we will revise the updated date at the top of the page. We encourage you to frequently check this page for any changes to stay informed and see if there have been any changes. You acknowledge and agree that it is your responsibility to review this Policy periodically and become aware of modifications.
If you have any questions about this Policy, please contact us!