Terms of use


These principles explain what you can expect from us and what we expect from you when creating and operating software services that consume Livestock Information Application Programming Interfaces (APIs) hosted on the Livestock Information (LI) Developer Hub. They do not create a legal relationship between LI and any software developer.

We reserve the right to remove your access to the Developer Hub and its APIs temporarily or permanently.

These principles may change from time to time and we will let you know when this happens. For major changes you may need to re-accept these principles, but for minor changes we will assume you agree to the changes unless we hear from you.

What you can expect from us

We will:

  1. work with you if we need to make a change, and give you as much notice as possible
  2. provide a test environment.
  3. provide 2 test accounts and test CPH, Flock, MHS and tag data to enable testing of the APIs
  4. provide you the assistance on managing your incidents based on sufficient evidence (with detailed evidence and linkage of incident with LIS APIs) you have provided us.

What we expect from you

We take the protection of customer data seriously. We expect you to do the same by following data protection law and protecting users in line with the:

You must also follow these acts and regulations if they’re changed or replaced.

Accessing data

You must give your users access to their data. We may also ask to access their data if we open an investigation.

If you withdraw a piece of software or a user stops using it, you must let them retrieve and export all their data so they can meet their obligations to us.

We recommend using multi-factor authentication to protect personal data.

Data breaches

If there’s a data breach or any other issue concerning customer data you must tell us immediately by emailing devsupport@livestockinformation.org.uk Under UK GDPR rules, you must also notify ICO about certain types of personal data breach (opens in a new tab) within 72 hours of becoming aware of it.

Security

You must:

  • check software for vulnerabilities through secure development and pre-release testing
  • check open source or reused proprietary code using resources like the Common Vulnerabilities and Exposures (opens in a new tab) database
  • react quickly if you find vulnerabilities in your code
  • have a patching policy in place

Your re-releases and upgrades should also follow secure development practices and pre-release testing.

We recommend following the security principles of:

Suspicious activity

We expect you to look out for and block suspicious attempts to access or manipulate user accounts.

If you need help or want to raise an incident go to LI Developer Support.