Box.net

Developer Terms of Use

These Terms of Use apply to anyone creating a software application that integrates with Box.net. Your use of the Box.net Web service APIs is conditioned upon your agreement to these terms. By using the Box.net Web service APIs, you are consenting to all of these terms and conditions.

We've published these terms to minimize the potential for abuse of Box.net, to ensure that everyone has fair access to box.net, and to encourage users and developers to use Box.net in a way that is operationally sustainable. If you have any questions about these terms as they apply to you or your application (including rate limit increase requests), please contact us at info@box.net.

Box.net provides a Web service API that enables third-party developers to create software applications that integrate with the Box.net service. Applications built upon the Box.net Web service APIs must be:

• Non-commercial. You cannot charge money for access to an application or Web site that uses the Box.net Web service APIs. (If you're interested in creating a commercial application that uses Box.net, please contact us for licensing terms.)
• Generally accessible. You may not create an intranet application that uses Box.net. It's OK to create an application for your own use, but if you share the application with others, it must be generally available for any Box.net user to use. (If you're interested in creating a private/intranet application that uses Box.net, please contact us for licensing terms.)
• In conformity with our consumer terms of service.
• General-purpose. With the Box Enabled platform, Box.net aims to make user-centric storage available to developers. This is different from other storage API platforms which provide application-specific storage. For example, while it's okay to develop a widget that will preview someone's music or photos, it's NOT okay to use Box.net as the back-end data store of your Web site. By general-purpose, we mean situations in which the access or storage of one's data from your application will be generally useful outside the context of your application. We realize that the distinction between "general-purpose" and non-general-purpose might be a little unclear since there are a lot of different possibilities, so if you're at all unclear, please email info@box.net with any questions you might have before you start coding.
• For individual users. Your application should be designed for use so that each person accessing it has their own, unique Box.net account.
• Consistent with our rate limits for Web service APIs. We currently have a per-application limit of 50,000 requests, applied in a rolling 24-hour window.

Any application that in our reasonable judgment does not comply with any of the above requirements may be removed without notice, or we may contact you to require changes in the application as a condition to further use. As noted above, if at any time you have any questions about such compliance, you should contact us at info@box.net.

You must report any security deficiencies or breaches related to your application as soon as possible upon discovering them, via email to sam@box.net. You must also take immediate action to correct any deficiency and disable any intrusion or intruder. You must not make any public statement regarding any such deficiency without the prior written consent of Box.net.

We may make changes in these terms from time to time; it's your responsibility to ensure that your application conforms to the current version of our terms. We will notify developers of significant changes to these terms on our weblog.