The Checks API contains powerful and easy-to-use privacy and compliance APIs that interact with the Checks product and its underlying technology.

Additional options for Checks#accountsAppsList.

Additional options for Checks#accountsAppsOperationsList.

Additional options for Checks#accountsAppsReportsGet.

Additional options for Checks#accountsAppsReportsList.

The request message for Operations.CancelOperation.

Defines the root interface for all clients that generate credentials for calling Google APIs. All clients should implement this interface.

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }

Represents an app in Checks.

The response message for AccountService.ListApps.

The request message for ReportService.AnalyzeUpload.

Information about the analyzed app bundle.

A check that was run on your app.

Regulation or policy that serves as the legal basis for the check.

Evidence concerning data security.

Evidence related to data in transit detected in your app.

Evidence concerning a data type that was found in your app.

Evidence concerning an endpoint that was contacted by your app.

Evidence collected from endpoint restriction violation analysis.

Details of the endpoint in violation.

Evidence for a check.

Evidence concerning a permission that was found in your app.

Evidence collected from permission restriction violation analysis.

Details of the permission in violation.

Evidence collected from your privacy policy(s).

Evidence conerning an SDK that was found in your app.

Evidence concerning an SDK issue.

Evidence collected from SDK restriction violation analysis.

Details of the SDK in violation.

Additional information about the check state in relation to past reports.

Represents the data monitoring section of the report.

Information about a data type that was found in your app.

Information about an endpoint that was contacted by your app.

Information about a permission that was found in your app.

Information about a data monitoring result.

Information about an SDK that was found in your app.

Evidence based on an endpoint that data was sent to.

Details of SDK that is attributed to the exfiltration.

Details of the endpoint the data type was sent to.

Evidence collected about a data type.

Evidence based on the inclusion of a permission.

Evidence based on information from the privacy policy.

Information about an endpoint.

The response message for ReportService.ListReports.

Information about a permission.

Information about a policy fragment.

Privacy report.

Information about an SDK.

The response message for Operations.ListOperations.

This resource represents a long-running operation that is the result of a network API call.

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

The request message for Operations.WaitOperation.