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

We have software([private]) that was developed in-house and one of our developers uploaded it to GitHub and made it public (https://github.com/x-zho14/opensource-hft). We notified this former employee who promptly deleted the content, but he claimed his account was hacked. We made contact for deletion, but he could not respond to our messages.It contains a lot of private information. For example, the 50th line of influxdb123.py file under the main branch personal private database configuration information ([private]). For example, the 69th line of the influxdb123_2_sell.py file contains the url of the database, the database [private]. For another example, line 65 contains the key information of another server's [private].Also, in this file, 81 contain query of database which contains the [private] on my server, completely exposing private information. Besides, the 321 line of file args.py also contains the private information of how much money we tested and lots of business secret including model parameters(line 45, dimension of [private]). In line 645 of backtest_core.py, it leaks the secret of how we conduct backtest and the secret buy_price and sell_price expression. Others can break my server and database information through the information in the this file, which involves company privacy and constitutes a security risk.

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

This repo was exposed before but deleted after communication. However, the person claims his account is hacked and this repo shows again today.
https://github.com/x-zho14/opensource-hft

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

The whole repository should be taken down.  
https://github.com/x-zho14/opensource-hft

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

Temporarily no.

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

All we have is just the github account.

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

[private], [private] Inifinity3Labs  
[private]

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

[private]
