Usage Policies

The Usage Policies, including the Terms of Use, License Agreements and Privacy Policy, specify how this website and the application (BlüeBox) or its services may be used, what limitations apply, and what steps the author (Tim Forsythe) takes to protect your privacy. Users should review these policies occasionally as they may change without notice. This document is intentionally kept short so please take a moment to read through it.

Use of this website, its services and/or applications constitutes acceptance of these policies.

Terms of Use

The applications are provided as-is without warranty of any kind. The author makes no guarantees that the applications or services will work as you might expect, or that existing services will be continuously, or will continue to be available.

License Agreements

This license agreement supersedes that found in the LICENSE.txt file in the distribution.

The application is licensed under the Creative Commons Attribution 4.0 International License

Creative Commons License

This license agreement states that you are free to download and use the application for personal or commercial purposes, and that you may modify it, but that you must provide appropriate attribution. Read the full license agreement for more details. The license agreement applies to the application only, not to the web pages generated by it. The generated web pages may be subject to additional third-party end-user license agreements depending on which plugins are loaded by your configuration. Please review the plugins for additional details.

Testing Service

A free service is provided for previewing and testing application databases. Administrators are responsible for all content appearing on their preview sites. Discriminatory and inappropriate speech and images are prohibited. No server executable code or hacking attempts are permitted.

Privacy Policy and Cookies

The application and services do not allow for or collect passwords, financial information, or any other types of secure or personal data. Update checks are logged to a file that includes the current timestamp, your IP address, the application version and the application id, none of which is personally identifiable, and is needed to support the testing service.