Local by default.Explicit when connected.

01 / Local processing

Your working data stays in the browser.

Byteplane parses pasted ABIs, method arguments, transaction drafts, and imported unsigned envelopes in the active browser session. The current release does not operate an application backend that persists this content. Byteplane does not intentionally receive or maintain a hosted account record of your contract workspace.

Work in an active page can still be exposed through your device, browser extensions, clipboard, downloaded files, screen sharing, or any service you independently use to transmit it. Review inputs and exported artifacts before sharing them.

02 / Browser storage

Small state, stored locally.

Byteplane uses localStorage for a local address watchlist, interface preferences, and participation-point status. This storage belongs to the browser profile on your device. It is not a transferable asset, server backup, real-time monitoring record, or proof of ownership.

• Clearing site data may permanently remove the local watchlist and points state.
• A different browser or device will not automatically have the same state.
• Byteplane does not promise recovery of locally stored or exported material.
• Downloaded envelope files remain wherever you or your device store them.

03 / Wallet connection

Connection is read-only context.

Byteplane requests wallet access only after you press Connect Wallet. A successful connection allows the interface to display the selected public address and active network context.

Your wallet software may process connection and device information under its own privacy terms. Public addresses and completed public transactions can be observed and associated by third parties.

04 / Provider requests

Reads leave the page only when requested.

When you choose to run a read, estimate gas, inspect a transaction status, or connect a wallet, your browser communicates with the selected provider. That provider may receive your IP address, public wallet address, network context, target contract, call data, and request timing. Its own privacy policy governs that processing.

05 / Payments and public actions

Separate approval, public metadata.

The optional 0.37 BOT upgrade is separate from wallet connection and points activation. It requires an independent review showing the recipient, amount, and active network, followed by confirmation in the wallet. The control remains unavailable until a verified recipient is publicly available.

If you approve a payment or another transaction, public systems may retain the sending address, receiving address, value, call data, fees, status, and timing indefinitely. Byteplane cannot erase or make a confirmed public record private.

06 / Site delivery

Standard infrastructure logs may exist.

The hosting and security services that deliver Byteplane may process standard request metadata such as IP address, user agent, requested path, timestamp, error details, and abuse-prevention signals. This information may be handled under the infrastructure provider's terms for delivery, security, diagnostics, and reliability.

The current product does not intentionally add advertising trackers to the contract workflow. Third-party font delivery, wallet software, and data providers may still receive ordinary connection metadata when the browser contacts them.

07 / Your controls

Choose the smallest necessary action.

• Inspect an ABI and build an envelope without connecting a wallet.
• Reject a provider or wallet request you do not understand.
• Review addresses, values, call data, and exported files before sharing or confirming.
• Remove browser-local state through your browser settings.
• Avoid public submission when a local draft or verification is sufficient.

This notice may change when the product's data handling changes. The update date above identifies the current public version.