GitHub collects Personal Data from you, automatically from your device, and from third parties
GitHub collects Personal Data directly from you, automatically from your device and from third parties. What it processes depends on how you interact with the Services (web, desktop or mobile apps), the features you use (such as pull requests, Codespaces or GitHub Copilot) and how you access the Services (such as your IDE).
Supporting quotations
Personal Data is collected from you directly, automatically from your device, and also from third parties.
The Personal Data GitHub processes when you use the Services depends on variables like how you interact with our Services (such as through web interfaces, desktop or mobile applications), the features you use (such as pull requests, Codespaces, or GitHub Copilot) and your method of accessing the Services (your preferred IDE).
Data Access & Collection · Company practice
Account data: handle, name, email, password, payment and transaction information when you open an account
When you open an account GitHub collects information such as your GitHub handle, name, email address, password, payment information and transaction information.
Supporting quotations
Account Data: We collect certain information when you open an account such as your GitHub handle, name, email address, password, payment information and transaction information.
Qualifications & exceptions
The list is introduced by "such as", so it gives examples rather than a complete list.
Data Access & Collection · Company practice
Personal Data inside your content is collected, including code, inputs, AI outputs, documents, images and feedback
When you use the Services GitHub collects Personal Data included in the information you provide, such as code, inputs, AI outputs, text, documents, images or feedback.
Supporting quotations
User Content and Files: When you use our Services, we collect Personal Data included as part of the information you provide such as code, inputs, AI outputs, text, documents, images, or feedback.
Qualifications & exceptions
The collected object is Personal Data that is part of what you provide, with examples introduced by "such as".
Data Access & Collection · Company practice
In some cases you provide demographic details such as ethnicity or gender
In some cases users provide GitHub with ethnicity, gender or similar demographic details, and GitHub lists these as data it collects from you.
Supporting quotations
Demographic information: In some cases, you provide us with ethnicity, gender, or similar demographic details.
Qualifications & exceptions
Collected only "in some cases" where you provide it.
Not stated here
The Statement does not say in which situations demographic details are requested or whether providing them is optional.
Data Access & Collection · Company practice
Feedback and support data: survey and review answers, and code, text or files sent to support
GitHub collects information you submit through surveys, reviews or interactive features, and, when you seek customer support, details such as code, text or multimedia files.
Supporting quotations
Feedback Data: This consists of information you submit through surveys, reviews, or interactive features.
Support Data: When you seek customer support, we collect details like code, text, or multimedia files.
Data Access & Collection · Company practice
Profile information such as a photo, extra emails, job title or biography is collected to create your profile
GitHub collects information to create a user profile, which may include a photo, additional email addresses, a job title or a biography.
Supporting quotations
Profile Information: We collect information to create a user profile, which may include a photo, additional email addresses, job title, or biography.
Data Access & Collection · Company practice
Sales and marketing data: name, email and company name given for promotional communications
GitHub collects information provided for promotional communications, such as your name, email address and company name.
Supporting quotations
Sales and Marketing Data: This includes information provided for promotional communications, such as name, email address, and company name.
Data Access & Collection · Company practice
Essential cookies and similar technologies store settings and recognize you
GitHub uses cookies and similar technologies to provide essential functionality, such as storing settings and recognizing you while you use the Services.
Supporting quotations
Essential Cookies and Similar Tracking Technologies: We use cookies and similar technologies to provide essential functionality like storing settings and recognizing you while using our Services.
Data Access & Collection · Company practice
Marketing emails may contain web beacons that report device, email client, opens and link clicks
GitHub's emails may contain web beacons that provide information on your device type, email client, email reception, opens and link clicks.
Supporting quotations
Email Marketing Interactions: Our emails may have web beacons that offer information on your device type, email client, email reception, opens, and link clicks.
Qualifications & exceptions
Emails "may" include beacons; not every email is said to.
Data Access & Collection · Company practice
Regional geolocation data is collected depending on the Service's functionality
Depending on a Service's functionality, GitHub collects regional geolocation data.
Supporting quotations
Geolocation Information: Depending on the Service's functionality, we collect regional geolocation data.
Qualifications & exceptions
The Statement describes the geolocation as regional, and collection depends on the Service's functionality.
Not stated here
How precise "regional" is and which Services collect it are not stated.
Data Access & Collection · Company practice
Service usage data: IP address, device and session details, timestamps, app versions and repository contributions
GitHub collects data about your interactions with the Services, such as IP address, device information, session details, date and time of requests, device type and ID, operating system and application version, information related to your contributions to repositories, and performance of specific features or Services. It also automatically logs website interactions, including the referring site, date and time of visit, pages viewed and links clicked.
Supporting quotations
Service Usage Information: We collect data about your interactions with the Services, such as IP address, device information, session details, date and time of requests, device type and ID, operating system and application version, information related to your contributions to repositories, and performance of specific features or Services.
Website Usage Data: We automatically log data about your Website interactions, including the referring site, date and time of visit, pages viewed, and links clicked.
Data Access & Collection · Company practice
Other users may share information about you through issues and comments, or by naming you on a company account
Other users may share information about you when they submit issues and comments. GitHub may also receive information about you if you are identified as a representative or administrator on your company's account.
Supporting quotations
Other users may share information about you when they submit issues and comments.
We may also receive information about you if you are identified as a representative or administrator on your company's account.
Data Access & Collection · Company practice
GitHub may acquire information about you from publicly available sources
GitHub may acquire information about you from publicly available sources.
Supporting quotations
Publicly Available Sources: We may acquire information about you from publicly available sources.
Not stated here
The public sources and the information obtained are not specified.
Data Access & Collection · Company practice
Linked third-party services, such as Google sign-in, send GitHub information based on your settings with them
When you or your administrator integrate third-party apps or services with GitHub, GitHub receives information based on your settings with those services, which can include your name and email from services like Google for authentication. What GitHub receives depends on the third party's settings and privacy policies, which GitHub tells you to review.
Supporting quotations
When you or your administrator integrate third-party apps or services with our Services, we receive information based on your settings with those services.
This can include details like your name and email from services like Google for authentication.
The information we receive depends on the third-party's settings and privacy policies.
Qualifications & exceptions
An administrator, not only you, can set up the integration.
Data Access & Collection · Company practice
Vendors, resellers, partners and affiliates may give GitHub information about you
GitHub may receive information about you from third parties such as vendors, resellers, partners or affiliates, for the purposes described in the Statement.
Supporting quotations
Vendors, Partners, and Affiliates: We may receive information about you from third parties, like vendors, resellers, partners, or affiliates for the purposes outlined in this statement.
Data Access & Collection · User right or choice
Codespaces and github.dev collect some VS Code telemetry by default; you can opt out in VS Code settings
GitHub Codespaces and github.dev offer Visual Studio Code in a web browser, where some telemetry is collected by default. Details are on the VS Code website. To opt out, go to File > Preferences > Settings in VS Code; opting out syncs that preference across all future web sessions in Codespaces and github.dev.
Supporting quotations
GitHub Codespaces and github.dev offer Visual Studio Code in a web browser, where some telemetry is collected by default.
To opt out, go to File > Preferences > Settings in the top left menu of VS Code. Opting out will sync this preference across all future web sessions in GitHub Codespaces and github.dev.
Qualifications & exceptions
Telemetry is on by default; you must opt out.
The opt-out applies to future web sessions.
Not stated here
The telemetry details are on the VS Code website, which is not supplied.
The recipient of the telemetry is not named in this passage, although it is listed under sharing.
Data Access & Collection · Company practice
Cookies keep you logged in, remember preferences, secure your device and compile statistics
GitHub uses cookies to provide, secure and improve its Service and to develop new features, for example to keep you logged in, remember your preferences, identify your device for security and fraud purposes, compile statistical reports and inform future development. It also uses similar technologies such as web beacons, local storage and mobile analytics to operate and provide the Services. GitHub says it provides more information about the cookies it sets, why, and when they expire.
Supporting quotations
GitHub uses cookies to provide, secure and improve our Service or to develop new features and functionality of our Service.
For example, we use them to (i) keep you logged in, (ii) remember your preferences, (iii) identify your device for security and fraud purposes, including as needed to maintain the integrity of our Service, (iv) compile statistical reports, and (v) provide information and insight for future development of GitHub.
We use cookies and similar technologies, such as web beacons, local storage, and mobile analytics, to operate and provide our Services.
Qualifications & exceptions
In the saved version this cookie text follows the "Other translations" heading without a heading of its own; it is read as the Statement's cookie section.
Not stated here
The more detailed cookie list it mentions is not supplied in this text.
Data Access & Collection · Company practice
Emails may contain a pixel tag that tells GitHub whether you opened them and your IP address
GitHub's emails to users may contain a pixel tag, a small clear image that can show whether you opened the email and what your IP address is. GitHub says it uses it to make its emails more effective and to avoid sending you unwanted email.
Supporting quotations
Our emails to users may contain a pixel tag, which is a small, clear image that can tell us whether or not you have opened an email and what your IP address is.
We use this pixel tag to make our email communications more effective and to make sure we are not sending you unwanted email.
Qualifications & exceptions
In the saved version this cookie text follows the "Other translations" heading without a heading of its own; it is read as the Statement's cookie section.
Data Access & Collection · Company practice
GitHub may use flash cookies (Local Shared Objects) to store information about your use
GitHub may also use flash cookies, also known as Local Shared Objects, to collect and store information about your use of the Services. The Statement notes these are commonly used for advertisements and videos.
Supporting quotations
We may also use so-called “flash cookies” (also known as “Local Shared Objects” or “LSOs”) to collect and store information about your use of our Services.
Flash cookies are commonly used for advertisements and videos.
Qualifications & exceptions
In the saved version this cookie text follows the "Other translations" heading without a heading of its own; it is read as the Statement's cookie section.
Not stated here
The Statement does not say how flash cookies can be removed or controlled.
Data Access & Collection · Company practice
Required cookies run essential functions such as login, language, cart, traffic routing and audience measurement
In the cookie table, required cookies perform essential website functions and provide the services, for example logging you in, saving language preferences, providing a shopping cart, improving performance, routing traffic, detecting screen size, measuring page load times, improving user experience and audience measurement. GitHub says these cookies are necessary for its websites to work.
Supporting quotations
GitHub uses required cookies to perform essential website functions and to provide the services.
For example, cookies are used to log you in, save your language preferences, provide a shopping cart experience, improve performance, route traffic between web servers, detect the size of your screen, determine page load times, improve user experience, and for audience measurement.
These cookies are necessary for our websites to work.
Qualifications & exceptions
Row of the cookie table (Purpose / Description).
Audience measurement is listed among the required-cookie uses.
Data Access & Collection · Company practice
US notice: collected categories include identifiers, demographics, payment, network activity, geolocation and inferences
GitHub may collect categories of personal information about website visitors and users of its Services, including identifiers and contact information, demographic information, payment and commercial information, internet or network activity, geolocation, audio, electronic, visual or similar information, and inferences drawn from them. It collects them for purposes including identifying accessibility gaps and offering targeted support, fostering diversity and representation, providing services, troubleshooting, billing and security, improving products and supporting research, communications, personalization, and safety and security.
Supporting quotations
US State Specific Information
That information includes identifiers/contact information, demographic information, payment information, commercial information, internet or electronic network activity information, geolocation data, audio, electronic, visual, or similar information, and inferences drawn from such information.
This includes identifying accessibility gaps and offering targeted support, fostering diversity and representation, providing services, troubleshooting, conducting business operations such as billing and security, improving products and supporting research, communicating important information, ensuring personalized experiences, and promoting safety and security.
Qualifications & exceptions
Applies to residents of certain US states with their own privacy laws; the states are not all named in this section.
Data Access & Collection · Context
California: categories collected in the last 12 months include identifiers, gender, payment card and inferences
For California compliance, GitHub discloses that in the last 12 months it collected identifiers and contact information, demographic information (such as gender), payment card information, commercial information, internet or network activity, geolocation, audio, electronic, visual or similar information, and inferences, from you directly, automatically or from third parties, for the purposes summarized in the Statement's Processing Purposes section.
Supporting quotations
California
We also make the following disclosures for purposes of compliance with California privacy law:
We collected the following categories of personal information in the last 12 months: identifiers/contact information, demographic information (such as gender), payment card information associated with you, commercial information, Internet or other electronic network activity information, geolocation data, audio, electronic, visual or similar information, and inferences drawn from the above.
The sources of personal information from whom we collected are: directly from you, automatically or from third parties.
The business or commercial purposes of collecting personal information are as summarized above and in our Privacy Statement under Processing Purposes.
Qualifications & exceptions
California disclosure covering the last 12 months.