Cloud Data Loss Prevention (Cloud DLP) is now a part of Sensitive Data Protection. The API name remains the same: Cloud Data Loss Prevention API (DLP API). For information about the services that make up Sensitive Data Protection, see Sensitive Data Protection overview.
Stay organized with collections
Save and categorize content based on your preferences.
Last modified: October 6, 2020
During the Term of the agreement under which Google has agreed to provide
Google Cloud Platform to Customer (as applicable, the "Agreement"),
the respective Covered Service will provide a Monthly Uptime Percentage to
Customer (the "Service Level Objective" or "SLO") as
follows:
Covered Service
Monthly Uptime Percentage
content.inspect API requests
>= 99.5%
content.deidentify API requests
>= 99.5%
If Google does not meet the SLO, and if Customer meets its obligations under
this SLA, Customer will be eligible to receive the Financial Credits described
below. This SLA states Customer's sole and exclusive remedy for any failure by
Google to meet the SLO. Capitalized terms used in this SLA, but not defined in
this SLA, have the meaning set forth in the Agreement. If the Agreement
authorizes the resale or supply of Google Cloud Platform under a Google Cloud
partner or reseller program, then all references to Customer in this SLA mean
Partner or Reseller (as applicable), and any Financial Credit(s) will only
apply for impacted Partner or Reseller order(s) under the Agreement.
Definitions
The following definitions apply to the SLA:
"Back-off Requirements" means, when an error occurs, Customer is
responsible for waiting for a period of time before issuing another request.
This means that after the first error, there is a minimum back-off interval
of 1 second and for each consecutive error, the back-off interval increases
exponentially up to 32 seconds.
"Covered Service" means Sensitive Data Protection content.inspect API requests
or content.deidentify API requests.
"Downtime" means more than a ten percent Error Rate and is measured
based on server side Error Rate.
"Downtime Period" means a period of one or more consecutive minutes of
Downtime. Partial minutes or intermittent Downtime for a period of less
than one minute will not be counted towards any Downtime Periods.
"Error Rate" means the number of Valid Requests that result in a
response with HTTP Status 500 and Code "Internal Error" divided by the total
number of Valid Requests during that period, subject to a minimum of 2000
Valid Requests in the measurement period. Repeated identical requests do not
count towards the Error Rate unless they conform to the Back-off
Requirements.
"Financial Credit" means the following:
Monthly Uptime Percentage
Percentage of monthly bill for the respective Covered Service* in the Region affected that does not meet SLO that will be credited to future monthly bills of Customer
99.0% - < 99.5%
10%
95.0% - < 99.0%
25%
< 95.0%
50%
* If either the content.inspect API or content.deidentify API do not
meet SLO, credit will be calculated based on fees during the applicable
month for Content Bytes Inspected (0CC0-BE8A-D1EB). If the
content.deidentify API does not meet SLO, credit will also be calculated
based on fees during the applicable month for Content Bytes Transformed
(3D4B-3FC2-6136).
"Monthly Uptime Percentage" means total number of minutes in a month,
minus the number of minutes of Downtime suffered from all Downtime Periods
in a month, divided by the total number of minutes in a month.
"Valid Requests" are requests that conform to the Documentation, and
that would normally result in a non-error response.
Customer Must Request Financial Credit
In order to receive any of the Financial Credits described above, Customer must
notify Google technical
support within 30
days from the time Customer becomes eligible to receive a Financial Credit.
Customer must also provide Google with log files showing Downtime Periods and
the date and time they occurred. If Customer does not comply with these
requirements, Customer will forfeit its right to receive a Financial Credit.
If a dispute arises with respect to this SLA, Google will make a determination
in good faith based on its system logs, monitoring reports, configuration
records, and other available information.
Maximum Financial Credit
The maximum aggregate number of Financial Credits issued by Google to Customer
for all Downtime Periods in a single billing month will not exceed 50% of the
amount due from Customer for the Covered Service for the applicable month.
Financial Credits will be in the form of a monetary credit applied to future
use of the Covered Service and will be applied within 60 days after the
Financial Credit was requested.
SLA Exclusions
The SLA does not apply to any (a) features or services designated pre-general
availability (unless otherwise set forth in the associated Documentation), (b)
features or services excluded from the SLA (in the associated Documentation), or
(c) errors (i) caused by factors outside of Google's reasonable control; (ii)
that resulted from Customer's software or hardware or third party software or
hardware, or both; (iii) that resulted from abuses or other behaviors that
violate the Agreement; or (iv) that resulted from quotas applied by the system
or listed in the Admin Console.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],[],[],[],null,["# Sensitive Data Protection Service Level Agreement\n\nLast modified: October 6, 2020\n\nDuring the Term of the agreement under which Google has agreed to provide\nGoogle Cloud Platform to Customer (as applicable, the \"Agreement \"),\nthe respective Covered Service will provide a Monthly Uptime Percentage to\nCustomer (the \"Service Level Objective \" or \"SLO\") as\nfollows:\n\nIf Google does not meet the SLO, and if Customer meets its obligations under\nthis SLA, Customer will be eligible to receive the Financial Credits described\nbelow. This SLA states Customer's sole and exclusive remedy for any failure by\nGoogle to meet the SLO. Capitalized terms used in this SLA, but not defined in\nthis SLA, have the meaning set forth in the Agreement. If the Agreement\nauthorizes the resale or supply of Google Cloud Platform under a Google Cloud\npartner or reseller program, then all references to Customer in this SLA mean\nPartner or Reseller (as applicable), and any Financial Credit(s) will only\napply for impacted Partner or Reseller order(s) under the Agreement.\n\nDefinitions\n-----------\n\nThe following definitions apply to the SLA:\n\n- **\"Back-off Requirements\"** means, when an error occurs, Customer is responsible for waiting for a period of time before issuing another request. This means that after the first error, there is a minimum back-off interval of 1 second and for each consecutive error, the back-off interval increases exponentially up to 32 seconds.\n- **\"Covered Service\"** means Sensitive Data Protection `content.inspect` API requests or `content.deidentify` API requests.\n- **\"Downtime\"** means more than a ten percent Error Rate and is measured based on server side Error Rate.\n- **\"Downtime Period\"** means a period of one or more consecutive minutes of Downtime. Partial minutes or intermittent Downtime for a period of less than one minute will not be counted towards any Downtime Periods.\n- **\"Error Rate\"** means the number of Valid Requests that result in a response with HTTP Status 500 and Code \"Internal Error\" divided by the total number of Valid Requests during that period, subject to a minimum of 2000 Valid Requests in the measurement period. Repeated identical requests do not count towards the Error Rate unless they conform to the Back-off Requirements.\n- **\"Financial Credit\"** means the following:\n\n \\* If either the `content.inspect` API or `content.deidentify` API do not\n meet SLO, credit will be calculated based on fees during the applicable\n month for Content Bytes Inspected (0CC0-BE8A-D1EB). If the\n `content.deidentify` API does not meet SLO, credit will also be calculated\n based on fees during the applicable month for Content Bytes Transformed\n (3D4B-3FC2-6136).\n- **\"Monthly Uptime Percentage\"** means total number of minutes in a month,\n minus the number of minutes of Downtime suffered from all Downtime Periods\n in a month, divided by the total number of minutes in a month.\n\n- **\"Region\"** means the applicable region described at\n [https://cloud.google.com/compute/docs/regions-zones/](/compute/docs/regions-zones),\n as may be updated by Google from time to time.\n\n- **\"Valid Requests\"** are requests that conform to the Documentation, and\n that would normally result in a non-error response.\n\nCustomer Must Request Financial Credit\n--------------------------------------\n\nIn order to receive any of the Financial Credits described above, Customer must\n[notify Google technical\nsupport](https://support.google.com/cloud/contact/cloud_platform_sla) within 30\ndays from the time Customer becomes eligible to receive a Financial Credit.\nCustomer must also provide Google with log files showing Downtime Periods and\nthe date and time they occurred. If Customer does not comply with these\nrequirements, Customer will forfeit its right to receive a Financial Credit.\nIf a dispute arises with respect to this SLA, Google will make a determination\nin good faith based on its system logs, monitoring reports, configuration\nrecords, and other available information.\n\nMaximum Financial Credit\n------------------------\n\nThe maximum aggregate number of Financial Credits issued by Google to Customer\nfor all Downtime Periods in a single billing month will not exceed 50% of the\namount due from Customer for the Covered Service for the applicable month.\nFinancial Credits will be in the form of a monetary credit applied to future\nuse of the Covered Service and will be applied within 60 days after the\nFinancial Credit was requested.\n\nSLA Exclusions\n--------------\n\nThe SLA does not apply to any (a) features or services designated pre-general\navailability (unless otherwise set forth in the associated Documentation), (b)\nfeatures or services excluded from the SLA (in the associated Documentation), or\n(c) errors (i) caused by factors outside of Google's reasonable control; (ii)\nthat resulted from Customer's software or hardware or third party software or\nhardware, or both; (iii) that resulted from abuses or other behaviors that\nviolate the Agreement; or (iv) that resulted from quotas applied by the system\nor listed in the Admin Console.\n\n**Previous versions**\n\n- None"]]
