Who we are
Our website address is: http://www.medinacommunityband.org/
What personal data we collect and why we collect it
Comments
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.
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.
Media
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.
Contact forms
All forms on this website collect data that you enter as well as the IP address of the terminal the inputs are filled out and submitted from. This data is kept indefinitely and not sold to third parties.
Cookies
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.
These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.
Analytics
We use Google Analytics to track users and usage of our website.
Who we share your data with
Donations are accepted using PayPal. Your data in reference to that donation is collected by PayPal but Medina Community Band never sees or has access to your account or bank transactions.
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.
Your contact information
PO Box 1477
Medina, OH 44258
Conductor Marcus Neiman: 330.725.8198
Additional information
How we protect your data
Our website software is regularly updated. Our users are required to use secure passwords. Third party vendors are reputable and established.
What data breach procedures we have in place
We have no formal data breach procedures in place. Please contact us for assistance.
What third parties we receive data from
We receive data from MailChimp – our mail campaign service.
Source: EWWW Image Optimizer
By default, the EWWW Image Optimizer does not store any personal data nor share it with anyone.
If you accept user-submitted images and use the API or ExactDN, those images may be transmitted to third-party servers in foreign countries. If Backup Originals is enabled, images are stored for 30 days. Otherwise, no images are stored on the API for longer than 30 minutes.
User-submitted images may be transmitted to image compression servers in the United States and stored there for up to 30 days.
User-submitted images that are displayed on this site will be transmitted and stored on a global network of third-party servers (a CDN).
Source: Akismet
Source: The Events Calendar
What personal data we collect and why we collect it
Event, Venue, and Organizer Information
Through the usage of The Events Calendar, Events Calendar PRO, The Events Calendar Filter Bar, Eventbrite Tickets, and Community Events plugins, as well as our Event Aggregator Import service (contained within The Events Calendar plugin), information may be collected and stored within your website’s database.
Suggested text:
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.
API Keys
The Events Calendar suite offers the use of third-party API keys. The primary functions are to enhance the features we’ve built in, some of which use Google Maps, PayPal, Eventbrite, and Meetup. These API keys are not supplied by Modern Tribe.
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.
What automated decision making and/or profiling we do with user data
We have no automated decision making/profiling in place that takes place on our website. PayPal, how we collect donations, may.
Industry regulatory disclosure requirements
None