Who we are

Our website address is: https://eastclevelandschools.org

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.

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 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.

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.

Who we share your data with

If you request a password reset, your IP address will be included in the reset email.

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 your data is sent

Visitor comments may be checked through an automated spam detection service.

Security

Our website uses specialist security software - ShieldPro. This helps to ensure data breaches do not occur and our website and data are protected against hacking attempts and intrusion. ShieldPro protects site visitors and works to block potential hacks while monitoring web traffic and filesystem changes.

To learn more about ShieldPro, please follow this link.

Cookies

1. The ShieldPro plugin never stores any sensitive, personally identifiable information in any cookie at any time.
2. In the case that the ShieldPro plugin needs to redirect a visitor or any request, it may use a cookie to prevent repeated/infinite redirect loops.
3. For registered/logged-in users, the ShieldPro plugin uses a cookie to track user sessions and control display of certain in-plugin admin notices.
4. The ShieldPro plugin does not normally use Cookies for unregistered site visitors. It may however use a cookie to register the closure of the undefined menu title security badge to prevent repeated display.

Data Storage: User Sessions

For logged-in users, the ShieldPro plugin stores information on the username, the IP address and the time of last login and last activity. This information is purged upon logout or data cleanup.

Data Storage: Audit Trail

The ShieldPro plugin has an Audit Trail feature that will log the following information:

1. Audit Trail message that may include email addresses
2. Logged-in username (where applicable)
3. Originating IP address of the request

For logged-in users this represents information that may be used to locate (by IP address) and identify individuals and their activity on the site.

This information is stored for security purposes by the site administrator.

This data is retained using an automated policy based on event sensitivity and then purged from the database. Retention currently spans approximately 24 hours (low signal), 30 days (standard), 180 days (warnings), and up to 730 days for high-value events.

 Akismet

We collect information about visitors who comment on Sites that use our Akismet Anti-spam service. The information we collect depends on how the User sets up Akismet for the Site, but typically includes the commenter's IP address, user agent, referrer, and Site URL (along with other information directly provided by the commenter such as their name, username, email address, and the comment itself).

What personal data we collect with Event Tickets and why we collect it

Event, Attendee, and Ticket Purchaser Information

Through the usage of Event Tickets, Event Tickets Plus, and Community Tickets, information may be collected and stored within your website’s database.

Suggested text:

If you create, submit, import, save, or publish event ticket information, as well as obtain RSVPs or purchase tickets to events, such information is retained in the local database:

1. Attendees information (RSVPs and Tickets): name and email address
2. Ticket information (RSVPs and Tickets): name, email address, and ticket number/SKU (via check-in page)
3. Ticket purchaser information: name and email address
4. Ticket purchaser billing address, which is collected through the use of WooCommerce, Easy Digital Downloads, or PayPal

Please note: The website owner can collect nearly any Attendee Information requested from ticket buyers by creating a custom registration form.

API Keys

Event Tickets 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 and PayPal. These API keys are not supplied by The Events Calendar.

Suggested text:

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 and PayPal.

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 request 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

The Events Calendar 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 personal data we collect with Events Calendear 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:

1. Venue information: name, address, city, country, state, postal code, phone, website, geographical coordinates (latitude and longitude)
2. Organizer information: name, phone, website, email
3. Event information: website, cost, description, date, time, image

Importing Events, Venues, and Organizers:

1. All data present within a CSV or ICS file and external URLs (for events, venues, organizers, and tickets)
2. 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)
3. 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 The Events Calendar.

Suggested text:

We make use of certain APIs, in order to provide specific features.

These APIs may include the following third party services: Google Maps (API key), Meetup (OAuth token), PayPal (email, Client ID, Client Secret), Eventbrite (API key, auth URL, Client Secret), and Zoom (email, Client ID, 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

The Events Calendar 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.