feat: prividium tm (#477)

# Description

Updates references of Prividium to follow trademark guidelines

## Linked Issues

N/A

## Additional context

Author: uF4No

content/10.zk-stack/10.zk-chains.md

@@ -131,7 +131,7 @@ Its key characteristics are:
 - **Controlled DA**: The hosting organization controls data availability.
   Although the funds held in validiums are secure against theft, they can be frozen if the data becomes unavailable.
   This scenario would not only lock users out of their assets but also potentially damage the reputation and operational status of the hosting organization.
-- **User-Level Privacy**: [ZKsync Prividium](/zk-stack/prividium) enables user-level privacy while giving the chain operator full visibility.
+- **User-Level Privacy**: [Prividium™](/zk-stack/prividium) enables user-level privacy while giving the chain operator full visibility.
   Because the host organization controls data availability, it has the power to restrict access.
 - **Lower Cost**: Validiums offer flexibility for operators to save costs when they don't require a high level of security (e.g. a gaming chain).
 

content/10.zk-stack/30.customizations/20.validium.md

@@ -261,7 +261,7 @@ so the procedure wouldn't differ a lot.
 
   ::panel{label="How can I enable privacy?"}
 
-  To enable privacy on your chain, check out the [ZKsync Prividium documentation](/zk-stack/prividium).
+  To enable privacy on your chain, check out the [Prividium™ documentation](/zk-stack/prividium).
 
   ::
 ::

content/10.zk-stack/35.prividium/00.overview.md

@@ -1,8 +1,8 @@
 ---
-title: Prividium Overview
-description: Learn about ZKsync Prividium.
+title: Prividium™ Overview
+description: Learn about Prividium™.
 ---
-ZKsync Prividium lets institutions operate a **private**, permissioned blockchain within their own infrastructure or cloud,
+Prividium™ lets institutions operate a **private**, permissioned blockchain within their own infrastructure or cloud,
 while still **anchoring every transaction to Ethereum** for security and finality.
 
 Sensitive data stays entirely off the public chain, but each state update is verified on Ethereum using zero-knowledge proofs.
@@ -11,21 +11,21 @@ This design solves a core challenge in enterprise blockchain adoption:
 **how to maintain privacy and control without giving up interoperability with the broader Ethereum ecosystem**.
 
 ::centered-container
-*Figure: High-level design of ZKsync Prividium*
-![ZKsync Prividium architecture diagram](/images/zk-stack/how-prividium-works.png)
+*Figure: High-level design of Prividium™*
+![Prividium™ architecture diagram](/images/zk-stack/how-prividium-works.png)
 ::
 
 ---
 
-### Key Differentiators of ZKsync Prividium
+### Key Differentiators of **Prividium™**
 
 **Privacy with Control:**
 Transaction data remains offchain, so internal details such as trades and balances stay confidential.
 Each block is verified on Ethereum using zero-knowledge proofs.
 Chain operators can selectively disclose specific data (for example, bytecode or token supply) to auditors or regulators without exposing the full ledger.
 
 **Role-Based Permissioning:**
-Prividium introduces a dynamic permissioning system managed through the **Admin Dashboard**, replacing static YAML files.
+Prividium™ introduces a dynamic permissioning system managed through the **Admin Dashboard**, replacing static YAML files.
 Administrators can:
 
 - Add and manage users with Okta or crypto-native (SIWE) authentication
@@ -45,7 +45,7 @@ Assets and data can move between Ethereum and other public or private ZKsync Cha
 using native zero-knowledge-based bridges without external custodians.
 
 **Scalability and Performance:**
-As a Validium chain, ZKsync Prividium stores state off-chain, achieving high throughput and low latency.
+As a Validium chain, Prividium™ stores state off-chain, achieving high throughput and low latency.
 It supports trading, payments, and settlement use cases that demand both privacy and speed.
 
 ---
@@ -59,15 +59,15 @@ Selective disclosure can optionally expose verified metrics such as total and ci
 through public read-only endpoints.
 
 Interactions with public networks such as deposits or withdrawals remain visible on the receiving chain,
-but all other state data is kept private within the Prividium database.
+but all other state data is kept private within the Prividium™ database.
 
 To learn more about data availability in the ZK Stack, visit the [Validium page](/zk-stack/customizations/validium).
 
 ---
 
 ### How It Works
 
-ZKsync Prividium enforces privacy and access control using built-in infrastructure within the ZK Stack.
+Prividium™ enforces privacy and access control using built-in infrastructure within the ZK Stack.
 
 - Users authenticate through **Okta SSO** or **Sign-in With Ethereum (SIWE)**.
 - All calls pass through the **Proxy RPC**, which checks the user’s token and permissions against the **Permissions API**.

content/10.zk-stack/35.prividium/02.features.md

@@ -1,21 +1,21 @@
 ---
 title: Features
-description: Dive into ZKsync Prividium's key features and capabilities.
+description: Dive into Prividium™'s key features and capabilities.
 ---
 
-ZKsync Prividium delivers private execution, enterprise-grade access control, and Ethereum-level security in a single composable stack.
+Prividium™ delivers private execution, enterprise-grade access control, and Ethereum-level security in a single composable stack.
 It is the only solution available today that combines this level of confidentiality, auditability, and interoperability, without tradeoffs.
 
 ## Composable Privacy
 
-ZKsync Prividium operates as a **permissioned ZKsync Chain**, where transaction inputs, calldata,
+Prividium™ operates as a **permissioned ZKsync Chain**, where transaction inputs, calldata,
 and full state are stored off-chain in an operator-controlled database.
 Only cryptographic commitments—state roots and STARK-based proofs—are submitted to Ethereum, ensuring public verifiability without exposing private data.
 
 **Key capabilities:**
 
 - Keep all data inside your infrastructure (no transaction details on Ethereum)
-- Configure contract access policies through the Prividium Admin Dashboard, defining which functions are public, private, or role-restricted
+- Configure contract access policies through the Prividium™ Admin Dashboard, defining which functions are public, private, or role-restricted
 - Update access settings without redeploying contracts
 - Supply Merkle proofs or DB extracts for selective disclosure (e.g., audits, investigations)
 
@@ -28,7 +28,7 @@ Only cryptographic commitments—state roots and STARK-based proofs—are submit
 
 ## Fine-Grained Access Control
 
-All interactions with the chain are routed through a Proxy RPC that enforces access policies managed in the Prividium Permissioning System.
+All interactions with the chain are routed through a Proxy RPC that enforces access policies managed in the Prividium™ Permissioning System.
 Administrators configure roles, users, and permissions through the Admin Dashboard, which stores policies dynamically in the Permissions API.
 **Features:**
 
@@ -44,7 +44,7 @@ Client → Proxy RPC (permission validation) → Permissions API (policy check)
 
 ## Compliance & Audit Support
 
-Regulated entities require visibility, traceability, and selective access. ZKsync Prividium is designed with that in mind.
+Regulated entities require visibility, traceability, and selective access. Prividium™ is designed with that in mind.
 
 **Features:**
 
@@ -55,11 +55,11 @@ Regulated entities require visibility, traceability, and selective access. ZKsyn
 
 ## Ethereum-Grade Finality
 
-Every finalized Prividium batch is proven and posted to Ethereum using the ZKsync Gateway.
+Every finalized Prividium™ batch is proven and posted to Ethereum using the ZKsync Gateway.
 
 **Finalization Flow:**
 
-1. The ZKsync Prividium sequencer finalizes a batch of blocks
+1. The Prividium™ sequencer finalizes a batch of blocks
 2. The prover generates a STARK proof for the batch and posts it on ZKsync Gateway
 3. The relayer submits the state root and proof to Ethereum
 4. Once verified on-chain, the batch becomes immutable (unless Ethereum reorganizes)
@@ -79,5 +79,5 @@ Daily operations remain private, but interoperability is opt-in and cryptographi
 
 ### Next Step
 
-See [Configure Prividium](./config/authentication.md)
+See [Configure Prividium™](./config/authentication.md)
 for detailed steps on setting up authentication, users, roles, permissions, and selective disclosure.

content/10.zk-stack/35.prividium/05.architecture.md

@@ -1,34 +1,34 @@
 ---
 title: Architecture Overview
-description: Understand how ZKsync Prividium works under the hood.
+description: Understand how Prividium™ works under the hood.
 ---
 
-ZKsync Prividium is built on a **permissioned Validium chain** with integrated, role-based access control.
+Prividium™ is built on a **permissioned Validium chain** with integrated, role-based access control.
 It runs a private instance of the ZKsync Chain, complete with its own sequencer and prover, inside an organization’s infrastructure or cloud.
 All transaction data and state are stored off-chain in a secure database, ensuring privacy by design.
 
 A **Proxy RPC layer** serves as the single entry point to the network.
 All interactions — from users, enterprise applications, block explorers, or bridge operations — must pass through this proxy.
-It enforces fine-grained access rules using the **Prividium Permissioning System**,
+It enforces fine-grained access rules using the **Prividium™ Permissioning System**,
 ensuring that only authenticated and authorized requests reach the chain.
-By separating the public interface from internal blockchain components, Prividium prevents unauthorized access and safeguards sensitive data.
+By separating the public interface from internal blockchain components, Prividium™ prevents unauthorized access and safeguards sensitive data.
 
 State updates are finalized on Ethereum through the **ZKsync Gateway**, which receives the chain’s state roots and zero-knowledge proofs.
 This anchors the chain to Ethereum, providing L1-grade security and enabling interoperability with other ZKsync Chains.
 
 This architecture delivers **privacy, compliance, and auditability** at the L2 level while inheriting the trust and finality of Ethereum,
-making ZKsync Prividium ideal for institutional use cases such as trading, settlement, asset issuance, and compliance-sensitive workflows.
+making Prividium™ ideal for institutional use cases such as trading, settlement, asset issuance, and compliance-sensitive workflows.
 
 ::centered-container
-*Figure: High-level architecture of ZKsync Prividium.*
-![ZKsync Prividium architecture diagram](/images/zk-stack/prividium-architecture.png)
+*Figure: High-level architecture of Prividium™.*
+![Prividium™ architecture diagram](/images/zk-stack/prividium-architecture.png)
 ::
 
 ---
 
 ### Components
 
-ZKsync Prividium extends the ZK Stack architecture with dedicated modules for privacy, governance, and access control.
+Prividium™ extends the ZK Stack architecture with dedicated modules for privacy, governance, and access control.
 These components work together to provide secure, verifiable, and customizable network operations.
 
 - [**Permissioning System**](/zk-stack/prividium/permissions-overview):
@@ -68,5 +68,5 @@ not managed through static configuration files.
 
 ### Next Step
 
-See [Configure Prividium](./config/authentication.md)
+See [Configure Prividium™](./config/authentication.md)
 for instructions on setting up authentication, users, roles, permissions, and selective disclosure.

content/10.zk-stack/35.prividium/06.deployment.md

@@ -1,9 +1,9 @@
 ---
 title: Deployment Model
-description: Learn where to deploy each ZKsync Prividium component.
+description: Learn where to deploy each Prividium™ component.
 ---
 
-This page outlines the recommended deployment model for running a ZKsync Prividium chain in production.
+This page outlines the recommended deployment model for running a Prividium™ chain in production.
 Components are grouped by trust boundary and network tier, following enterprise best practices for security, scalability, and maintainability.
 
 ### DMZ / API Gateway Tier
@@ -65,9 +65,9 @@ Unauthorized requests are filtered before reaching internal systems.
 - **Outbound-only proof posting:** The relayer submits proofs to ZKsync Gateway without opening any inbound ports.
 - **Data-at-rest controls:** Databases and blob stores are isolated and regularly backed up to support compliance and disaster recovery.
 
-## Running a ZKsync Prividium Chain
+## Running a **Prividium™** Chain
 
-To run a local ZKsync Prividium chain, go through the [Run ZKsync Prividium Chain](/zk-stack/prividium/run-prividium-chain) page.
+To run a local Prividium™ chain, go through the [Run Prividium™ Chain](/zk-stack/prividium/run-prividium-chain) page.
 
-For a full example application running on ZKsync Prividium,
+For a full example application running on Prividium™,
 check out this [example escrow application](https://github.com/JackHamer09/interop-escrow-double-zero/tree/single-chain-demo).

content/10.zk-stack/35.prividium/10.run-prividium-chain.md

@@ -1,17 +1,17 @@
 ---
-title: Run ZKsync Prividium Chain
-description: Get started running a local ZKsync Prividium chain with ZKsync Stack.
+title: Run Prividium™ Chain
+description: Get started running a local Prividium™ chain with ZK Stack.
 ---
 
 ::callout{icon="i-heroicons-light-bulb"}
 This guide is not yet updated to use the latest [Permissions API](/zk-stack/prividium/permissions-overview) or Atlas upgrade.
 ::
 
-This guide shows you how to use the ZKsync Stack CLI to run local a ZKsync Prividium chain.
+This guide shows you how to use the ZK Stack CLI to run local a Prividium™ chain.
 By following this guide you will:
 
 - Set up a local **Elastic Network ecosystem**
-- Create a **ZKsync Prividium chain**
+- Create a **Prividium™ chain**
 - **Deploy a smart contract** to your chain
 - **Test interacting** with your contract
 - Run a local **block explorer**
@@ -68,5 +68,5 @@ The next step is to set up the block explorer and contract verifier service.
 
 ## Next Steps
 
-To see a full example application running on ZKsync Prividium,
+To see a full example application running on Prividium™,
 check out this [example escrow application](https://github.com/JackHamer09/interop-escrow-double-zero/tree/single-chain-demo).

content/10.zk-stack/35.prividium/20.proxy.md

@@ -1,11 +1,11 @@
 ---
 title: Proxy RPC API
-description: Learn about the Prividium Proxy RPC API.
+description: Learn about the Prividium™ Proxy RPC API.
 ---
 
 In a standard rollup, there is a standard RPC API that provides full access
 to transaction data for users.
-With Prividium, the Proxy RPC is an additional layer in between end users and the chain's standard RPC API.
+With Prividium™, the Proxy RPC is an additional layer in between end users and the chain's standard RPC API.
 
 The purpose of the Proxy RPC API is to filter blockchain transactions and wallet interactions.
 It serves as an intermediary between web apps/wallets
@@ -35,16 +35,16 @@ L1-L2 transactions, also known as forced transactions, originate from Ethereum (
 In a public chain, this mechanism helps ensure censorship resistance for users,
 and allows them to retain full control of their assets.
 
-For ZKsync Prividium chains though,
+For Prividium™ chains though,
 forced transactions can also be a vector for deploying arbitrary contracts,
 performing arbitrary contract writes,
 and leaking data through blind attacks.
 The ZKsync protocol contracts have a way to
 [request arbitrary transaction](https://github.com/matter-labs/era-contracts/blob/29f9ff4bbe12dc133c852f81acd70e2b4139d6b2/l1-contracts/contracts/bridgehub/Bridgehub.sol#L216)
 to be executed from Ethereum,
-and it can be used to bypass the privacy configuration of a ZKsync Prividium chain.
+and it can be used to bypass the privacy configuration of a Prividium™ chain.
 
-Currently **L1-L2 transactions are not automatically disabled** in ZKsync Prividium chains.
-ZKsync Prividium chain operators can be protected against malicious use of these forced transactions by implementing [transaction filtering](/zk-stack/customizations/transaction-filtering).
+Currently **L1-L2 transactions are not automatically disabled** in Prividium™ chains.
+Prividium™ chain operators can be protected against malicious use of these forced transactions by implementing [transaction filtering](/zk-stack/customizations/transaction-filtering).
 Note that for users, this means that the chain has the ability to censor transactions.
 It is the responsibility of the chain operator to decide how to implement this filtering.

content/10.zk-stack/35.prividium/30.permissions-overview.md

@@ -1,14 +1,14 @@
 ---
 title: Permissions Overview
-description: Learn about the Prividium Permissioning API and Selective Disclosure.
+description: Learn about the Prividium™ Permissioning API and Selective Disclosure.
 ---
 
 ::callout{icon="i-heroicons-light-bulb"}
 The permissioning and selective disclosure systems are not yet publicly available.
 This documentation serves as a preview.
 ::
 
-Prividium offers flexible and customizable ways for chain operators to have granular control over access to reading onchain data or calling contracts.
+Prividium™ offers flexible and customizable ways for chain operators to have granular control over access to reading onchain data or calling contracts.
 There are two systems used to manage this control: the [permissions API](#permissions-api), and [selective disclosure](#selective-disclosure).
 
 ## Permissions API
@@ -27,7 +27,7 @@ For unauthenticated access, you can use the [selective disclosure](#selective-di
 ## Admin Panel
 
 To configure access to different smart contracts on your chain,
-ZKsync Prividium offers an admin panel.
+Prividium™ offers an admin panel.
 The admin panel provides a user interface for permission management where admins can configure data access rules and monitor system access patterns.
 
 Admins can view and edit [users](#users), [roles](#roles), and [contract permissions](#contract-permissions).
@@ -76,14 +76,14 @@ Users can login via an identity provider and add/manage wallets associated with
 The registration flow looks like this:
 
 1. On first login, the user authenticates with the identity provider in the User Panel.
-1. The user receives a Prividium session, and is prompted to connect their wallet.
+1. The user receives a Prividium™ session, and is prompted to connect their wallet.
 1. The User Panel issues an EIP-712 challenge, which the user signs to prove they control the wallet.
-1. The Prividium Proxy API saves the user-address mapping in the Permissions API,
+1. The Prividium™ Proxy API saves the user-address mapping in the Permissions API,
 enabling all future reads/writes to be authorized by both the identity provider and linked wallet address.
 
-### Login with Prividium
+### Login with **Prividium™**
 
-After initial registration, the user can login to other applications using the [Prividium SDK](/zk-stack/prividium/sdk).
+After initial registration, the user can login to other applications using the [Prividium™ SDK](/zk-stack/prividium/sdk).
 The SDK allows the user to connect either with the identity provider or the wallet they have previously linked with their account.
 
 ### Calling Contracts

content/10.zk-stack/35.prividium/36.config/10.authentication.md

@@ -1,10 +1,10 @@
 ---
 title: Configure Auth
-description: Setting up authentication for your Prividium chain.
+description: Setting up authentication for your Prividium™ chain.
 ---
 
-Authentication controls how users and administrators log in to Prividium and access the permissioned network.
-Prividium supports two authentication methods:
+Authentication controls how users and administrators log in to Prividium™ and access the permissioned network.
+Prividium™ supports two authentication methods:
 
 - **Okta (OIDC)** for enterprise single sign-on
 - **Crypto-native Sign-in With Ethereum (SIWE)** for wallet-based access