Skip to content

Commit 3d72f87

Browse files
author
dmca-sync-bot
committed
Process DMCA request
1 parent 926d211 commit 3d72f87

File tree

1 file changed

+86
-0
lines changed

1 file changed

+86
-0
lines changed
Lines changed: 86 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,86 @@
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 [private] of proprietary software known as “FrostbiteV2”, "Phantom" and "Frostbot" and compiled source included in the software known as "FrostbiteWebsite". All rights, title, and interest in the software, including its source code, are exclusively owned by [private]. The software is not open source and is distributed under a restricted license that prohibits redistribution or public disclosure.
20+
21+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
22+
23+
The copyrighted work consists of private backend source code for “Frostbite”, including but not limited to server logic, authentication systems, and internal implementation files. This code was developed privately and is not authorized for public distribution or publication.
24+
25+
**If the original work referenced above is available online, please provide a URL.**
26+
27+
[private]
28+
[private]
29+
[private]
30+
Frostbot was never uploaded to github since it was in early developement and the above repositories contain the original, proprietary source code for [private] software products, and all are exclusively owned by [private].
31+
32+
**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.**
33+
34+
**Based on the above, I confirm that:**
35+
36+
The entire repository is infringing
37+
38+
**Identify the full repository URL that is infringing:**
39+
40+
https://github.com/kovryn/Razers-new-backend-stuff
41+
42+
**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.**
43+
44+
Yes
45+
46+
**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
47+
48+
The backend is distributed only to licensed users via restricted access channels. Unauthorized access requires circumventing authentication and license checks implemented in the code, which are technological protection measures.
49+
50+
**How is the accused project designed to circumvent your technological protection measures?**
51+
52+
The infringing project obtained unauthorized access to [private] backend source code, bypassing license restrictions and private distribution controls. The code was copied and published publicly, circumventing authentication and access mechanisms intended to restrict use to licensed users only.
53+
54+
**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:**
55+
56+
**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.**
57+
58+
**Is the work licensed under an open source license?**
59+
60+
No
61+
62+
**What would be the best solution for the alleged infringement?**
63+
64+
Reported content must be removed
65+
66+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
67+
68+
GitHub username: kovryn
69+
[private] : [private]
70+
[private] : [private]
71+
72+
**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.**
73+
74+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
75+
76+
**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.**
77+
78+
**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>.**
79+
80+
**So that we can get back to you, please provide either your telephone number or physical address.**
81+
82+
[private]
83+
84+
**Please type your full name for your signature.**
85+
86+
[private]

0 commit comments

Comments
 (0)