Skip to content

Commit 12d1637

Browse files
author
dmca-sync-bot
committed
Process DMCA request
1 parent 3ea8177 commit 12d1637

File tree

1 file changed

+88
-0
lines changed

1 file changed

+88
-0
lines changed

2025/06/2025-06-25-pokemonbot.md

Lines changed: 88 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,88 @@
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 copyright holder of the Pokemon-HQ bot and all its source code/All the Repository in that Project of Pokemon-HQ. The repository in question contains code that [private] [private] developed and own also the sensitive data like Database URL, Bot Token and many other secrets got public. I did not authorize this code to be published or distributed publicly on GitHub by anyone else.
20+
21+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
22+
23+
The original copyrighted work is the [private] source code and intellectual property of [private] Pokemon-HQ Discord bot, developed and maintained [private] by [private] ([private]). This includes, but is not limited to, all source files, scripts, configurations, and documentation related to the Pokémon-HQ bot. This code was never intended to be made public and was published to GitHub without [private] permission by a team member.
24+
25+
**If the original work referenced above is available online, please provide a URL.**
26+
27+
[private]
28+
[private]
29+
This is [private] [private] and Project
30+
31+
https://pokemonbot.com/
32+
Website
33+
34+
**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.**
35+
36+
**Based on the above, I confirm that:**
37+
38+
The entire repository is infringing
39+
40+
**Identify the full repository URL that is infringing:**
41+
42+
https://github.com/Pokemon-HQ/Bot
43+
https://github.com/Pokemon-HQ/Image-Server
44+
https://github.com/Pokemon-HQ/image-server-assets
45+
46+
**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.**
47+
48+
Yes
49+
50+
**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
51+
52+
The source code was stored in a [private] accessible only to authorized team members of DISBOT TECHNOLOGIES LLP. Access required login credentials and was restricted to specific users within the company. The code was never intended to be made public or distributed outside of this controlled environment. No one was authorized to publish or share the code publicly on GitHub or any other platform.
53+
54+
**How is the accused project designed to circumvent your technological protection measures?**
55+
56+
An authorized team member who had access to the [private] and its contents intentionally made the source code public on GitHub without the consent or authorization of DISBOT TECHNOLOGIES LLP. By publishing the code to a public repository, they bypassed the access restrictions that were in place, making the proprietary content available to anyone without authorization.
57+
58+
**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:**
59+
60+
**Is the work licensed under an open source license?**
61+
62+
No
63+
64+
**What would be the best solution for the alleged infringement?**
65+
66+
Reported content must be removed
67+
68+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
69+
70+
[private]
71+
72+
[private] Username:- [private] ([private])
73+
74+
**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.**
75+
76+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
77+
78+
**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.**
79+
80+
**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>.**
81+
82+
**So that we can get back to you, please provide either your telephone number or physical address.**
83+
84+
[private]
85+
86+
**Please type your full name for your signature.**
87+
88+
[private]

0 commit comments

Comments
 (0)