Privacy policy
Last updated: 29 September 2026
This policy explains what personal data we process when you visit easybankdata.com, when you create an EasyBankData account and when you connect your banks: what we use it for, who we share it with, how long we keep it and how to exercise your rights.
1. Who processes your data
- Controller: EasySoft Tech S.L.
- Tax ID (NIF): B16885766
- Address: Calle Gil de Jaz 4, 1º N, 33004 Oviedo (Asturias), Spain
- Contact, including to exercise your rights: [email protected]
2. Two kinds of data, two roles
EasyBankData holds two kinds of data, and the role of EasySoft Tech S.L. is not the same for both:
- Your account, billing, service usage and enquiry data. We process it as controller, to sign you up, charge you, keep the service secure and reply to you.
- The bank data of the accounts you connect: balances, transactions and the people who appear in them as payers or payees. We process it on behalf of the company or professional who subscribes to the service, who is the controller. EasySoft Tech S.L. acts as processor (article 28 GDPR) and only uses it to provide the service to them.
If you appear in the transactions of one of our customers (for example, because you paid them or they paid you) and you want to exercise your rights, contact that customer. If you write to us, we will pass your request on to them and help them deal with it.
3. What data we process
3.1. Your account data
- Name and email address.
- Password, which we store transformed with a hash function and never in plain text.
- The companies you register, with their tax details (name, tax ID and address), needed to invoice you.
- Your role in each company, the permissions you have been given and, if you turn it on, two-factor authentication.
3.2. Bank data of the accounts you connect
- Identification of accounts and products: account number or IBAN, bank, product type and holder.
- Balances and transactions: date, amount, description and the category the bank assigns to them.
- The payer or payee in each transaction: name, identity document and account, when the bank provides them.
- The technical details of each authorisation, which let the accounts be updated without typing your credentials again.
- What you add: categories, rules, tags, cost centres, notes and attachments.
Your bank credentials never reach EasySoft Tech S.L.: you enter them on the screen of the account information provider, which keeps them under its own responsibility.
A bank transaction can indirectly reveal sensitive data (for example, a payment to a trade union or a clinic). We do not process it for that purpose, we do not build profiles from it and we do not use it for anything other than providing the service.
3.3. Payment data
You enter your card number on the Redsys page, and it never goes through our servers. From the card we keep the brand, the last four digits, the expiry date and an encrypted payment reference that lets us charge each period. We also keep the charges and the invoices.
3.4. Technical and usage data
- The IP address and browser details of requests, for security and usage limits.
- Each company's access log: what was viewed, by whom and with which API key.
- The API keys you generate, of which we only keep a fingerprint (SHA-256), not the key.
- The usage counts of your plan (connections, updates).
3.5. Contact form
If you write to us through the site's form, we process your name, your email, the profile you choose if you give one and the message, solely to reply to you. The message is not stored in any database: it is sent to our mailbox and stays there, with the same retention as the rest of our correspondence. We also use the IP address it is sent from, only to stop automated submissions.
3.6. Notice of sub-processor changes
If you sign up in the trust centre to be told when the list of sub-processors changes, we keep only your email (encrypted), the language we write to you in and whether you have confirmed it, solely to send you that notice. If you do not confirm with the link we send you, we delete it when the link expires. Every notice carries its unsubscribe link, and unsubscribing deletes your email.
3.7. Site visit statistics
To know which pages of easybankdata.com are visited we use Umami, a statistics tool installed on a server owned by EasySoft Tech S.L. (analytics.easysoft.es), not by a third party. It sets no cookies and stores nothing in your browser, it does not keep your IP address and it is not combined with anyone else’s data: it counts visits in aggregate (page viewed, the site you came from, country, language and type of device and browser). So as not to count the same visit twice it computes, from the IP and browser data, a code that does not reveal who you are. If your browser asks not to be tracked (“Do Not Track”), the visit is not counted. It is only on the public pages of the site, never in the panel.
4. What we use it for
- Providing the service: signing you up, connecting your banks, fetching, organising and categorising the transactions, and letting you view them, export them and read them through the API.
- Managing your subscription: applying your plan's limits, charging you and issuing invoices.
- Keeping you informed: service emails, such as account confirmation, a finished reading, a connection that needs renewing or a failed payment.
- Keeping it secure: authentication, access log, usage limits and abuse prevention.
- Supporting you: support staff can only see your company's content if you expressly authorise it, while that authorisation remains in force and without being able to change anything.
- Replying to your enquiries from the contact form.
- Telling you about sub-processor changes, if you sign up in the trust centre.
- Knowing what is visited on the site: aggregated statistics of the public pages, to improve them.
We do not sell or share your data, we do not use it for advertising, we do not build profiles and we do not use it to train artificial intelligence models. EasyBankData does not use artificial intelligence to process your bank data.
5. Legal basis
- Performance of the contract (art. 6.1.b GDPR): the account, the service and the subscription.
- Legal obligation (art. 6.1.c): invoicing and tax and accounting obligations.
- Legitimate interest (art. 6.1.f): the security of the service, abuse prevention, operational notices and aggregated statistics of site visits. For the payer and payee data in transactions, the basis is the customer's legitimate interest in reconciling their collections and payments with their accounts.
- Consent (art. 6.1.a): the contact form, where you accept this policy with a checkbox before sending the message; the notice of sub-processor changes, which you confirm with a link; and marketing communications, if you ever accept them. You can withdraw it at any time.
The authorisation you give on the provider's screen for it to read your accounts is the explicit consent required by payment services law (article 39 of Spanish Royal Decree-Law 19/2018), and it is collected by the provider. You can withdraw it at any time by disconnecting the bank.
6. Who we share it with
We do not disclose data to third parties unless required by law. To provide the service we rely on providers acting as processors or sub-processors:
- Wealth Reader, S.L., authorised by the Bank of Spain under no. 6939, which connects with your bank and delivers the account data to us, and ONNA Digital, holder of the contract with Wealth Reader through which that access is provided.
- The hosting, email and network providers.
The full list, with each company's name, location, what data it receives and with what safeguard, is on the sub-processors page, which is the single source on this matter and is updated whenever the chain changes.
Wealth Reader also acts as an independent controller for what payment services law entrusts to it: its contract with you as account holder, the safekeeping of your bank credentials, the consent you give on its screen, and its obligations towards the Bank of Spain and on anti-money laundering. That part is governed by its own privacy policy.
Card payments are processed by Redsys through our bank; both process the transaction data under their own responsibility.
Data also reaches whoever you authorise: if you generate an API key or connect an assistant through MCP, whatever is read with it reaches the system that uses it. If that system belongs to a third party (your accountant, your ERP vendor, your assistant's provider), that third party processes the data on your behalf.
7. International transfers
The data is hosted in the European Economic Area: the application in Germany, and Wealth Reader's infrastructure on Google Cloud, in European Economic Area regions (Madrid, Spain).
There are two cases in which data may leave the European Economic Area:
- Remote access by Google LLC (United States) for the maintenance and support of Wealth Reader's infrastructure, covered by the EU-US Data Privacy Framework.
- Cloudflare's network, through which the traffic of the easybankdata.com domain passes.
The details of each case and its safeguard are on the sub-processors page.
8. How long we keep it
- What the provider delivers, as it arrives: 30 days, encrypted. It is then deleted automatically.
- Balances and transactions: for as long as you are a customer. They are deleted when you leave or when you ask.
- The identity of the payer or payee (name and document): 30 days. It is then masked, and the rest of the transaction is kept so it still makes sense.
- The authorisation for each bank: until you disconnect the bank, revoke it or it expires. The bank requires it to be renewed every 180 days or sooner.
- Account data: for as long as the relationship lasts and, afterwards, for the limitation periods of any liabilities that may arise from it.
- Invoices and charges: the periods required by commercial and tax law (generally, six years).
If you cancel your subscription, your account moves to the free plan and you keep your data. If you want it deleted, write to [email protected].
9. Security
- Encryption in transit (HTTPS) for all communications.
- Bank data is stored encrypted (AES-256) with its own key, separate from the rest of the application's. Account numbers can only be searched through a fingerprint computed with a second key.
- Attachments are stored encrypted and are never served from a public address.
- Two-factor authentication available to everyone, mandatory for support staff, and enforceable by each company on its team.
- Roles and permissions per company and, if needed, per bank account.
- An access log per company, which the customer can view.
- Automatic notifications (webhooks) are signed and carry no amounts, balances, account numbers or payer or payee names.
10. Your rights
You can exercise your rights of access, rectification, erasure, restriction, portability and objection by writing to [email protected] and proving your identity. We will reply within one month (article 12.3 GDPR).
You can download your transactions at any time from the panel or read them through the API. And you can withdraw the authorisation to read your accounts by disconnecting the bank.
If you believe we have not respected your rights, you can lodge a complaint with the Spanish Data Protection Agency (aepd.es).
11. Automated decisions
The categories and rules the service applies are an aid for your accounting and you can change them. We do not take automated decisions producing legal effects on people and we do not build profiles (article 22 GDPR), and the terms of service forbid using its data to assess the creditworthiness of individuals or to make employment decisions about them.
12. Cookies
The site and the panel only use technical cookies, needed to keep the session and protect forms. We do not use advertising or tracking cookies, and fonts and stylesheets are served from our own servers. The site visit statistics (section 3.7) use no cookies. Details are in the cookie policy.
13. Changes to this policy
We may update this policy because of legal or service changes. We will always publish the current version with its date, and if the change is significant, we will tell you by email.