Legal
Privacy Policy
Effective 23 September 2026
This policy explains what personal data Crypto Tax Report (CTR) collects, why, who it is shared with, how long it is kept, and the rights you have under the EU General Data Protection Regulation (GDPR). It applies alongside our Terms of Service.
1. Who is responsible
The data controller is Baltas Mazgas, registered in Lithuania, company code 307574335. Contact for anything in this policy: [email protected].
2. What we collect and why
We only process data CTR needs to work, to keep accounts safe, and to meet our legal obligations.
| Data | Why we process it | Legal basis |
|---|---|---|
| Account: email address, name, password (stored only as a bcrypt hash), language, tax country and settings | To create and run your account and calculate your figures under the right country's rules | Contract (Art. 6(1)(b)) |
| Google or Facebook sign-in: the provider's account id, and the verified email and name it reports | To sign you in and to link that identity to your account. We never receive your provider password. | Contract |
| Transaction history you import: CSV files, exchange data read through API keys, public blockchain activity for wallet addresses you add | The core of CTR: cost-basis accounting, tax figures, reports, reconciliation and harvesting tools | Contract |
| Exchange API keys | To read your exchange history on your behalf. Stored encrypted (AES-256-GCM); the keys must be read-only. | Contract |
| Security and audit log: logins and failed logins, IP address, browser user agent, sensitive account actions (connecting an exchange, adding a wallet, exporting data, creating an accountant link) | To detect account takeover, brute-force attempts and abuse, and to show you what happened on your account | Legitimate interest in security (Art. 6(1)(f)) |
| Accountant links: the label and optional email you enter, when the link was opened and from which IP address | To let you share a read-only view with your accountant and see when it was used | Contract; legitimate interest |
| Subscriptions, payments and service credit: the plan or feature purchased, tax country, subscription status and period, amounts, VAT, discounts, credit balance, and Stripe customer, subscription, invoice and payment identifiers | To process purchases, grant paid access, show payment history and invoices, account for service credit, and meet legal accounting obligations | Contract; legal obligation (Art. 6(1)(c)) |
| Bug reports: your description, page URL, host, language, browser information, administrator response and any screenshots you choose to attach | To investigate the issue you report, reply and tell you its outcome | Contract; legitimate interest in improving and protecting the service |
| Newsletter signup: email address and the site it was entered on | To email you product news you asked for | Consent (Art. 6(1)(a)) — withdraw at any time |
| Support correspondence | To answer you | Legitimate interest |
We do not sell personal data, do not build advertising profiles, and do not use your transaction data for anything other than providing CTR to you.
3. Cookies and analytics
Session cookie. A signed, HTTP-only cookie keeps you logged in. It is strictly necessary and set only when you sign in.
Preferences. Small settings such as your selected tax year, table columns and filter choices are kept in your browser’s local storage and never sent to us as tracking data.
Analytics and marketing. Google Analytics is on by default. On every page we load Google Tag Manager and use Google Analytics for usage and conversion measurement (pages visited, approximate location, device type and actions in the product), including while you are signed in: by creating an account and using CTR you accept that analytics and marketing cookies are enabled by default, before you have answered the cookie banner. No transaction history, names or email addresses are sent to it. You can turn it off at any time, and it is a real switch: open below, untick Analytics and save, and the tag stops running, the cookies it set are cleared and nothing further is sent. Marketing cookies are on by default in the same way. Google Ads uses conversion data for advertising attribution and personalization from your first page unless you turn it off, which you do exactly as above: open , untick Marketing and save. Google may set cookies and processes the data under its own terms. Your choice is stored in this browser for this website for 180 days, and if you are signed in when you make it we also record it on your account, so that we can show you what you selected and evidence it; the copy in this browser is what governs this browser. Withdrawing stops future tracking; it does not erase data already sent to Google.
4. Who we share data with
We use a small number of service providers, each only for the purpose named:
- Hosting. CTR and its database run on a server we rent in a European Union data centre. Backups are kept on that server.
- Exchanges and blockchain data providers. When you connect an exchange or add a wallet, we send that exchange or a public blockchain explorer only what is needed to read your history (your API key, or the public address). They see the request come from us.
- Market price providers (for example CoinGecko and CoinMarketCap). We request prices for asset symbols and dates. No account or personal data is included in those requests.
- Google and Facebook, only if you choose to sign in with them. They learn that you used your account to sign in to CTR.
- Stripe. If you buy a plan, an additional feature or service credit, we send Stripe your email address, the purchase selected and the amount due. You enter payment-card details directly in Stripe's environment; we do not store the full card details. We retain payment-related Stripe identifiers, subscription status and invoice data.
- AI providers (OpenAI, Anthropic or Google Gemini), only when you use “Ask AI about this transaction”. That transaction's details are sent to the provider we currently use, on our own account with them — you no longer supply a key of your own — and are processed under that provider's terms. Nothing is sent unless you press the button, and each answer is paid from your account credit.
- Email delivery. Transactional emails (accountant invitations, security notices, newsletter) go through our SMTP provider.
- Google Analytics, as described in section 3.
- Your accountant, only through a read-only link you create yourself and can revoke at any time.
We disclose data to authorities only where the law requires it.
5. International transfers
Your account and transaction data are stored in the EU. Some providers above, including Google, Facebook, Stripe, OpenAI, Anthropic, CoinGecko and CoinMarketCap, are established or process data in the United States. For transfers outside the European Economic Area, we rely on an applicable European Commission adequacy decision, including the EU–US Data Privacy Framework for participating organisations, or the European Commission’s Standard Contractual Clauses. We send only the necessary data described above.
6. How long we keep data
- Account and transaction data: for as long as your account exists. You can delete every transaction, disconnect every source and remove saved keys yourself at any time; when your account is closed the data is deleted.
- Subscription, payment and service-credit records: while your account exists. The payment provider may retain payment and invoice data for longer where required by its legal obligations.
- Bug reports and attached screenshots: while your account exists; they are deleted with the account when it is closed.
- Security and audit log: kept while the account exists so you and we can review activity on it, and for a reasonable period afterwards to investigate abuse.
- Login-attempt and rate-limit counters: a few hours to days, then deleted automatically.
- Upstream request monitoring (which of our providers we called, how fast, whether it failed): individual records for 7 days, hourly totals for 90 days. These contain no transaction data.
- Accountant links: until they expire (at most one year) or you revoke them; the record of when a link was used stays with the account.
- Newsletter address: until you unsubscribe.
- Backups: rotated on a short cycle, so deleted data leaves backups within a few weeks.
7. Your rights
Under the GDPR you can ask us at any time to:
- access the personal data we hold about you;
- correct it (most of it you can edit yourself under Settings);
- delete it (close your account, or delete your transactions and connections yourself);
- receive a copy in a portable format — the Transactions page exports your full history as CSV, and your reports as PDF;
- restrict or object to processing based on our legitimate interests;
- withdraw consent where processing is based on it (the newsletter, and optional analytics and advertising cookies) without affecting what was done before.
Write to [email protected]; we answer within one month. You also have the right to complain to a supervisory authority — in Lithuania, the State Data Protection Inspectorate (VDAI, vdai.lrv.lt) — or to the authority in the EU country where you live.
8. How we protect data
- All traffic is encrypted in transit (HTTPS).
- Passwords are stored only as bcrypt hashes; exchange API keys are encrypted at rest with AES-256-GCM.
- Exchange connections require read-only API keys; wallet imports use public addresses only — we never ask for a private key or seed phrase.
- Repeated failed logins lock the account and the source address temporarily; sensitive actions are rate-limited and logged; automated monitoring raises alerts on suspicious patterns.
- Changing your password signs you out on every device; a suspended account stops working within minutes.
- Accountant links are random 256-bit tokens of which only a hash is stored, and are read-only by construction.
9. Children
CTR is for adults. We do not knowingly collect data from anyone under 18; if you believe a child has created an account, contact us and we will delete it.
10. Changes to this policy
We may update this policy as CTR changes. The effective date at the top shows the current version; for material changes we will notify registered users by email or an in-app notice.
11. Contact
Questions or requests about your data: [email protected].