Privacy
Privacy Notice
How the Eterano private beta handles personal data, including information received through Open Banking.
Eterano is temporarily operated by Nikola Nachev in Denmark. No Eterano company has been incorporated yet. The service is not currently offered as a public commercial Open Banking service.
1. Who is responsible
For Eterano account administration, service security, product communications and the operation of this private beta, the data controller is:
Nikola Nachev
Individual operator of Eterano · Denmark
Email: privacy@eterano.com
No company registration number applies at this stage.
The email address above is the primary privacy contact. A postal contact channel can be provided where legally required or reasonably necessary to handle a verified request.
2. Scope and data-protection roles
This notice applies to the Eterano application, its public order and payment pages, support communications and connected Open Banking features.
When Eterano is the controller
Eterano decides how data is used for user accounts, authentication, security, service administration, operational notices and direct support.
When a business user is the controller
A business using Eterano normally decides why and how its customer, order, invoice, receipt and bookkeeping data is handled. For that data, the business user is normally the controller and Eterano acts as its service provider or processor to the extent required by applicable law. Customers should first contact the business they dealt with when their request concerns that business's records.
3. Personal data we process
| Category | Examples | Source |
|---|---|---|
| Account and identity | Email address, user ID, authentication events, workspace membership and role. | You, invited workspace administrators and the authentication service. |
| Business and customer records | Business profile, contact details, products, availability, customer names, emails, phone numbers, addresses, notes, orders and uploaded inspiration images. | Business users and customers submitting public forms. |
| Invoices, payments and accounting | Invoice and receipt details, payment status, refunds, journal entries, VAT settings, fiscal periods, bank reconciliation decisions and audit history. | Business users, payment providers and records generated by confirmed actions. |
| Receipt documents and AI suggestions | Uploaded receipt or invoice files, extracted supplier/date/amount/VAT fields, confidence scores and corrections. | Files uploaded by the user and, only when requested, the AI scanning provider. |
| Open Banking data | Institution and account labels, account identifiers or masked identifiers, currency, balances, booked transactions, counterparties, references, consent status and expiry, synchronization health and reconciliation actions. | Your bank and Enable Banking after your explicit authorization. |
| Communications | Support messages, privacy requests and service emails. | You, Eterano and email delivery providers. |
| Technical and security data | IP address, browser/device information, timestamps, request and error logs, security events and essential local preferences. | Your device, hosting, database and security systems. |
Eterano does not intentionally request special-category personal data. Do not place sensitive health, political, religious or similar information in free-text fields or uploads unless it is strictly necessary and lawful.
4. Why we use data and the legal bases
- Provide the requested service: create accounts and workspaces, store business records, issue invoices, process confirmed payments, synchronize authorized bank data and provide reconciliation tools. The basis is performance of a contract or steps requested before entering one.
- Operate and secure the beta: authenticate users, prevent abuse and duplicates, troubleshoot failures, maintain audit records and protect the service. The basis is legitimate interests in operating a secure and reliable service.
- Meet legal obligations: respond to lawful requests and maintain records where accounting, tax, fraud-prevention or other law requires it.
- Communicate: send transactional messages, consent-expiry or repeated-sync-failure alerts and answer support/privacy requests. The basis is contract, legitimate interests or legal obligation as appropriate.
- Optional features: use AI receipt scanning, connect an Open Banking account or enable optional notifications only when the user deliberately activates the feature. Where consent is the appropriate basis, it can be withdrawn for future processing.
Where legitimate interests are used, Eterano balances those interests against the rights and reasonable expectations of the people concerned.
5. Open Banking
Eterano never asks for or stores your online-banking password, PIN or authentication codes.
Authorization takes place with your bank and Enable Banking. You choose the account and information to share.
After authorization, Eterano receives the account information made available under the consent. It is used to import booked transactions, prevent duplicate imports, monitor connection health and suggest possible matches with invoices, payments or expenses.
Synchronization and matching suggestions do not change bookkeeping by themselves. A user must review and confirm a match. The separate confirmation of an invoice payment may create the normal payment posting, subject to accounting-period locks and the user's explicit confirmation.
You can disconnect the connection in Eterano and may also revoke bank consent through your bank where supported. Revocation stops new collection but does not automatically erase information already lawfully imported or records that must be retained.
During the present beta, Open Banking uses Enable Banking's sandbox or a restricted, non-commercial personal pilot. It is not available for general public or business-account use until the required commercial agreement and verification are complete.
6. Who receives data
Eterano does not sell personal data. Data is shared only as needed to provide, secure or legally operate the service. Current provider categories include:
- Supabase: authentication, database, file storage and server functions.
- Netlify: website hosting and delivery.
- Enable Banking: bank authorization and delivery of account information when Open Banking is connected.
- Stripe: payment processing when a Stripe payment feature is used. Stripe may act as an independent controller for parts of its regulated processing.
- Resend: delivery of transactional and operational emails.
- One.com: hosting of the privacy mailbox and related email communications.
- OpenAI: analysis of a receipt or invoice only when a user initiates AI receipt scanning; the result remains a suggestion that the user must review.
Data may also be disclosed to professional advisers, authorities or courts where necessary to establish or defend legal claims, comply with law, or protect users and the service.
7. International transfers
Some providers may process data outside Denmark or the European Economic Area. Where GDPR transfer rules apply, Eterano relies on an adequacy decision, approved standard contractual clauses or another lawful safeguard, depending on the provider and processing location. Contact us to request more information about safeguards relevant to your data.
8. How long data is kept
Data is kept only as long as needed for the purposes above, taking account of account status, the user's deletion request, legal obligations, dispute and fraud-prevention needs, and secure backup cycles.
- Account and workspace data is generally kept while the beta account remains active.
- Open Banking consent and synchronization metadata is kept while the connection is active and afterwards only as needed for audit, security or legal purposes.
- Imported bank rows and reconciliation history may form part of a business's accounting evidence and can be subject to statutory retention duties.
- Abandoned temporary AI receipt uploads are removed when practical; saved receipt documents follow the business record's retention period.
- Security and operational logs are kept for a limited period proportionate to troubleshooting and abuse prevention.
Deletion from active systems may not immediately remove encrypted backup copies. Backups are isolated and expire under the applicable backup cycle.
9. Your rights
Subject to the GDPR and any applicable exceptions, you may request access, correction, deletion, restriction, portability or objection. Where processing is based on consent, you may withdraw it for the future. You may also complain to a data-protection authority.
For Denmark, the supervisory authority is Datatilsynet (the Danish Data Protection Agency).
Send requests to privacy@eterano.com. Identity verification may be required before disclosing or changing data. If the request concerns records controlled by a business using Eterano, Eterano may refer the request to that business or assist it in responding.
Automated suggestions
Eterano may rank possible reconciliation matches or extract fields from a receipt. These are reviewable suggestions. They do not produce legal or similarly significant effects without user confirmation.
10. Security, children and changes
Eterano uses access controls, encrypted transport, restricted server credentials, tenant separation, audit history, duplicate protection and confirmation gates. No online service can guarantee absolute security; suspected incidents should be reported promptly to the privacy email.
The beta is intended for adults and business administration. It is not directed to children.
This notice may be updated as Eterano changes or a company is incorporated. Material changes will be identified by a new effective date and, where appropriate, communicated in the application.
11. Contact
Privacy questions or rights requests
Nikola Nachev · Individual operator of Eterano · Denmark
