|
| 1 | +**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.** |
| 2 | + |
| 3 | +Yes, I am the copyright holder. |
| 4 | + |
| 5 | +**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?** |
| 6 | + |
| 7 | +No |
| 8 | + |
| 9 | +**Does your claim involve content on GitHub or npm.js?** |
| 10 | + |
| 11 | +GitHub |
| 12 | + |
| 13 | +**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.** |
| 14 | + |
| 15 | +I am authorized to act on behalf of AMB Solutions Co., Ltd., the copyright owner. Additionally, I serve as the legal representative of AMB Solutions Co., Ltd. |
| 16 | + |
| 17 | +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** |
| 18 | + |
| 19 | +The copyrighted work is proprietary source code developed by AMB Solutions Co., Ltd. It is part of the software system published on https://reuse-tenshoku.com/. The work includes original algorithms and implementation details that are unique to our service. |
| 20 | + |
| 21 | +**If the original work referenced above is available online, please provide a URL.** |
| 22 | + |
| 23 | +https://reuse-tenshoku.com/ |
| 24 | + |
| 25 | +**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.** |
| 26 | + |
| 27 | +**Based on the above, I confirm that:** |
| 28 | + |
| 29 | +The entire repository is infringing |
| 30 | + |
| 31 | +**Identify the full repository URL that is infringing:** |
| 32 | + |
| 33 | +https://github.com/rey0601/AMB-Backend |
| 34 | + |
| 35 | +**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.** |
| 36 | + |
| 37 | +No |
| 38 | + |
| 39 | +**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:** |
| 40 | + |
| 41 | +**Is the work licensed under an open source license?** |
| 42 | + |
| 43 | +No |
| 44 | + |
| 45 | +**What would be the best solution for the alleged infringement?** |
| 46 | + |
| 47 | +Other Change |
| 48 | + |
| 49 | +**Describe the change.** |
| 50 | + |
| 51 | +The content contained in the repository in question is copyrighted by our company and has been made publicly available without authorization. |
| 52 | +This repository contains backend resources, and its public exposure raises serious security concerns and poses significant risks to our systems and services. |
| 53 | +For these reasons, we strongly request the complete removal of the repository. |
| 54 | + |
| 55 | +**Do you have the alleged infringer’s contact information? If so, please provide it.** |
| 56 | + |
| 57 | +I do not have any contact information for the alleged infringer other than the GitHub username: rey0601. |
| 58 | + |
| 59 | +**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.** |
| 60 | + |
| 61 | +**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.** |
| 62 | + |
| 63 | +**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.** |
| 64 | + |
| 65 | +**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>.** |
| 66 | + |
| 67 | +**So that we can get back to you, please provide either your telephone number or physical address.** |
| 68 | + |
| 69 | +[private] |
| 70 | + |
| 71 | +**Please type your full name for your signature.** |
| 72 | + |
| 73 | +[private] |
0 commit comments