Privacy notice
This notice covers the docuron.ai website and the Docuron app: what we handle about whom, why and for how long. The data in the documents processed is the responsibility of the organisation that uploads them; section 4 explains this.
In force from 2026-11-20.
1. Who holds your data
The undertaking is being registered. Its details — name, registered office, registration number, tax number — will be filled in here once that is done. Until then, whoever runs this site can be reached at:
- [email protected]
2. The website: the contact form
There is one place on the website where we ask for personal data: the contact form.
| Data | Required | What it is for |
|---|---|---|
| Name | no | so that we know who we are writing to |
| Company | no | so that the answer fits your situation |
| E-mail address | yes | this is where we reply |
| What you process, and roughly how many a day | no | so that the answer says something |
Purpose: to answer your enquiry and carry on the conversation. Legal basis: steps taken at your request before entering into a contract (GDPR Article 6(1)(b)). If you do not give us your e-mail address we cannot reply; there is no other consequence.
On sending, Cloudflare Turnstile receives a check value and your IP address to screen out robots. The message then travels on as an e-mail to our help desk, where it is kept as a ticket; the website itself does not keep it.
The vulnerability report page asks for your e-mail address and the text of the report; there the basis is our legitimate interest (Article 6(1)(f)) in hearing about security faults in our service. Beyond this, the website collects nothing about you.
3. Users of the app
Your organisation’s administrator adds you to the app. There is no separate password: you sign in with a Google or Microsoft account, and on an own-server installation with the company’s Windows directory as well.
| Data | What it is for |
|---|---|
| E-mail address, how you sign in, role | so that you can sign in and see only what concerns you |
| Event log: who did what and when, from which IP address and browser | so that every step leaves a trace; the log cannot be changed afterwards |
| Support access: who, when, why | if your organisation has allowed support; every such access shows in the organisation’s own log |
Legal basis: our and your organisation’s legitimate interest (Article 6(1)(f)) in a secure app in which every step can be traced. Support access is off by default; the organisation’s owner switches it on, one access lasts at most 60 minutes, and the supporter has to give a reason.
4. The documents processed
The data in the documents — names, addresses, tax numbers — is the responsibility of the organisation that uses Docuron: it is the controller, and we work on its behalf as a processor. The terms are set out in the data processing agreement made with it.
Processing takes place in Europe. The extracted data is kept while the organisation’s contract runs; when the contract ends, we delete it within a period agreed with the organisation. The finished export is kept until it is delivered and then for the 1–7 days the organisation sets; if the destination cannot be reached, we keep trying to deliver it for up to 30 days. If the organisation has switched on the document store, exported documents are kept there for good; a document deleted from the store is removed for good after 30 days.
Hungarian invoices are looked up with the organisation’s own access to the Hungarian tax authority (NAV); we submit nothing to the authority.
If you have a question as someone named in a document, turn to the organisation that uploaded it; we help it answer.
5. Our sub-processors
These providers work on our behalf with data that may include personal data:
| Who | What they do | Where |
|---|---|---|
| Hostinger | the app’s server and database | Frankfurt, Germany |
| Google (Vertex AI) | text recognition and data extraction from the documents, with Google’s own model | a European Union region; a US parent company, under the European Commission’s standard contractual clauses (SCC) |
| Cloudflare, Inc. | serving the website, robot screening, passing e-mail on; transient and lasting storage of the documents | storage under EU jurisdiction, the data stays within the EU; a US company, under SCC |
| Zoho Corporation | help-desk ticketing | a data centre in the European Union |
Under its terms, Google does not use its customers’ data to train its models; we do not train on it either.
On an own-server installation the app and the store run on the organisation’s own server; machine processing (Google) remains the one sub-processor there.
We do not sell the data, and we pass it to nobody for advertising. If this list changes, we update it here.
6. How long we keep it
We keep an enquiry from the website and the correspondence that belongs to it for 24 months from the last message, and then delete it. The same for a vulnerability report, counted from the release of the fix.
By default the app’s event log is kept for two years and then deletes itself; technical logs are kept for 30 days. A user account is kept while the organisation’s contract runs; the account of someone who has left is disabled, not deleted, because the event log refers to it.
Section 4 covers how long document data is kept. If an enquiry turns into a contract, accounting records are kept for the period the law prescribes.
7. Cookies and measurement
- The website uses no analytics or marketing cookies: no visitor counter, no advertising code, no social embed, and so no cookie banner. The typeface is served from our own origin.
- The app uses one sign-in cookie to keep you signed in (for up to 7 days), and for a Microsoft sign-in a short-lived cookie for the duration of the sign-in. These are needed for it to work; the app does no measurement or tracking either.
- The robot screening handles the technical data it needs to work, and only comes into play when the website form is sent.
8. Your rights
Write to [email protected]. We answer within 30 days; if the request is a complex one we may extend that once, by at most two months, and we will tell you.
| Right | What it means here |
|---|---|
| Access | we write out what data of yours we hold and what for |
| Rectification | we correct what is wrong |
| Erasure | we delete what we do not have to keep; the event log, during its retention time, is the exception |
| Restriction | we keep it but work with it no further until the question is settled |
| Objection | where we rely on a legitimate interest, you can ask us to stop |
| Portability | you get what you gave us, in machine-readable form |
Requests about the document data described in section 4 are met by the organisation that uploaded the document; we help it.
If the retention time is up and we have deleted your data, our answer is that we hold no data about you. We do not keep data so as to be able to hand it over on a possible request.
If you believe your rights have been infringed, you can complain to the Hungarian supervisory authority (Nemzeti Adatvédelmi és Információszabadság Hatóság, 1055 Budapest, Falk Miksa utca 9–11., naih.hu), to the authority of the country you live in, or go to court.
9. Other
- We make no automated decisions about you and do no profiling. The machine processing of documents is about the data in the document, not about you.
- We have not appointed a data protection officer; questions reach us at [email protected].
- If this notice changes, we update it here and change the date it is in force from.