Legal

Privacy Policy

Effective 15 October 2026 · applies to the Pasiv desktop app, the Pasiv Companion mobile app, and pasiv.network

1. Who we are

Pasiv ("we", "us") makes the Pasiv desktop mining app and operates the website pasiv.network. For anything in this policy, contact support@pasiv.network.

2. What the desktop app processes

Stored on your device only

Your configuration — payout addresses, chosen coin, Auto mode and other toggles — and the local fee ledger are stored on your machine. They are not uploaded to us, with one exception: if you sign in while paid through unMineable, that payout address (USDT or BTC) is stored on your account (see Optional wallet sign-in below).

Mining pools (when you press start)

Mining means your machine connects directly to the pool configured for your payout route. By default that pool is unMineable, which converts what you mine to USDT and pays your own address; installs from before version 0.5.0 that pay a coin address directly may still use MoneroOcean, LuckyPool, LuckPool or HeroMiners. The pool necessarily sees your IP address, payout address, and mining activity (shares, hashrate, worker name). Pools are independent services under their own privacy terms; Pasiv is not in that path and does not receive this data.

Auto / Max-Profit mode (opt-in)

If you enable Auto mode (available only to installs that pay a coin address directly), the app periodically fetches public market data — coin prices from CoinGecko and pool statistics from HeroMiners — to rank coin profitability. These are ordinary web requests: the services see your IP address and an app identifier in the request, nothing about your wallet.

Software updates

The app checks a signed release manifest on our release CDN (hosted on Supabase Storage) to offer updates. The host sees standard request metadata (IP address, user agent). Updates are cryptographically signed and verified on your device before install.

Optional wallet sign-in

You can optionally sign in with a wallet (e.g. MetaMask or Phantom) using a signed message. If you do, your public wallet address is stored with our authentication provider (Supabase) as your account identifier. Signing in never exposes private keys, and Pasiv cannot move funds. While you are signed in, product analytics (below) are linked to your account by an opaque id — a one-way hash of your account number, never your wallet address — so your events count as one person across the desktop app (from version 0.5.0) and the phone app (from version 1.0.18). If you are paid in USDT, your USDT payout address is also stored on your account, because that is the only way a headless node (pasivd) can learn where to pay you. Delete it in the phone app (Settings → Delete account, see pasiv.network/account-deletion) or email support@pasiv.network to delete this record.

Share & earn codes (optional)

If you create a Share & earn code (it needs a wallet sign-in), we store your code, the asset you chose (BTC or USDT), the payout address it pays, and its tier (regular or creator) with your account, so the app of anyone who enters your code can show them exactly who it pays before they confirm. When a miner confirms a code, we record only an anonymous count for that code — no account, no device id, no IP address — so its owner can see how many machines use it. The miner's own copy of the code and address is kept on their machine. Analytics never carry a code or an address. Delete it in the phone app (Settings → Delete account, see pasiv.network/account-deletion) or email support@pasiv.network to delete your code.

Pasiv Cloud and the mobile companion (opt-in)

Pasiv Cloud is off unless you turn it on in Settings. With it on, the desktop app sends a status row for each machine to Supabase roughly every 30 seconds, so the Pasiv Companion app on your phone can show it and start or stop it. That row contains:

• The machine's name (and any name you give it in the companion), operating system, and Pasiv version.
• A hardware summary (e.g. CPU model, core count, GPU model) used to show the rig and estimate earnings.
• Which coin is selected, whether Auto mode is on, mining state, hashrate, accepted/rejected shares, and how long the current session has been mining.
• If a miner fails to start, one word for why, chosen from a fixed list: binary_missing, blocked_by_security, permission_denied or other. It lets the companion tell you a rig needs attention instead of showing an error with no cause. The underlying message can name files and folders on your machine, so it stays on your device — only the category is sent, and it is one of those four words, never any part of the message itself.

Payout addresses are not included in a rig's updates. They stay on your device and at your pool (the one exception, your unMineable payout address — USDT or BTC — stored on your account for headless nodes, is described above). Earlier builds did send them; they were never read, they have been deleted, and the server now discards the field no matter which version sends it.

The companion can only start a rig, stop it, or ask it to update — and an update installs a release we signed, verified against a key built into the app before anything is written to disk, so it cannot deliver anything else. It cannot change which coin you mine, your pool, or your payout address — the app has no way to express those commands, and commands expire after two minutes. Turning Pasiv Cloud off stops the sync and removes that rig from your account; delete it in the phone app (Settings → Delete account, see pasiv.network/account-deletion) or email support@pasiv.network to delete the rest.

Analytics in the mobile companion (anonymous unless you sign in, your choice)

The Pasiv Companion app can send a small set of events, anonymous unless you sign in, to PostHog (US cloud). The first time you open the app it asks (from version 1.0.26): "Keep it on" or "Turn off". Nothing is sent before you answer, and the answer can be changed any time in Settings → Usage data.

• Events: the app opening (and how it was opened), signing in or a sign-in that failed and why (a fixed reason such as no_evm_account — never the wallet), opening the demo, starting, stopping or updating a rig, renaming a rig (the name is never sent), adding a headless node, opening or using the share sheet, viewing or sharing the Share & earn card (the tier only — never the code), turning usage data on or off, and deleting your account. The full, current list is in the app's source and in the desktop's analytics document.
• In the demo, the only thing counted is that the demo was opened. Nothing you do inside it is sent.
• If the app crashes: the error's type (for example StateError), whether it was fatal, and where it happened — the lines in Pasiv's own code, or, when the error happened entirely inside a library the app uses (the wallet-connect library, Flutter), the library's own frames so we can tell which library. The error message is never sent, because a message can quote whatever the app was holding — an address, a rig name, a folder on your phone.
• Attached to each event: the app version, the platform (iOS or Android), and the device context PostHog's SDK adds — device model, OS version, locale, timezone, screen size and network type (Wi-Fi or cellular). Your IP address is used by PostHog to receive the event and to derive a country; it is not stored with the event.
• No wallet address, no payout address, no rig or team names, no screen contents, no session recording, and no advertising identifier.
• Signed out, no profile is built about you. The app never identifies you to PostHog; events carry PostHog's random per-install id. Signed in (from version 1.0.18), events are linked to your account by the same opaque id the desktop app uses — a one-way hash of your account number, never a wallet or payout address — so your devices count as one person. Nothing is linked to other companies' data, so there is no tracking in the App Store's sense.
• Send feedback (Settings) sends the text you typed to PostHog as a survey response. It is sent even if usage data is off — because you pressed Send — and in that case it lands in a shared anonymous bucket that is not a profile of you. Don't put anything in it you don't want us to read.
• The app reads no remote configuration: no feature flags, no remote surveys, and no wallet-SDK telemetry (the wallet-connect library's own analytics are switched off; it talks only to the WalletConnect relay to reach your wallet).
• Switched off, the app sends one last message saying usage data was turned off — the platform, app version and roughly how old the install is (day one, first week, first month, later), with no identifier and no profile — and then does not start the analytics SDK at all: it makes no further request to PostHog, rather than making one and discarding it. That single message is how we tell "people switched it off" apart from "the app stopped working", which matters to us; it cannot be tied to you. Turning it back on sends one message saying so. (Feedback, above, is the other deliberate exception.) The desktop app does the same from version 0.6.3.
• Data the app keeps on your phone: your sign-in session, and the wallet-connect pairing, which the wallet library stores in the system keychain (iOS) or encrypted preferences (Android). On iOS the keychain entry can survive uninstalling the app; deleting your account, or signing out before uninstalling, clears what matters.

Analytics in the desktop app (anonymous unless you sign in, optional)

The desktop app sends a small set of anonymous product events to PostHog (US cloud) so we can tell whether features work:

• Events: app opened, mining started/stopped, coin switched, Auto mode toggled, payout address saved (the coin name only — never the address).
• No autocapture, no session recording, no screen contents, and "Do Not Track" is respected.
• Events are anonymous unless you sign in. Signed in, they are linked to your account by an opaque id (a one-way hash of your account number) so your devices count as one person (the phone app too, from version 1.0.18); never by your wallet or payout address.
• You can turn analytics off entirely in Settings.

3. What the website processes

pasiv.network is a static site. It uses PostHog for anonymous page-view and click analytics (e.g. which download button was pressed, and whether a visitor arrived with a friend's Share & earn code — never the code itself; the code is kept only in your browser for 90 days so it can be shown to you at setup), loads fonts from Google Fonts (Google sees your IP when serving them), and serves downloads from our release CDN. The site sets no advertising cookies.

4. What we never collect

• Private keys or seed phrases — never asked for, never stored, no UI exists for them.
• Payout addresses on our servers — they live on your device and at your chosen pool. The exceptions are the unMineable payout address (USDT or BTC) of a signed-in user, stored on their account for their headless nodes, and the payout address of a Share & earn code, stored with that code (section 2).
• Files, documents, clipboard, camera, microphone, or anything else on your machine unrelated to mining.
• Browsing history or cross-site tracking of any kind.

5. Service providers

We share data with no one else, and we never sell it.

6. Retention and your rights

Analytics events are anonymous unless you sign in, and are used as aggregate product statistics. The only personal records we can hold belong to an optional sign-in: its public wallet address, the payout address (USDT or BTC) stored on it, and analytics events linked to its opaque id — delete them yourself in the phone app (Settings → Delete account) or email us and we will. Depending on where you live (e.g. GDPR in the EU/UK, CCPA in California) you may have rights of access, correction, deletion, and objection; we honour requests to support@pasiv.network regardless of jurisdiction. Account deletion has its own page: pasiv.network/account-deletion. Uninstalling the app removes its local data.

7. Children

Pasiv involves cryptocurrency and is not intended for anyone under 18. We do not knowingly process children's data.

8. Changes

If this policy changes materially, we'll update this page and note it in the app's release notes. The effective date above always reflects the current version.