Skip to main content


Scuba Docs

How to request a GDPR privacy purge

The European Union (EU) General Data Protection Regulation (GDPR) was designed to protect EU citizens data privacy, and reshape the way organizations approach data privacy. 

Scuba's Privacy Purge enables you to comply with GDPR and other privacy regulations, as well as any voluntary privacy policies your company may adhere to. For more information, see How to comply with GDPR.

This document explains the GDPR purge process, and outlines the information you must submit for a GDPR privacy purge request. Click a link to jump directly to a topic:

Contact your TAM  

Communicating fully with your Technical Account Manager (TAM) is essential. Review the following sections and discuss the items with your TAM, as they pertain to your data. 

What happens in a GDPR privacy purge

A GDPR purge is a simple process. The procedure includes identifying the Personally Identifiable Information (PII) user data to be deleted, sending this information to Scuba, after which a purge is performed. The following illustration outlines the details of the process.


After completing an GDPR purge request, all traces of an individual are removed from Scuba. The following table lists the PII data Scuba removes, and what you are responsible for manually removing from your data.

Scuba's Privacy Purge removes the following PII data: 
  • Event data
  • String data
  • Query result history
  • Query definition history
  • Named expressions, global filters, dashboards, and derived columns
You are responsible for removing the following PII data: 
  • PII data in original source logs
  • PII data in lookup files


Named expressions, global filters, dashboards, and derived columns that reference purged users in their filters or other query parameters, will be adversely affected when the purged user data is deleted.

Information we need for a GDPR privacy purge 

Your TAM will need the following information to process your GDPR purge request:

  1. A JSON or CSV file with the following information and format:
  • Names of the columns that contain user data to be purged
  • Unique identifiers of the individuals whose data must be purged
  • Use the following format:
"Filters": {

Optionally, you can include a CommandID value for to the request, as shown in the following example:

"Filters": {
"CommandId": "tracking-number-or-value"
  1. The location where the purge request file is located. Scuba must have access privileges to download the file.
  2. The frequency at which the purges are to be run.

GDPR purges scan the entire cluster and may impact performance. Work with your TAM to schedule purges during
non-peak hours.

  • Was this article helpful?