1. Controller
The Nullark operator controls processing performed for the hosted Service. Never include seed phrases, private keys, recovery notes, note secrets, wallet unlock signatures, or other spendable material in a request. We may ask for limited information needed to verify a request, but we will never ask for a wallet secret.2. Data handled by the Service
Website and infrastructure data
When you load Nullark, hosting and security infrastructure may process:- network identifiers such as IP address and approximate region;
- request, response, browser, device, and language information;
- security and abuse-prevention signals.
Wallet and RPC data
When you connect a wallet or query a network, the browser, wallet provider, and configured RPC provider may handle:- your public wallet address and selected network;
- blockchain queries, transaction requests, and transaction status;
- wallet approval or rejection results.
Relayer request data
When you choose relayer submission, the relayer receives the information needed to validate and submit the transaction, including:- the transaction request and public data required for validation and submission;
- network and request metadata used for reliability, security, and abuse prevention;
- submission status and resulting public transaction identifier.
Data kept in your browser
Normal hosted flows generate proofs and handle recovery material in your browser. Browser storage may contain:- private-balance and recovery data needed to recognize or use funds;
- local transaction and recovery status;
- interface preferences and the accepted legal-document version.
Public blockchain data
Transactions sent through Nullark become public according to the network’s rules. Public data may include submitter and recipient addresses, amounts or denominations, timing, contract interactions, fees, transaction status, and other protocol-required public data. Public ledger data may be copied, indexed, inferred from, and retained by unrelated parties. Independently maintained blockchain records sit outside Nullark’s erasure or correction capability.3. Data Nullark avoids collecting
Hosted application code contains no account-registration system, advertising pixel, behavioral analytics SDK, or marketing tracker. Nullark sells no personal information and performs no sharing for cross-context behavioral advertising. The application has no need for your seed phrase or private key. Keep them out of every Nullark field, support request, issue, and message. Cloudflare or another infrastructure provider may use essential security technologies under its own policy. Nullark application code sets no advertising or analytics cookies.4. Why data is processed
Data is processed to:- deliver the website and documentation;
- support wallet, network, contract, recovery, and relayer functions you request;
- process and reconcile relayer submissions;
- prevent fraud, abuse, attacks, and unintended duplicate activity;
- diagnose failures, maintain availability, and protect users and infrastructure;
- comply with law and establish, exercise, or defend legal claims.
5. Sharing and recipients
Data may be processed by:- Cloudflare for hosting, delivery, security, and operated service infrastructure;
- your selected wallet provider;
- configured blockchain RPC providers and network participants;
- the Nullark relayer when you choose relayer submission;
- public blockchains, explorers, indexers, and anyone reading public network data;
- professional advisers, authorities, or counterparties where lawfully required or needed to protect rights and security;
- a new operator during a merger, reorganization, financing, or transfer, subject to appropriate safeguards.
6. Retention
Retention depends on where data lives:- Browser data: remains until you clear it, the application replaces it, or browser policy removes it.
- Legal acknowledgement: stores the current policy version locally until cleared or superseded.
- Relayer, operational, and security data: retained only as long as reasonably needed for transaction handling, reliability, abuse prevention, dispute handling, legal obligations, and provider requirements.
- Public blockchain data: retained according to the network and independent copies; it may be effectively permanent.

