Privacy Policy

ZapArc

Last updated: August 31, 2026

Overview

ZapArc is a self-custodial Bitcoin and Lightning wallet available as a mobile application and browser extension. This policy explains what ZapArc handles, what remains on your device, and what may be processed by third-party networks or optional services. Your seed phrase and private keys remain under your control and are not collected by us.

Data Stored Locally by Default

• Wallet seed and private keys. Generated or restored on your device and protected using the storage mechanisms available on that platform. They are not transmitted to us. If you lose access without a valid backup, we cannot recover your funds.
• Transaction history and wallet state. Cached locally for display and synchronization. Relevant payment information is also processed by the networks and infrastructure needed to perform the transaction.
• Contacts you add. Lightning addresses, Spark addresses, and notes you save in ZapArc's address book.
• Settings and preferences. Display currency, theme, security settings, selected wallet, and similar preferences.
• Optional notes and labels you attach to transactions.
• Diagnostic history. Bounded payment lifecycle and SDK logs may be retained locally to help diagnose wallet issues. They are not automatically uploaded. You choose whether to copy or export them and where to send them.

Data Sent to Third Parties

For ZapArc to perform requested wallet operations, certain non-secret information is processed by third-party protocols and service providers. Their own privacy policies and network rules apply.

Breez Technology, Bitcoin, Lightning, Spark, and related providers

ZapArc uses the Breez SDK and related infrastructure to synchronize wallets and perform Bitcoin, Lightning, Spark, and supported token operations. Depending on the feature you use, the following may be processed as necessary:

• Your Spark identity public key, transaction signatures, payment amounts, and routing data.
• If you choose to claim a Lightning Address (name@breez.tips), that mapping is registered with Breez's LNURL server. The address itself is intentionally public so others can pay you.
• Payment requests, payment hashes, public addresses, amounts, fees, routing information, timestamps, status, and other protocol data necessary to provide the requested wallet operation.
• For optional payment notifications, notification routing information such as a push token, public wallet identity, and optional wallet nickname.

Apple Push Notification Service (APNs) and Google Firebase Cloud Messaging (FCM)

On Mobile, if notifications are enabled, ZapArc registers with Apple's APNs or Google's FCM. A device-specific push token is generated and processed to route notifications to your device.

ZapArc notification relay

We operate notification infrastructure that receives payment-arrival events and forwards notifications through APNs or FCM. It may store:

• Your Spark identity public key (so it can route the right notification to the right device).
• Your push token.
• An optional wallet nickname you set in the App (used to identify the wallet in the notification body).

The backend never sees, stores, or has access to your seed, your private keys, or the value of your funds. Source code and infrastructure are operated by 21DigitalAI.

Optional platform and backup services

If you explicitly use an optional platform sign-in, cloud backup, sharing, or file-export feature, the selected operating-system or service provider processes the information you choose to provide under its own terms and privacy policy. ZapArc does not automatically upload diagnostic exports.

Information We Do Not Collect

• We do not collect your seed phrase, private keys, or any data that would allow us to access your funds.
• We do not run analytics or behavioral tracking inside ZapArc. There are no third-party analytics SDKs.
• We do not share wallet data with advertisers.
• We do not require you to create an account with us to use the App's core features.

On-Chain Data Is Public by Nature

Bitcoin transactions and other protocol data may be publicly observable or disclosed to participants in the networks and services used to perform a transaction. Lightning payments are not recorded on the Bitcoin blockchain in the same way as on-chain transactions, but routing and service providers may process payment metadata. These are properties of the underlying systems, not additional collection by ZapArc.

Children's Privacy

ZapArc is not directed at children under 13. We do not knowingly collect personal information from children.

Changes to This Policy

We may update this Privacy Policy from time to time. The "Last updated" date at the top of this page reflects the most recent revision. Material changes will be communicated through ZapArc or another reasonable channel where required.

Contact

For privacy questions, contact 21digitalai+support@gmail.com.

← Back to all policies