Digital Tool Haven is committed to honoring the licenses of all third-party software components that we use in our products. Our software tools may include open-source libraries or other third-party code, which are subject to their own license terms. This page provides information on how we disclose and give attribution for those components.

1. Open Source and Third-Party Components
   We incorporate certain open-source software components into our products in order to build functionality efficiently and reliably. Each of these components is distributed under an open-source license (for example, MIT, Apache 2.0, GPL, etc.) or another type of third-party license. Under the terms of those licenses, we are required to provide proper attribution, copyright notices, and in some cases the full text of the license to you. We take these obligations seriously and ensure that all required notices are provided.
   By consulting the provided third-party license file in the product, you can see:
   We recommend reviewing the THIRD-PARTY-LICENSES.txt (or similarly named) file included with the product if you are interested in the open-source components that our software uses. You have rights under those third-party licenses independent of our software license. For example, some licenses may grant you the right to obtain source code for the component, or to modify and redistribute the component under certain conditions. Our inclusion of the component in our product does not limit your rights under its original license.
   Component Name and Version: The name of the library or tool we used, and often the version number
   License Name
   The type of license governing that component (e.g., “MIT License”, “Apache License 2.0”, etc.).Copyright Notice: The original copyright holder’s notice for that component.
   Full License Text: Many open-source licenses require that the full text of the license be provided. We include the complete license text for each component as required (either directly in the notices file or via a reference if the license is very common and well-known).Rather than listing every third-party component and license on this webpage, we have included the details within the software itself. For each of our products, you will find a file (or menu section) usually named “THIRD-PARTY-LICENSES.txt”, “Open Source Licenses”, or similarly clear, which contains a list of the third-party components used in that product along with their licenses and copyright statements. This file is typically packaged with the software download (for example, located in the installation directory or included alongside the executable or app package). In some cases, the software’s “About” dialog or documentation may also refer to third-party acknowledgments.

1. How to Find Third-Party License Information
   Included Text Files
   As mentioned, check the installation folder or package contents for a file named “LICENSE”, “NOTICE”, “COPYING”, or “THIRD-PARTY-NOTICES”. For example, if you installed our software on Windows, you might find a “ThirdPartyLicenses.txt” in the program directory. On macOS, the app bundle might contain a Resources folder with open-source licenses. On Linux, there might be a licenses directory. We strive to make it obvious; instructions are usually in the README or user manual if needed.
   In-App Acknowledgments:
   Some products may have an “About” section or menu that lists third-party credits. This can be another place to quickly see major components and their licenses.
   Contact Us:
   If you have trouble locating the third-party notices or have questions about them, feel free to contact us. We can provide you with the list of third-party components and copies of their licenses upon request. We can also provide the source code of any GPL/LGPL or similarly licensed components if we are obligated to do so (for example, if our product used GPL-licensed code and that triggers a requirement to provide source – note: we generally avoid copyleft components in our proprietary software, but if any exist, we will comply with all requirements).

1. Respecting Licenses
   We respect all intellectual property and licenses for software we use. Open-source licenses often allow us to use wonderful libraries for free, in exchange for proper attribution and keeping the license terms intact. We have not made any changes to the open-source components that would violate their licenses and any modifications we made (if any) are documented as required.
   By using our product, you are not subject to any additional restrictions on those open-source components beyond what their original licenses state. In other words, we do not impose any license on those components other than the original one. Our Terms of Service apply to our own software as a whole, but do not override the freedoms granted by open-source licenses for the third-party portions. For example, if we use an MIT-licensed library, you still have the rights under MIT for that library.
   Conversely, our Terms of Service’s restrictions (such as not redistributing the product) apply to our proprietary code, not to the open-source parts used within. If you were to separate an open-source component from our software, that component could be used under its own license terms independently.

1. List of Common Third-Party Components
   (The following is an example list – the actual components will be detailed in the product’s TXT file. We list a few here illustratively.)
   ExampleLibrary – Copyright 2019 Example Corp. – Licensed under the Apache License 2.0.Awesome
   Framework – Copyright 2015-2021 Awesome Contributors – Licensed under the MIT License.
   AnotherTool (v1.2.3) – Licensed under GNU LGPL 2.1 – Source available from the original author’s website.(Please refer to the actual third-party notice file for the complete, up-to-date list relevant to your version of the product.)
   

1. Our Responsibilities and Yours
   We acknowledge and thank the open-source community and third-party developers for their contributions. We have complied with all applicable license conditions to the best of our knowledge. If you believe any attribution is missing or incomplete, please let us know and we will address it promptly. We want to be fully transparent about others’ work that we benefit from.
   When you use our products, you must also respect the license terms of included third-party software. Using our software in accordance with our Terms of Service should not normally conflict with any open-source license obligations, since those components are just internal parts of our tool. However, if an open-source license (for example, the GPL) imposes certain conditions on use or distribution of that component, those conditions apply to the component itself.
   In practical terms, this mostly matters if you were to extract or separately use the open-source component outside of our software. As a regular end user, you generally just need to be aware that the component is under a certain license. We ensure that none of the open-source components we use will impose any obligation on you to, say, open-source your own data or work – they are used in a way that is consistent with end-user usage.