SUPRX coin
SUPRX Privacy Policy

Privacy

What the SUPRX app and services do and do not collect.

SUPRX is designed so wallet secrets stay with the user. This policy explains the limited operational data the app, website, and APIs may process, and what users should never send us.

Plain version

The short version first.

Policy

What we may process.

1. Information you submit

Depending on which features you use, official SUPRX services may receive public operational data such as wallet addresses for scanning, transaction IDs, signed raw transactions for broadcast, restore job requests, and support messages you send voluntarily.

2. Device and request metadata

Standard server logs and API infrastructure may record request metadata such as IP address, timestamps, endpoint usage, response status, and basic user-agent information for reliability, security, and abuse prevention.

3. Public blockchain data

Public blockchain addresses, balances, UTXOs, and transaction history may be processed because that is required to power wallet features, explorers, proof pages, and status tools.

4. Support messages

If you contact support, we may process the information you send us to respond and troubleshoot. Do not include private wallet secrets.

5. What we do not want

We do not want you to send us your recovery phrase, xprv, private descriptors, private keys, or wallet database files. The mobile wallet is intended to keep that material local to your device.

6. Self-custody model

Wallet backup material is intended to remain under the user’s control. If a future app feature stores encrypted local wallet data, that is still meant to remain on the device unless the feature clearly says otherwise.

7. Public chain visibility

Blockchain systems are public ledgers. If you use SUPRX or related public services, your public addresses and transactions may be visible to anyone using a public explorer.

8. Security use

We may use operational data to rate-limit abusive traffic, monitor uptime, investigate API misuse, and maintain service security.

Use and retention

How we use information.

Why we use it

  • To return balance, UTXO, history, and transaction data.
  • To broadcast signed native SUPRX transactions.
  • To run restore scan jobs and report their status.
  • To secure public endpoints and reduce abuse.
  • To answer support requests.

Retention

  • Operational logs may be retained for security and reliability.
  • Restore-job or backend data may be retained for service continuity, debugging, and abuse review.
  • Public blockchain data is not erasable by us because it is part of a public ledger.

Third parties

External systems and platforms.

Infrastructure

The app and website may rely on third-party infrastructure such as hosting, network providers, Apple platform services, blockchain nodes, or analytics and crash-reporting tools if enabled in the app build or platform environment.

App Store

If you download the app through Apple’s App Store, Apple may process data under its own policies. That is separate from this project policy.

Explorers and chains

When public explorers are used, public address and transaction data may be visible through those explorer systems. That visibility is a normal part of public blockchain use.

Contact

Official links.