Податковазапросила підтвердження?

Balance data is queried live from public blockchains through providers such as Alchemy, Etherscan, Moralis, and Helius. We do not operate a permanent blockchain snapshot archive as a standalone data product. If you opt in, public wallet addresses and labels can be stored in your account (cloud).

Balance Proof reads balances directly from blockchain data sources. Accuracy depends on underlying chain data and provider availability. Please validate results independently for tax-relevant use cases.

Final requirements depend on the responsible tax office. In practice, wallet address, reporting date, token amounts, valuation basis, and transparent methodology are commonly expected. Balance Proof helps you export that structure.

Balance Proof combines token balances at the selected reporting date with historical pricing data from integrated providers. If reliable historical pricing is unavailable for specific tokens or dates, EUR valuation can be limited.

Balance Proof is a technical documentation tool and does not provide tax or legal advice. CSV exports can support your documentation process but do not replace professional assessment.

The stack runs on Supabase (backend/auth/database) and Netlify (frontend/CDN). Payments are processed via Stripe.

Wallet addresses are stored locally in your browser when local storage is enabled. If you enable cloud sync (opt-in), public wallet addresses and labels can be stored in your account (Supabase) and deleted at any time. On the server side, wallet addresses are also technically processed during requests and temporarily stored within run-authorization scope for credit enforcement and abuse prevention.

We store account data (e.g. email, name), credit/payment records, and security-relevant technical logs. Wallet addresses are processed for queries and temporarily stored in run-authorization scope for credit enforcement and abuse prevention. If you opt in, public wallet addresses and labels can be stored in your account and removed at any time. We do not keep permanent blockchain snapshots as a standalone historical archive.

Historical lookups are available for native coins and ERC-20 balances by reporting date. SPL tokens are currently provided as snapshots. ERC-721/NFT and DeFi/staking data are mainly current snapshots, and fully complete historical NFT states are not always available.

Use spot checks: compare wallet address, reporting date, and selected token balances against public explorers and your own source records. For tax submissions, run an additional professional review.

You can add the proof wizard output as a Word document with questions, answers, and wallet data. Depending on the case, exchange statements, transaction ledgers, and tax-office correspondence are useful supporting documents.

Often within minutes. Runtime depends on the number of wallets, reporting dates, chains, and selected query scope. One credit is consumed per wallet × reporting date.

No. Balance Proof is read-only. You only enter a public wallet address. There is no wallet connect, no signature, and no access to private keys or seed phrases.

1 credit = 1 query for 1 wallet address at 1 reporting date. Example: 3 wallets at 2 dates consume 6 credits.

No subscription. You buy a one-time credit package and use it until consumed.

Yes. You receive a proper invoice with VAT from a GmbH based in Germany.

Native coins, ERC-20, and SPL tokens are supported through API providers. NFT and DeFi/Staking data is primarily available as current snapshots where supported. For ERC-721/NFT history, provider APIs (including Moralis and Etherscan) do not always return a complete reporting-date snapshot, so we cannot guarantee 100% historical NFT accuracy.