Cloud DLP pricing

This page provides pricing information for Cloud Data Loss Prevention (DLP). Prices on this page are listed in US dollars (USD).

Cloud DLP requires billing information for all accounts before you can start using the service. To sign up for billing, go to your project's billing page in the Google Cloud Console.

The Cloud DLP charges for usage based on the following price sheet. At the end of each billing cycle, a bill is generated that lists the usage and charges for that cycle. Prices on this page are listed in US dollars (USD).

You can use the Google Cloud pricing calculator to estimate Cloud DLP costs based on type and quantity of content scanned.

Inspection and transformation pricing

Cloud DLP provides a set of features for inspecting and transforming data. Across these scenarios, you pay only for what you use, with no upfront commitments.

Supported features

Cloud DLP supports the features summarized in the following table:

Feature Description
Inspection with built-in infoType detectors Each built-in classifier detects a different data element such as names, phone numbers, email addresses, Social Security numbers, and more.
Inspection with custom infoType detectors Allows custom defined dictionary to classify new elements or augment predefined infoTypes.
Image redaction Extracts text from images, classifies the text, and generates a new image with rectangular boxes that mask any findings.
De-identification Transforms tabular or free-text data to mask, redact, or obfuscate by column, record, or infoType finding.

Storage inspection job pricing

Cloud DLP storage jobs are billed based on bytes inspected according to the following schedule:

Storage data inspected per month Price per gigabyte (GB)
Up to 1 GB Free
1 GB to 50 terabytes (TB) $1.00
Over 50 TB $0.75
Over 500 TB $0.60

For more information about inspecting content stored within Google Cloud, see Inspecting storage and databases for sensitive data.

Content method inspection and transformation pricing

The content methods are listed in the following table, along with notations of the types of charges each method may be billed for:

API method Content inspection Content transformation
projects.image.redact Yes No
projects.content.inspect Yes No
projects.content.deidentify Yes Yes
projects.content.reidentify Yes Yes

Content inspection method pricing

Cloud DLP content method pricing is billed based on bytes inspected according to the following schedule:

Content data inspected per month Price per GB
Up to 1 GB Free
Over 1 GB $3.00
Over 1 TB $2.00

Content transformation method pricing

Cloud DLP content method pricing is billed based on bytes transformed according to the following schedule:

Content data transformed per month Price per GB
Up to 1 GB Free
Over 1 GB $2.00
Over 1 TB $1.00

If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.

A minimum of 1 KB is billed per content inspect or transform request.

Other charges and no-charge features

In addition to the billing charges directly incurred by the Cloud DLP, requests that are configured to invoke other Google Cloud products may result in their own billing charges. For example, the projects.content.inspect method may incur Cloud Storage charges if directed to inspect Cloud Storage objects.

Some methods can result in billing charges for either inspection, transform, or both depending on how they are configured. This is the case for the projects.content.deidentify and projects.content.reidentify methods when, for example, transformation is configured but inspection is not. The same applies to transformation when only inspection is configured.

Simple redaction, which includes the RedactConfig and ReplaceWithInfoTypeConfig transformations, is not counted against the number of bytes transformed when infoType inspection is also configured.

Example pricing scenarios

This section contains several example Cloud DLP usage scenarios, along with pricing calculations for each.

Scenario 1: Data inspection and transformation using content methods

Suppose you have just over 1 GB of structured (tabular) data. You stream it to the DLP API, instructing Cloud DLP in the request to inspect for 50 different built-in infoType detectors, and to de-identify any matches it finds by using a cryptographic tokenization transformation. After performing the de-identification operation, you note that Cloud DLP has matched on and transformed around 1% of the data, or around 10 MB.

Pricing:

  • Inspection: 1 GB of data × $3.00 per GB = $3.00
  • Transformation: 0.01 GB × $2.00 per GB = $0.02
  • Total: $3.02

Scenario 2: Structured data transformation only using content methods

Suppose you have a 1 GB table and want to transform three columns (user_id, email, phone_number) using a cryptographic tokenization transformation. The three columns represent about 30% of the table. Because you're specifying entire columns to transform, no inspection is necessary.

Pricing:

  • Inspection: 0 GB of data = $0.00
  • Transformation: 0.3 GB of data × $2.00 per GB = $0.60
  • Total: $0.60

Scenario 3: Storage repository inspection using storage jobs

Suppose you have 1,000 BigQuery tables that you want to inspect. Each table is around 1 GB in size, making the total size of the data 1 TB. Not wanting or needing to scan the entirety of every table, you've turned on sampling so that just 1,000 rows of each table is scanned. Each row is roughly 10 KB in size.

Pricing:

  • Data to inspect: 1,000 tables × 1,000 rows per table × 10 KB per row = 10 GB total scanned
  • Total: 10 GB × $1.00 per GB = $10.00

Risk analysis

Risk analysis uses resources in BigQuery and charges will appear as BigQuery usage. Cloud DLP does not add any additional charges for risk analysis.

Risk analysis jobs are created using the projects.dlpJobs.create method with the following configuration objects:

Controlling costs

Depending on the quantity of information that you instruct the Cloud DLP to scan, it is possible for costs to become prohibitively high. To learn several methods that you can use to keep costs down while also ensuring that you're using the Cloud DLP to scan the exact data that you intend to, see Keeping Cloud DLP costs under control.