Privacy Policy — Narrow L1

Narrow Wallet is a non-custodial cryptocurrency wallet. We do not hold your private keys, seed phrases, or crypto assets on your behalf. We are not a bank, broker, exchange, or regulated financial institution. On-chain transactions you authorize are public and generally irreversible.

1. Introduction

This Privacy Policy explains how Narrow (“Narrow,” “we,” “us,” or “our”) handles information when you use Narrow Wallet, visit our websites, interact with Narrow L1 network services (including RPC and explorer), or otherwise contact us.

Narrow builds software and infrastructure for the Narrow L1 blockchain — an object-centric Layer 1 aimed at game economies, player ownership, and studio-issued assets — including wallet experiences, network APIs, and public explorers under the narrowl1.com domain family.

By installing or using Narrow Wallet, visiting our websites, or interacting with our network services, you acknowledge this Policy. If you do not agree, do not use the app or related services.

2. Scope

This Policy applies to:

The Narrow Wallet mobile application for Android, package name com.narrowl1.wallet (a Capacitor app that loads the wallet interface in a WebView), and any iOS build we distribute under the same product name
The wallet web interface at https://testwallet.narrowl1.com
The marketing, documentation, whitepaper, and legal pages at https://narrowl1.com
Related Narrow L1 services such as network RPC / node APIs, bridge-related endpoints, and the public explorer (for example https://testexplorer.narrowl1.com)

This Policy does not cover third-party websites, wallets, exchanges, RPC providers, game studios, or apps that you access through links or by pasting addresses outside our control. Their privacy practices are governed by their own policies.

Public community channels (including Telegram) are operated in part on third-party platforms; see Section 9.

3. Who we are / roles

For personal data processed through our websites, support email, and Narrow-operated hosting and RPC infrastructure, Narrow is the organization responsible for deciding how that data is processed (the “controller” under GDPR-style laws, where those laws apply).

Narrow L1 is a public blockchain. Once you broadcast a transaction, copies of ledger data may be held by independent node operators, indexers, and explorers that we do not control. Those parties are separate controllers for the copies they keep.

4. Information we collect (and what we don’t)

4.1 Information you provide voluntarily

Ordinary use of Narrow Wallet does not require creating a Narrow account or registering with us. You generate or import a wallet locally on your device.

If you contact us (for example by email at [email protected]), we receive the content of your message and any contact details you include (such as your email address, Discord or Telegram handle, or wallet address you choose to share). We use that information to respond and to manage support correspondence.

4.2 Information collected automatically (technical / network data)

When the app or website connects to Narrow infrastructure over HTTPS (or HTTP where a deployment is not TLS-terminated), our servers and standard hosting / reverse-proxy layers may process ordinary technical data, including:

IP address
Date and time of the request
Requested URL / API endpoint and HTTP method
User-Agent and similar device or browser headers
Referrer URL (if sent by your browser)
Approximate network location derived from IP (city / region level, if provided by hosting or CDN logs)
Diagnostic or error information if a request fails
Rate-limit and abuse-prevention counters associated with IP or similar keys

This data is generated as a normal part of operating web and API services. We do not use it to build advertising profiles or to sell access to your identity.

4.3 Information processed on your device (local)

The wallet may store data locally on your device so the product can function, including encrypted wallet key material, addresses, preferences, UI state, and cached network responses. See Section 6. Local device storage is controlled by you and your device OS; we do not remotely extract private keys or seed phrases from your device.

4.4 What we do not intentionally collect

We do not intentionally collect or require any of the following for ordinary wallet use:

Legal name, government ID, or KYC documents (we are non-custodial and do not operate an identity-verified exchange)
Phone contacts, SMS contents, or call logs
Precise GPS location for advertising or tracking
Photos, microphone, or camera access for marketing
Your seed phrase or private keys transmitted to Narrow for storage or recovery
Payment card numbers for Narrow Wallet itself (we do not process card payments for wallet custody)

If a future feature requests optional permissions (for example camera for scanning a QR code), that use will be limited to the stated in-app purpose and will remain under your control on the device.

5. Blockchain / on-chain data

Narrow L1 is a public blockchain network. Information recorded on-chain is public by nature and may be copied, indexed, and displayed by anyone running a node, explorer, or indexer — including third parties unrelated to Narrow.

On-chain and network-visible data typically includes:

Wallet / account addresses
Balances and asset holdings associated with those addresses (including NAR and NR20 coin objects)
Transaction history, amounts, fees (gas), timestamps, and related metadata
Package, escrow, offload, bridge, and other program interaction data you choose to submit

When you broadcast a transaction through Narrow Wallet, that transaction is submitted to the Narrow L1 network (and, if you use bridge features, may also involve another network such as Ethereum Sepolia). Once confirmed, transactions are generally irreversible. Narrow cannot “delete” public ledger history the way a traditional database operator might delete a row.

Blockchain addresses are pseudonymous. Do not treat them as private. If you link an address to your real-world identity (for example in a support email, social media, Telegram, or a public forum), that linkage may become known to others.

6. Wallet keys & local storage

Narrow Wallet is non-custodial. Private keys and recovery phrases (seed phrases / mnemonics) are generated and stored on your device (for example in local storage or other app storage exposed to the WebView), not on Narrow’s servers.

We do not have access to your private keys or seed phrases and cannot recover them for you.
If you lose your device, uninstall the app without a backup, or lose your recovery phrase, your assets may be permanently inaccessible.
You are solely responsible for safeguarding your seed phrase, private keys, device unlock credentials, and any backups you create.
Never share your seed phrase with anyone — including anyone claiming to be Narrow support. Legitimate Narrow support will never ask for your seed phrase.
Where the wallet signs transactions locally (for example plain NAR sends via WebCrypto Ed25519), the raw secret key is intended to remain on-device for that path. Other advanced flows may depend on node configuration; prefer local signing whenever available.

The Android app is built with Capacitor and loads the wallet UI in a WebView from Narrow’s wallet service (currently https://testwallet.narrowl1.com). Local key material remains subject to the security of your device, OS, and any backups you enable.

7. RPC, explorer, faucet & bridge

7.1 RPC and APIs

When the wallet or other clients call Narrow RPC endpoints (health, account queries, broadcast, faucet, bridge, package, escrow, NR20, and similar), operators of those nodes process the technical request data described in Section 4.2, plus the content of the API call you send (for example a signed transaction payload, a recipient address, or an asset symbol). That content may become part of public chain state once included in a block.

Nodes may apply rate limits, optional RPC tokens for privileged write paths, and abuse-prevention controls. Those controls process IP and request metadata.

7.2 Explorer

The public explorer displays blockchain data that is already public. Viewing pages may generate ordinary web server logs. Search queries you type into an explorer UI may appear in access logs (for example address or transaction digests in URL parameters).

7.3 Faucet

If you use a public faucet, the faucet request associates your wallet address with mint activity (subject to lifetime and rate limits). That association is visible on-chain and may be retained in node state for cap enforcement.

7.4 Bridge / Sepolia

If you use bridge features between Narrow and another network (for example Ethereum Sepolia), additional parties may process data:

Narrow RPC and bridge-related endpoints
Smart contracts and events on the foreign chain
Relayer or issuer infrastructure that observes deposits/burns and submits mints/releases
Foreign-chain RPC providers you or we configure (Infura, Alchemy, public RPCs, etc.)

Bridge designs may be trusted-relayer or otherwise operator-dependent on testnet. Foreign-chain transactions and Narrow mint/burn records are public. Fees (for example ETH deposit fees or NAR bridge fees) are recorded according to protocol and contract rules.

8. Cookies & similar technologies

Our marketing site and documentation pages are primarily static. We do not currently use third-party advertising cookies or behavioral ad pixels on narrowl1.com.

We may use:

Strictly necessary / functional storage — for example local storage or session storage in the wallet UI to keep encrypted vault material, preferences, or UI state
Server-side logs — not cookies, but similar operational telemetry as described above
Font / CDN requests — loading fonts (for example Google Fonts) may cause your browser to contact a CDN, which receives standard request metadata under that provider’s policy

If we introduce analytics cookies or similar technologies in the future, we will update this Policy and, where required by law, provide notice or choice.

You can clear cookies and site data through your browser or OS settings. Clearing wallet site data can delete local keys if you have not backed up your seed phrase.

9. Telegram & community channels

Narrow maintains community presence on Telegram, including:

Channel: https://t.me/narrowchain_official
Group: https://t.me/narrowchain_group

Telegram is a third-party service. If you join or message those channels, Telegram (and other members of public groups) may process your Telegram username, profile, messages, and metadata under Telegram’s own terms and privacy policy. Narrow moderators may see messages you post in Narrow-operated chats and may retain screenshots or exports as needed for moderation, security, or legal compliance.

Do not post seed phrases, private keys, or sensitive personal data in Telegram.

10. How we use information

We use information described in this Policy to:

Operate, maintain, and improve Narrow Wallet and Narrow L1 network services
Process RPC, API, wallet UI, explorer, faucet, and bridge-related requests you initiate
Diagnose outages, abuse, fraud, security incidents, and performance issues
Enforce rate limits, caps, and network integrity controls
Respond to support requests you send us
Communicate service notices when you have contacted us or where we have another lawful basis
Comply with applicable law and enforce our terms or policies where required
Protect the integrity and availability of the network and our infrastructure

We do not use personal information to serve third-party behavioral advertising inside Narrow Wallet, and we do not sell personal information (see Section 13).

11. Legal bases (EEA / UK and similar)

Where data-protection laws require a legal basis, we typically rely on:

Performance of a contract / requested service — providing wallet UI, RPC, explorer, and related features you ask to use
Legitimate interests — securing infrastructure, preventing abuse, improving reliability, and understanding aggregate traffic patterns in ways that do not override your rights
Consent — where we ask for it (for example optional communications), and you may withdraw consent for that processing
Legal obligation — when we must retain or disclose information to comply with law

12. Third-party services

To run the wallet and network, we rely on infrastructure and, in some cases, external network endpoints. Categories include:

Narrow L1 RPC nodes and related APIs — used to read chain state and submit transactions you authorize
Wallet UI / API hosting — the interface loaded by the app and browser (including testwallet.narrowl1.com)
Website hosting — servers that serve narrowl1.com and related static content (for example Contabo or similar VPS / hosting)
Reverse proxies / TLS termination — such as Caddy or nginx in front of public endpoints
Optional bridge / Ethereum network RPCs — if you use bridge features, components may communicate with Sepolia (or other) RPC endpoints operated by Narrow or by third parties
Email delivery — messages to [email protected] may be processed by our email provider (for example Cloudflare Email Routing or a similar mailbox / forwarding service)
Fonts / static assets — Google Fonts or similar CDNs may receive standard request metadata when your browser fetches assets
App stores / OS vendors — Google Play, Apple, and device OS vendors process install and update data under their policies
Telegram — see Section 9

We select providers we believe are reasonably necessary to operate the service. We do not authorize them to use your information for their own unrelated advertising based on Narrow Wallet usage, except as stated in their own independent policies for traffic they receive directly (for example a public RPC you configure or a CDN serving a font file).

We do not sell personal data. We do not rent or trade email lists or identity profiles derived from Narrow Wallet use.

We may share or disclose information only in these limited situations:

Service providers who process technical or support data on our behalf (hosting, email, infrastructure) under instructions consistent with this Policy
Legal requirements — if we are compelled by valid law, regulation, legal process, or governmental request
Safety and security — to protect users, the public, Narrow, or the network against fraud, abuse, or imminent harm, where we believe disclosure is reasonably necessary
Business transfers — if Narrow is involved in a merger, acquisition, reorganization, or asset sale, information described in this Policy may transfer as part of that transaction, subject to appropriate confidentiality and this Policy’s spirit
Public blockchain data — on-chain data is inherently public and may be accessed by anyone; that is not a “sale” by Narrow but a property of public ledgers
With your direction — for example if you ask us to coordinate with a studio or partner and you provide information for that purpose

14. International transfers

Narrow infrastructure and support may be located in, or accessible from, countries other than where you live. Technical logs, support email, and hosting may therefore be processed in multiple jurisdictions.

Where personal data is transferred internationally, we take steps we consider appropriate for the nature of the data (primarily technical logs and voluntary support correspondence) and the services involved. By using the Services, you understand that your information may be processed outside your home country, which may have different data-protection laws.

15. Data retention

Local wallet data remains on your device until you delete it, clear app or site storage, or uninstall the app (subject to any backups you control).
Server / access logs are retained only as long as reasonably needed for operations, security, abuse prevention, and legal compliance, then deleted or aggregated. Retention periods may vary by system.
Support email is retained as long as needed to handle your request and for ordinary business record-keeping.
Faucet / cap state may persist in node or checkpoint storage for as long as needed to enforce lifetime caps.
On-chain data persists according to the rules of the relevant blockchain network and is not controlled by a traditional “delete account” workflow.
Moderation records from community channels may be kept as long as needed for safety and dispute handling.

16. Security

We implement technical and organizational measures designed to protect our websites, APIs, and infrastructure — including HTTPS for public web traffic where applicable, access controls for administrative systems, rate limiting, and operational practices aimed at reducing unauthorized access.

No method of transmission or storage is completely secure. Non-custodial wallets depend heavily on your device security and key hygiene. You should:

Keep your device OS and app updated
Use a strong device lock (PIN, biometric, or equivalent)
Store your seed phrase offline in a safe place; never screenshot it or store it in plain cloud notes
Verify URLs and avoid phishing sites that impersonate Narrow
Understand that malware, physical device access, or social engineering can compromise local keys

17. Children’s privacy

Narrow Wallet and related services are intended for users who are 18 years of age or older. We do not knowingly collect personal information from children under 18. If you believe a child has provided us personal information (for example via a support email), contact us at [email protected] and we will take reasonable steps to delete it from our systems where applicable.

18. Your rights

Depending on where you live, you may have rights regarding personal information we hold about you — such as the right to request access, correction, deletion, or restriction of processing; to object to certain processing; to data portability; or to withdraw consent where processing is consent-based — subject to legal exceptions.

Important practical limits for a non-custodial crypto wallet:

We cannot retrieve, reset, or delete your seed phrase or private keys because we do not possess them.
We cannot erase public blockchain history associated with addresses you used.
You can stop local collection of new technical traffic by uninstalling the app and discontinuing use of our websites and APIs.
For support correspondence or log-related requests that we can reasonably fulfill, email [email protected].

We may need to verify that a request is legitimate before acting on it. If your request relates only to on-chain data, we may explain that the ledger itself is outside a standard erasure workflow. You may also lodge a complaint with a supervisory authority in your country if applicable.

19. Region-specific notes (including California)

If you are a California resident, you may have rights under the CCPA/CPRA to know, delete, and correct certain personal information, and to opt out of “sale” or “sharing” for cross-context behavioral advertising. We do not sell personal information and do not share it for cross-context behavioral advertising as those terms are commonly understood. To exercise applicable rights, contact [email protected]. We will not discriminate against you for exercising privacy rights.

Categories of personal information we may process are limited primarily to identifiers and internet activity (IP, device/browser data, support email content) as described in this Policy, plus public blockchain identifiers you choose to use.

20. Changes to this policy

We may update this Privacy Policy from time to time — for example when we add features, change infrastructure, or respond to legal requirements. When we do, we will revise the effective date at the top of this page.

Material changes may also be highlighted on https://narrowl1.com or within the wallet interface when practical. Continued use of Narrow Wallet or related services after an update means you accept the revised Policy. If you do not agree, stop using the services and uninstall the app.

21. Contact

For privacy questions, support, or data-related requests:

Website: https://narrowl1.com
Email: [email protected]
Privacy Policy: https://narrowl1.com/privacy.html
Whitepaper: https://narrowl1.com/whitepaper.html

Wallet: https://testwallet.narrowl1.com
Explorer: https://testexplorer.narrowl1.com
Telegram channel: @narrowchain_official · Group: @narrowchain_group