YOUR DATA, EXPLAINED

Privacy Policy

Last updated: October 17, 2026

Pulz: Crypto Wallet is developed and published by Blockchain Solutions Labs (“we”, “us”).

This policy describes how Pulz (“Pulz”, “we”, or “us”) handles information when you use the Pulz Android wallet and this website. Pulz is a self-custody wallet. Your private keys stay on your device. Your recovery phrase is stored on your device by default; if you explicitly choose the optional Google Password Manager backup, Google stores a copy in your Google account.

1. Information Pulz handles

• Public wallet information. Public addresses, selected networks, and requests needed to show balances, transaction history, prices, or prepare a transaction. Public addresses are not secret, but can be linked to activity on public blockchains.
• App and installation data. A per-install identifier derived from an Android device identifier where available, app events such as opening a screen or starting a send or swap, event timestamps, and basic app configuration such as the selected display currency. We use this to operate, troubleshoot, and improve the app. Event names and labels are designed not to include recovery phrases, private keys, or transaction amounts.
• Credential data. Android Credential Manager handles passkey sign-in. If you explicitly choose password-manager backup for your recovery phrase, the phrase is stored by Google Password Manager in your Google account and may sync to your other devices under Google's controls. Pulz does not receive that Google account password.
• Push notification data. If you enable balance notifications and grant Android notification permission, the app sends a Firebase Cloud Messaging token and the wallet/network subscription needed to deliver those notifications. You can turn notifications off in the app; the app then asks our server to remove the push registration.
• Support messages. Text you choose to send in in-app support, along with the installation identifier needed to reply in the app. Support messages are routed through Telegram to the support team. Do not include passwords, recovery phrases, or private keys; the app and server are designed to reject recovery phrase-like content.
• Camera input. If you grant camera permission, the camera is used to scan a QR code. The scan is processed in the app; camera frames are not sent to Pulz servers.
• Deletion requests. When you delete your data, Pulz keeps a minimal record that the request was made and honoured: a random receipt number, the channel, the times, the outcome and a row count per step. It holds no installation ID, wallet address, secret, IP address or message text. The website route uses a one-time pairing code that you approve in the app, or a message you sign with your wallet; Pulz never asks for a recovery phrase or private key. See Delete data.
• Website request data. When you visit this site, Cloudflare processes the network request to deliver and protect the site. Cloudflare may process technical information such as IP address, request headers, and security events under its own policies.

2. Information we do not receive

Your recovery phrase, private keys, and locally stored wallet secrets are not sent to Pulz servers. Signing takes place on your device. Pulz does not custody your crypto and cannot reverse or sign a transaction for you.

3. Why we use information

We use the information above to display wallet data and quotes, submit signed transactions to the network when you request it, deliver notifications you enable, answer support messages, protect the service against abuse, and understand app reliability and feature usage.

4. Service providers and blockchain networks

To provide wallet features, the app or our server may send public addresses or transaction requests to blockchain networks and infrastructure, pricing, portfolio, and swap providers. These can include Alchemy, QuickNode, DeBank, CoinGecko, Jupiter, Li.Fi, 0x, STON.fi, Mempool.space, TON Center, TronGrid, and the relevant public blockchain network, depending on the feature and network you use. These services receive the data needed to answer the request and handle it under their own terms and privacy practices.

Google Credential Manager handles passkey operations. If you opt in to phrase backup, Google Password Manager receives and stores that backup under your Google account. Google Firebase Analytics processes app events and associated app/device information when configured in the app build. Firebase Cloud Messaging processes push tokens and notification delivery when you enable notifications. In-app support is relayed using Telegram. Cloudflare provides delivery and security for this website. Our API runs on Railway, which receives the requests the app sends to it and keeps routine server logs. We do not control the independent privacy practices of these services.

5. Sharing and sale

We do not sell personal data or share it for cross-context behavioral advertising. We provide the minimum information needed to the service providers listed above so the feature you request can work. Blockchain transactions and public addresses can be visible to anyone using the relevant public network.

6. Storage, security, and retention

Wallet secrets remain on your device. Our API uses HTTPS in transit and access controls for server operations. No internet service can be guaranteed completely secure.

Our server stores installation records, public wallet addresses and network subscriptions, analytics events, support messages, and push registrations to provide the service. These records do not currently have a single automatic time-based deletion schedule. We keep them while needed to operate and protect the service, and you can delete them at any time in the app or on our Delete data page. Routine database backups and server logs are not edited record by record and age out on the hosting providers' schedules. Disabling notifications removes the associated push registration.

7. Your choices and deletion requests

You can deny camera or notification permissions in Android settings; some app features may then be unavailable. You can disable balance notifications in the app.

To delete the information we hold, use Profile, Delete my data in the app. It deletes the server-side records for your installation first, and only after the server confirms does it erase the wallet and local data from the phone. If you no longer have the app, start a deletion on our Delete data page, either by approving a code in the app or by signing a message with your wallet address. The wallet route deletes the records tied to that address; records that belong to an installation itself can only be deleted from that installation. Neither route needs an email address, and neither asks for a recovery phrase or private key.

Logging out of a wallet removes it from your phone and asks our server to unlink the wallet from your installation and, when no wallet is left, to drop your push registration. It does not by itself erase the other data already sent to the server, such as usage events, support messages and stored balances and history. Deleting your data does not remove public blockchain records, copies held by independent service providers, or a recovery phrase backup in Google Password Manager, which you remove there. The Delete data page lists what remains.

8. Children

Pulz is not designed for children, and we do not knowingly collect personal information from children.

9. Changes to this policy

We may update this policy as the app changes. We will post the current version on this page and update its “Last updated” date.

10. Contact

For privacy questions, contact info@pulz.cc. You do not need to email us to delete your data: use the app or the Delete data page.