Last updated · 18 May 2026

Privacy, by default.

BitGarth is designed to keep private financial data in your app instance unless you choose a feature that needs a network request. This notice explains the main data boundaries.

What you can use without telling us

You do not need to give BitGarth your legal name, postal address, or email address to use the app. Wallet sync uses public wallet information such as addresses and xpubs, not seed phrases or private keys.

i.

App DB and encrypted user DB

The app DB stores registered users, login metadata, and app-level records such as which Terms and Privacy Notice version an app account acknowledged. The app DB is not encrypted, so it must stay minimal.

Your wallet data, transaction history, labels, settings, saved API keys, and saved invoice details belong in the encrypted user DB. This user DB is protected by your password.

ii.

Self-hosted and downloaded apps

If you run BitGarth yourself, app DB records and encrypted user DB records stay with that app instance. The app does not send legal acknowledgement records back to BitGarth central services by default.

iii.

Hosted services

If BitGarth operates a hosted app instance in the future, BitGarth may operate the app DB for that hosted service and keep the minimum records needed to run accounts, payments, support, and entitlements.

iv.

Payments

For paid plans, BitGarth needs enough information to recognize payment history. The app uses a privacy-preserving anonymous payment ID that is separate from your app user ID.

Cryptocurrency payment privacy depends on the asset and network. Monero is the strongest payment privacy option among supported assets.

v.

Invoices

If invoice support is added, invoice details will be entered inside the app. You will choose whether to save them. Saved invoice details should live in your encrypted user DB, not in a central BitGarth account.

vi.

Providers

BitGarth can contact blockchain explorers such as Mempool and Etherscan to sync public transaction history for addresses and xpubs you add. Those providers can see the public wallet data being queried.

BitGarth can also fetch prices from services such as CoinMarketCap or CoinGecko. Price fetching is optional and off by default. It is enabled only when you choose to fetch prices or display asset values in another currency.

vii.

Analytics and cookies

The app does not use in-app analytics today. If privacy-preserving app analytics are added later, they should be off by default unless you enable them.

The landing site is a static website and does not need an account cookie to read these pages.

viii.

Contact

Questions about privacy: hello@bitgarth.app

Security reports: security@bitgarth.app

Last updated · 18 May 2026