You must have a GitHub account to use Replicate — you cannot create a standalone Replicate account, which means your access to Replicate is tied to and dependent on your GitHub account status.
Your Replicate access is entirely dependent on your GitHub account — if GitHub suspends or restricts your account for any reason, you will lose access to Replicate and any models, data, or workflows stored there.
Cross-platform context
See how other platforms handle Account Requires GitHub Authentication and similar clauses.
Compare across platforms →Mandatory GitHub authentication means that if your GitHub account is suspended, restricted, or compromised, you automatically lose access to Replicate and all associated data — creating a single point of failure for your Replicate access and data.
(1) REGULATORY FRAMEWORK: This provision engages GDPR Art. 28 (GitHub as a sub-processor handling authentication data) and potentially GDPR Art. 46 (international transfers if GitHub processes EU authentication data in the US). CCPA §1798.140 applies to the personal data shared with GitHub as part of the authentication flow. The FTC Act Section 5 is implicated if mandatory third-party authentication creates data sharing consumers are unaware of. (2)
Compliance intelligence locked
Regulatory citations, enforcement risk, and due diligence action items.
Watcher: regulatory citations. Professional: full compliance memo.