Last modified: MM/DD/YYYY
The Boulder Track Club (BTC) is a Colorado non-profit corporate organization which promotes running, racing, and socializing. Our website address is: https://BoulderTrackClub.com.
When you join, BTC collects your name, phone #, email address, physical address, gender, and shirt size. This information is not transmitted to any third parties without your written permission or a court order. You can see and edit your personal information at any time (except you cannot change your name). Website administrators can also see and edit that information.
When you enter race results on the site, we collect the data shown in the data entry form, and also your IP address and browser user agent string to help spam detection. Race results can be edited or deleted at any time if you’re signed-in. If you can’t sign-in, you can request your race results to be removed.
When a site visitor uses the Contact Form to send a message to BTC, the visitor’s name, email address, and optionally their phone # are collected for the sole purpose of responding to the visitor’s message.
If you sign-in to the BTC web site and choose the option to stay signed in, then an encrypted cookie with your identity is stored on your current device. Otherwise, a temporary session cookie is created which, in most web browsers, expires when you close the web tab or browser.
BTC uses third party software on the web site. The BTC web site is built, in part, using WordPress software. Word Press will create its own cookies. For further information, visit the WordPress privacy policy.
If you have an account on this site, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us which we've stored. 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. Otherwise, member data is retained indefinitely.
The BTC sign-in process relies on Google’s single sign-on (SSO) service. This is also known as Firebase. When using the Firebase service, your authentication data (eg email or phone #) can be sent to Google’s Firebase as well as third party identity authenticators (eg Yahoo.com, Github.com, etc). According to Firebase: “Phone numbers that end-users provide for authentication will be sent and stored by Google to improve our spam and abuse prevention across Google services, including but not limited to Firebase.” (https://firebase.google.com/docs/auth/web/phone-auth)