Skip to content

Legal

Privacy Policy

Last updated 3 August 2026

01Where your data lives

Quasarr splits data in two: what stays on your device, and the small amount needed to run licensing. Nothing in the first column is ever transmitted.

On your device only

  • Wallet private keys
  • Seed phrases and mnemonics
  • Keystore passwords
  • Custom RPC URLs
  • Task configurations

On our server

  • License key and status
  • Hardware ID, for device verification
  • Discord ID, for role-based access
  • Linked public wallet address

02Quasarr Quick Task browser extension

The Quasarr Quick Task browser extension is a companion to the locally installed Quasarr desktop application. It reads the transaction or collection data needed to prepare a Quick Task from supported EVM explorer transaction pages, OpenSea collection overview pages and Catchmint pages.

  • The extension may read page data such as a transaction hash, contract address, calldata, transaction value, gas data or a collection slug.
  • When the user clicks Create Task, the selected task data is passed to the local Quasarr application using the quasarr:// protocol.
  • For Blockscout and Catchmint pages, the extension may request the relevant transaction data from the active site's public API.
  • The extension does not collect or transmit private keys, seed phrases, passwords, wallet credentials, browsing history, analytics or advertising data. It does not sign or submit blockchain transactions.

Quick Task data is not sent to Quasarr servers for storage by the extension. The local desktop application handles the task after the user starts the integration.

03Public blockchain data

Blockchain activity is public by nature. When you use Quasarr to transact on a network such as Ethereum:

  • Your activity becomes a permanent public record.
  • Your transaction history, holdings and contract interactions are visible to anyone.
  • We have no control over that record and cannot delete or amend it.

04Third-party services

Quasarr reaches blockchains through RPC nodes, which you choose.

  • Public endpoints. These may log your IP address and request data under their own privacy policies.
  • Private endpoints. We recommend running your own, both for privacy and for speed during a drop.

05Security measures

  • Encryption at rest. Private keys are encrypted with AES-256-GCM.
  • Memory handling. Sensitive values are cleared from memory as soon as they are no longer needed.
  • Transport. All communication with our servers runs over TLS 1.3.

06Retention and deletion

Because we hold so little, deletion is straightforward.

  • You can request deletion of your server-side account at any time.
  • Local data is removed entirely by uninstalling the app and deleting its data folder.

07Contact and your rights

For privacy requests, including access and deletion, contact us through our Discord server.

Questions about this document? Open a ticket in the Quasarr Discord.