GitHub Apps access repository code, commit history, pull requests, issues, and contributor data through GitHub's API. Depending on the permissions requested, a GitHub App can read private source code, access organization member lists, and modify repository content. GitHub's App Marketplace requires a privacy policy, and enterprise organizations will require detailed documentation of what your app reads and stores before approving installation across their organization. The United States has a sectoral approach to data privacy — no single federal law covers all businesses, but multiple laws apply depending on your industry and the data you collect.
No signup required Download as HTML Ready in 2 minutes
All sections are included and pre-filled for GitHub App businesses
Introduction
Included in all documents
Information We Collect
Included in all documents
How We Use Your Information
Included in all documents
How We Share Your Information
Included in all documents
Cookies and Tracking Technologies
Included in all documents
Data Retention
Included in all documents
Your Rights Under the GDPR
Included in all documents
Your California Privacy Rights (CCPA)
Included in all documents
Your Rights Under the DPDPA (India)
Included in all documents
Children's Privacy
Included in all documents
Data Security
Included in all documents
Third-Party Links
Included in all documents
Changes to This Privacy Policy
Included in all documents
Contact Us
Included in all documents
The United States has a sectoral approach to data privacy — no single federal law covers all businesses, but multiple laws apply depending on your industry and the data you collect. Key federal laws include COPPA (children's data), HIPAA (health data), GLBA (financial data), and CAN-SPAM (email marketing). FTC enforcement can result in significant penalties for deceptive data practices.
A Privacy Policy for GitHub App businesses must specifically address the following considerations that are unique to this industry. Unlike generic templates, your policy needs to reflect how github app businesses actually collect and process data.
Data typically collected by GitHub App businesses: GitHub usernames and profile data, repository content and code (based on permissions), commit history and authorship data, pull request and issue content, organization membership data, webhook event data, installation and usage analytics
Yes. If you collect any personal data from users — including email addresses, analytics cookies, or payment information — you are legally required to have a Privacy Policy under FTC Act Section 5, COPPA, CAN-SPAM Act, HIPAA (if applicable), State privacy laws (CCPA, VCDPA, CPA, etc.). Non-compliance can result in significant fines.
A US-compliant Privacy Policy for GitHub App businesses must disclose: what data you collect (GitHub usernames and profile data, repository content and code (based on permissions), commit history and authorship data, pull request and issue content, organization membership data, webhook event data, installation and usage analytics), the legal basis for processing, data retention periods, and users' rights. Privacy policy must accurately describe actual data practices (FTC Act Section 5).
A GitHub App typically collects: GitHub usernames and profile data, repository content and code (based on permissions), commit history and authorship data, pull request and issue content, organization membership data, webhook event data, installation and usage analytics. Under US, each category of data must be explicitly disclosed in your Privacy Policy along with the purpose for collecting it and the legal basis used. Failing to disclose any collected data category is a violation.
Non-compliance with US requirements can result in regulatory investigations, enforcement actions, and reputational damage. HIPAA Business Associate Agreements required if handling health data.