Aller au contenu

This document is available in English and Spanish.

Privacy policy

TaxChain handles your financial history, so we keep what we collect to what the service needs, and we say exactly where it goes. This policy explains what we hold, why, who else sees it, for how long, and how you control it.

Who is responsible

The controller of your personal data is [Legal name to be added], NIF [NIF to be added], [Postal address to be added] ("TaxChain", "we"). For anything about your data, write to privacy@taxchain.eu.

What we collect

  • Account: your email address, an optional name, your password (stored only as a bcrypt hash), your country of tax residence, language and tax settings (cost method, and filing choices such as Spain's repurchase rule, the German loss years whose carry-back you waive or, in France, whether staking rewards are taxed as BNC income), and, if you turn it on, your two-factor authentication secret (encrypted).
  • Financial data you give us: the transactions in files you upload, the public wallet addresses you add (for Bitcoin and Litecoin, possibly an extended public key, from which every address of that wallet follows) and the history we fetch for them, exchange API keys if you connect any, with their secret and, where the exchange issues one, their passphrase (each encrypted with AES-256-GCM), the answers you give for an informational return (which of your exchange accounts a Spanish entity holds, and your estimate of a coin's value where no price exists), what you tell us about your transactions and accounts (that a withdrawal went to a wallet of your own, that an airdrop or reward was received for a task, referral or service, and which accounts' provider withholds Austrian KESt), if you file in the UK, the taxable income other than gains you enter for each tax year, and the tax calculations and reports we produce from all of this.
  • Waitlist: if you join the beta waitlist, your email address, your country and, if you write one, your note about the exchanges and wallets you use.
  • Payments: if you buy a plan, Stripe handles your card details; we receive only a customer reference and what you bought.
  • Technical data: your IP address, used to limit sign-in and sign-up attempts and kept for at most one hour; server logs; and error reports, which are stripped of email addresses, wallet addresses, amounts and identifiers before they are stored.

Visit counts: we count visits with Umami, an analytics tool we host ourselves on the same server. For each page view it records the address of the page (without anything after a ? or #), the site you came from, your browser, operating system, device type, screen size and language, and the country your IP address points to. It sets no cookie and stores nothing in your browser. Your IP address is used, with your browser, to tell one visit from another within the month, and is not stored. A browser that sends Do Not Track is not counted.

We do not use advertising tools, and we do not buy data about you from anyone.

Why, and on what legal basis

  • To provide the service you signed up for: importing your data, calculating your taxes, producing reports, and sending the emails the service needs (address confirmation, password reset, invitations, notices about your account). Basis: performing our contract with you (GDPR art. 6.1.b).
  • To keep the service and your account secure: rate limits, two-factor authentication, error tracking. Basis: our legitimate interest in a secure service (art. 6.1.f).
  • To see which pages are used and where visitors come from, so we can improve the site: visit counts. Basis: our legitimate interest in improving the service (art. 6.1.f); you can object at any time, and turning on Do Not Track in your browser stops it.
  • To run the beta waitlist and invite you. Basis: steps you asked us to take before a contract (art. 6.1.b); you can ask us to remove you at any time.
  • To keep the records tax and accounting law requires when you pay. Basis: legal obligation (art. 6.1.c).

We do not send marketing emails, we do not sell or rent your data, and we make no automated decisions about you that have legal or similar effects.

Who else processes it

Only service providers who need it to run TaxChain, each under a data processing agreement:

  • DigitalOcean, LLC: hosting. Our server and database are in Frankfurt, Germany.
  • Zoho Corporation: our mailboxes and the emails the app sends. Zoho stores this email in the United States.
  • Stripe Payments Europe, Ltd. (Ireland): payments, if you buy a plan.
  • Blockchain data providers (Etherscan and its sister explorers, Routescan for Avalanche, Solana's public RPC, Hyperliquid, mempool.space and litecoinspace.org for Bitcoin and Litecoin, TronGrid for Tron, Ripple's public XRP Ledger servers, Koios for Cardano, toncenter for TON, Horizon for Stellar, AlgoNode for Algorand, the Aptos Labs indexer for Aptos, Sui GraphQL for Sui, FastNEAR for NEAR): they receive the public addresses of the wallets you add (each address, never an extended key), so we can fetch their history. We do not send them your name or email.

An exchange you connect by API key receives requests signed with that key, asking for your own account's history, which it already holds; we send it nothing else. Price sources (CoinGecko, the European Central Bank) receive only asset and date queries, nothing about you. Error reports and visit counts go to tools we host ourselves on the same server.

Transfers outside the EU

Zoho stores email in the United States, and DigitalOcean, Zoho and Stripe are, or belong to, US companies. Where personal data reaches the United States, the transfer relies on the EU–US Data Privacy Framework, or on the European Commission's standard contractual clauses where a provider is not certified. You can ask us for a copy of the safeguards.

How long we keep it

  • Your account and financial data: until you delete your account. Deleting it removes everything at once.
  • Backups: 30 days, after which deleted data is gone from them too.
  • Uploaded files: deleted as soon as the import finishes, or fails for good.
  • Waitlist entries: until you join, until you ask us to remove you, or until the beta ends.
  • Payment records: as long as Spanish tax and commercial law requires (generally six years), kept by Stripe and in our accounts.
  • Rate-limit counters with your IP address: at most one hour.
  • Counts of refused requests per kind of limit and per day, which hold no IP address or account and identify no one: eight days.
  • Visit counts, which hold no name, email, account or IP address: for as long as the statistics are useful to us, and deleted on request where a visit can be told apart.

Your rights

You can access, correct, delete or export your data, restrict or object to how we use it, and withdraw any consent you gave. Two of these are built in: Settings → Your data lets you download everything as a file or delete your account. For anything else, write to privacy@taxchain.eu. We answer within one month.

If you think we have not handled your data properly, you can complain to the Spanish data protection authority, the Agencia Española de Protección de Datos (www.aepd.es), or to the authority where you live.

Security

Connections are encrypted (TLS). Passwords are hashed with bcrypt. API keys and two-factor secrets are encrypted at rest. The database is not reachable from the internet. You can turn on two-factor authentication in Settings.

Cookies

We only use what the site needs to work, so no consent banner is needed:

  • authjs.session-token: keeps you signed in.
  • authjs.csrf-token and authjs.callback-url: protect the sign-in form.
  • NEXT_LOCALE: remembers your language.
  • taxchain-year: remembers the tax year you are looking at.
  • In your browser's local storage: your light or dark theme, and the progress of a tax calculation you started.

Our visit counts use no cookies and nothing in your browser's storage.

Children

TaxChain is for adults managing their own taxes. It is not meant for anyone under 18.

Changes

If we change this policy in a way that matters, we email you before the change takes effect. The date below shows the current version.

Last updated: November 19, 2026