Floemdata
BI & Reporting

KVKK in BI: Personal Data Visibility

Personal data in BI reports should be considered under Turkish KVKK. We explain the data security duty and access-rule design. Not legal advice.

Floemdata · · 3 min read
A data table with one fully masked personal-data column and an arrow to a purple shield with a keyhole

This article is not legal advice. Clarify your own situation with a lawyer and a personal-data-protection specialist. The legal information below is taken from the pages of the Turkish Personal Data Protection Authority (kvkk.gov.tr) and mevzuat.gov.tr; points we could not verify are marked.

The law: 6698

Personal data protection in Turkey is regulated by Law No. 6698 on the Protection of Personal Data (KVKK); the law was published in the Official Gazette dated 7 April 2016, number 29677 (mevzuat.gov.tr). What the law counts as 'personal data' (Article 3) and its processing principles (Article 4) are not verified in this article; read those articles in the text of the law.

The data security duty (Article 12)

According to the KVKK's own page, Article 12 of the law places three duties on the data controller: to prevent unlawful processing of personal data, to prevent unlawful access, and to ensure the data is safeguarded. All necessary technical and administrative measures must be taken for this; the measures must fit the organization's structure, activities and risks, and there is no single model. When third parties process the data, responsibility is shared and the data controller has to carry out audits.

Practical questions in BI

The following are design questions, not legal requirements.

  • Is personal data really needed in the report? For most reports totals and trends are enough; show a group or region instead of customer name and code.
  • Who should see which row? Write rules up front, such as a sales rep seeing only their own customers and a regional manager only their region.
  • Export and sharing: even if dashboard visibility is restricted, a file exported to Excel can bypass the rule. Tie exports to the rule as well.
  • Who looked at what? Keep an access log; being able to see an unusual access afterwards is a safeguard.
  • Testing and development: do not copy real personal data into the test environment.

Where Floemdata stands

Panel access in Floemdata Analytics comes in two kinds: the administrator login sees all companies in the installation; an access key (Bearer token) shows only that key's company. So the separation is at company level. A row-level or person-level visibility rule (for example 'a rep sees only their own customers') is not a verified feature (not verified). We also make no claim about the product's compliance with KVKK.

To get started, split your reports into two lists, 'contains personal data' and 'does not', and write the access rule for the first list. Sources: KVKK, data security obligations, mevzuat.gov.tr, Law No. 6698.

← All guides