GitHub Traffic Viewer ("us", "we", or "our") operates this website (the "Service").
17 | 18 |
19 | This page informs you of our policies regarding the collection, use, and disclosure of personal data when you
20 | use our Service and the choices you have associated with that data. Our Privacy Policy for GitHub Traffic Viewer
21 | is managed through{' '}
22 |
29 | We use your data to provide and improve the Service. By using the Service, you agree to the collection and use
30 | of information in accordance with this policy. Unless otherwise defined in this Privacy Policy, terms used in
31 | this Privacy Policy have the same meanings as in our Terms and Conditions, accessible from
32 |
40 | We collect several different types of information for various purposes to provide and improve our Service to 41 | you. 42 |
43 | 44 |49 | While using our Service, we may ask you to provide us with certain personally identifiable information that can 50 | be used to contact or identify you ("Personal Data"). Personally identifiable information may include, but is 51 | not limited to: 52 |
53 | 54 |61 | We may also collect information how the Service is accessed and used ("Usage Data"). This Usage Data may include 62 | information such as your computer's Internet Protocol address (e.g. IP address), browser type, browser version, 63 | the pages of our Service that you visit, the time and date of your visit, the time spent on those pages, unique 64 | device identifiers and other diagnostic data. 65 |
66 | 67 |69 | We use cookies and similar tracking technologies to track the activity on our Service and hold certain 70 | information. 71 |
72 |73 | Cookies are files with small amount of data which may include an anonymous unique identifier. Cookies are sent 74 | to your browser from a website and stored on your device. Tracking technologies also used are beacons, tags, and 75 | scripts to collect and track information and to improve and analyze our Service. 76 |
77 |78 | You can instruct your browser to refuse all cookies or to indicate when a cookie is being sent. However, if you 79 | do not accept cookies, you may not be able to use some portions of our Service. 80 |
81 |Examples of Cookies we use:
82 |GitHub Traffic Viewer uses the collected data for various purposes:
94 |106 | Your information, including Personal Data, may be transferred to — and maintained on — computers located outside 107 | of your state, province, country or other governmental jurisdiction where the data protection laws may differ 108 | than those from your jurisdiction. 109 |
110 |111 | If you are located outside Germany and choose to provide information to us, please note that we transfer the 112 | data, including Personal Data, to Germany and process it there. 113 |
114 |115 | Your consent to this Privacy Policy followed by your submission of such information represents your agreement to 116 | that transfer. 117 |
118 |119 | GitHub Traffic Viewer will take all steps reasonably necessary to ensure that your data is treated securely and 120 | in accordance with this Privacy Policy and no transfer of your Personal Data will take place to an organization 121 | or a country unless there are adequate controls in place including the security of your data and other personal 122 | information. 123 |
124 | 125 |129 | GitHub Traffic Viewer may disclose your Personal Data in the good faith belief that such action is necessary to: 130 |
131 |141 | The security of your data is important to us, but remember that no method of transmission over the Internet, or 142 | method of electronic storage is 100% secure. While we strive to use commercially acceptable means to protect 143 | your Personal Data, we cannot guarantee its absolute security. 144 |
145 | 146 |148 | We may employ third party companies and individuals to facilitate our Service ("Service Providers"), to provide 149 | the Service on our behalf, to perform Service-related services or to assist us in analyzing how our Service is 150 | used. 151 |
152 |153 | These third parties have access to your Personal Data only to perform these tasks on our behalf and are 154 | obligated not to disclose or use it for any other purpose. 155 |
156 | 157 |We monitor and analyze the use of our Service.
159 |162 | Analytics 163 |
164 |165 | We use a self-hosted analytics solution with server in Germany to track data like browser, operating system 166 | and visited pages. 167 |
168 |173 | Our Service may contain links to other sites that are not operated by us. If you click on a third party link, 174 | you will be directed to that third party's site. We strongly advise you to review the Privacy Policy of every 175 | site you visit. 176 |
177 |178 | We have no control over and assume no responsibility for the content, privacy policies or practices of any third 179 | party sites or services. 180 |
181 | 182 |Our Service does not address anyone under the age of 18 ("Children").
184 |185 | We do not knowingly collect personally identifiable information from anyone under the age of 18. If you are a 186 | parent or guardian and you are aware that your Children has provided us with Personal Data, please contact us. 187 | If we become aware that we have collected Personal Data from children without verification of parental consent, 188 | we take steps to remove that information from our servers. 189 |
190 | 191 |193 | We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy 194 | Policy on this page. 195 |
196 |197 | We will let you know via email and/or a prominent notice on our Service, prior to the change becoming effective 198 | and update the "effective date" at the top of this Privacy Policy. 199 |
200 |201 | You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are 202 | effective when they are posted on this page. 203 |
204 | 205 |If you have any questions about this Privacy Policy, please contact us:
207 |