Licenses and notices
Understand where software and distribution notices belong.
At a glance
Notices must come from the actual website and app dependency inventories and remain associated with the builds to which they apply.
This website design
This prototype uses locally authored HTML, CSS, JavaScript and vector illustrations, plus system font fallbacks. It loads no external font service, bundled framework, stock image library or third-party analytics script. This is a statement about this design’s files, not the Notes app dependency inventory.
Installed application notices
Each app may include third-party software and platform-specific notice requirements. Those notices need to ship through the appropriate application and distribution channels so a local-only user can access them. A website cannot stand in for missing notices inside a distributed package.
Keep notices with the right version
Version the reviewed notice set with the corresponding release or build. A later website update must not remove information needed for an already distributed version. Required attribution is different from an optional “powered by” marketing message.
Inventory and review
Engineering must supply the actual dependencies, license texts and notice files. The reviewer determines publication and distribution obligations. This draft does not reproduce unknown license terms or imply the application has no third-party components.