Who we are
Fierceblooms is a website dedicated to wild garden style floristry. Our site address is: https://fierceblooms.com
What personal data we collect and why we collect it
The fierceblooms site utilises the Wordpress platform from developers Automatic whose privacy notice for visitors to their users' sites can be found here
More specifics about the personal data collected on the site follows below.
If you have subscribed to follow the blog, we retain your email address to allow us to immediately send each new fierceblooms blog post when just published to your email account
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.
After approval of your comment, if you are a Gravatar user then your profile picture is visible to the public in the context of your comment.
We use the Wordpress plugin Contact Form 7 as the basis for our contact page. This does not store any information on the fierceblooms website but passes it as an email to the fierceblooms mail account.
If you leave a comment on the fierceblooms 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.
Embedded content from other websites
Some articles on the fierceblooms site may include embedded content in the form of videos, images, articles, etc. For example, for performance purposes we serve most of our video content from our own fierceblooms account on Vimeo and periodically feature the fierceblooms Instagram feed in one of the blog footer bars.
Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
The fierceblooms site utilises the Wordpress platform and we use the Jetpack stats module to optimise our content by reviewing numbers of post and page views, outbound link clicks, referring URLs and search engine terms, and country.
Who we share your data with
We do not share personal information with third-parties nor do we store information we collect about your visit to this blog for use other than to analyze content performance.
How long we retain your data
If you have subscribed to follow the blog, we retain your email address to allow us to send each new blog post when published to your email account until you advise us you wish to opt out of this service (an unsubscribe option is available on each new blog post emailed to a blog follower).
If you leave a comment on a blog post, the comment and its metadata are retained indefinitely. This is so we can recognise 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 subscribed to follow the blog (i.e. receive each new blog post via email), or have left comments on the blog, 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. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Where we send your data
Visitor comments may be checked through an automated spam detection service.
How we protect your data
All interaction with the fierceblooms site and your desktop or mobile browser is via an encrypted (secure sockets layer SSL or https://) connection. This minimises the chance of your data being malevolently intercepted as it passes over the internet. A visual cue that this is in place will be a lock image somewhere in your browser’s status or location bar.
Login to our fierceblooms website host server and our content delivery network (Cloudflare) are both protected via a two-step-authentication password process. On Cloudflare we also deploy their web application firewall (WAF) to protect the fierceblooms site from common vulnerabilities like SQL injection attacks, cross-site scripting, and cross-site forgery requests.
We are not responsible for the republishing of the content found on this blog on other Web sites or media without our permission.
If you wish to communicate with us regarding privacy-specific concerns, please utilise our contact form accessible via the button below.