Legal requirements

Overview of the legal requirements for onboarding DNV applications on Veracity.

For non-DNV applications, contact the Veracity onboarding team.

Terms and conditions requirement

Any product delivered to DNV customers must be governed by terms and conditions. This requirement also applies to free services.

DNV Group Legal is the only authority that can issue terms and conditions for distributing products. Terms and conditions used in traditional contracts cannot be reused because different laws apply to online distribution.

The information below helps prepare requests to Group Legal and can make the process smoother.

Compliance requirements for DNV applications

If you work for DNV, ensure that your application meets the following requirements:

• Updated agreements exist for the use of intellectual property not owned by DNV.
• The application complies with current GDPR requirements.
• Licences for all components have been reviewed and the application complies with them.

The product or service owner is responsible for ensuring compliance with these points. DNV Group Legal can assist with guidance.

Information required for onboarding

To onboard a DNV-owned application, contact the Veracity onboarding team.

Prepare to answer the following questions about your application:

• Are you using third-party data?
• Are you using third-party components?
• Have you entered into the necessary legal agreements to use third-party data and components?
• Are you using open-source components? If yes, do you comply with their distribution licences?
• Are you storing personal data?

Open-source licence considerations

Open-source licences typically fall into three categories:

• Permissive licences, such as MIT, Unlicense and Apache 2.0. These licences are rarely problematic.
• Hybrid or weak copyleft licences, such as MPL 2.0 and LGPL. These licences are usually acceptable, but the licence text must be reviewed carefully.
• Copyleft licences, such as GPL and EUPL. These licences are often problematic and should generally be avoided. Using multiple licences of this type can make distribution of the application impossible. Consider alternative dependencies with more permissive licences.

Veracity recommends using a licence compliance tool such as VeraCode to obtain an overview of the licences used by your software components (dependencies).

DNV reference materials

For more information about DNV policies related to licences, see the resources below.

Public licence reference materials

For more information about public licences, see the resources below.