Senza Privacy Policy

Last updated: March 11, 2026

Overview

Senza is a Chrome extension wallet for Ethereum-compatible confidential token operations. Senza lets users manage wallet accounts, connect to decentralized applications, sign messages, and submit blockchain transactions involving confidential token workflows.

This policy describes what Senza stores, what it accesses, and what it does not collect.

What Senza Does

Senza provides:

• local wallet creation and import
• encrypted local key storage
• dApp connection and approval flows
• Ethereum message signing and transaction submission
• confidential token operations using Zama FHEVM-compatible flows

Data Senza Stores

Senza stores data locally in the browser extension storage area on the user’s device.

This may include:

• encrypted wallet vault data
• imported or generated account metadata
• selected network and RPC configuration
• dApp connection permissions
• pending request state
• extension settings such as auto-lock preferences

Private keys are intended to be stored in encrypted form in local extension storage, not in plaintext.

Data Senza Accesses

To function as a browser wallet, Senza may access:

• website origin information for sites requesting wallet access
• wallet request payloads from websites the user interacts with
• Ethereum addresses needed for connection and signing flows
• transaction data submitted for user approval

Senza also communicates with user-selected or app-configured RPC endpoints and blockchain indexing/query endpoints as needed for wallet functionality.

What Senza Does Not Sell

Senza does not sell personal data.

What Senza Does Not Intend To Collect As A Hosted Service

Senza is designed as a local-first extension wallet. It is not intended to collect or centrally host user private keys on a Senza-operated backend.

At the current project stage, Senza does not include a dedicated hosted backend for account custody.

Website Access And Permissions

Senza injects a provider into web pages so decentralized applications can discover and connect to the wallet. This requires broad page access patterns commonly used by wallet extensions.

Senza uses page access to:

• expose the wallet provider to compatible dApps
• receive connection, signing, and transaction requests
• show approval prompts to the user

Senza is not intended to read unrelated page content except as needed to support wallet connection behavior.

Data Sharing

Senza may share data only in the following ways as part of normal wallet operation:

• with blockchain nodes / RPC providers to read chain state or broadcast transactions
• with connected dApps when the user explicitly approves account access or signs/submits data
• with blockchain indexers or query services used for wallet activity display

Because blockchain networks are public or semi-public systems, submitted transactions, signatures, addresses, and related metadata may become visible to network participants or infrastructure providers.

Security

Senza is designed to encrypt wallet secrets at rest and require explicit user approval for sensitive operations. However:

• browser extensions carry inherent browser-platform risk
• blockchain transactions are irreversible
• the project may still be under active development and not yet formally audited

Users should treat Senza as experimental software unless and until a formal production-readiness statement is made.

User Choices

Users can:

• lock the wallet
• revoke dApp permissions
• remove the extension
• clear browser extension storage
• choose whether to connect accounts to sites

Removing the extension or clearing browser storage may permanently remove locally stored wallet data unless the user has backed up recovery material.

Children

Senza is not designed for use by children.

Changes

This policy may be updated as the product evolves. The latest version should be published at the public URL used in the Chrome Web Store listing.

Contact

Add your support or contact email before publishing.