32 docs tagged with "Integrations"

For Direct Contact Processors managing multiple requests from DataGrail simultaneously, we provide a configuration option to send processors a weekly email summary with their active requests.

Invoke internal or third-party REST APIs to fulfill data subject access, deletion, opt-out, and identifier retrieval requests.

The Internal Systems API specification defines how to build consistent, scalable, and secure REST APIs for any organization's internal system, like databases, data warehouses, unstructured data stores, or homegrown applications, in order to provide an interface with the DataGrail Platform to process privacy requests.

DataGrail's API integrations execute access and deletion using either synchronous or asynchronous requests. These API request types can impact the time it takes for an integration to process. This article describes the differences between these API request types and how it affects your DataGrail workflow.

Authenticated Data Subject Request Handling is allows customers to select if a Direct Contact connection is meant for a 3rd party processor or an Internal System Owner, which can be configured with your SSO solution.

Automate the fulfillment of data subject access, deletion, opt-out, and identifier retrieval requests in Google BigQuery.

The Request Manager Agent’s behavior is dictated by environment variables set in the container. These variables define the target systems to connect to, the operations to perform, and other metadata to instruct actions.

Integrations allow DataGrail to connect directly to your first and third-party systems to introduce automations and help you get the most out of the platform.

This section covers how to create new Agents and API key in DataGrail.

By default, DataGrail provides Direct Contact Integrations with 14 days to respond. When connecting a Direct Contact Integration to DataGrail, you will be provided two different options for what to do when that 14 day deadline is hit.

There may be circumstances where data should me anonymized vs being deleted. This article will cover the differences between each process and how to action if anonymization is the preferred route.

After configuring the environment variable, you're ready to configure the container that will run within your network.

Direct Contact Integrations allow DataGrail to automatically facilitate Privacy Requests against systems without a dedicated API. Direct Contact Integrations utilize an email workflow with a secure form that allows a configured processor to action requests for both access and deletion.

After creating the Agent and API key in DataGrail, you're ready to configure the environment variable used by the agent container.

Our Approach

Overview

DataGrail's Integrations power and automate processing of Privacy Requests against your organization's systems. There are four types of integrations within DataGrail:

DataGrail offers integration with 2000+ systems. How we integrate with these systems can vary based on the system itself and the permissions granted to access their API. This article will explain the different ways DataGrail connects to systems and help customers make a connection type decision that's best for them.

Automate the fulfillment of data subject access, deletion, opt-out, and identifier retrieval requests in MySQL.

Automate the fulfillment of data subject access, deletion, opt-out, and identifier retrieval requests in Oracle.

The DataGrail Integration Network features over 2,000 tech partners including Salesforce, Okta, Atlassian, HubSpot, Zendesk, Greenhouse, and many more. The integration network powers:

For many modern businesses, internal data systems are large repositories of sensitive personally identifiable information (PII). To process growing volumes of Data Subject Requests (DSR), companies must interact with every data system containing PII the organization uses, regardless of the storage medium.

Responsible Data Discovery is built to give you a better, more accurate view into your organization's privacy risk. It enables privacy managers to have automated and up-to-date inventory reports and informed impact assessments. It can help inform the logic used during the fulfillment of access and deletion requests. And it shifts your risk reduction to be more proactive with better informed policies and controls around your data processing.

The Request Manager Agent uses resources like a credentials manager and cloud storage to facilitate data subject request processing. A credentials manager stores client credentials, connection strings, PEM keys, API tokens, etc. that the Agent will use to connect to other resources. A cloud storage bucket stores the results of requests so that Personally Identifiable Information (PII) never leaves your private network.

Automate the fulfillment of data subject access, deletion, opt-out, and identifier retrieval requests in PostgreSQL.

Automate the fulfillment of data subject access, deletion, opt-out, and identifier retrieval requests in Redshift.

If an Integration is no longer utilized by your organization, it is best practice to remove it from DataGrail, so it does not impact your Privacy Requests.

The Request Manager Agent establishes connections to internal systems through a set of componentized integrations. DataGrail provides and is regularly adding to a standard set of integrations for use with common systems (databases, APIs, etc), however, the DataGrail Agent is designed to be extended through the use of custom components to encompass any needs specific to your organization.

Automate the fulfillment of data subject access, deletion, opt-out, and identifier retrieval requests in Snowflake.

Automate the fulfillment of data subject access, deletion, opt-out, and identifier retrieval requests in SQL Server.

Automate the fulfillment of data subject access, deletion, opt-out, and identifier retrieval requests using a command line argument on a remote server.

DataGrail's API integrations execute deletion using one of two methods, "standard" or "whole record". This article will outline the differences between the two methods and how it will impact your DataGrail workflow.