Privacy Policy

The Registry is a living record and registered parties can update their entries through Nooriam Core when information changes. Updates to publicly visible registry information are normal, expected, and straightforward. The current public-facing state of an entry reflects the most recently submitted information. Updates to registry entries do not overwrite or remove prior states. Each update is recorded as a new entry in the history of the relevant record. The current state of an entry reflects the most recent update. The complete history of all prior states, and the dates on which each state was current, is preserved as part of the permanent record. Nooriam does not delete registry entries or any part of the historical record of an entry. The evidentiary and transactional value of The Registry depends on the certainty that what was registered is recorded and that the record cannot be silently altered after the fact. A registry that permits retroactive removal of entries without trace is not a registry in any legally meaningful sense: it is a mutable database, and its records carry no greater authority than any other editable document. For this reason, Nooriam does not delete registry entries in response to erasure requests, whether under privacy law or otherwise. This position is supported by multiple distinct legal bases. First, all major privacy frameworks include a statutory exception to the right of erasure where processing is necessary for the establishment, exercise, or defence of legal claims, or where retention is required or authorised by law. These exceptions exist precisely because legislatures recognised that the right to erasure cannot be absolute where legal records and obligations are involved. The Australian Privacy Principles, the GDPR (Article 17(3)), the UK GDPR, the Singapore PDPA, and the CCPA each contain equivalent carve-outs. Second, where Nooriam’s registry functions are legally recognised, operate under contractual frameworks that give them legal effect, or are relied upon as authoritative records in legal or commercial transactions, the retention of those records may be independently authorised or required by law. Established legal registries worldwide retain historical records on this basis: the legal and evidentiary value of a registry depends on the integrity and continuity of its records, and applicable legislation governing such registries typically requires that historical records be maintained and prohibits their removal. The same principle applies to any registry that performs a legally operative function, including The Registry. Third, where a registry entry records a transaction or obligation to which more than one party is bound, deletion at the request of one party would directly prejudice the legal rights of the other. Privacy law in all major jurisdictions recognises that an individual’s privacy rights do not override the legitimate legal interests of third parties. Nooriam will continue to develop its formal legal basis for registry retention as The Registry’s role in legally recognised transactions and frameworks matures. In the meantime, the position set out above reflects both current legal authority and the structural requirements of any system that aspires to function as a reliable legal registry.

Where a registered party needs to reflect a change in their entry, whether an update to publicly visible information, a change in status, a transfer, a withdrawal, or a correction, they can make that change through Nooriam Core. The updated information becomes the current public-facing state of the entry. The prior state is preserved in the entry history and remains part of the permanent record. Where a party wishes to record that an entry is disputed or superseded, or where a correction is needed to address inaccurate information rather than simply updated information, contact us at info@nooriam.com. Nooriam will assess the request and record the appropriate change where all parties consent, or pursuant to a court order from a court of competent jurisdiction. Counterparties who have relied on the prior state of an entry retain the right to access the historical record.

The Registry operates on the principle that if an Agent is not registered, it does not legally exist for the purposes of Nooriam’s authentication framework. Registration is the act that confers legal identity within the Nooriam ecosystem. Personal information processed in connection with registration is therefore integral to the legal existence of the registered entity and cannot be separated from the registration record without destroying the record’s legal meaning. Individuals seeking to exercise data rights in respect of information embedded in a registration entry should contact us to discuss the options available, having regard to this constraint.

The Registry distinguishes between information that is publicly visible and information that is held within Nooriam Core. Public users of The Registry, meaning any person accessing The Registry without a Nooriam Core account, can access only a defined non-confidential subset of information about a registered Nooriam Data Object or Agent. This public-facing view consists of descriptor and summary fields that identify and describe the asset at a level sufficient for verification purposes, without exposing the full detail of the underlying record or any confidential information associated with it. Nooriam Core users who are logged in and hold appropriate access permissions may be able to view additional information about assets registered by their organisation or in which they hold a recognised interest, subject to the visibility controls configured for each asset. The specific fields that are publicly visible are either determined by Nooriam as part of the standard registry architecture, or set by the registering party using the visibility controls available within Nooriam Core. Registered parties are responsible for the content of the public-facing fields associated with their assets. By registering an asset and completing any descriptor, title, narrative, or summary fields that are designated as publicly accessible, the registering party consents to that information being visible to any person who accesses The Registry, including persons who do not hold a Nooriam Core account, and accepts responsibility for ensuring that those fields do not contain personal information, confidential material, or any other content that the registering party does not intend to make publicly accessible. This responsibility is not discharged by the fact that Nooriam Core permits information to be entered in those fields: it is the registering party’s obligation to review the content of all public-facing fields before and after registration and to ensure that content accurately reflects what they have chosen to disclose. Nooriam does not review the content of public-facing fields for personal information or confidentiality prior to publication. Where a registering party discovers that a public-facing field contains information they did not intend to make publicly accessible, they should contact us promptly. We will work with the registering party to annotate or update the relevant fields through Nooriam Core, subject to the registry integrity principles described in Section 3.2 and the rights of any other parties to the record. Terms of use: The obligation to ensure that public-facing registry fields do not contain information the registering party does not wish to disclose publicly is a condition of use of The Registry. Users are directed to the Nooriam Terms of Use for the full terms governing this responsibility, including the allocation of liability where a registering party places sensitive or personal information in a public-facing field.