# Public chain privacy Source: https://docs.settlemint.com/docs/compliance-security/privacy/overview The compliance and security entry point for deciding whether a regulated asset can use a public EVM network. Public EVM networks are useful for transparent token records, but they are not private databases. Use one for a regulated asset only when your programme can tolerate visible wallet activity, token events, registry relationships, transaction timing, and contract state. DALP keeps private evidence out of the chain path where your programme design allows it. It does not make on-chain transactions confidential by default. ## Choose the audience path [#choose-the-audience-path] Inspect which addresses, token events, claim relationships, transaction inputs, and contract state the public chain exposes. Review network, transaction-routing, mempool, provider-log, and ordering-risk decisions in your deployment architecture. These choices govern how much pending transaction activity is visible prior to finality. Compare public, permissioned, and private EVM patterns. Use this path before deciding whether your asset programme, investor population, and target jurisdictions can tolerate on-chain disclosure of wallet and transaction activity. Run the pre-launch checklist: review on-chain fields, confirm evidence storage, classify routing controls, and record approval decisions before launch. ## Short answer [#short-answer] DALP separates public enforcement data from private evidence. Claims, registries, token events, wallet addresses, transaction inputs, and contract state written to a public EVM network remain visible according to that network's behaviour. KYC, KYB, AML, sanctions, beneficial ownership, investor files, and review notes stay off-chain in approved evidence systems. DALP supports the enforcement pattern through identity registries, trusted issuers, claims, compliance modules, custody integrations, signing workflows, and configured EVM networks. Private mempools, encrypted order flow, confidentiality frameworks, zero-knowledge proofs, shielded tokens, stealth-address designs, and permissioned network controls are deployment architecture choices. Your team must select and integrate each one, operate it with explicit approval, and verify the confidentiality guarantee it provides for your specific asset programme. ## Decision summary [#decision-summary] | If the asset requires | Public EVM fit | Read next | | ---------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | | Public issuance with regulated transfer controls | Suitable only when wallet activity, token events, registry relationships, and contract state can be public. | [Public EVM visibility model](/docs/compliance-security/privacy/public-evm-visibility-model) | | Private KYC, KYB, AML, sanctions, ownership, or accreditation evidence | Keep evidence off-chain. Publish only claim topics, issuer attestations, and wallet-to-identity links required for enforcement. | [Identity and compliance](/docs/compliance-security/security/identity-compliance) | | Confidential investor registers or sensitive commercial terms | Do not encode names, account references, private document identifiers, tranche labels, or commercial terms in public metadata, claim data, URIs, or transaction inputs. | [Pre-launch privacy review](/docs/compliance-security/privacy/pre-launch-review) | | Network-level access control | Use a private or permissioned EVM network. DALP can operate with configured EVM networks, but network privacy comes from the selected network. | [Privacy architecture patterns](/docs/compliance-security/privacy/architecture-patterns) | ## DALP boundary [#dalp-boundary] DALP can keep source evidence off-chain, enforce configured eligibility through SMART Protocol contracts, track submitted operations, and index confirmed events. Those events are queryable from the Console, the Platform API, and audit reports. It does not make on-chain transactions confidential, hide wallet graph relationships, rewrite committed chain data, or provide a bridge protocol. It also does not determine your legal basis, retention period, data-transfer mechanism, or privacy notice wording. ## Where to go next [#where-to-go-next] | Need | Read next | | ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | | Inspect what becomes visible on public EVM networks | [Public EVM visibility model](/docs/compliance-security/privacy/public-evm-visibility-model) | | Review pending transaction, mempool, and ordering exposure | [Transaction ordering privacy](/docs/compliance-security/privacy/transaction-ordering-privacy) | | Compare privacy patterns and deployment choices | [Privacy architecture patterns](/docs/compliance-security/privacy/architecture-patterns) | | Review identity enforcement and claim design | [Identity and compliance](/docs/compliance-security/security/identity-compliance) | | Review private transaction routing choices | [Private mempool routing](/docs/compliance-security/privacy/private-mempool-routing) |