Skip to main content
SQLOZ
Chapter 20 DBA & Production Safety

Chapter 20: OzMask - PII Anonymizer

Info: This chapter explains automatically masking personal data (PII) such as email, phone, identity and card numbers in live data, together with the related clipboard and export safety restrictions.

In this chapter:

20.1 Overview

The plaintext display of personal data such as customer identity, card, phone, email and passwords in live databases creates two risks:

  1. Legal risk (GDPR/KVKK): Displaying personal data on an unauthorized employee’s screen is a compliance violation and can incur fines.
  2. Data-leakage risk: Sensitive data can leak during screenshot sharing or shoulder surfing.

OzMask instantly masks sensitive data in the live data grid, aiming for compliance and zero data leakage.

20.2 Automatic Sensitive Column Detection

While reading the data, OzMask analyzes column names and data patterns to detect and automatically mask sensitive fields.

Data TypeExample
Email address (email, mail)ozkan@ozcanyazilim.com.tr → o***n@ozcanyazilim.com.tr
Phone number (phone, gsm, mobile)05358779014 → 0535***9014
Card number (card_no, credit_card)4543 1234 5678 9012 → **** **** **** 9012
TC/SSN/ID number (tckn, ssn, tax_id)12345678901 → 123*****901
Password / hash (password, secret)Fully hidden (******)

20.3 Enabling the Mask

  1. Click the OzMask Shield icon on the toolbar while working in the data grid to enable PII protection.
  2. Columns containing sensitive data appear masked.
  3. Export safety: OzMask masks grid display and clipboard copy paths. While masking is enabled, Copy as SQL INSERT is disabled. File exports preserve raw query data rather than silently substituting masked display strings, so every exported file must be treated as sensitive output.

Important: Masking protects the rendered grid and clipboard paths; it does not make raw database data safe to export. Verify the necessary authorization before exporting, copying, or sharing results.