Terms, without the thicket.

Using BitGarth

BitGarth is self-custody accounting software. You are responsible for the wallets, addresses, xpubs, records, exports, backups, and reports you choose to use with the app.

BitGarth does not ask for seed phrases or private keys and cannot move your funds. Do not enter private keys, seed phrases, or exchange login passwords into BitGarth.

Accounts and access

The app may ask you to create an app account so it can protect access to your app data and encrypted user database. You are responsible for choosing a strong password and keeping backups or exports where appropriate.

If you forget your password and have no backup or export, BitGarth cannot recover your encrypted user database for you.

Paid plans

Paid plans unlock additional sync limits or features. Prices, plan limits, payment methods, and availability may change over time. The app should show the applicable plan details before you pay.

Cryptocurrency payments have different privacy properties depending on the asset and network. Monero is the strongest payment privacy option among supported assets.

No professional advice

BitGarth helps organize records. It is not tax, legal, financial, accounting, or investment advice. You are responsible for reviewing exports, reports, classifications, and balances before relying on them.

Software limits

BitGarth depends on your device, browser or app runtime, configured providers, public blockchain data, and the information you enter. Bugs, provider outages, chain reorganizations, import mistakes, and classification mistakes can happen.

Use backups, review important outputs, and keep independent records where the result matters.

Privacy and security

The Privacy Notice explains what information BitGarth needs for different workflows. The Security page explains how BitGarth protects wallet data and where the limits are.

Changes

These terms may change as BitGarth changes. If a change materially affects app accounts or paid plans, the app should make the new terms visible before asking users to continue.