Crypto tax software needs enough information to reconstruct transactions, but it should never need the secrets that control your assets. This CoinLedger privacy guide explains the practical boundary: what a public wallet address, transaction-history export and read-only exchange API can reveal; what a seed phrase and private key can do; and how to reduce unnecessary exposure while keeping records usable for tax reporting.

Last reviewed: October 5, 2026. Product controls, supported integrations, data-retention practices and account interfaces can change. Confirm the current options in CoinLedger and the connected exchange before acting. This independent educational article is not tax, legal, cybersecurity or privacy advice.

Quick answer: use public addresses only where they are needed, create exchange API keys with read-only permissions, protect CSV exports like financial records, and never give CoinLedger—or an accountant, support agent or browser extension—a seed phrase, private key, exchange password, withdrawal permission or two-factor authentication code.

Privacy in crypto tax reporting is about data minimisation

Tax reporting is not anonymous. A complete record can connect exchange activity, public blockchain addresses, transaction timestamps, asset quantities, counterparties visible on-chain and fiat values. The objective is therefore not to promise invisibility. It is to provide only the data required for a legitimate reporting task, restrict powerful permissions, secure copies of the data and remove access that is no longer needed.

CoinLedger describes several ways to import activity: connecting an exchange through an API, uploading transaction-history files and adding blockchain wallet activity. Its official security page says API imports require read-only permissions and do not provide access to funds or private keys. That distinction is central to a safe setup.

What CoinLedger may need—and what it must never need

Information or permission Typical purpose Should you provide it?
Public wallet address or xpub Read visible on-chain transaction history Only for the relevant wallet or account
Exchange transaction CSV Import trades, deposits, withdrawals, rewards and fees Yes, after checking the file and source
Read-only API key Synchronize transaction history from an exchange Yes, if it has no trading or withdrawal rights
Exchange login password No legitimate tax-import need No
Trading or withdrawal API permission Moves funds or places orders No
Seed phrase or private key Controls self-custody funds Never
Two-factor code or recovery code Confirms account access Never share it

A public address is not a spending secret, but it is still sensitive financial metadata. Anyone who has it can often inspect balances and transaction history on the relevant blockchain. An extended public key can reveal activity from many derived addresses. Share the narrowest identifier that provides the required history, and do not casually post it in support tickets, screenshots or public chat rooms.

Public blockchain data is visible, but its meaning is not always obvious

Blockchains publish transactions, not a complete explanation of their purpose. An observer may see an address receive ETH, interact with a smart contract or send funds to an exchange deposit address, but may not know who controls every address, whether a movement was a sale or a self-transfer, or why it occurred. Tax software combines this visible history with data from exchanges and user classifications to make it useful for reporting.

That combination can create a more complete financial picture than any single transaction alone. Importing several wallets and exchanges is often necessary to preserve cost basis, but it also means the account becomes a high-value record. Treat account access, exported reports and invitations to tax professionals with the same care as other financial documents.

How to create a safer read-only exchange API

An API key is an access credential created inside an exchange account. The labels vary—Read, View, Query, History or Portfolio—but the safe principle is consistent: CoinLedger needs to read transaction history, not trade, transfer or withdraw assets. Create a dedicated key for the tax connection instead of reusing one that a bot, portfolio tracker or another application already uses.

  1. Start from the real exchange. Type the known domain or use a bookmarked official link; do not follow an API setup link from an unsolicited email or ad.
  2. Open API management. Name the key clearly, for example “CoinLedger Tax 2026,” so it can be audited and revoked later.
  3. Enable only read or view access. If the exchange separates balances, orders, trade history and transfers, select the smallest set CoinLedger’s current official guide requires.
  4. Leave trading, transfers, internal movement, withdrawals and address management disabled. A tax-record connection should not be capable of moving assets.
  5. Use an IP allowlist only when you understand the maintenance trade-off. A stale allowlist can break an import; do not enter an IP address from a message or unverified web page.
  6. Store the secret carefully. Enter it only in the legitimate connection flow, then do not keep it in a screenshot, plain-text note or unencrypted spreadsheet.
  7. Review the imported result. Compare date range, transaction count and major balances with the exchange before relying on reports.

If a form appears to require withdrawal permission, a trading key, a seed phrase or a remote-control screen share, stop. It could be an incorrect setup path or a scam. Independently locate the exchange’s and CoinLedger’s current instructions before continuing.

Read-only does not mean risk-free

Read-only access cannot directly authorize a withdrawal, but leaked account data can still expose portfolio size, trading behavior, linked services and personally identifying details. It can also help a criminal make a phishing email look plausible. Limit the number of connected applications, use unique account passwords and enable the strongest available multi-factor authentication on the exchange and email account.

Review API keys periodically. Remove keys for tax years, exchanges or applications that no longer need ongoing synchronization. If you suspect a key was exposed, revoke it from the exchange first, review account activity and create a replacement only after confirming the device and login account are safe.

CSV exports: useful evidence with real privacy risk

A CSV can contain more than a trade list. Depending on the exchange, it may include email or account identifiers, deposits and withdrawals, full timestamps, fees, order IDs, asset balances, referral information or transaction hashes. Spreadsheet software may create local copies, cloud sync can distribute a file to another device, and email attachments are easy to forward accidentally.

Safer CSV practice Why it matters
Download only from the authenticated exchange account Reduces fake-export and phishing risk
Keep the original file unchanged Preserves evidence if calculations must be reviewed later
Use encrypted device storage and a unique account password Limits exposure if a laptop or cloud account is compromised
Do not upload the same history through API and CSV without checking Helps avoid duplicate transactions and conflicting records
Share only through an agreed protected channel Avoids accidentally sending a full financial history by email or chat
Delete working copies under your retention plan Reduces unnecessary copies while preserving required tax evidence

Do not edit a native exchange export merely to make it look cleaner unless the documented import process requires it. Spreadsheet applications can alter timestamps, large identifiers and decimal values. When a correction is necessary, preserve the original and record what changed and why.

Do not confuse wallet visibility with wallet control

Adding a wallet address lets software read activity that is already public on that blockchain. It does not grant signing authority. Signing authority belongs to the seed phrase or private key. A genuine crypto tax workflow may ask for an address, but it must not ask you to connect a wallet and sign a transaction merely to read historical activity.

This rule protects against a common social-engineering pattern: someone claims that a wallet must be “verified,” “synchronized,” “validated for taxes” or “recovered” by entering recovery words on a website. There is no safe exception. Anyone with the seed phrase can recreate the wallet and spend its assets; anyone with a private key can control the associated address.

Privacy when working with an accountant or tax professional

A professional may need reports, transaction context and supporting files, but sharing access should be deliberate. Before inviting another person to a tax account, confirm their identity using independently obtained contact details, define the task and agree on how documents will be shared. Use a personal account rather than a shared family or team login, and remove the invitation after the engagement when appropriate.

  • Share a report or a limited export when that answers the question; do not automatically disclose every account credential.
  • Keep a record of which files, years and wallets were shared.
  • Ask the professional how they protect client records and how long they retain them.
  • Never send a wallet recovery phrase, private key, hardware-wallet PIN, exchange password or two-factor code to a tax professional.
  • Verify unexpected document requests by calling a known number, not by replying to the message.

Account deletion, API revocation and record retention

There are three different actions, and they solve different problems. Revoking an API key at the exchange stops that key from accessing exchange data. Deleting a connection or transaction data inside CoinLedger affects the data held in that account. Deleting a local CSV or report removes only that particular copy. Do not assume one action completes the other two.

CoinLedger states that users can delete transaction data and exchange API connections from within their accounts. Before deletion, identify which documents must be retained under the tax rules that apply to you, export what you are entitled and required to keep, and secure those records. Deleting data to improve privacy should not leave you unable to substantiate a filed return.

  1. Download final reports and the supporting records your professional or local rules require.
  2. Record the report year, calculation settings and any manual classification decisions.
  3. Revoke unneeded API keys at each connected exchange.
  4. Remove unneeded connections and transaction data in the tax-service account.
  5. Delete temporary downloads from devices and cloud folders according to your retention plan.
  6. Review active sessions, recovery methods and trusted devices on the email and exchange accounts.

Common CoinLedger privacy mistakes

Mistake Why it is risky Better approach
Using a trading-enabled API key A compromised key may have more power than a tax connection needs Create a separate read-only key
Sending a full CSV through ordinary chat It can expose years of financial activity and be copied indefinitely Use an agreed protected transfer method
Giving a seed phrase to “support” It grants control of self-custody assets Never disclose recovery words to anyone
Leaving old exchange API keys active Unused access expands the attack surface Review and revoke keys after each reporting cycle
Posting screenshots without redaction Addresses, balances, order IDs and personal details may be visible Redact unnecessary identifiers before sharing
Relying on a browser search result for login Typosquatting and malicious ads can imitate financial sites Use a password-manager entry or verified bookmark

A practical annual privacy checklist

  1. Inventory every exchange, wallet and tax tool that can see transaction history.
  2. Confirm every exchange API key is read-only and separately named.
  3. Remove duplicate, obsolete and unfamiliar API keys.
  4. Use unique passwords and strong MFA for the primary email, exchanges and CoinLedger account.
  5. Check that imported addresses belong to you and cover the required history without adding unrelated wallets.
  6. Encrypt devices that hold exports and reports; avoid public or shared computers.
  7. Save final reports and source evidence in a protected location.
  8. Revoke unused access only after preserving the records you need.

Frequently asked questions

Can CoinLedger withdraw crypto from my exchange?

A properly configured tax connection should use read-only permissions, not withdrawal or trading permission. Verify the permissions on the exchange itself; never assume a label alone is enough.

Does CoinLedger need my seed phrase or private key?

No. A tax application can read blockchain history from a public address. A seed phrase or private key controls assets and must never be entered into tax software, support chat, a spreadsheet or a website claiming to perform a tax import.

Can someone identify me from a public wallet address?

A blockchain address does not automatically display a legal name, but activity can be linked through exchange records, public posts, counterparties, repeated patterns and other data. Treat addresses as sensitive financial information.

Should I delete my CoinLedger data after filing?

First retain the records required for your circumstances. Then consider revoking obsolete API keys, removing old connections and reducing local copies. The right retention period depends on jurisdiction and personal facts, so seek qualified advice when unsure.

Key takeaway

CoinLedger can help organize crypto tax history without receiving control over crypto assets. Use that boundary actively: public addresses and read-only data imports may be appropriate; passwords, recovery phrases, private keys and withdrawal permissions are not. Restrict each connection, protect exported records, preserve necessary evidence and remove access that no longer serves a clear purpose.

Official references: CoinLedger Security and How CoinLedger Works.