diff --git a/2022/07/2022-07-05-restorecord.md b/2022/07/2022-07-05-restorecord.md
new file mode 100644
index 000000000..703012d15
--- /dev/null
+++ b/2022/07/2022-07-05-restorecord.md
@@ -0,0 +1,69 @@
+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?**
+
+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'm the [private] of restorecord, in January 2022 the [private] has sold [private] the Source Code, Domain and legal rights to restorecord.
+
+**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.**
+
+Just 5 months after the [private] sold it to [private], he released it online for everyone to download on this Github page: https://github.com/wnelson03/RestoreCord-Source-Code. As you can see, he mentions that he didn't assign copyrights to [private], which is wrong. You can see here: [invalid] the original source has been private on [private] since February just a month after he sold it to [private], I'm the [private] of [private] & the [invalid] domain also verified via the github organization. You can also see in the leaked source (https://github.com/wnelson03/RestoreCord-Source-Code) that he has made a very clear tutorial how to set it up, so anyone with just a bit of knowledge could set it up and damage our company.
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+https://github.com/wnelson03/RestoreCord-Source-Code
+
+**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.**
+
+No
+
+**Have you searched for any forks 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.**
+
+No, forks as of the report.
+
+**Is the work licensed under an open source license?**
+
+No
+
+**What would be the best solution for the alleged infringement?**
+
+Repository can be made private
+
+**Do you have the alleged infringer’s contact information? If so, please provide it.**
+
+Name: [private]
+Address: [private]
+Several Emails: [private], [private], [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 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 legal name below to sign this request.**
+
+[private]