9 docs tagged with "Intake"

When a Data Subject requests to know the type of data categories you store, they will submit an Access Categories request.

When a Data Subject wants all their data deleted from your systems, they will submit a Deletion request. The purpose of a deletion request is to remove any of the Data Subject's personally identifiable information from systems that your organization uses.

When your company receives an email at a specified address (e.g., privacy@company.com), forwarding rules can be set up to automatically forward that email to DataGrail, where the message and sender information will be parsed and converted into a privacy request within the Request Queue.

Personal data is sometimes keyed using different identifiers that are not email, such as unique identifiers, phone numbers or cookies. This article will walk through how to set up the Multiple Identifier feature and find all personal information from data subjects stored in data systems, while eliminating the possibility of missing data.

When a Data Subject wants you to stop processing their personal data certain purposes, such as public interest or direct marketing, they will submit an Object to Processing request.

By default, DataGrail verifies a data subject's identity through a verification message sent to their email. DataGrail also offers "Smart Verification" functionality, with an increased number of data points that must be verified in order to process a Privacy Request.

If your company utilizes the DataGrail-enabled toll-free number to intake privacy requests, all calls to this toll-free number will create a privacy request in DataGrail.

When a Data Subject requests to forward their personal information that your company maintains on them to a recipient, they will submit a Transfer request.

When a Data Subject requests to update an error in data you hold about them, they will submit an Update Inaccuracies request.