diff --git a/.github/script/validate-filepaths/index.js b/.github/script/validate-filepaths/index.js
index c2c60cf9e..9e615fa3a 100644
--- a/.github/script/validate-filepaths/index.js
+++ b/.github/script/validate-filepaths/index.js
@@ -25,7 +25,7 @@ let commentCopyForFilesChangedInThisPr =
   prChangedFilesWithInvalidDates.length ||
   prChangedFilesNotInCorrectFolder.length
     ? ` I've scanned the changed files and found some issues to double check:`
-    : ` All DCMA notices changed in this PR look good to me.`;
+    : ` All DMCA notices changed in this PR appear to have valid YYYY-MM-DD dates and seem to be in the correct folder.`;
 
 commentCopyForFilesChangedInThisPr += prChangedFilesWithInvalidDates.length
   ? `\n\n**Notices that don't contain a date that conforms to the YYYY-MM-DD format:**\n\n${prChangedFilesWithInvalidDates
@@ -72,7 +72,7 @@ const [filesInCorrectFolder, filesNotInCorrectFolder] = partition(
 let commentCopyForAllDmcaNoticesInRepo =
   filesWithInvalidDates.length || filesNotInCorrectFolder.length
     ? `\n# Other Files in Repo\nI've also scanned the rest of the repo and found some files to double check:`
-    : `\n# Other Files in Repo\nThe other DCMA notices in the repo look good to me.`;
+    : `\n# Other Files in Repo\nThe other DMCA notices in the repo appear to have valid YYYY-MM-DD dates and seem to be in the correct folder.`;
 
 const invalidDatesList = filesWithInvalidDates.length
   ? `\n\n**Notices that don't contain a date that conforms to the YYYY-MM-DD format:**\n\n${filesWithInvalidDates
diff --git a/2022/02/2022-02-14-byteboard.md b/2022/02/2022-02-14-byteboard.md
new file mode 100644
index 000000000..018107e9d
--- /dev/null
+++ b/2022/02/2022-02-14-byteboard.md
@@ -0,0 +1,62 @@
+**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
+
+Yes, I am authorized to act on the copyright owner's behalf.
+
+**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 work in [private] for Byteboard Inc, the creator of the content in question. I have read and understand GitHub's Guide to Filing a DMCA Notice.
+
+**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.**
+
+The two repositories in question are proprietary Byteboard Assessments used to evaluated technical skills on behalf of hiring companies. The individuals who posted these materials to GitHub were both candidates who we invited to the interview and posted the materials online in contradiction of their agreement to "not share your code, text and other data or information that you create while using the Service with any other party." Beyond the material the candidates created, the repositories include substantial amounts of the existing codebase that candidates are provided to work in that is also proprietary content. While we cannot link directly to the assessments because they are not publicly available, you can see our homepage (https://byteboard.dev/) and note that both repositories explicitly identify the material as a Byteboard interview.
+
+**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
+
+Entire repository: https://github.com/rtwhite10/byteboard  
+Entire repository: https://github.com/BakariMorris/ByteBoardAssignment
+
+**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
+
+**<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.**
+
+Yes
+
+**Is the work licensed under an open source license?**
+
+No
+
+**What would be the best solution for the alleged infringement?**
+
+Reported content must be removed
+
+**Do you have the alleged infringer’s contact information? If so, please provide it.**
+
+We have attempted to reach out to the posters at the following email addresses that they submitted as Byteboard candidates:   
+[private]: [private]  
+[private]: [private] ([private] also lists [private] on the GH profile)
+
+**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.**
+
+My phone number is [private]. If possible, please contact me for this matter at my Byteboard email address, [private].
+
+**Please type your full legal name below to sign this request.**
+
+[private]