> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.3/governance-catalog/governed-data-query.md).

# Governed Data Query

Governed Data Query (GDQ) is a tool that helps organisations retrieve customer information, precisely Personally Identifiable Information (PII), from their databases in compliance with GDPR and other regulations. For instance, when a customer subscribes to a service from a vendor, such as a cell phone provider, all their personal information is stored in the provider's databases. The provider's IT team must develop processes to retrieve this data from various sources if the customer requests to view or delete all their information. OvalEdge simplifies this by cataloging the data, allowing the IT team to classify and audit privacy information using the Data Classification module. Privacy data can be grouped under business terms created for each domain, and appropriate data objects can be associated with these terms. Sensitive data can be masked or restricted when creating terms. When users request the discovery and deletion of their information, the provider can use the GDQ module. The IT team can build search patterns around business terms and discover associated data objects, efficiently gathering the customer's information across the organisation.

Examples of Personal Data found in Data Sources:

* First name, last name/surname, maiden name
* Email address
* Home address (street, zip, postal code, city)
* Phone number
* Photo
* Date of birth
* Bank account number
* Credit card number
* National Identification Number, (Social) Insurance Number, Social Security Number
* Taxpayer Identification Number, Tax File Number, Permanent Account Number
* Passport number, national ID number, driver's license number
* Vehicle registration plate number
* Employee number
* IP address
* Location data
* Handwriting
* Login
* Password
* Social media profile IDs/links
* Mobile device IDs
* Employment history, job title
* Education History
* Payroll data
* R & D data
* Personal Medical Data

## Business Glossary Domain 

A domain in data governance is a logical grouping of related data based on business functions or subjects (e.g., Customer Data, Employee Data, Financial Data). Domains help structure and segregate data governance activities, ensuring compliance and security.

**What is a Privacy Domain?**

* A Privacy Domain focuses on managing sensitive customer data (PII) in compliance with GDPR, CCPA, and HIPAA regulations.

**Why is it important?**

* Organisations must track and control who accesses privacy-related data and how it is used.

Example:

* A customer requests the deletion of all their data under GDPR. The Privacy Domain ensures that all relevant PII across systems is identified.

***

Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA USA


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ovaledge.com/release8.3/governance-catalog/governed-data-query.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.