Skip to content

Commit c32762d

Browse files
author
dmca-sync-bot
committed
Process DMCA request
1 parent 24371fb commit c32762d

1 file changed

Lines changed: 69 additions & 0 deletions

File tree

2022/06/2022-06-17-cpunto.md

Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
2+
3+
Yes, I am the copyright holder.
4+
5+
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
6+
7+
Yes
8+
9+
**Please provide the Zendesk ticket number of your previously submitted notice. Zendesk ticket numbers are 7 digit ID numbers located in the subject line or body of your confirmation email.**
10+
11+
1670058
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 [private] of the following repository:
20+
[private]
21+
22+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed. If possible, include a URL to where it is posted online.**
23+
24+
The repository published by this developer https://github.com/andrejPajtas/cpunto
25+
bears our companies name: Cpunto
26+
http://cpunto.com
27+
we did not allow the user andrejPajtas to use our name
28+
29+
our private repository:
30+
[private] has been stolen and pulicly published by this user andrejPajtas [private] ago.
31+
structure of of files is in private repository with first commit in [private]. - [private] , email with pictures of the structure has been set to you.
32+
33+
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
34+
35+
https://github.com/andrejPajtas/cpunto
36+
37+
**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.**
38+
39+
No
40+
41+
**<a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">Have you searched for any forks</a> of the allegedly infringing files or repositories? Each fork is a distinct repository and must be identified separately if you believe it is infringing and wish to have it taken down.**
42+
43+
yes, no forks found
44+
45+
**Is the work licensed under an open source license?**
46+
47+
No
48+
49+
**What would be the best solution for the alleged infringement?**
50+
51+
Reported content must be removed
52+
53+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
54+
55+
**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.**
56+
57+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
58+
59+
**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.**
60+
61+
**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>.**
62+
63+
**So that we can get back to you, please provide either your telephone number or physical address.**
64+
65+
[private]
66+
67+
**Please type your full legal name below to sign this request.**
68+
69+
[private]

0 commit comments

Comments
 (0)