|
| 1 | +While GitHub did not find sufficient information to determine a valid anti-circumvention claim, we determined that this takedown notice contains other valid copyright claim(s). |
| 2 | + |
| 3 | +--- |
| 4 | + |
| 5 | +**Are you the copyright holder or authorized to act on the copyright owner's behalf? If you are submitting this notice on behalf of a company, please be sure to use an email address on the company's domain. If you use a personal email address for a notice submitted on behalf of a company, we may not be able to process it.** |
| 6 | + |
| 7 | +Yes, I am the copyright holder. |
| 8 | + |
| 9 | +**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?** |
| 10 | + |
| 11 | +No |
| 12 | + |
| 13 | +**Does your claim involve content on GitHub or npm.js?** |
| 14 | + |
| 15 | +GitHub |
| 16 | + |
| 17 | +**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.** |
| 18 | + |
| 19 | +I am the [private] and copyright owner of this software project. The source code was written entirely by [private] and stored in [private] private [private] repository for personal use only. |
| 20 | + |
| 21 | +The project was never licensed, sold, shared, or released as open source, and no permission was granted to any third party to access, copy, modify, or distribute this code. |
| 22 | + |
| 23 | +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** |
| 24 | + |
| 25 | +The original copyrighted work consists primarily of a single Python source file that contains the complete core logic and functionality of the project. |
| 26 | + |
| 27 | +In addition to the main Python file, the repository also contains supporting files such as a Dockerfile and configuration-related files. These additional files include unique comments, structure, and implementation details written by [private] and serve as strong evidence of ownership. |
| 28 | + |
| 29 | +The entire project, including the main Python file and supporting files, was hosted only in [private] private [private] repository and was never made public. |
| 30 | +Also [private] source still private in [private] account |
| 31 | + |
| 32 | +**If the original work referenced above is available online, please provide a URL.** |
| 33 | + |
| 34 | +[private] |
| 35 | + |
| 36 | +**We ask that a DMCA takedown notice list every specific file in the repository that is infringing, unless the entire contents of the repository are infringing on your copyright. Please clearly state that the entire repository is infringing, OR provide the specific files within the repository you would like removed.** |
| 37 | + |
| 38 | +**Based on the above, I confirm that:** |
| 39 | + |
| 40 | +The entire repository is infringing |
| 41 | + |
| 42 | +**Identify the full repository URL that is infringing:** |
| 43 | + |
| 44 | +https://github.com/RishuBot/WishperBot |
| 45 | + |
| 46 | +**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology">Complaints about Anti-Circumvention Technology</a> if you are unsure.** |
| 47 | + |
| 48 | +Yes |
| 49 | + |
| 50 | +**What technological measures do you have in place and how do they effectively control access to your copyrighted material?** |
| 51 | + |
| 52 | +The copyrighted source code was protected by [private]’s access control mechanisms. The repository was set to private, accessible only to [private] as the owner. Access required authenticated GitHub credentials and was not publicly available. |
| 53 | + |
| 54 | +Additionally, access to the repository was restricted through [private] account permissions and private repository visibility settings. |
| 55 | + |
| 56 | +**How is the accused project designed to circumvent your technological protection measures?** |
| 57 | + |
| 58 | +The accused project circumvents [private] technological protection measures by publishing [private] private source code publicly on GitHub without authorization. |
| 59 | + |
| 60 | +This public distribution bypasses [private]’s private repository access controls and allows unrestricted access to code that was originally protected and intended for personal use only. |
| 61 | + |
| 62 | +**If you are reporting an allegedly infringing fork, please note that each fork is a distinct repository and <i>must be identified separately</i>. Please read more about <a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">forks.</a> As forks may often contain different material than in the parent repository, if you believe any of the repositories or files in the forks are infringing, please list each fork URL below:** |
| 63 | + |
| 64 | +**Is the work licensed under an open source license?** |
| 65 | + |
| 66 | +No |
| 67 | + |
| 68 | +**What would be the best solution for the alleged infringement?** |
| 69 | + |
| 70 | +Reported content must be removed |
| 71 | + |
| 72 | +**Do you have the alleged infringer’s contact information? If so, please provide it.** |
| 73 | + |
| 74 | +No |
| 75 | + |
| 76 | +**I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law.** |
| 77 | + |
| 78 | +**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.** |
| 79 | + |
| 80 | +**I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.** |
| 81 | + |
| 82 | +**I have read and understand GitHub's <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/">Guide to Submitting a DMCA Takedown Notice</a>.** |
| 83 | + |
| 84 | +**So that we can get back to you, please provide either your telephone number or physical address.** |
| 85 | + |
| 86 | +[private] Country - [private] Phone: [private] |
| 87 | + |
| 88 | +**Please type your full name for your signature.** |
| 89 | + |
| 90 | +[private] |
0 commit comments