Pearl Hub

Privacy Policy

← Pearl Hub

Last updated: October 15, 2026

Pearl Hub provides a native self-custody cryptocurrency wallet and mining monitor for the Pearl ($PRL) network, a Chrome wallet extension, and a web mining companion. We do not sell your data or use advertising trackers. The native app's optional alerts and the web companion's server requests and encrypted sync are described below.

Optional email accounts, no tracking

Local features work without an account. Email sign-in is optional and enables configuration sync, device management and purchase linking. We do not use advertising or analytics SDKs. Cloudflare Turnstile verifies email requests to prevent abuse; Cloudflare Email Service sends one-time verification codes.

Your keys stay on your device

In the native app, your wallet recovery phrase and private keys are generated on your device and stored, encrypted, in the device Keychain / Secure Enclave. They never leave your device and are never transmitted to us. Viewing your recovery phrase or sending funds is protected by Face ID / Touch ID.

Price Alerts (optional, Pearl Hub Pro)

If you unlock Pearl Hub Pro and add price alerts, the app sends our alert server (pearlhub.net, hosted on Cloudflare) what it needs to do that: this device's Apple push notification token, the alert conditions you set (for example "PRL rises to $1.20"), the app's display language and, if you limit notifications to certain hours, those hours and your time zone. The server uses them only to check the $PRL price every minute and notify you through Apple's push service when a condition is met. For price alerts it does not receive wallet recovery phrases or private keys. If you sign in, your notification token is associated with your account device. Removing all your alerts deletes this data from the server; tokens that Apple reports as no longer valid are deleted automatically. The Lock Screen live price works the same way: while it is running the server holds the push token Apple issues for it, and forgets it when it ends.

Offline Alerts (optional, Pearl Hub Pro)

Offline alerts are off until you switch them on for a pool monitor. When you do, the app sends the same alert server what it needs to ask that pool about that monitor: the pool's name, the payout address you entered for it (for F2Pool, the key of the read-only page link you entered, and its account name), the name you gave the monitor, the delay you chose, this device's push notification token and the app's display language. The server asks the pool's public API about that address every few minutes and notifies you when a worker has been offline for the time you chose, and again when it is back online; it keeps the worker names and online status the pool last reported, for that purpose only. It never receives your recovery phrase, private keys or balances. Switching the alert off, or deleting the monitor, removes it from the server.

In-app purchases

Pearl Hub Pro is a one-time in-app purchase processed entirely by Apple. We never receive your payment details or your Apple Account; the app checks your purchase on-device with Apple's StoreKit. If you turn on the alerts above, the app also sends the alert server Apple's signed record of that purchase, and Apple notifies the server of purchases and refunds. The server keeps the purchase's transaction identifier, with the price and storefront country Apple reports, to confirm that alerts belong to a Pro purchase and to stop them if it is refunded.

Web version

The web version sends pool identifiers you add (including an F2Pool read-only link key) to our service to query the relevant pool. Results are cached briefly and are not associated with an identity. Your lists and preferences are stored in your browser. We never request recovery phrases or private keys.

The read-only wallet page sends watch addresses to our service, which queries Blockbook for balances and paginated transaction history, including fees and counterparties. Mining income queries also send your monitored payout addresses to exclude transfers between them. These results are briefly cached using hashed address keys. The web page cannot sign or send transactions. Watch addresses remain in local settings and optional encrypted sync. A collapsed card on the same page contains the Chrome extension download and installation guide.

USD exchange rates come from ExchangeRate-API's public USD feed; extended price history comes from BigONE's public PRL/USDT daily candles. These requests contain no wallet address or identity. The candlestick chart on the Market page is the one exception that does not pass through our service: your browser loads it directly from SafeTrade's public PRL/USDT market data (safetrade.com), without an address, account or cookies, so SafeTrade receives your IP address. Network charts use public Blockbook samples retained by our service. Device lists, rental costs and calculator preferences remain in your browser and, if enabled, your encrypted settings sync. Synchronizing pool workers into your device list queries only the monitors you have enabled.

Email accounts and configuration sync

Signing in stores your email, random account and installation identifiers, device names, platform, login times and recent activity on Cloudflare D1. Six-digit codes expire in five minutes and are stored as keyed hashes. Request limits use keyed hashes of IP addresses and emails. Web sessions use Secure, HttpOnly cookies. Native apps keep access and refresh credentials in the device-only Keychain; the extension keeps them in local storage restricted to trusted extension contexts.

Sync includes public watch addresses (from the native app, each wallet's first receive address and its name, shown read-only on the Web), contacts (names, addresses and notes), monitors, alerts, devices, calculator inputs, language and display preferences. It excludes recovery phrases, private keys, wallet passwords, API secrets and signed transactions. Transport uses HTTPS. Cloud configuration is encrypted at rest with a key stored in Cloudflare Worker secrets. This is not end-to-end encryption: the server can read the configuration to validate it and process notifications.

Browser notification subscriptions belong to a local purchase credential or an account device. Signing out or removing a device revokes its sessions and stops its account notifications; a valid purchase saved in this browser can continue with local settings. Local caches are separated by account; sign-out restores guest settings. An account-managed setting is not also mirrored through iCloud. Wallet storage and local wallet unlock are independent of the account.

PRL checkout works without an email account. The browser automatically saves a random purchase credential in local storage before checkout. The server stores its hash, an installation identifier, order amounts and payment transaction identifiers. This credential can access only its purchases and browser notifications; it is excluded from exported and synced settings. A confirmed payment enables Pro in that browser. Optionally linking a verified email lets you restore purchases and use them on other devices. Clearing site data removes the local credential, so email linking is recommended for recovery. Linking an App Store purchase verifies Apple's signed transaction and associates its original transaction identifier with one account. Refunds revoke that purchase's entitlement while retaining independent valid purchases. Linked PRL and App Store purchases grant the same account Pro features in supported app versions. Local App Store purchases also work without an email account.

The account page provides configuration export, device removal, verified email changes and account deletion. Deletion removes your email and cloud configuration and revokes sessions and notifications. De-identified payment, purchase/refund and notification-claim records remain to prevent receipt replay and prevent revoked devices from reconnecting through older interfaces. Local wallets are not deleted. Expired codes and request budgets are cleaned up automatically; sessions expire after 30 days of inactivity or 90 days from sign-in.

Chrome wallet extension

The extension encrypts recovery phrases and pending transaction records in local extension storage using your password. It does not sync private keys through a Chrome account or our web service. Blockchain queries send account extended public keys, addresses and transaction identifiers to the selected network's Blockbook service; transfers send signed transactions. Recovery phrases and private keys are not sent. Uninstalling the extension removes its local wallet records.

On mainnet the extension requests the public PRL price and exchange rates from our service to show an estimate of your balance; these requests carry no wallet address or identity. Contacts you save (name, address and note) are stored unencrypted in local extension storage. Optional email account sync shares these contacts with Web and native apps, over HTTPS. Cloud configuration is encrypted at rest and readable by the server. Account credentials remain in trusted local storage. Signing out stops sync and restores guest contacts. Local account caches are separated by user, and no data is synced through your Chrome or Microsoft account.

Opening a public wallet address in the Web companion places the selected address in the URL fragment. The browser reads it after the page loads; it is not sent in the initial page request.

Third-party services the app contacts

To provide its features, the native app makes direct requests from your device to public services. These requests carry only what is needed to fulfill them (for example a wallet or mining address you enter), and each service has its own privacy policy:

We do not control these services. Native app queries go directly to them; web queries pass through our service as described in the Web version section, except the SafeTrade candlestick chart, which the browser loads directly.

iCloud sync (optional, Apple-encrypted)

While signed out of the email account, iCloud can sync your preferences (language, currency, pool setup) across your own devices through Apple iCloud, and a SafeTrade API key you add is kept in your iCloud Keychain. This data is handled by Apple under Apple's privacy policy; we have no access to it.

Children

The app is not directed to children.

Changes

We may update this policy from time to time. Material changes will be reflected on this page with a new "Last updated" date.

Contact

Questions about this policy? Reach us on Telegram at @prl_hub.