Who we are
Chiefland Farmer’s Flea Market
1209 N Young Blvd
Chiefland, Florida 32626
Phone: (352) 493-2022
Our website address is: https://chieflandfleamarket.com.
What personal data we collect and why we collect it
By default, WordPress does not collect any personal data about visitors, and only collects the data shown on the User Profile screen from registered users. However, some of your plugins may collect personal data. You should add the relevant information below.
We do not collect or keep any of your personnel data except that which is stated in these other sections. We do reserve the right to add, change or delete any information in this page when required.
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 do use a contact form program for our customers and future vendors can use to contact us directly with your questions and answers. The form collects your name and email address along with your questions. We keep the email for 30 days unless you become a vendor then your information stays on file.
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 visit our login page, 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.
At the current time we do not use any analytics programs except collecting visitor’s data using JetPack program that records the number of visitors, what country they access the sites and which pages or posts were visited.
Who we share your data with
We do not share your personal data with anyone that we have not mentioned in other sections of this page.
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.
Where we send your data
Visitor comments may be checked through an automated spam detection service. Otherwise we do not send your data anywhere unless specifically sited in other sections of the page.
Your contact information
Should have any questions or concerns about your information please contact us via email: firstname.lastname@example.org
None at this time.
How we protect your data
Your information and our website information is protected by the SSL service as well as Cerber Security Anti-Spam and Malware protection program. Your log-in information requires two-factor authorization. We only have a couple employees and all have been trained to protect the customers and vendors information.
What data breach procedures we have in place
We keep our website updated to prevent security risks to the software, database and customer and vendor information that is contained within. We also employ the use of security software monitoring.
What third parties we receive data from
Your data is not shared with any third parties for any reason unless stated specifically in other sections of this page.
What automated decision making and/or profiling we do with user data
None at this time.
Industry regulatory disclosure requirements
We do not have any industry regulatory disclosure requirements that we are aware of other than those already posted in other sections of the page.
Disclaimer: This information is only for guidance and not to be considered as legal advice.
What personal data we collect and why we collect it
Event, Venue, and Organizer Information
If you create, submit, import, save, or publish Event, Venue, or Organizer information, such information is retained in the local database:
Venue information: name, address, city, country, state, postal code, phone, website, geographical coordinates (latitude and longitude)
Organizer information: name, phone, website, email
Event information: website, cost, description, date, time, image
Importing Events, Venues, and Organizers:
All data present within a CSV or ICS file and external URLs (for events, venues, organizers, and tickets)
Import origin data (URL from where events are being imported—such as Eventbrite, MeetUp, other compatible URL sources, and more, which can include similar or same data as listed above)
Eventbrite Ticket information: name, description, cost, type, quantity
Please note that to create new events through the Community Events submission form, a user must hold a website account on this domain. This information is retained in the local database. It is also possible to create events anonymously, if the site owner has this option enabled.
When purchasing Eventbrite Tickets, attendee, purchaser, and order information are stored and managed by Eventbrite.
We make use of certain API keys, in order to provide specific features.
These API keys may include the following third party services: Google Maps, Meetup, PayPal, and Eventbrite (API key, auth URL and Client Secret).
How Long You Retain this Data
All information (data) is retained in the local database indefinitely, unless otherwise deleted.
Certain data may be exported or removed upon users’ requests via the existing Exporter or Eraser. Please note, however, that several “edge cases” exist in which we are unable to perfect the gathering and export of all data for your end users. We suggest running a search in your local database, as well as within the WordPress Dashboard, in order to identify all data collected and stored for your specific user requests.
Where We Send Your Data
Modern Tribe does not send any user data outside of your website by default.
If you have extended our plugin(s) to send data to a third-party service such as Eventbrite, Google Maps, or PayPal, user information may be passed to these external services. These services may be located abroad.
Smush sends images to the WPMU DEV servers to optimize them for web use. This includes the transfer of EXIF data. The EXIF data will either be stripped or returned as it is. It is not stored on the WPMU DEV servers.
Smush uses a third-party email service (Drip) to send informational emails to the site administrator. The administrator’s email address is sent to Drip and a cookie is set by the service. Only administrator information is collected by Drip.