How Sailfork handles copyright notices and counter-notices, and when an account that keeps infringing is ended.
Last updated
Copyright notices
To tell us that content on Sailfork infringes your copyright, send a notice through the abuse page. A valid notice leads us to disable the repository, issue or pull request, and we tell its owner what the notice said, with the sender’s name and email.
Knowingly sending a false notice can make you liable for damages.
Counter-notices
If your content was disabled after a copyright notice and you believe that was a mistake or a misidentification of the material, send a counter-notice. The email we send when we disable content links to the form. You must be signed in as the author of the issue or pull request, the creator of the repository, or an owner of its organization.
A counter-notice has your signature, identifies the material and where it was before we disabled it, states under penalty of perjury that you believe in good faith it was removed by mistake or misidentification, and gives your name, address and phone number. It also consents to the jurisdiction of the federal district court for your address, or, outside the United States, any district where Sailfork may be found, and accepts service of process from the sender of the notice.
We send the counter-notice, with your name, address, phone number and email, to the person who sent the notice.
We restore the material 10 business days after we receive the counter-notice, unless the sender tells us before then that they filed an action seeking a court order to restrain you from infringing activity relating to the material. If they do, the material stays disabled while that action is pending. Knowingly sending a false counter-notice can make you liable for damages.
Repeat infringers
Each copyright notice that leads us to disable your content is a strike on your account. The strike goes to the author of an issue or pull request, or to the person who created a repository.
A strike is removed when the material is restored: after a counter-notice that the sender did not answer with a lawsuit, or when we find the notice was mistaken. While a counter-notice is inside its waiting period, its strike does not count toward ending the account.
When an account has 3 strikes, we terminate it: it is signed out, cannot sign in, and its personal repositories are disabled.
If you think a strike or a termination is wrong, write to us through the contact page.
Questions about this page go through the contact page. Fenil, who runs Sailfork, reads every message.