Who we are
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.
We use contact forms for "Prayer Requests" and "Testimonials". All data will be kept private and will not be used for any monetary or legal actions.
If you leave a comment 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 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.
Who we share your data with
Some data are shared with Facebook.com, Google.com, Bing.com, WordPress, and third-party web monitoring systems. RSS data feeds are also linked to third-party websites who may collect general online data.
How long we retain your data
If you leave a comment, prayer request, or testimony, these items 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.
Where we send your data
Visitor comments, prayer requests, and testimonials are checked through an automated spam detection appliance.
Your contact information
Please email the website developer at: email@example.com
Facebook items are covered by Facebook privacy policies. Please visit www.facebook.com for Privacy Information.
Google YouTube items are covered by Google privacy policies.
How we protect your data
FICC website uses GoDaddy.com SSL data package using 256-bit encryption. Additional security appliances are installed in the website such as Asimet! anti-spam plugin and Google.com reCAPTCHA v2 anti-robot security.
What data breach procedures we have in place
In the event of a breach, the website will automatically be taken offline and the source of the breach will be submitted to cyber-related crimes law enforcement agencies.
Industry regulatory disclosure requirements
No personal data, such as home addresses, full names, non-business phone numbers, and personal emails, are to be used in the website. Although some pages are "not mapped" or rendered invisible to the Internet, all data should be considered PUBLIC.