Confidentiality & License Data Protection | Neves Licensing Authority
Confidentiality framework

Confidentiality & License Data Protection

This page explains what information may be displayed through public verification, what information is restricted, and the Authority’s approach to confidentiality and data protection for license-related records.

Controlled disclosure No bulk access / no APIs Misuse-resistant records
Verify a license → Request confirmation →
Public verification provides high-level confirmation only. Detailed information is shared through controlled channels where appropriate.

Overview

The Neves Licensing Authority maintains license-related information in a controlled internal database. The Authority adopts a confidentiality-first approach to protect license information, prevent misuse, and ensure that public verification remains accurate, current, and authoritative.

Controlled database Restricted disclosure Verification-led

1) What information may be disclosed

The Authority may display a limited set of high-level information through the Verify License tool to enable public confirmation of license claims. Typical disclosed fields may include:

License number / reference

Unique identifier used for verification and record matching.

License holder name

Legal name as recorded, where available and appropriate.

License type / category

High-level category (e.g., NFSA / NGA), where displayed.

Status outcome

Status label (Active, Suspended, etc.) at time of verification.

Effective / expiry dates

May be displayed where necessary for clarity.

Registered agent (if applicable)

May be shown where required for identification.

Note: Displayed fields may vary depending on the license type, entry status, and the purpose of the verification output. The Authority may limit disclosure where necessary to protect confidentiality and data integrity.

2) What information is restricted

The Authority restricts access to information that could create privacy risk, enable misuse, or expose sensitive operational details. Restricted information may include (non-exhaustive):

  • Personal data of directors, officers, beneficial owners, or employees.
  • Internal correspondence, application working papers, and review notes.
  • Supporting documents submitted during application or lifecycle updates.
  • Detailed compliance submissions, internal controls documentation, or third-party reports.
  • Banking, payment, settlement, and operational account details.
  • Security architecture, system identifiers, or database structure.
Why restricted: Restricting these categories reduces identity risk, protects legitimate confidentiality interests, and prevents mass harvesting or cloning of records.

3) No bulk access, scraping, or third-party mirroring

The Authority does not provide APIs, automated data feeds, bulk exports, or permissions for third parties to mirror or republish license data. Public confirmation is available only through the Authority’s website interface.

  • No third-party “official register” mirrors are authorised.
  • Automated harvesting or scraping may be blocked and treated as misuse.
  • Verification outcomes should be retained as a point-in-time record (e.g., screenshot or PDF, where available).
Important: If a third-party website claims it can “verify” an NLA license outside the official website, treat the claim with caution and use the official verification tool instead.

4) Controlled access and written confirmations

Where written confirmation is required for an institutional process, the Authority may issue a confirmation or attestation through controlled channels. Requests may be subject to identity checks, authority to request, and scope limitations.

  • Requests are processed through the Authority’s official contact channels.
  • Requests must include sufficient identifying details (license number, legal name, purpose).
  • Confirmation scope may be limited to status and high-level particulars.
Next step: Use License Confirmation & Attestation Requests to submit a request.

5) Data quality, integrity, and security controls

The Authority maintains administrative and technical controls intended to protect the confidentiality and integrity of license records. Controls may include:

  • Restricted internal access based on role and need-to-know.
  • Audit logs for administrative actions and record updates.
  • Change controls for license record amendments.
  • Security measures designed to prevent unauthorised access and tampering.
Accuracy: Verification outputs reflect the information available in the internal database at the time of the query. If you believe an output is incorrect, follow the correction request pathway.

6) Correction requests

If a license holder believes that public verification displays incorrect or outdated high-level information, a correction request may be submitted. The Authority may require supporting documentation to validate the request.

  • Submit requests via the official contact channel.
  • Provide license number, legal name, and the specific field(s) requiring correction.
  • Where appropriate, provide supporting documentation or references.
Contact: Use the Contact page to submit a correction request.

Frequently asked questions

Why doesn’t the Authority publish an open register?

The Authority maintains a controlled database model to reduce misuse, protect confidentiality interests, and keep verification outcomes accurate and current through a single authoritative interface.

Can a bank or service provider obtain written confirmation?

Yes. Where required for an institutional process, written confirmation may be requested through the Authority’s official channels. Confirmation scope may be limited to status and high-level particulars.

What should I do if I find my details displayed incorrectly?

Submit a correction request through the official contact channel with your license number, legal name, and the specific fields requiring correction, along with supporting references where appropriate.

At a glance

High-level disclosure
Public verification provides limited fields required for confirmation.
Restricted data
Sensitive and personal data is not disclosed via public tools.
No bulk access
No APIs, feeds, bulk exports, or third-party mirrors are authorised.
Controlled confirmation
Written confirmations may be provided through official channels.
Corrections pathway
license holders can request correction of displayed high-level fields.
Misuse prevention
Controls help reduce cloning, harvesting, and misrepresentation risks.