GDPR Data Subject Requests

The Request Was Answered. Two Records Were Missed

A data subject asks what you hold about them, or asks you to delete it. Your team searches by email and finds a CRM contact. The support tickets under a married name and the marketing record under an old email are never found, so the answer is incomplete and the data stays.

Search: [email protected]Without an identity layer
crm.contactsMaria Garcia[email protected]Found
support.ticketsM. Garcia-Lopez[email protected]Found
marketing.listMary Garcia[email protected] · 410 Elm StMissed

The erasure request is closed, and a marketing profile with her old email is still sending her offers.

The Problem

A Search Is Not An Identity

Data subject requests are usually handled by searching each system for the identifier the person gave you: an email, a phone number, a customer number. That finds the records that use exactly that identifier and nothing else.

People do not keep one identifier. They change email, change surname, use a nickname, mistype a street, or were entered by a call centre agent who spelled the name the way it sounded. Each of those records is about the same person, and each one is invisible to a search on the identifier in the request.

The gaps are hard to see from the inside. The response looks complete because every record that was found was handled. What was never found is exactly the data the request was meant to cover.

Exact Searches Miss

Search by email or ID finds records with that value and misses every other spelling of the same person.

Data Spread Across Systems

CRM, support, marketing, billing and the warehouse each hold part of the person, under their own keys.

Incomplete Without Warning

An answer can look complete while records under another name or email were never touched.

The Solution

Resolve The Person, Then Answer

Resolve people across systems before requests arrive. Match records that describe the same person, whatever name, email or address they use, and give each person one identity that lists every record behind it.

When a request comes in, find the person once, then work from the list of their records: export it for access, correct it for rectification, delete it for erasure. The scope of the request is the person, not the search term.

Data Subject Request: Maria GarciaGDPR · Chapter III rights
SARRight of accessArt. 15RTBFRight to erasureArt. 17RectifyRectificationArt. 16PortData portabilityArt. 20RestrictRestrictionArt. 18ObjectRight to objectArt. 21ConsentWithdraw consentArt. 7(3)
RequestDSAR-4821
RTBF · Art. 17Please erase all my personal dataFrom [email protected]Received by the DPO · one month to respond (Art. 12)
Resolved by Zingg6 records
ZINGG_ID · 5d20-7be1Maria Garcia, Austin
crm.contactsMaria Garcia · [email protected]
support.ticketsM. Garcia-Lopez · ticket #20931
marketing.listMary Garcia · [email protected]
loyalty.membersMaria G. · card #88213
billing.invoicesM Garcia · 410 Elm St, Austin
warehouse.eventsMaria Garcia · web sessions
Matched on name, nickname, email and address, not on the one email in the request.
Action in each system6 of 6
crm.contactsErased
support.ticketsErased
marketing.listErased
loyalty.membersErased
billing.invoicesKept · Art. 17(3)(b)
warehouse.eventsAnonymized

6 of 6 records found. 4 erased, 1 anonymized and 1 kept under a legal obligation, with the evidence for the DPO.

Resolve People Ahead Of Time

Every record about a person is linked to one identity before anyone asks.

Find The Person Once

Any identifier in the request leads to the whole identity, not a single row.

Act On The Full List

Access, correction and erasure use the complete list of records behind that person.

Where Zingg Sits

The Identity Layer Under Privacy

Zingg runs as a workload inside your data platform and gives every entity one persistent ZINGG_ID. Everything above it reads the same resolved entities.

Used by
BI & dashboardsAI agents & RAGOperational appsReverse ETLData science

Reads your tables in placeWrites golden records and ZINGG_ID backNo copies leave the platform

Your data platform
DatabricksSnowflakeMicrosoft FabricGCPAWS

The same layer powersCustomer Analytics & MarketingFinancial Crime & RiskSupply Chain & ProcurementProduct 360Master Data ManagementAI and Agentic Foundations

Every Record, One Identity

One ZINGG_ID Per Person

Zingg links records across systems to one persistent ZINGG_ID with every source record listed.

Fuzzy Matching Plus Rules

Matching learned from your labels catches name, nickname and address variations; deterministic rules on email or customer number add certainty.

Show Why Records Belong

Every link has evidence, so a reviewer can check the scope before acting. Explainability

Personal Data Stays Put

Zingg runs inside your own data platform. Personal data is not copied to another vendor to be matched.

FAQ

Data Subject Request Questions

Why do data subject requests miss records?

Because each system is searched for the identifier in the request. Records about the same person that use a different email, name or spelling never match the search.

Does Zingg handle the request workflow?

No. Zingg resolves the person and lists every record behind their ZINGG_ID. Your request process, tooling and legal review work from that list.

How does Zingg decide two records are the same person?

With matching trained on pairs your team labels, combined with deterministic rules you define. Each match can be inspected with explainability.

Does personal data leave our environment?

No. Zingg runs inside your Databricks, Snowflake, Microsoft Fabric, Google Cloud or AWS account.

Start Every Request FromThe Whole Person

Resolve people inside your own data platform, then answer requests from one complete identity.