Legal Information

At DBF, we take legal and ethical considerations seriously in the development of our software solutions for enterprise clients. This Legal Information section provides an overview of our use of open-source libraries, compliance with licensing requirements, and other legal considerations related to our software. Please read this information carefully.

1. Use of Open Source Libraries

Our software integrates numerous open-source libraries to deliver efficient and innovative solutions to our clients. Open-source software (OSS) plays a role in the technology ecosystem, and we are committed to adhering to all applicable legal obligations when using these resources.

• MIT Licensed Libraries: The open-source libraries we use are licensed under the MIT License, one of the most permissive and widely adopted licenses in the open-source community. The MIT License allows for the use, modification, and distribution of software with minimal restrictions, provided that the original copyright and license notice are included in any distributed software.
• Other Open Source Licenses: In addition to MIT-licensed libraries, our software may incorporate components distributed under other open-source licenses, including the Apache License 2.0, GNU General Public License (GPL), Lesser General Public License (LGPL), Berkeley Software Distribution (BSD) License, and others. Each of these licenses has its own terms and conditions that we strictly follow.some text
  • Apache License 2.0: This license allows for the use of software for any purpose, including distribution, modification, and private use. However, it also imposes requirements regarding the inclusion of notices, changes to the code, and an express grant of patent rights.
  • GNU General Public License (GPL): The GPL is a copyleft license that requires any derivative work to be licensed under the GPL as well. If our software incorporates GPL-licensed code, we ensure that we comply with all obligations, including making the source code available to users.
  • Lesser General Public License (LGPL): The LGPL is a more permissive version of the GPL, allowing LGPL-licensed libraries to be linked with proprietary software under certain conditions. We adhere to the requirements of the LGPL when integrating such libraries into our solutions.
  • BSD License: The BSD License allows for almost unrestricted use and redistribution of software, provided that the original copyright notice and disclaimer of warranties are maintained.

2. Compliance with Licensing Obligations

We ensure full compliance with all licensing obligations associated with the open-source libraries used in our software. This includes, but is not limited to:

• License Documentation: We include the necessary license documentation for all open-source components within our software. This ensures that the original licenses, copyright notices, and disclaimers are preserved and appropriately communicated to our users.
• Source Code Availability: For libraries licensed under the GPL, LGPL, or other licenses that require the distribution of source code, we provide access to the source code as required by the license terms. If you need access to the source code for any open-source components used in our software, please contact us at [Your Contact Email].
• Attribution Notices: We respect the efforts of open-source developers by providing proper attribution for all libraries used in our software. This includes listing the libraries, their authors, and links to the original projects where applicable. Our "Open Source Acknowledgments" section contains detailed information on these attributions.

3. Modifications to Open Source Code

In some instances, we may modify open-source libraries to better fit the specific needs of our enterprise clients. When we modify such code, we do so in full compliance with the original licensing terms. Depending on the license, this may include:

• Contributing Back: If the license requires or encourages contributions back to the community (e.g., under the GPL), we make our modifications available to the public under the same license terms.
• Documentation of Changes: Where applicable, we document the changes made to the original open-source code and provide this documentation to our users. This ensures transparency and allows others to benefit from our enhancements or fixes.

4. Warranty Disclaimer and Limitation of Liability

While we strive to ensure the reliability and security of our software, including all open-source components, it is important to note that:

• No Warranty: Open-source libraries integrated into our software are provided "as is" without any warranties of any kind, whether express or implied. This includes, but is not limited to, implied warranties of merchantability, fitness for a particular purpose, and non-infringement.
• Limitation of Liability: We do not assume any liability for damages, losses, or issues arising from the use of third-party open-source libraries. The responsibility for ensuring the suitability and security of open-source components lies with the user, and we disclaim any liability for issues that may arise from their use.

5. Intellectual Property Rights

Our proprietary software code and the open-source libraries we integrate each have distinct intellectual property (IP) rights:

• Proprietary Code: The proprietary components of our software are protected under copyright, trademark, and other intellectual property laws. We retain full ownership of our proprietary code, and users are granted licenses to use it subject to the terms of our End User License Agreement (EULA).
• Open Source Code: The open-source libraries used in our software remain under the ownership of their respective authors. We respect and acknowledge these IP rights, ensuring that all uses of open-source software are in compliance with the applicable licenses.

6. Contributions and Collaboration with the Open Source Community

We believe in the importance of giving back to the open-source community. As such, we may contribute to open-source projects by:

• Submitting Patches and Enhancements: When we identify bugs or areas for improvement in open-source libraries, we may contribute patches or enhancements back to the original projects. This helps improve the quality of the libraries we rely on and benefits the broader community.
• Collaborative Development: We may participate in collaborative development efforts with the open-source community. This can include sponsoring projects, participating in discussions, or providing resources to support the continued development of key open-source tools.

7. Updates and Changes to Open Source Components

The landscape of open-source software is constantly evolving. We regularly review and update the open-source libraries used in our software to ensure that we are utilizing the most secure and efficient versions available.

• Version Updates: We may update the versions of open-source libraries used in our software to benefit from security patches, performance improvements, or new features. These updates are communicated to our clients through release notes or other appropriate channels.
• Library Replacements: In some cases, we may replace one open-source library with another to better meet the needs of our software. This could be due to licensing changes, deprecation of a library, or the availability of a better alternative. Any significant changes to the open-source components used in our software will be documented and communicated to our clients.

8. Third-Party Software and Dependencies

In addition to open-source libraries, our software may interact with third-party software or services. These third-party components are subject to their own licensing terms and conditions, which may differ from those governing the open-source libraries we use.

• Third-Party Licensing: We ensure that all third-party software integrated into our solutions is properly licensed. However, it is the responsibility of our clients to review and comply with the licensing terms of any third-party software or services they choose to use in conjunction with our software.
• Dependencies: Our software may have dependencies on certain open-source or third-party libraries. We manage these dependencies to ensure that they are compatible with our software and that their licenses are adhered to. Clients should be aware of any potential licensing obligations associated with these dependencies.

9. No Endorsement or Affiliation

The inclusion of open-source libraries or third-party software in our solutions does not imply endorsement or affiliation with the original authors, maintainers, or organizations behind those projects. We use these libraries independently, and any issues, modifications, or integrations are solely our responsibility.

10. Contact Information and Support

If you have any questions, concerns, or requests regarding our use of open-source libraries, third-party software, or any other legal matters related to our software, please reach out to us:

• Email: hello@digitalbluefoam.com

We are committed to transparency and are here to provide any necessary information or support regarding our software and its legal aspects.

11. Changes to This Legal Information

We reserve the right to update or modify this Legal Information section at any time. Any changes will be posted on this page and will be effective immediately upon posting. We encourage you to review this section regularly to stay informed about our legal practices and compliance efforts.

‍