Legal
Upstream terms
These terms cover repositories and community content on upstream.codes. They supplement the Coline terms of service, which also apply to your Upstream account. If the two conflict about an Upstream feature, these terms control for that feature. The Coline privacy policy explains how we handle personal information on Upstream.
Last updated October 11, 2026
What you can publish
Upstream is operated by Coline Technologies, Inc. You can host code repositories and publish commits, issues, change requests, reviews, discussions, releases, profile information, and other project content. You keep ownership of what you submit. You are responsible for your content and for having the rights needed to upload, share, and license it, including content submitted by people or tools acting through your account.
The license in the Coline terms allows us to store, process, display, transmit, and otherwise handle your content to operate Upstream. It does not transfer ownership of your code to Coline, and we don't use your code to train AI models.
Your account and public profile
Upstream uses your Coline account. Your profile at upstream.codes/your-handle shows your handle, display name, avatar, and the bio, website, pinned repositories, and organizations you choose to add. It also shows your activity in public repositories, including a contribution calendar. You can turn off contribution activity in your profile settings.
Commits include the author name and email address recorded by Git. In a public repository, anyone can see them. We link commits to your profile only through email addresses you have verified.
Public repositories and forks
A public repository can be viewed, searched, cloned, and forked by others. By making content public, you permit Upstream to provide those features and permit others to view, clone, and fork that content through the service. Public visibility alone does not grant a license to use code outside those service features. If you want to grant broader rights, include a license in your repository.
A fork is a separate repository. Changes to your repository's visibility or deletion do not automatically remove existing forks, copies already cloned by others, or information retained as required by law. Check what you publish before making a repository public. Do not commit passwords, private keys, tokens, or other secrets.
If you contribute to someone else's repository, its license and contribution rules may also apply. You are responsible for understanding those rules before contributing.
Respect other people's rights
Do not upload or distribute content that you lack permission to share, infringes copyright or other rights, exposes another person's private information, or violates the Coline acceptable use rules. We may restrict access to content, repositories, or accounts while we review reports or address violations.
We maintain a policy to terminate accounts of repeat copyright infringers in appropriate circumstances. We consider the facts of each report, including whether a claim was withdrawn or successfully disputed. See our copyright and takedown policy for how to report a claim or respond to a removal.
AI review and triage
Repository owners can turn on AI code review and issue triage. When they do, change requests, diffs, issues, and comments in that repository are sent to AI model providers to produce reviews, labels, and summaries. Triage can flag content that looks like spam, and maintainers decide what to do with it. AI output can be wrong, so review it before relying on it.
GitHub sync and mirrors
If you sync or mirror a repository with GitHub, its contents and history are copied to GitHub, and GitHub's terms apply to the copy there. Removing a repository from Upstream doesn't remove the copy on GitHub.
Reports and questions
For copyright claims, use the copyright and takedown policy. For other content concerns, contact support@coline.app. For questions about these terms, contact legal@coline.app.