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
What Are Cookies
Included in all documents
Types of Cookies We Use
Included in all documents
Third-Party Cookies
Included in all documents
Cookie Consent
Included in all documents
Managing and Disabling Cookies
Included in all documents
Data Collected Through Cookies
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 Cookie 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
A Cookie Policy is best practice for US, even if not strictly mandated. It demonstrates transparency and builds user trust. For GitHub App businesses using analytics or advertising tools, it is strongly recommended.
A typical GitHub App website uses: essential session cookies, analytics cookies (Google Analytics, etc.), functional preference cookies, and marketing/advertising cookies if you run paid campaigns. Each type must be disclosed in your Cookie Policy with its purpose.
Under US, a Cookie Policy alone is not sufficient. A consent mechanism is recommended for analytics and marketing cookies to align with global privacy best practices.