|
| 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 authorized to act on the copyright owner's behalf. |
| 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 a [private] at Software Group, which is the legal owner of the copyrighted source code in question. |
| 20 | + |
| 21 | +The content being reported consists of proprietary source code developed internally by Software Group as part of the BNCTL Mobile Banking. This code is not open source and is not authorised for public distribution. |
| 22 | + |
| 23 | +I have been explicitly authorised by Software Group to act on its behalf in submitting this DMCA takedown request regarding unauthorised publication of this code on GitHub. |
| 24 | + |
| 25 | +This authorisation includes the right to identify infringement and request removal of the infringing content. |
| 26 | + |
| 27 | +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** |
| 28 | + |
| 29 | +The original copyrighted work consists of proprietary software source code developed and owned by Software Group as part of the BNCTL Mobile Banking Project. |
| 30 | + |
| 31 | +This includes front-end application, business logic, APIs and related components implemented using technologies such as Swift, Objective C & Kotlin. The system includes sensitive financial transaction processing logic, account management workflows, and integration components used in banking/payment systems. The codebase was developed internally by our engineering team for commercial use and is maintained in private repositories with restricted access. |
| 32 | + |
| 33 | +The software is not open source and has never been authorised for public distribution. It contains confidential implementation details, system architecture, and business logic specific to a particular project. |
| 34 | + |
| 35 | +The infringing material appears to be a direct copy or substantial portion of this proprietary codebase, published without authorisation. |
| 36 | + |
| 37 | +**If the original work referenced above is available online, please provide a URL.** |
| 38 | + |
| 39 | +The original work is hosted in private repositories owned by Software Group and is not publicly accessible. |
| 40 | + |
| 41 | +If required, we can provide additional verification or evidence of ownership directly to GitHub under appropriate confidentiality. |
| 42 | + |
| 43 | +**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.** |
| 44 | + |
| 45 | +**Based on the above, I confirm that:** |
| 46 | + |
| 47 | +The entire repository is infringing |
| 48 | + |
| 49 | +**Identify the full repository URL that is infringing:** |
| 50 | + |
| 51 | +https://github.com/harshvishu/BNCTL-Mobile-Banking-App-iOS-Android |
| 52 | + |
| 53 | +**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.** |
| 54 | + |
| 55 | +Yes |
| 56 | + |
| 57 | +**What technological measures do you have in place and how do they effectively control access to your copyrighted material?** |
| 58 | + |
| 59 | +The copyrighted material is stored in private, access-controlled repositories owned by Software Group. |
| 60 | + |
| 61 | +Access is restricted through authenticated user accounts and role-based access controls, ensuring that only authorised personnel can view or modify the source code. Additional controls such as secure credential management and internal access policies are enforced to prevent unauthorised access or distribution. |
| 62 | + |
| 63 | +These measures ensure that the source code is not publicly accessible and is only available to individuals with explicit permission. The presence of this code on GitHub indicates unauthorised use or disclosure outside of these controlled environments. |
| 64 | + |
| 65 | +**How is the accused project designed to circumvent your technological protection measures?** |
| 66 | + |
| 67 | +The accused repository is not designed to circumvent technological protection measures. |
| 68 | + |
| 69 | +However, it contains proprietary source code that is normally protected within private, access-controlled repositories. The presence of this code in a public repository indicates that it was obtained and disclosed without authorisation, likely through misuse or breach of authorised access, thereby bypassing the intended access restrictions. |
| 70 | + |
| 71 | +**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:** |
| 72 | + |
| 73 | +**Based on the representative number of forks I have reviewed, I believe that all or most of the forks are infringing to the same extent as the parent repository.** |
| 74 | + |
| 75 | +**Is the work licensed under an open source license?** |
| 76 | + |
| 77 | +No |
| 78 | + |
| 79 | +**What would be the best solution for the alleged infringement?** |
| 80 | + |
| 81 | +Reported content must be removed |
| 82 | + |
| 83 | +**Do you have the alleged infringer’s contact information? If so, please provide it.** |
| 84 | + |
| 85 | +I have the person's [private] profile |
| 86 | + |
| 87 | +[private] |
| 88 | + |
| 89 | +**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.** |
| 90 | + |
| 91 | +**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.** |
| 92 | + |
| 93 | +**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.** |
| 94 | + |
| 95 | +**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>.** |
| 96 | + |
| 97 | +**So that we can get back to you, please provide either your telephone number or physical address.** |
| 98 | + |
| 99 | +[private] |
| 100 | + |
| 101 | +**Please type your full name for your signature.** |
| 102 | + |
| 103 | +[private] |
0 commit comments