21 docs tagged with "Asynchronous"

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

Abstract

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.

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 are a core function of DataGrail and help you get the most out of the platform. By connecting these systems, customers are able to reduce compliance risk and the overall time to complete requests.

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.

Our Approach

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.

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.

DataGrail customers often change services they use, no longer need to use the system, or simply decide to switch from an API to a Direct Contact (or vice versa) integration. This article describes how you can remove connections you no longer utilize from your DataGrail account.

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.