GitHub · GitHub Acceptable Use Policies · View original document ↗

Spam, Bulk Activity, and Inauthentic Engagement Prohibition

Low severity Medium confidence Explicitdocumentlanguage Unique · 0 of 343 platforms
Share 𝕏 Share in Share 🔒 PDF
Monitor governance changes for GitHub Create a free account to receive the weekly governance digest and monitor one platform for governance changes.
Create free account No credit card required.
Document Record

What it is

The agreement prohibits using GitHub's systems to send spam, conduct excessive automated bulk activity, relay unsolicited advertising, or operate get-rich-quick solicitation schemes.

This analysis describes what GitHub's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

This provision restricts automated and bulk communications activity through GitHub infrastructure, which is relevant for organizations using GitHub Actions, bots, or API integrations for high-volume operations that may approach the threshold of prohibited bulk activity.

Interpretive note: The term 'excessive automated bulk activity' is not defined with a specific operational threshold, leaving the boundary between permissible high-volume automation and prohibited bulk activity subject to GitHub's discretionary interpretation.

Consumer impact (what this means for users)

Under this clause, using GitHub's systems to send unsolicited communications, operate bulk automated activity beyond permissible thresholds, or relay advertising solicitations is prohibited. API integrations and GitHub Actions workflows that involve high-volume outbound communications should be assessed against this restriction.

How other platforms handle this

Shopify Medium

You may not use Shopify's Services to send spam, unsolicited communications, or engage in harassment of any person. This includes using Shopify's email or messaging tools to send bulk unsolicited messages to consumers who have not opted in to receive communications from you.

Redfin Medium

You may not automatedly crawl or query the Services for any purpose or by any means (including, without limitation, screen and database scraping, spiders, robots, crawlers and any other automated activity with the purpose of obtaining information from the Services) unless you have received prior exp...

PayPal Medium

relate to transactions involving (f) the promotion of hate, violence, racial or other forms of intolerance that is discriminatory or the financial exploitation of a crime... (i) involve offering or receiving payments for the purpose of bribery or corruption.

See all platforms with this clause type →

Monitoring

GitHub has changed this document before.

Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.

Start Monitor free trial Or create a free account →
▸ View Original Clause Language DOCUMENT RECORD
"
You may not use our servers for any form of excessive automated bulk activity (including, for example, sending spam or cryptocurrency mining), to place undue burden on our servers through automated means, or to relay any form of unsolicited advertising or solicitation through our systems, such as get-rich-quick schemes.

— Excerpt from GitHub's GitHub Acceptable Use Policies

ConductAtlas Analysis

Institutional analysis (Compliance & governance intelligence)

1) REGULATORY LANDSCAPE: This provision engages the CAN-SPAM Act, which regulates commercial email and unsolicited bulk electronic messaging in the US. International equivalents include Canada's CASL and the EU's ePrivacy Directive. The FTC is the primary US enforcement authority for CAN-SPAM violations. 2) GOVERNANCE EXPOSURE: Low to Medium. The prohibition on spam and unsolicited advertising is standard across developer platform acceptable use policies. The reference to 'excessive automated bulk activity' without a defined threshold creates interpretive uncertainty for organizations running high-volume legitimate automation. 3) JURISDICTION FLAGS: Organizations operating across jurisdictions should assess whether their GitHub-mediated communications comply with CASL (Canada) and ePrivacy requirements (EU) in addition to CAN-SPAM. The 'get-rich-quick schemes' reference may also engage FTC regulations on deceptive marketing practices. 4) CONTRACT AND VENDOR IMPLICATIONS: Marketing automation workflows, CI/CD-triggered notification systems, and API-driven bulk operations should be reviewed to confirm they do not constitute prohibited bulk activity under this provision. GitHub's API rate limiting policies should be reviewed alongside this prohibition. 5) COMPLIANCE CONSIDERATIONS: Legal teams should confirm that any automated notification, alerting, or communication workflows integrated with GitHub comply with applicable anti-spam laws and do not constitute prohibited bulk activity under the AUP.

Full compliance analysis

Regulatory citations, enforcement risk, and due diligence action items.

Track 1 platform — free Try Monitor free for 14 days

Free: track 1 platform + weekly digest. Monitor: 25 platforms + same-day alerts. No credit card required.

Applicable agencies

  • FTC
    The FTC enforces CAN-SPAM and has jurisdiction over deceptive practices including unsolicited advertising and get-rich-quick scheme promotions conducted through digital platforms
    File a complaint →

Applicable regulations

CFAA
United States Federal
DMCA
United States Federal
DSA
European Union

Provision details

Document information
Document
GitHub Acceptable Use Policies
Entity
GitHub
Document last updated
May 12, 2026
Tracking information
First tracked
May 20, 2026
Last verified
May 20, 2026
Record ID
CA-P-012419
Document ID
CA-D-00790
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
4cb1cc8f63e15186f39023d0124a0552f90d900ee77625b9086bf67218c19c3e
Analysis generated
May 20, 2026 21:06 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: GitHub
Document: GitHub Acceptable Use Policies
Record ID: CA-P-012419
Captured: 2026-05-20 21:06:09 UTC
SHA-256: 4cb1cc8f63e15186…
URL: https://conductatlas.com/platform/github/github-acceptable-use-policies/spam-bulk-activity-and-inauthentic-engagement-prohibition/
Accessed: June 8, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Low
Categories

Other risks in this policy

Compliance Governance Intelligence

Need to monitor specific governance provisions?

Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.

Arbitration clauses AI governance Data rights Indemnification Retention policies
Start Compliance free trial

Or start with Monitor →

Built from archived source documents, structured governance mappings, and historical version tracking.

Frequently Asked Questions

What does GitHub's Spam, Bulk Activity, and Inauthentic Engagement Prohibition clause do?

This provision restricts automated and bulk communications activity through GitHub infrastructure, which is relevant for organizations using GitHub Actions, bots, or API integrations for high-volume operations that may approach the threshold of prohibited bulk activity.

How does this clause affect you?

Under this clause, using GitHub's systems to send unsolicited communications, operate bulk automated activity beyond permissible thresholds, or relay advertising solicitations is prohibited. API integrations and GitHub Actions workflows that involve high-volume outbound communications should be assessed against this restriction.

Is ConductAtlas affiliated with GitHub?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by GitHub.