Feb 21, 2019 is our Club Contest. Visitors welcome!

Who we are

Our website address is: https://dallastoastmasters.com.

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.

Security Logs

The IP address of visitors, user ID of logged in users, and username of login attempts are conditionally logged to check for malicious activity and to protect the site from specific kinds of attacks. Examples of conditions when logging occurs include login attempts, log out requests, requests for suspicious URLs, changes to site content, and password updates. This information is retained for 21 days.

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.

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:

  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

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

Contact forms

By submitting your information to us via any contact form, any information you provide will be collected by us. We use this information to reply to your email. This information does go to a club member who will be responding. Email addresses are not collected by the club for marketing purposes. By submitting an email via the contact form, you understand that your email address is transmitted to a club member, and the club has no control over how they store or protect your email address.

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. Cookies are used to handle importing and restoring backups. Cookies used during the restore/import process expire after 24 hours.
Visiting the login page sets a temporary cookie that aids compatibility with some alternate login methods. This cookie contains no personal data and expires after 1 hour.

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

A QR code image is generated for users that set up two-factor authentication for this site. This image is generated using Google Chart's API. As part of generating this image, your username is sent to the API. For details about Google Chart's privacy policy, please see Security and Privacy in Charts. When using the Remember Device for Two-Factor, a cookie (itsec_remember_2fa) will be set with a secure token that expires in 30 days.

This site is scanned for potential malware and vulnerabilities by Sucuri's SiteCheck. We do not send personal information to Sucuri; however, Sucuri could find personal information posted publicly (such as in comments) during their scan. For more details, please see Sucuri's privacy policy.

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. Security logs are retained for 21 days.

Backups

Backup retention is completely up to the website owner. This can vary from less than one minute to indefinitely.

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. This web site uses a third party service to manage administrative tasks. If you leave a comment, submit personal information via a contact form, or otherwise exchange personal details with us, it is possible that we may use this service to manage that data. Please visit the iThemes Privacy Policy for more information regarding the way they handle their data.
This site is part of a network of sites that protect against distributed brute force attacks. To enable this protection, the IP address of visitors attempting to log into the site is shared with a service provided by ithemes.com. For privacy policy details, please see the iThemes Privacy Policy.

Backups

Backups are not automatically sent to remote destinations automatically, however backups can be configured to be sent to third-party servers.

Backup Destinations

Backups can be sent to third-party destination servers, including but not limited to:

Links to third party privacy policies have been included

How we protect your data

Backups

Backup zip files are stored with hashed file names to prevent filename guessing and directory browsing is disabled.