OMIT

YOUR DATA / CURRENT RELEASE

Privacy &
local data.

What stays in your browser, what a network request shares, and how to remove local data.

Updated 14 October 2026 · Web app and companion v0.3

01

Local Solana keys

The app's optional Local wallet card creates an Ed25519 key in your browser only after you choose to create one. Its saved private key is encrypted with your password in local browser storage. Creation, unlocking and recovery do not send the key, password or recovery code to OMIT's server.

The OMIT1 recovery code contains the unencrypted key. Store it offline. The app never requests another wallet's seed phrase. Clearing browser data removes the saved key; you need the complete recovery code to restore it. After unlocking, the card can sign the SDK key-derivation message and allowlisted devnet operations only after a separate approval. Confidential viewing keys are derived and used in the browser; neither those keys nor the derivation signature are sent to the relay.

02

Public wallet checks

When you choose to inspect a wallet through the OMIT network service, your selected network, public wallet address and requested method are sent to our server. The server queries the selected Solana RPC provider and returns public balances or recent transaction signatures.

In the browser companion, choosing Direct public RPC sends the query to that provider directly. It does not route that query through OMIT's network service. Public wallet addresses and onchain transactions can reveal financial activity; a read-only query does not make them private.

03

The browser companion

The read-only companion stores a public address, network, connection route and display theme in local extension storage. It requests storage access and access to the OMIT service and the two public Solana RPC hosts. It has no content scripts, transaction-signing capability or access to the web app's private key storage.

Checks require an explicit action and route-specific consent. Opening the app visits the configured OMIT website. The companion does not read your browsing history or collect page contents.

04

Transactions and network metadata

For a confidential devnet operation, the app sends the signed transaction, public owner, test mint, expiry and a signed relay authorization to the devnet service. It also sends ephemeral proof-context authorizations when needed. The service validates the request, adds its own devnet fee signature and submits the transaction. The account index reads public addresses, encrypted account data and transaction receipts from Solana. Decrypted balances stay in the browser.

OMIT is hosted on Vercel. Website requests and RPC queries can expose IP addresses, request times and HTTP metadata to hosting and network providers. The RPC handler omits wallet addresses and request parameters from its own error messages, but infrastructure may maintain operational logs. This release makes no guarantee that network requests are unlogged.

No advertising SDK or analytics tracker is included in this release. External wallets and Solana Explorer links operate under their own data practices. The default RPC hosts are api.devnet.solana.com and api.mainnet-beta.solana.com; the companion's OMIT route is omit-solana.vercel.app.

05

Remove or retain your data

You control local browser and extension storage. Save and verify your recovery code before clearing the web app's site data. Removing the companion or its local data clears its saved public address and settings; it does not remove onchain transactions or the separately stored web app wallet.

The web app stores a public pending-transaction record locally when a submission begins: owner, test mint, sponsor, operation, message hashes, blockhash window, time and any known transaction signature. It contains no private keys or transaction bytes. It survives locking and reload so an uncertain outcome can be checked before another write, and is removed after the exact outcome is established. Clearing it manually can lose this reconciliation history.

Public blockchain records cannot be deleted by OMIT. A local recovery code restores its Solana key. After approval, that key can derive the same confidential viewing keys and decrypt its existing devnet account. Public and encrypted onchain account data remain on Solana.

06

Contact and release status

For support or privacy enquiries, contact omitpriv@gmail.com. Never send a password, seed phrase, private key or recovery code by email.

Capabilities and limits are recorded in the release documentation. An extension countdown is a schedule, and does not mean a Chrome Web Store review has been completed.

Release evidence ↗