# Pre-launch privacy review

Source: https://docs.settlemint.com/docs/compliance-security/pre-launch-privacy-review
Operator checklist for reviewing on-chain fields, evidence storage, transaction routing, and legal approval before a regulated asset uses a public EVM network.




Use this checklist before a regulated asset programme uses a public EVM network. The goal is simple: confirm what becomes public, keep private evidence off-chain, and record which privacy choices belong to the deployment architecture.

This page is for operators, security reviewers, and compliance teams preparing a launch. For the decision frame, start with [Public chain privacy](/docs/compliance-security/public-chain-privacy). For the chain-visible data model, read [Public EVM visibility model](/docs/compliance-security/public-evm-visibility-model).

## Review the on-chain data set [#review-the-on-chain-data-set]

1. List every field written to token contracts, identity registries, OnchainID claims, trusted issuer registries, compliance modules, feeds, and transaction inputs.
2. Remove personal data, confidential commercial terms, document identifiers, private URLs, raw evidence, and internal notes from public-chain fields.
3. Confirm token names, symbols, metadata, claim topics, issuer labels, feed topics, and event parameters are approved for public discovery.
4. Confirm wallet, identity, issuer, custodian, and operator addresses can be associated with their roles.

## Keep source evidence off-chain [#keep-source-evidence-off-chain]

1. Store KYC, KYB, AML, sanctions, beneficial ownership, investor files, review notes, and legal evidence in approved off-chain systems.
2. Configure claims and compliance modules to enforce eligibility from attestations and rules, not from raw evidence.
3. Confirm the off-chain evidence owner, retention period, access-control model, and audit-export path.
4. Check the [privacy policy](/docs/business/legal/privacy-policy) and [terms of service](/docs/business/legal/terms-of-service) for the legal treatment of blockchain data.

## Classify routing and ordering controls [#classify-routing-and-ordering-controls]

1. Decide whether pending mints, burns, redemptions, treasury actions, reserve updates, freezes, forced transfers, or role changes can be visible before finality.
2. Classify each mempool, ordering, privacy-framework, proof-system, stealth-address, and private-order-flow requirement as one of these:
   * a DALP platform pattern
   * a configured EVM network capability
   * a deployment-specific provider integration
   * outside the default DALP capability
3. If a private route is required, record the provider, supported chains, submission route, failure behaviour, monitoring, audit evidence, and fallback path.
4. Confirm the configured network in [supported networks](/docs/architects/architecture/integrations/supported-networks) is the intended EVM environment.

## Approval record [#approval-record]

| Area                | Required decision                                                               | Typical owner                          |
| ------------------- | ------------------------------------------------------------------------------- | -------------------------------------- |
| On-chain metadata   | Public values are safe for disclosure.                                          | Product owner and compliance reviewer  |
| Identity and claims | Claim topics expose eligibility state without source evidence.                  | Compliance reviewer and verifier owner |
| Evidence storage    | Source files remain in approved off-chain systems.                              | Operations owner and legal reviewer    |
| Transaction routing | Public or private submission path matches the asset risk.                       | Architect and operator                 |
| Network choice      | The selected EVM network matches visibility, access, and recovery requirements. | Architect and business sponsor         |

## Where to go next [#where-to-go-next]

* [Public chain privacy](/docs/compliance-security/public-chain-privacy) for the decision summary.
* [Public EVM visibility model](/docs/compliance-security/public-evm-visibility-model) for the data that becomes visible.
* [Transaction ordering privacy](/docs/compliance-security/transaction-ordering-privacy) for pending transaction exposure.
* [Privacy architecture patterns](/docs/compliance-security/privacy-architecture-patterns) for deployment choices.