Docking@Home Rules and Policies
Run Docking@Home only on authorized computers
Run Docking@Home only on computers that you own, or for which you have obtained the owner's permission. Some companies and schools have policies that prohibit using their computers for projects such as Docking@Home.
How Docking@Home will use your computer
When you run Docking@Home on your computer, it will use part of the computer's CPU power, disk space, and network bandwidth. You can control how much of your resources are used by Docking@Home, and when it uses them.
The work done by your computer contributes to the goals of Docking@Home, as described on its web site. The application programs may change from time to time.
Privacy policy
Your account on Docking@Home is identified by a name that you choose. This name may be shown on the Docking@Home web site, along with a summary of the work your computer has done for Docking@Home. If you want to be anonymous, choose a name that doesn't reveal your identity.
If you participate in Docking@Home, information about your computer (such as its processor type, amount of memory, etc.) will be recorded by Docking@Home and used to decide what type of work to assign to your computer. This information will also be shown on Docking@Home's web site. Nothing that reveals your computer's location (e.g. its domain name or network address) will be shown.
To participate in Docking@Home, you must give an address where you receive email. This address will not be shown on the Docking@Home web site or shared with organizations. Docking@Home may send you periodic newsletters; however, you can opt out at any time.
Is it safe to run Docking@Home?
Any time you download a program through the Internet you are taking a chance: the program might have dangerous errors, or the download server might have been hacked. Docking@Home has made efforts to minimize these risks. We have tested our applications carefully. Our servers are behind a firewall and are configured for high security. To ensure the integrity of program downloads, all executable files are digitally signed on a secure computer not connected to the Internet.
The applications run by Docking@Home may cause some computers to overheat. If this happens, stop running Docking@Home or use a utility program that limits CPU usage.
Docking@Home was developed by University of Delaware. BOINC was developed at the University of California.
Liability
Docking@Home and University of Delaware assume no liability for damage to your computer, loss of data, or any other event or condition that may occur as a result of participating in Docking@Home.
Other BOINC projects
Other projects use the same platform, BOINC, as Docking@Home. You may want to consider participating in one or more of these projects. By doing so, your computer will do useful work even when Docking@Home has no work available for it.
These other projects are not associated with Docking@Home, and we cannot vouch for their security practices or the nature of their research. Join them at your own risk.
If you are completely new, check out the Getting Started Guide
Let's go ahead and Create an Account
Go back to Join Docking@Home