Information obligation

Information on the processing of personal data

for people whose data was obtained from public sources  ·  Article 14 GDPR  ·  effective from 2 November 2026  ·  version 2026-11-02  ·  Polska wersja

Who this notice is for

If a business has checked its counterparty using LegitView.eu and you appear in a public source as:

— then we have processed data about you that is publicly available in that source. In line with Article 14 GDPR we explain below where we obtained it, why and on what basis we process it, for how long, and what rights you have.

As briefly as possible: we do not build our own database about people. We retrieve data from public sources on demand, at the moment a single check is performed, for a single report for a single business that wants to know who it is dealing with. We do not sell that data, we do not use it for advertising, and we do not combine it with data from data brokers or social media.

If you are our user — that is, you have an account with us — the Privacy Policy applies to you; it describes processing connected with using the Service. This page is for people whose data appeared in a check result.

1. Data controller

DAWID JUSTYŃSKI (sole proprietorship)

ul. Mostowa 33, 05-800 Pruszków, Poland

VAT ID (NIP): 5342688114  ·  Statistical number (REGON): 540490658

E-mail for data protection matters: rodo@legitview.eu

General e-mail: info@legitview.eu  ·  Phone: +48 535 777 646

The controller has not appointed a Data Protection Officer, because the conditions in Article 37(1) GDPR are not met. All data protection matters are handled personally by the controller — write to rodo@legitview.eu.

2. Where we obtained your data

Exclusively from publicly available sources in the countries where we provide the Service, and from information supplied to us by the business ordering the check. These are:

We provide the Service for entities from fourteen countries: Poland, the Czech Republic, Slovakia, Lithuania, Latvia, Estonia, Bulgaria, Romania, France, Serbia, Slovenia, Spain, Italy and Croatia. Which sources concern you depends on the country of the entity that was checked.

Want to know exactly which source a given piece of information about you came from? We will tell you. Each data point in a report carries the name of the source, a link and the time of retrieval, and we will state it explicitly in response to a request under Article 15 GDPR. We do not, however, publish a consolidated list of all the sources we use — the manner and extent of their use is a trade secret of our business.

What we do not do: we do not buy data from data brokers, we do not take it from social media, we do not use marketing databases, and we do not process your image, biometric data, credit history, or data concerning health, opinions or membership of organisations.

3. What data about you we process

Depending on which source you appear in and in what role:

National identification number (PESEL) — partial form only

On screen, in the report and in the stored snapshot of a check, the PESEL number is masked (for example 6711***40). Masking is performed by our server, before the data is stored and before it reaches the browser of the person who ordered the check.

In extracts from the Polish National Court Register the number is masked by the register itself — only the first digit is disclosed. We pass it on exactly in that form and we do not reconstruct the missing digits.

The full number exists in only two places, where removing it would destroy the evidential value of the document: in the raw response of the source stored in the evidence store, and in the original extract from the register of beneficial owners, downloaded from that register’s own server and not modified by us. Both stores have file-system level access restrictions and are deleted after 365 days.

We never process identity card numbers or any other identity document numbers.

4. Why and on what basis

PurposeLegal basis
A one-off counterparty check ordered by a business: querying the sources, showing the result on screen and generating a reportArticle 6(1)(f) GDPR — the legitimate interests of the controller and of the ordering party in securing business transactions and preventing fraud. Recital 47 GDPR expressly names fraud prevention as a legitimate interest.
Checking a vehicle’s insurance and roadworthiness test on the basis of a registration plate supplied by the ordering partyArticle 6(1)(f) GDPR — the same interest. In road transport the absence of valid insurance is one of the principal risks for the party commissioning the carriage.
Checking the domain and e-mail address indicated by the ordering partyArticle 6(1)(f) GDPR — detecting impersonation of existing companies, a typical fraud mechanism in freight forwarding.
Storing a snapshot of the check and the evidence package (raw source responses)Article 6(1)(f) GDPR — documenting what a source showed and when. This also works in your favour: if you contest a result, we are able to reconstruct exactly what the source returned at the time.
Handling data protection requests and correspondenceArticle 6(1)(c) GDPR — a legal obligation under Articles 12 and 15–22 GDPR.
Establishing, pursuing and defending claimsArticle 6(1)(f) GDPR
Tax and accounting obligations (where the report was produced under a paid service)Article 6(1)(c) GDPR — accounting and tax legislation.

We do not use your data for marketing purposes. We do not sell it, we do not share it with anyone for the purpose of building databases, and we run no marketing on it.

Legitimate interests assessment

Before we began processing we carried out the balancing test required under Article 6(1)(f) GDPR, taking into account the European Data Protection Board’s Guidelines 1/2024 (version adopted for public consultation on 8 October 2024), and we update it as the Service develops. Our conclusions:

We keep the documentation of the test and present it to the Polish supervisory authority on request.

5. How long we keep the data

WhatHow long
Snapshot of the check stored in the ordering party’s history3 years from the check; after 12 months the record moves to an archive and after 3 years it is deleted
PDF report stored on our side12 months
Evidence package — raw source responses365 days
Original documents downloaded from sources365 days
A report downloaded by the ordering party onto their own deviceOutside our control — the ordering party is an independent controller of it and decides how long to keep it
Audit log (who performed which operation and when, IP address)3 years plus a one-year buffer — the limitation period runs to the end of the calendar year
Technical server access logsUp to 30 days, then rotated
Your data protection request and our reply3 years from resolution — so that we can show we replied on time
Database backups3 daily and 4 weekly copies (restore going back roughly one month), then overwritten

After those periods the data is deleted. Erasure at your request is carried out irrespective of the periods above, to the extent that it does not conflict with a legal obligation or with the defence of claims.

6. Who else sees this data

The complete and current list of recipients is in the Privacy Policy, and that list is the only binding one.

Transfers outside the European Economic Area

Your data as a person listed in a source is processed exclusively on servers within the EEA. The egress addresses used when querying sources are also within the EEA.

The only case of data leaving the EEA concerns a check of a Serbian entity: the query containing the entity identifier or a registration plate then goes to a register in Serbia. This is the sending of a query, not the transfer of a data set, and it takes place at the request of the person ordering the check (Article 49(1)(b) and (c) GDPR). Serbia is a party to Convention 108+ and has data protection legislation modelled on the GDPR.

Visit statistics and, formerly, typefaces — the only elements connected with the USA — concerned solely people visiting our public website of their own initiative, never people whose data we retrieve from sources. Since 1 November 2026 we serve typefaces from our own server, so that element has fallen away as well.

7. Your rights

You can exercise them at any time, free of charge:

Access (Article 15)The right to know what data about you we process, where we obtained it and who we disclosed it to — and to receive a copy
Rectification (Article 16)The right to have inaccurate data corrected or incomplete data completed
Erasure (Article 17)The right to be forgotten — in particular where the data is no longer necessary or you have successfully objected
Restriction (Article 18)The right to have processing suspended, for example while the accuracy of the data is checked
Portability (Article 20)The right to receive the data in a structured format — applies to processing based on a contract or consent
Objection (Article 21)The right to object to processing based on legitimate interests, on grounds relating to your particular situation
Important as regards rectification. We do not operate a register and cannot change the data at its source. If the data in a source is incorrect, it has to be corrected with the operator of that source — we show what the source returns. We can, however, correct or delete what we hold on our side, and record your position alongside the result.

Deadlines. We reply without undue delay and in any case within one month of receiving the request (Article 12(3) GDPR). In particularly complex cases we may extend that period by a further two months — we will then inform you of the extension and its reasons within the first month.

Identity verification. So as not to disclose data to an unauthorised person (Article 12(6) GDPR), where we have reasonable doubts we may ask for additional information — only to the extent necessary for identification, for example the identification number of the entity you are connected with. We never ask for scans of identity documents.

8. Right to lodge a complaint

If you believe that we process your data unlawfully, you have the right to lodge a complaint with a supervisory authority. The authority competent for us is:

President of the Personal Data Protection Office (Prezes UODO)

ul. Stawki 2, 00-193 Warsaw, Poland

uodo.gov.pl

You may also lodge a complaint with the supervisory authority of your habitual residence or place of work (Article 77 GDPR). For the countries where we provide the Service these are, respectively: Úřad pro ochranu osobních údajů (Czech Republic), Úrad na ochranu osobných údajov (Slovakia), Valstybinė duomenų apsaugos inspekcija (Lithuania), Datu valsts inspekcija (Latvia), Andmekaitse Inspektsioon (Estonia), Комисия за защита на личните данни (Bulgaria), ANSPDCP (Romania), CNIL (France), Informacijski pooblaščenec (Slovenia), AEPD (Spain), Garante per la protezione dei dati personali (Italy), AZOP (Croatia). In Serbia the competent authority is the Poverenik za informacije od javnog značaja i zaštitu podataka o ličnosti.

9. Automated decisions and the right to human intervention

The summary of a check result — data consistency, discrepancies, gaps — is produced by deterministic rules comparing data from independent sources. We do not use machine learning, statistical models or artificial intelligence for this. We use machine learning models for technical purposes only, to read captcha-type protections on source websites, and they have no influence whatsoever on the result.

We do not take decisions about you based solely on automated processing that produce legal effects concerning you or similarly significantly affect you (Article 22(1) GDPR). A report organises information, but the assessment and the decision — for example whether to enter into a contract — are taken by a human on the side of the business that ordered the check.

We are mindful of the judgment of the Court of Justice of the EU of 7 December 2023 in case C-634/21, according to which a third party’s scoring may be treated as an automated decision where the decision-maker routinely and substantially relies on it. That is why we advise ordering parties to assess every result themselves, and why we grant you the rights below regardless of how our mechanism is legally classified.

If you believe the result is wrong or has harmed you — for example it led to a refusal to contract with you — you may ask us for:
  • human review of the result,
  • the opportunity to express your own point of view and to have it recorded alongside the result,
  • contestation of a specific piece of information or of its interpretation in the report.
Channel: rodo@legitview.eu. We apply the standards of Article 22(3) GDPR accordingly and reply within the period set by Article 12(3).

A principle we follow: silence from a source is not information that a fact does not exist. We mark missing data as missing data, not as a negative result concerning you.

10. Were you required to provide this data

No — and you did not provide it to us. We obtained it from a public source in which it was disclosed by operation of law. It was the legislator, not us and not you, who decided that this information is public.

If you want to change or remove data at the source, the right route is to contact the operator of that source — it is the operator that decides on the content of the entry. We can only change what we hold on our side.

11. Version history

VersionDateWhat changed
2026-11-02 2 November 2026 First English version, published together with version 2026-11-02 of the Polish text, which describes the actual scope: fourteen countries (including Italy) instead of Polish sources only, categories of sources instead of a list of registers, vehicle and insurance data, domain and e-mail data, the evidence package and original documents; retention periods aligned with the Privacy Policy; the handling of the PESEL number clarified; supervisory authorities of all the countries covered added.
Language. This document is a translation provided for convenience. In the event of any discrepancy, the Polish version prevails: Informacja RODO.