What personal data we collect and why we collect it
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.
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.
If you leave a comment via the native WordPress Comment system 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.
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.
If you have an account that allows you to edit or publish an article, 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. It expires after 1 day.
Embedded content from other websites
Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
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.
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.
What rights you have over your data
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. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
The Frederick H. Leonhardt Foundation collects and stores certain personal data through our website for the purpose of processing grant applications, scholarships and other various intake forms. You must consent to the collection of your data and that consent is given upon submitting and applying to any of our grant applications, scholarships or intake forms on this website.
Where we send your data
We use the Disqus comment hosting service for our blog comment system and the Formstack platform for various forms (including our Contact Us form) on our website. In order for these services to work your data must be transmitted and managed by these third-party services. You can find links to their privacy policies at the end of this document.
Our contact information
If you need to contact us for any privacy-specific concerns, data export or erasure requests please use our Contact Form. https://legacy.fhlfoundation.org/contact/
How we protect your data
Any data you provide us directly, or is synced from any third-party tools we use, is stored on our secure servers and transmitted to our servers via Secure Socket Layer (SSL), an encryption based technology.
What data breach procedures we have in place
We have enabled several security measures to block, avoid and detect breaches of our servers. If a breach is discovered and any data exposed we will notify any affected user(s) within 72 hours of first becoming aware of the breach.
What third parties we receive data from
We use the Disqus commenting hosting service for our blog as a replacement to the standard WordPress comment system. We use the “Sync” feature of the Disqus plugin to maintain a copy of comments created and edited in Disqus to our local WordPress database for backup purposes.
We also offer the Bowlby Less Traveled (BLT) blog as an email subscription via the FeedBurner service as a convenience to our visitors. Our newsletter is hosted through a third-party service called MailChimp. We recommend reviewing their privacy policies linked down below.
Third party Privacy Policies