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).

---

**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 am the [private] of Acuity Technology Solutions Inc and duly authorized to file this complaint. I am sending this notice under a good faith belief that use of the materials, described above as allegedly infringing, is not authorized. The copyrighted material in question includes but it not limited to our proprietary software code, extensions and schema related documentation, which are being infringed upon by unauthorized distribution and use. I certify, under the penalty of perjury, that the information in this notice is correct.

**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 original content is in active development in [private]: [private] and [private] respectively. The copyrighted work is a web application hosted on: https://we-schedule.ca  
The offending repo: https://github.com/muniba-objectual/weschedulepwa/ is an exact version of the codebase from September 2023 which indicates that a previous developer cloned the repo and uploaded it to [private] Github account.

**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**

https://github.com/muniba-objectual/weschedulepwa/

**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.**

Yes

**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**

All [private] are set to private with forking disabled across the origination. Developer access is managed internally and is solely worked on from company-managed assets.

We do not claim that anti-circumvention technology was used to access the copyrighted content. The copyright content was and is protected by reasonable technology measures from unlawful disclosure or access.

**How is the accused project designed to circumvent your technological protection measures?**

After initial investigation, we do not believe the actions of the developer were nefarious in nature; however it is assumed that the developer mistakenly uploaded it onto his public account. No additional forks, branches, issues, or PRs have been made to offending repository for over a year.

**<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, there does not seem to be any additional forks.

**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.**

No, we do not have contact information for the repository creator.

**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.**

Mobile: [private]  
Office: [private]  
Physical Office Address: [private]  

**Please type your full legal name below to sign this request.**

[private]  
