Traverse Landing Page

What Information does Traverse collect?

When using Traverse (https://bkfighter.com/traverse) users may have the following data collected and stored about them by Traverse or third party services. If you do not agree to the policies as outlined you should not use Traverse.

For all users

Traverse collects and stores the following information in logs regarding http/https requests for all users.

IP Address
Page Accessed
Timestamp
Browser/Platform

For users signed in with Google’s Sign-In button

Upon initial sign-in, Traverse collects and stores the following data from your Google account, as well as other site activity over time.

OAuth User Id - A unique identifier for your Google account used to link your Google and Traverse accounts. This is not visible to clients and can’t be changed.
Username - Your Google account’s full name by default. This is visible to clients and can be changed once every 30 days from your profile page when signed in. (Link in site footer).
Email - Your Google account’s email address. This is not visible to clients and can’t be changed. Currently your email is not used by Traverse but by creating an account you agree to allow Traverse to email this address in the future when notification settings are implemented.
Picture - Your Google account’s profile picture link by default. This is visible to clients and can be changed once every 30 days from your profile page when signed in. (Link in site footer).
Other site activity - Traverse may collect data as you interact with the site including, but not limited to, time stamps, comments, and other interactions.

To delete or modify your account, or if you have additional questions, you may email bkfighter@bkfighter.com.

What Traverse doesn’t associate with signed-in users.

Geolocation - Traverse does not collect geolocation data in our servers. (See Third Party Services for more information).
Financial/Government Identification - Traverse does not collect credit/debit cards, social security numbers, drivers licenses, and other forms of financial/government identification forms.
Passwords - Traverse uses Google OAuth services for sign-in and doesn’t store any passwords to achieve this.

Third Party Services

Traverse uses third party services for various purposes. Traverse uses these services as detailed.

Google Sign-In Button - Traverse uses Google accounts for sign in and account creation services (as detailed in For users signed in with Google’s Sign-In button). More information on this service can be accessed at their support page (https://support.google.com/accounts/answer/112802) or Google’s privacy policy (https://policies.google.com/technologies/partner-sites).
Google Analytics - Traverse uses Google Analytics for monitoring site use. Traverse doesn’t tie Analytics data to Traverse Users. Information collected by this service may also be used by Google. More information on this service can be accessed at their landing page (https://marketingplatform.google.com/about/analytics/) or Google’s privacy policy (https://policies.google.com/technologies/partner-sites).
Google AdSense - Traverse uses Google AdSense to display paid ads to users. AdSense ads may be influenced by information obtained by Google Analytics or other data collected by Google on other sites/services. You can change your AdSense settings/preferences at (https://google.com/settings/ads/) or more broadly at (http://www.aboutads.info/choices/). Google’s privacy policy (https://policies.google.com/technologies/partner-sites).

What Cookies does Traverse use?

Traverse (https://bkfighter.com/traverse) and it's third party services may use cookies to track users as they use the site. If you do not agree to the policies as outlined you should not use Traverse.

For all users

Traverse itself only uses cookies on signed out users to check if they have previously accepted the privacy and cookie policy of this site. However, all users may be subject to tracking by cookies from third party services used by Traverse. (See Third Party Services for more information).

Cookie_agree - Used to track users who have accepted the privacy and cookie policy in the last 30 days.

For users signed in with Google’s Sign-In button

To track signed in users and keep them signed in across different pages, Traverse uses some cookies in conjunction with Google’s Sign-In button.

PHPSESSID - Used to track signed in users by Traverse.
G_ENABLED_IDPS, _ga, _gid - Used to track signed in users by Google.

Third Party Services

Traverse uses third party services which may place cookies on the users device.

Google Sign-In Button - Google Sign-In uses cookies (detailed in For users signed in with Google’s Sign-In button) to sign users into Traverse.
Google Analytics - Google Analytics may use cookies to track a users’ use of Traverse. This includes but is not limited to information like pages visited, duration, and session information. More information on Analytics’ use of cookies can be accessed at their developer page (https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage).
Google AdSense - Google AdSense may use cookies to help target ads to users and track ad engagements. More information on AdSense’s use of cookies can be accessed at their support page (https://support.google.com/adsense/answer/7549925).

Last updated: November 20, 2019