> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rns.id/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage Legal DID Privacy and Claims

> Understand public Legal DID metadata, separate KYC access, claims profiles, identity updates, and cached third-party displays.

Legal DID has two separate controls: a public metadata profile and a KYC-access setting. Selecting **Minimal** metadata does not limit every verification channel to the Minimal fields.

## KYC verifiability

The KYC setting controls access through supported KYC-verification requests. For the permission-based partner service, both the KYC setting and the requesting application's granted permissions are checked.

This service is not limited to a yes-or-no verification result. An authorized request can return personal details and, at higher permission levels, identity images where available. The **Minimal** and **Standard** public metadata profiles do not set this separate service's data-access level.

<Note>
  Enabling KYC does not by itself grant a third party access. Verification depends on a supported integration and the permissions granted to it. Public token metadata is controlled separately.
</Note>

Turning KYC off blocks supported KYC requests that check this setting. It does not hide your selected public metadata, erase historical blockchain records, or remove the Legal DID from its wallet.

## Claims profiles

RNS.ID currently presents two public metadata profiles:

| Profile | Metadata fields |
| - | - |
| **Minimal** | Internal ID, validity, jurisdiction, sanctions result, age-over-21, age-over-18, and zero-knowledge version |
| **Standard** | All Minimal claims, plus ID type, gender, birth year, photo hash, uploaded-ID-picture hash, issue date, and expiration date |

The available fields and values can vary with the identity type and status. The photo-hash fields contain hash values, not image files. This does not mean that the separate KYC service is restricted to hashes or anonymous data.

If you use **Update KYC** for a linked Palau ID, approved identity changes may be reflected in public metadata without changing your selected profile. See [Effect on Legal DID](/palau-id/update-personal-information#effect-on-legal-did).

Treat the selected metadata as public information. Review the fields before choosing a profile, and select the smaller profile if you do not want to expose the additional fields.

## Change the settings

1. Open the Legal DID management page.
2. Review the KYC-sharing control and current claims profile.
3. Select the preferred setting.
4. Confirm the change.

The settings apply to the Legal DIDs associated with that identity. Saving them does not require a blockchain fee. A wallet or marketplace may continue to show cached metadata until it refreshes.

## Refresh third-party metadata

Some wallets and marketplaces cache token metadata. After changing the profile, use the available refresh action in RNS.ID or the third party's metadata-refresh control. A stale display does not necessarily mean the setting failed.

<Note>
  Public token metadata and blockchain history can be copied or cached by third parties. Changing a current claims profile or turning KYC off cannot guarantee removal of information that another party previously received or recorded.
</Note>