Privacy Policy.

Obsidio Wallet browser extension · Last updated: 15 October 2026 · Effective for Chrome Web Store listing

Non-custodial. Obsidio Wallet does not hold, custody, transmit, or have access to your private keys or seed material on our servers. Keys are generated and stored locally in your browser using Chrome extension storage. We cannot recover lost keys or reverse transactions for you.

1. Who we are

This policy covers the Obsidio Wallet Chrome extension (MV3), a self-custody wallet for the Obsidio network. Contact: hello@obsidio.network · Site: https://obsidio.network

2. Single purpose

The extension’s sole purpose is to provide a non-custodial cryptocurrency wallet for Obsidio: create/import accounts, view balances, sign and submit transactions, and expose a page provider (window.obsidio) so websites can request wallet actions with your approval.

3. Data we process

Stored only on your device (Chrome storage):

Wallet public addresses and account metadata you create
Encrypted or locally held key material required to sign (never uploaded to Obsidio servers as a recovery service)
UI preferences (e.g. selected account)

Sent over the network (HTTPS) only as needed for wallet features:

Public blockchain RPC requests to https://obsidio.network (balances, nonces, transaction broadcast, public chain status)
Signed transactions you explicitly approve — broadcast to the Obsidio network

We do not collect: name, email, phone, government ID, browsing history for advertising, payment card data, or analytics SDKs that track you across sites.

4. How we use data

To show balances and account state
To sign and broadcast transactions you approve
To inject the wallet provider so Obsidio dApps can connect

We do not sell personal data. We do not use wallet data for advertising. Limited Use: data is used only to provide or improve the disclosed wallet purpose.

5. Permissions (why they exist)

storage — save wallet accounts and preferences locally
Host access to obsidio.network — call Obsidio JSON-RPC over HTTPS
Content script on HTTPS pages — inject window.obsidio so sites can request accounts/signatures (standard wallet pattern; you approve each sensitive action in the extension UI)

6. Security

Manifest V3; no remote executable code — WASM crypto ships inside the extension package
RPC traffic uses HTTPS
Private keys never leave your device except as signatures embedded in transactions you approve

You are responsible for backing up recovery material. If you lose it, funds cannot be recovered by Obsidio.

7. Third parties

Blockchain data you broadcast is public by design (addresses, amounts, transaction hashes). We do not share your private keys with third parties. Chrome may process installs via Google’s Web Store infrastructure under Google’s terms.

8. Children

The extension is not directed at children under 13 / under the digital age of consent in your jurisdiction.

9. Changes

We may update this policy; the “Last updated” date will change. Material changes will be reflected on this page.

10. Contact

Questions: hello@obsidio.network