The Privacy page tracks data subject requests and searches for the subject’s identifiers across the datastores
DSPM has read. TigerGate does not delete data for you: an erasure request finds the data, you delete it in the source
system, and a second search confirms it is gone.
Request types
| Type | Use it when |
|---|
| Access | The subject asks for a copy of their personal data. Find every place it is held. |
| Erasure | The subject asks for their data to be deleted. Find it, delete it, then search again to confirm. |
| Locate | You need to know where a person’s data is held, for an investigation or before another request. |
Create a request
Open the form
Go to DSPM → Privacy and select New request.
Fill it in
- Type: Access, Erasure or Locate.
- Regulation: sets the default deadline (see below). Received is the date the request arrived, and
Days to respond (1 to 365) can be changed.
- Identifiers the subject gave: add each one with Add identifier: email address, phone number, national ID
or tax ID, IBAN, bank account number or health ID.
- Reference: a ticket or case number to find the request by. It must not be an identifier.
- Note: optional.
Create it
Select Create request. TigerGate searches the scanned datastores and lists where each identifier appears.
Each identifier is turned into a keyed fingerprint on the server, and only the fingerprint is kept. You cannot see
the identifiers again, on the request or in its export, so give the request a reference you can find it by.
Deadlines
| Regulation | Default days to respond |
|---|
| GDPR | 30 |
| CCPA / CPRA | 45 |
| DPDP Act (India) | 90 |
| Other | 30 |
Work a request
A request moves from Queued to In progress, then Fulfilled or Rejected. A closed request can be
reopened. Use Search again after data was deleted or new scans ran, and Export CSV to keep a record of where
the data was found.
What a search can find
- Only content-scanned datastores can be searched. The request shows how many stores were searchable at the last
search, and “Not found in scanned data” means exactly that. Check Deployments → Coverage for stores that were
not read.
- Stores read by an in-account scanner record fingerprints under that deployment’s own key, so their values never
leave your environment.
- Stores read by hosted scans (SaaS tools and warehouses) are searchable only when your TigerGate operator has
configured the hosted fingerprint key. The Privacy page says so when it is missing.
- With the sampled profile, values outside the sample a scan read cannot be found.
