Process DMCA request

Author: dmca-sync-bot

2026/04/2026-04-23-fitzone.md

@@ -0,0 +1,154 @@
+Before disabling any content in relation to this takedown notice, GitHub  
+- contacted the owners of some or all of the affected repositories to give them an opportunity to [make changes](https://docs.github.com/en/github/site-policy/dmca-takedown-policy#a-how-does-this-actually-work).  
+- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice).  
+  
+To learn about when and why GitHub may process some notices this way, please visit our [README](https://github.com/github/dmca/blob/master/README.md#anatomy-of-a-takedown-notice).  
+  
+---  
+  
+**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 the [private] and copyright owner of the FitZone E-Commerce  
+Store project. [private] personally designed, coded, and published this entire project  
+from scratch in early 2025 under [private] GitHub account "hassanjaved17". The project  
+is published under an Apache 2.0 License which [private] applied [private] as the copyright  
+owner. [private] am acting on [private] as the [private] and rights holder  
+of this work.  
+  
+**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**  
+  
+The original copyrighted work is "FitZone E-Commerce Store" — a fully custom-built  
+multi-page frontend e-commerce website that [private], [private], designed and developed  
+entirely from scratch in early 2025.  
+  
+The work includes:  
+  
+1. Custom HTML structure across 6 unique pages: Home, Shop, Features, About,  
+Accessories, and Contact  
+2. Original CSS styling including a complete custom design system, color scheme,  
+typography, animations, and responsive layout  
+3. Custom JavaScript functionality including a shopping cart system, product  
+filtering, countdown timer, and interactive UI components  
+4. Original copywriting and text content including all headings, taglines,  
+product descriptions, and marketing copy  
+5. Original image assets with custom filenames used throughout the site  
+6. Custom footer, newsletter section, WhatsApp integration, and navigation system  
+  
+The project is publicly available at:  
+Original GitHub Repository: https://github.com/hassanjaved17/FitZone-E-com-store  
+Original Live Site: https://hassanjaved17.github.io/FitZone-E-com-store/  
+  
+The project is licensed under Apache 2.0, applied by [private] as the [private] copyright  
+owner, which requires any use or redistribution to include proper attribution  
+and preserve the original copyright notice.  
+  
+**If the original work referenced above is available online, please provide a URL.**  
+  
+https://hassanjaved17.github.io/FitZone-E-com-store/  
+  
+https://github.com/hassanjaved17/FitZone-E-com-store  
+  
+**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/usama-ahmed-rajput/Fit-zone  
+  
+**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.**  
+  
+No  
+  
+**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:**  
+  
+**Is the work licensed under an open source license?**  
+  
+Yes  
+  
+**Which license?**  
+  
+apache-license-2.0  
+  
+**How do you believe the license is being violated?**  
+  
+The Apache 2.0 License under which [private] project is published has clear conditions  
+that the infringing user has completely violated:  
+  
+1. ATTRIBUTION REMOVED — The license requires that the original author's name  
+and copyright notice be preserved in all copies. The infringing user deliberately  
+removed [private] name ([private]) and all copyright markers from the project.  
+  
+2. NO LICENSE INCLUDED — The license requires that a copy of the Apache 2.0  
+License be included in any redistribution. The infringing repository contains  
+no license file whatsoever.  
+  
+3. NO CHANGES DECLARED — The license requires that any modifications to the  
+original work be clearly stated. The infringing user made no such declaration  
+and instead presented the work as entirely their own original creation.  
+  
+4. FALSE OWNERSHIP CLAIM — The infringing user is actively presenting [private] work  
+as their own original project on their public GitHub profile, which directly  
+contradicts the terms of the Apache 2.0 License.  
+  
+In summary, the infringing user did not use [private] work under the terms of the  
+Apache 2.0 License — they simply stole it, removed all evidence of [private] ownership,  
+and republished it as their own, which is a clear and direct violation of both  
+the license terms and [private] copyright.  
+  
+**What changes can be made to bring the project into compliance with the license? For example, adding attribution, adding a license, making the repository private.**  
+  
+While technically the infringing user could attempt to bring the repository  
+into compliance by taking the following steps:  
+  
+1. Adding full attribution to the original author — [private]  
+(GitHub: hassanjaved17) — in the README and all relevant files  
+2. Adding the complete Apache 2.0 License file to the repository  
+3. Clearly stating all changes made from the original work  
+4. Removing any false claim of original ownership  
+  
+However, [private] do NOT consent to the infringing user continuing to host and  
+present [private] work publicly in any form. The copying was done deliberately and  
+in bad faith — [private] name and copyright information were intentionally removed.  
+This was not an innocent mistake.  
+  
+Therefore, [private] preferred resolution is the complete takedown of the infringing  
+repository (https://github.com/usama-ahmed-rajput/Fit-zone) and its associated  
+GitHub Pages site (https://usama-ahmed-rajput.github.io/Fit-zone/) entirely,  
+rather than any compliance modifications.  
+  
+**Do you have the alleged infringer’s contact information? If so, please provide it.**  
+  
+GitHub Profile: https://github.com/usama-ahmed-rajput  
+GitHub Pages Site: [private]  
+[private] Number (found on infringing site): [private]  
+  
+**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 <a href="https://www.lumendatabase.org/topics/22">fair use</a> 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 <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/">Guide to Submitting a DMCA Takedown Notice</a>.**  
+  
+**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]