|
| 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 rights holder of the original design, structure, content, and source files of the “[private]” web project. The project materials were shared with the user “KIS-IT-PRODUCTION” only within our team/company for development purposes, and were never published on GitHub or any other public platform. The user was not authorized to publicly distribute, share, or post any of these materials. Therefore, I am the rightful copyright owner of all materials unlawfully posted on GitHub. |
| 20 | + |
| 21 | +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** |
| 22 | + |
| 23 | +The copyrighted materials include the design, content, structure, and source files of the web project “Ibedrola”. These materials were shared internally within our company/team for development purposes only, under strict confidentiality. The user “KIS-IT-PRODUCTION” publicly posted these materials on GitHub without permission, violating confidentiality and our copyright. |
| 24 | + |
| 25 | +**If the original work referenced above is available online, please provide a URL.** |
| 26 | + |
| 27 | +The original work is not publicly available online. |
| 28 | + |
| 29 | +**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.** |
| 30 | + |
| 31 | +**Based on the above, I confirm that:** |
| 32 | + |
| 33 | +The entire repository is infringing |
| 34 | + |
| 35 | +**Identify the full repository URL that is infringing:** |
| 36 | + |
| 37 | +https://github.com/KIS-IT-PRODUCTION/Ibedrola |
| 38 | + |
| 39 | +**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.** |
| 40 | + |
| 41 | +Yes |
| 42 | + |
| 43 | +**What technological measures do you have in place and how do they effectively control access to your copyrighted material?** |
| 44 | + |
| 45 | +The user “KIS-IT-PRODUCTION” circumvented the access restrictions by publicly posting the project on GitHub without authorization, despite the materials being strictly internal and confidential. |
| 46 | + |
| 47 | +**How is the accused project designed to circumvent your technological protection measures?** |
| 48 | + |
| 49 | +The accused project bypassed the technological protection by being publicly published on GitHub, even though the original project “Ibedrola” was stored in a private repository with access restricted only to authorized personnel. |
| 50 | +No one outside the project team was allowed to view or distribute the materials, but the user posted the entire repository publicly, circumventing these access controls. |
| 51 | + |
| 52 | +**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:** |
| 53 | + |
| 54 | +https://github.com/KIS-IT-PRODUCTION/Ibedrola |
| 55 | + |
| 56 | +**Is the work licensed under an open source license?** |
| 57 | + |
| 58 | +No |
| 59 | + |
| 60 | +**What would be the best solution for the alleged infringement?** |
| 61 | + |
| 62 | +Reported content must be removed |
| 63 | + |
| 64 | +**Do you have the alleged infringer’s contact information? If so, please provide it.** |
| 65 | + |
| 66 | +Name: KIS-IT-PRODUCTION |
| 67 | +GitHub profile: https://github.com/KIS-IT-PRODUCTION |
| 68 | +Email: unknown (maybe: [private]} |
| 69 | +Phone: unknown |
| 70 | + |
| 71 | +**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.** |
| 72 | + |
| 73 | +**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.** |
| 74 | + |
| 75 | +**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.** |
| 76 | + |
| 77 | +**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>.** |
| 78 | + |
| 79 | +**So that we can get back to you, please provide either your telephone number or physical address.** |
| 80 | + |
| 81 | +[private] |
| 82 | + |
| 83 | +**Please type your full name for your signature.** |
| 84 | + |
| 85 | +[private] |
0 commit comments