Third-party Notices
Version: Draft 0.1 · Last updated
Draft pending legal review. This document is not yet in force. Highlighted items are still to be confirmed.
DeskAcross is built with the help of open-source software. This page explains where the license notices for those components are published and how to ask about them.
1. What a notice is
Many open-source licenses ask that anyone who distributes the software keeps the copyright statement and license text with it. A third-party notice is that statement: the name of the component, its version, its copyright holders, and the license under which it is used.
Using DeskAcross does not require you to do anything with these notices. They are published so that the authors of the components are credited and the license terms are available to you.
2. The website
This website is built with the following open-source projects:
- Next.js, the web framework.
- React, the user interface library.
- Tailwind CSS, for styling.
- Lucide, for icons.
These projects in turn depend on other packages. To be confirmed: the generated list of website dependencies with versions and license texts, produced from the lockfile at release. The full list will be published on this page once it is generated as part of the release process.
3. The desktop application
The desktop application for Windows and macOS also includes third-party components. Their notices will be made available in two places:
- Inside the application package. Each release ships with a notices file that matches the exact versions included in that release.
- On this page. A copy for the current release, with a link to notices for earlier releases.
To be confirmed: the list of desktop application dependencies, versions, and license texts for the first public release.
To be confirmed: where in the application the notices can be opened, for example an About or Licenses screen.
4. Versions
Notices are tied to a release. When a dependency is added, removed, or updated, the notices file for the next release changes with it. The notices file is kept under version control alongside the source so that each release can be matched to the components it contained. The release notes identify each release.
5. Source code offers
Some licenses require that the source code of a component be offered to recipients. Where a component in DeskAcross carries such a requirement, the notice for that component will say how to obtain the source. To be confirmed: whether any included component carries a source-offer obligation, after the dependency review.
6. Trademarks
Names of third-party projects and products mentioned on this website, including Windows, macOS, Dropbox, iCloud Drive, OneDrive, and Google, belong to their respective owners. They are used to describe compatibility and do not imply endorsement.
7. DeskAcross's own license
The notices on this page concern third-party components only. Your right to use DeskAcross itself is set out in the End User License Agreement.
8. Questions and corrections
If you maintain a project that DeskAcross uses and believe a notice is missing or incorrect, or if you need the notices for a specific release, write to us through the contact page. We will correct errors in the next release and on this page.