GitPro — Platform Terms & DMCA Policy
Version 1.0 · Effective: 2026-04-04
What GitPro Is
GitPro is a decentralized, peer-to-peer code distribution protocol — not a hosting service.
When you run GitPro, you are running your own server, on your own hardware, serving your own repositories. There is no central GitPro server. There is no GitPro Inc. There is no rack of drives somewhere storing your code. The code lives on the machine of whoever added it.
This distinction matters legally.
DMCA & Copyright Claims
GitPro is infrastructure, not a host.
Compare: SMTP is the protocol email travels over. You cannot DMCA the SMTP protocol. You cannot file a takedown against Postfix or Sendmail. You file against the server operator who is serving the mail.
GitPro is to code distribution what SMTP is to email. The repository owner is the host. The repository owner is responsible for what they serve.
If You Have a Copyright Claim
A copyright claim should be directed to the person operating the GitPro instance that is distributing the disputed material — not to this codebase, not to its authors, and not to any other instance of GitPro.
Each GitPro instance is independently operated. The operator of that instance is the relevant party under 17 U.S.C. § 512 (DMCA Safe Harbor).
To find who operates an instance:
/apps/gitpro/identity route on that instance shows the operator's public identity cardNo Central Takedown Path
There is no "report this repo" button that notifies a central authority, because there is no central authority. This is by design.
If a court orders a specific instance taken down, the operator of that instance receives the order — just like a self-hosted GitLab or a personal web server would. Other instances are unaffected.
DMCA Safe Harbor Applicability (Instance Operators)
If you run a GitPro instance and receive a DMCA notice, you may qualify for 17 U.S.C. § 512(c) safe harbor by:
1. Designating an agent — Register a DMCA agent with the U.S. Copyright Office (required for safe harbor)
2. Responding promptly — Remove or disable access to the disputed content upon receiving a valid notice
3. Counter-notice process — Follow the standard counter-notice procedure if the uploader disputes the claim
4. No direct financial benefit — Do not receive a direct financial benefit from the infringing activity
GitPro's architecture supports compliance: each repo has a known path on disk, identity-tracked committers, and can be disabled per-repo by the instance operator without affecting other repos.
Operator Responsibility
By running a GitPro instance accessible to others, you (the operator) accept that:
1. You are responsible for content served from your machine
2. You are the relevant party for any DMCA notices regarding that content
3. You should establish a process to receive and respond to copyright claims if you operate a public-facing instance
4. The GitPro software authors are not liable for content served by your instance
No Liability for Downstream Instances
The authors of GitPro (the software) are not liable for:
This is no different from how the Linux kernel authors are not liable for what runs on Linux, or how git's authors are not liable for what code gets committed.
Governed By ASIL
GitPro is part of the Open-Veil platform and is governed by the Astra Sovereign Intelligence License (ASIL) v1.0 (/LICENSE). Use of this software implies acceptance of those terms.
Contact
For questions about this policy: raise an issue in the repository this software came from.
For DMCA notices against a specific instance: contact the operator of that instance directly.
*GitPro does not take sides in copyright disputes. It takes sides on decentralization.*