|
| 1 | +Dear GitHub Copyright Team, |
| 2 | + |
| 3 | +I am submitting an urgent DMCA takedown request, private information removal request, and account review request regarding the unauthorized public upload of our private/proprietary source code. |
| 4 | + |
| 5 | +Infringing repository URL: |
| 6 | +https://github.com/msar-beep/Msar |
| 7 | + |
| 8 | +Repository owner / GitHub username: |
| 9 | +msar-beep |
| 10 | + |
| 11 | +I am [private], [private] / authorized representative of Tech AI Bridge (Private) Limited. Tech AI Bridge is an IT services provider, and this project was developed and managed under our company’s ownership, [private] repositories, servers, backend infrastructure, and internal control systems. |
| 12 | + |
| 13 | +The repository above contains private proprietary source code for our MSAR / Driver and Passenger application. This code is not open source and was never authorized to be published publicly on GitHub. |
| 14 | + |
| 15 | +The repository contains confidential business logic, mobile application code, backend/API implementation, project architecture, application structure, configuration references, database/API details, server-related implementation references, and other private implementation material. Public availability of this repository creates serious privacy, security, commercial, and operational risk for our company. |
| 16 | + |
| 17 | +Ownership / authorization proof: |
| 18 | +Our official [private] organization: |
| 19 | +[private] |
| 20 | + |
| 21 | +Our original project repositories: |
| 22 | +[private] |
| 23 | +[private] |
| 24 | + |
| 25 | +All source code, APIs, backend logic, server-side implementation, application architecture, and project materials belong to Tech AI Bridge (Private) Limited and are maintained through our official [private] repositories, servers, and internal systems. |
| 26 | + |
| 27 | +We believe this unauthorized public repository was uploaded by, or in connection with, a person who was hired remotely to work on this project from 20 May 2026 to 13 June 2026. After that, he suddenly stopped responding. We have communication and project access references through WhatsApp, sign-in/application activity, and our back office control panel records. |
| 28 | + |
| 29 | +Person / contractor reference: |
| 30 | +Name: [private] |
| 31 | +Phone: [private] |
| 32 | +Email: [private] |
| 33 | +Resume attached: [private] |
| 34 | + |
| 35 | +We understand that the GitHub account used to publish the repository may not be his direct account and may be another account used for this purpose. We request GitHub to investigate the repository owner account and any related accounts involved in this unauthorized publication. |
| 36 | + |
| 37 | +Copyrighted work: |
| 38 | +Private proprietary source code owned by Tech AI Bridge (Private) Limited for our MSAR / Driver and Passenger application. |
| 39 | + |
| 40 | +Infringing material: |
| 41 | +The entire repository appears to be an unauthorized copy/publication of our private proprietary codebase. |
| 42 | + |
| 43 | +Requested action: |
| 44 | + |
| 45 | +Please urgently disable or remove public access to the entire repository: |
| 46 | +https://github.com/msar-beep/Msar |
| 47 | + |
| 48 | +Please remove or disable any forks, mirrors, or copies containing the same private proprietary code. |
| 49 | + |
| 50 | +Please review the repository and related account activity for violation of GitHub’s Terms of Service, copyright policies, and private information policies. |
| 51 | + |
| 52 | +Due to the serious nature of this unauthorized publication and the privacy/security risk caused to our company, we request GitHub to take appropriate enforcement action against the account involved, including suspension or blocking if GitHub confirms policy violations. |
| 53 | + |
| 54 | +Private information and security concern: |
| 55 | +The repository may expose sensitive/private information within the codebase, including internal architecture, backend routes, API references, database structure, configuration references, server implementation references, secret references, and other confidential implementation details. We request urgent review and removal under GitHub’s private information removal process as well. |
| 56 | + |
| 57 | +Evidence available: |
| 58 | + |
| 59 | +Screenshot of the public GitHub repository |
| 60 | + |
| 61 | +Official GitHub organization and original repository links |
| 62 | + |
| 63 | +Resume reference for the person who worked on the project |
| 64 | + |
| 65 | +WhatsApp communication records |
| 66 | + |
| 67 | +Sign-in/application access records |
| 68 | + |
| 69 | +Back office control panel records |
| 70 | + |
| 71 | +Internal project ownership records |
| 72 | + |
| 73 | +Original private project/source code records |
| 74 | + |
| 75 | +Server and API ownership/control records |
| 76 | + |
| 77 | +I can provide additional evidence if GitHub requires it. |
| 78 | + |
| 79 | +Good faith statement: |
| 80 | +I have a good faith belief that the use of the copyrighted materials described above is not authorized by the copyright owner, its agent, or the law. |
| 81 | + |
| 82 | +Accuracy statement: |
| 83 | +I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or authorized to act on behalf of the copyright owner, of an exclusive right that is allegedly infringed. |
| 84 | + |
| 85 | +Contact information: |
| 86 | +Name: [private] |
| 87 | +Company: Tech AI Bridge (Private) Limited |
| 88 | +Role: [private] |
| 89 | +Email: [private] |
| 90 | +Phone: [private] |
| 91 | +Address: [private] |
| 92 | + |
| 93 | +[private] |
| 94 | +[private]. Tech AI Bridge (Private) Limited |
0 commit comments