Public-records privacy policy
How Entyrix obtains, combines and republishes data taken only from public business registers in the EU. For the general privacy notice of the service see Privacy notice.
1. Data sources
We process data only from the following public business registers and their authorised aggregators:
| Country | Register | Statutory basis |
|---|---|---|
| 🇸🇰 SK | RPO, RPVS, ORSR | § 27 Obchodného zákonníka (513/1991), zákon 315/2016 Z. z. (RPVS), zákon 455/1991 Z. z. § 66a (Živnostenský register) |
| 🇨🇿 CZ | ARES, OR (Justice.cz), ISIR | zákon 304/2013 Sb. (Veřejné rejstříky), 455/1991 Sb. (Živnostenský zákon) |
| 🇫🇷 FR | SIRENE / RNE (Insee + INPI) | Code de commerce L123-1, Licence Ouverte Étalab |
| 🇬🇧 GB | Companies House | Companies Act 2006 ss. 1064-1093, FOI Act 2000 |
| 🇩🇪 DE | Bundesanzeiger / Handelsregister | HGB § 9, FamFG § 387, Bundesanzeiger Verordnung |
| 🇦🇹 AT | Firmenbuch (BMJ) | FBG § 32-39, FBDV (Firmenbuchdatenbankverordnung) |
| 🇮🇪 IE | CRO (Companies Registration Office) | Companies Act 2014 Part 2 |
| 🇳🇴 NO | Brønnøysund Register Centre | Enhetsregisterloven § 22, Foretaksregisterloven § 8-1 |
| 🇫🇮 FI | PRH (Patentti- ja rekisterihallitus) | Yritys- ja yhteisötietolaki 244/2001 § 16 |
| 🇱🇹 LT | JAR (Registrų centras), LSD EVRK | Civil Code 2.66, Statistics Lithuania open data licences |
| 🇱🇻 LV | UR (Uzņēmumu reģistrs) | Komerclikuma § 4, atvērto datu licence CC-BY 4.0 |
| 🇪🇪 EE | Äriregister (RIK) | Äriseadustik § 28-32, Estonian open data |
| 🇸🇮 SI | AJPES, FURS Seznam davčnih zavezancev | Zakon o sodnem registru, Zakon o davčnem postopku |
| 🇭🇷 HR | Sudski registar (FINA) | Zakon o sudskom registru NN 1/95 |
| 🇺🇦 UA | EDR (Ministry of Justice) | Закон № 755-IV (Про державну реєстрацію юридичних осіб), data.gov.ua open data, CC-BY 4.0 |
The full catalogue of licences and refresh intervals is on Data sources. Pan-EU layers: GLEIF (LEI), sanctions lists (EU/OFAC/UN/UK), ICIJ Offshore Leaks, EUIPO, EBA EUCLID, EIOPA, ESMA, CORDIS, TED.
2. Legal basis
Processing is based on the legitimate interest of the controller (Art. 6(1)(f) GDPR). Our legitimate interest assessments cover four documented purposes: KYC/KYB compliance, credit and commercial intelligence, sales prospecting (identification of businesses only, no contact details of natural persons), and academic and journalistic research.
Processing relies on the statutory public-register exception in every jurisdiction we cover (see the table in section 1). These registers are public by law and their content may be reused under the applicable open-data licences and reuse conditions. "Public" does not automatically mean "any further use is allowed": we apply data minimisation, purpose limitation and transparency as Recital 154 GDPR expects.
3. Why we do not notify every data subject individually (Art. 14(5)(b) GDPR)
Entyrix combines data on about 34.6 million companies and several million officers, beneficial owners and sole traders. Contacting each data subject individually under Art. 14(1) to (4) GDPR would be a disproportionate effort within the meaning of Art. 14(5)(b) GDPR, in particular because:
- We hold no contact details of natural persons. Our dataset deliberately contains no email addresses or phone numbers of natural persons (officers, beneficial owners, sole traders). This is the decisive difference from the Polish Bisnode case (a fine of PLN 943,000, about EUR 220,000, from the Polish supervisory authority UODO), where the controller held such contact details.
- The source registers are public by law, and data subjects were informed of that public status when they were entered in the register (§ 27 of the Slovak Commercial Code and the national equivalents).
- Alternative measures under Art. 14(5)(b) are in place: public information (this page and the privacy notice), a request form for data subjects, an access log for every request, and technical safeguards.
The detailed proportionality assessment is an internal document and is available on request.
4. Specific technical safeguards
- Sole traders are filtered out of the public autocomplete.
/public/autocompletewithout an API key returns no records of natural persons running a business; those are only available through the authenticated API, limited to the purposes set out in the terms. - Credit grade only for confirmed legal entities. On the public surface without sign-in, a credit grade is shown only for confirmed legal entities (
entity_type='legal_entity'). For natural persons the grade stays hidden (a measure following CJEU C-634/21 SCHUFA). - Beneficial owners' dates of birth are reduced to the year. The full date of birth is not available through any public or authenticated API endpoint.
- Tax debtors are only reachable by looking up a specific company. Every read of the debtor table is bound to
WHERE company_id = <company id>: no endpoint lists, searches or ranks debtors. A record we could not match to a company in our database (more than half of them) is therefore not reachable by any route. If the matched company belongs to a natural person, the natural-person gate applies as well: its profile returns410 Goneand the record is excluded from search surfaces. - Enforcement proceedings against natural persons from the Slovak enforcement register are marked
internal_use_only=TRUE. Every read filters oninternal_use_only = FALSE, so they reach neither the public API nor the company profile. (This flag concerns the enforcement dataset, not tax debtors; those are protected by the mechanism above.) - Access log for every request (
gdpr.access_log) on the routes that return personal data, including searches that return many subjects at once. Supports the record of processing (Art. 30) and traceability (Art. 32(1)(d)). - Rate limits per API key by plan (Free 1,000 requests per month and 120 per minute), without a key ~600 requests per minute per IP; the terms forbid bulk extraction and technical controls work against mass scraping.
- IP hashing: we never store raw IP addresses; SHA-256 with a salt that rotates daily.
5. Rights of data subjects
Even though the source registers are public, as a data subject you have these rights against Entyrix:
- Right of access (Art. 15 GDPR): you can ask for a copy of the data we process about you.
- Right to rectification (Art. 16 GDPR): if the data is wrong, we correct it within 30 days. Note that the primary correction has to happen in the source register; we pick it up within 7 days of the next refresh.
- Right to erasure (Art. 17 GDPR): erasure is limited, because we have to keep our copy consistent with the public register. We erase when the source register removed the record, OR the legal ground for processing has ceased, OR your objection outweighs the legitimate interest.
- Right to object (Art. 21 GDPR): you can object to processing based on legitimate interest. We assess whether your particular situation changes the balance of interests.
- Right to restriction of processing (Art. 18 GDPR): while an objection is being assessed.
- Complaint to the supervisory authority: you can complain to the Slovak Office for Personal Data Protection (dataprotection.gov.sk).
6. How to send a request
To exercise any of these rights, contact us:
- Email: [email protected] (subject:
DSAR Public Records) - Request form: privacy notice, requests
- Data protection: [email protected] (no data protection officer is appointed; the address is a mailbox for requests, including contesting a credit grade under Art. 22(3) GDPR, personality rights claims and corrections of inaccurate data)
- Reporting illegal or incorrect content under Art. 16 DSA (wider: copyright, sanctions and other types): reporting page, [email protected]
We reply within 30 calendar days (Art. 12(3) GDPR). For complex or numerous requests we may extend this by a further 2 months and will tell you so.
Before we disclose any data we need to verify your identity (name plus a national ID or company ID, and one further identifying detail), as Art. 12(6) GDPR allows.
7. Controller contact details
Controller: Inger s.r.o., company ID 50178831, registered seat: Azalková 6524/10, 974 01 Banská Bystrica, Slovak Republic (controller details).
Email: [email protected]
Data protection officer: not appointed (Art. 37 GDPR: Entyrix does not meet the criteria for a mandatory appointment; this is reviewed as part of the full data protection impact assessment).