From 2fada17e13e1c3bdeb6132fff9dea488d5e19589 Mon Sep 17 00:00:00 2001 From: dmca-sync-bot Date: Mon, 8 Jun 2026 18:09:54 +0000 Subject: [PATCH] Process DMCA request --- 2026/06/2026-06-08-swalay.md | 87 ++++++++++++++++++++++++++++++++++++ 1 file changed, 87 insertions(+) create mode 100644 2026/06/2026-06-08-swalay.md diff --git a/2026/06/2026-06-08-swalay.md b/2026/06/2026-06-08-swalay.md new file mode 100644 index 0000000000..63d31c74cf --- /dev/null +++ b/2026/06/2026-06-08-swalay.md @@ -0,0 +1,87 @@ +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). + +--- + +**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.** + +Yes, I am the copyright holder. + +**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?** + +No + +**Does your claim involve content on GitHub or npm.js?** + +GitHub + +**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.** + +I am an authorized representative of SwaLay. We are the [private] [private] [private] and [private] owners of the proprietary, closed-source copyrighted technology and source code for our platform. I have full legal authority to act and file this takedown notice on behalf of the copyright owner, SwaLay. + +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** + +The copyrighted work consists of the proprietary, 100% closed-source software application code, infrastructure logic, and client-side architecture developed exclusively by and for SwaLay. This is proprietary commercial technology that has never been licensed, open-sourced, or authorized for public distribution, replication, or hosting by third parties. + +**If the original work referenced above is available online, please provide a URL.** + +The original copyrighted source code is proprietary and securely hosted within SwaLay's internal, private development infrastructure and private repo to protect our trade secrets and intellectual property. It is not publicly available online. +The proprietary code runs our commercial platform. Our official public brand presence can be verified at our website: https://swalay.com + +**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.** + +**Based on the above, I confirm that:** + +The entire repository is infringing + +**Identify the full repository URL that is infringing:** + +https://github.com/Mrpradhanji/client-swalay-plus + +**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our Complaints about Anti-Circumvention Technology if you are unsure.** + +Yes + +**What technological measures do you have in place and how do they effectively control access to your copyrighted material?** + +Our proprietary copyrighted source code is strictly protected using industry-standard access control measures. This includes housing the codebase within securely authenticated, private development environments and restricting access exclusively to authorized, verified internal personnel via multi-factor authentication (MFA) and secure SSH protocols. + +**How is the accused project designed to circumvent your technological protection measures?** + +The accused individuals bypassed our established access boundaries by improperly exfiltrating the protected codebase from our private corporate environment and making it publicly viewable on GitHub without authorization. By cloning and publishing this proprietary code online, they completely stripped away our access controls and trade secret protections. + +**If you are reporting an allegedly infringing fork, please note that each fork is a distinct repository and must be identified separately. Please read more about forks. 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:** + +**Is the work licensed under an open source license?** + +No + +**What would be the best solution for the alleged infringement?** + +Other Change + +**Describe the change.** + +The only acceptable solution is the immediate and complete removal of the entire infringing repository (https://github.com). Furthermore, because this is an intentional case of commercial data theft and fraudulent brand impersonation, we request that severe administrative sanctions or a permanent ban be levied against both user accounts (Mrpradhanji and [private]) for violating GitHub's acceptable use terms. + +**Do you have the alleged infringer’s contact information? If so, please provide it.** + +We do not have direct personal contact information. However, the individuals are operating through their public GitHub profiles :- +1.⁠ ⁠[private] +2.⁠ [private] +where they are publicly and falsely claiming affiliation with our brand, SwaLay. + +**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.** + +**I have taken fair use into consideration.** + +**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.** + +**I have read and understand GitHub's Guide to Submitting a DMCA Takedown Notice.** + +**So that we can get back to you, please provide either your telephone number or physical address.** + +[private] + +**Please type your full name for your signature.** + +[private]