Document AI Security & Compliance
Security
In order to ensure service security in Document AI, read the following questions applicable in these scenarios.
How does Google protect and ensure the security of the data I send to Document AI?
Refer to the Google Cloud Security page which describes the security measures in place for Google Cloud Services.
What security horizontals does Document AI support?
Document AI supports the following:
- Data Residency
- VPC Service Controls (VPC-SC)
- Access Transparency
- Customer-managed encryption keys (CMEK)
Security compliance
This section describes the questions related to compliance.
What compliance does Document AI offer?
Google Cloud undergoes regular independent third-party audits to verify alignment with security, privacy, and compliance controls. Google Cloud has regular audits for standards such as ISO 27001, ISO 27017, ISO 27018, SOC 2, SOC 3, and PCI DSS.
You can read more about Google Cloud compliance on the Compliance resource center
Is Document AI FedRAMP compliant?
Document AI is FedRAMP Moderate compliant.
Is Document AI HIPAA compliant?
Document AI is HIPAA compliant.
Security data usage
This section describes data inquiries.
Does Google use customer data to improve the model(s)?
No. Google does not use any of your content (such as documents and predictions) for any purpose except to provide you with the Document AI service. See the Document AI data usage policy.
At Google Cloud, we never use customer data to train our Document AI models.
For more information, see this blog post: Sharing our data privacy commitments for the AI era
In the future, will Google share the document I send to Document AI?
We won't make the document that you send available to the public, or share it with anyone else, except as necessary to provide the Document AI service. For example, sometimes we may need to use a third-party vendor to help us provide some aspect of our services, such as storage or transmission of data. Our vendors are under appropriate security and confidentiality contractual obligations. We don't share documents you send with other parties or make them public for any other purpose.
Will documents I send to Document AI, their results, or other information about requests, be stored on Google servers? If so, how long and where, and can I access it?
When you send a document to Document AI using a batch request, we must store that document (encrypted with an ephemeral key, meaning that no human has access to it) for a short period of time in order to perform the analysis and return the results to you. For batch operations, the stored document is typically deleted immediately after the processing, with a failsafe Time to live (TTL) of one day. If the batch abends abnormally, the data may persist with a TTL of up to seven days.
Synchronous processes
For online (immediate response) operations, the document data (sent in the request) is processed in memory, encrypted in flight, and not persisted to disk. Google also temporarily logs some metadata about your Document AI API requests (such as the time the request was received and the size of the request) to improve our service and combat abuse.
For more information, see:
Does Google claim ownership of the content I send in the request to Document AI
Google does not claim any ownership in any of the content (including documents and predictions) that you transmit to Document AI. Documents and custom models are considered to be (private) customer data. We never use customer data to improve our models. In the rare circumstance where both parties agree to such an arrangement, an explicit data sharing agreement is crafted.
What is considered Personally Identifiable Information (PII) that needs to be redacted on documents before being shared with Google?
For document sharing purposes, PII is any information defined as personal identifiable data under applicable laws. Customers must redact the documents prior to sharing them with Google, for example when voluntarily done for technical support purposes to reproduce a problem.
Examples of PII include but are not limited to:
- Date of birth, for example:
2/10/1988 - Names of individuals, for example:
Kiran Darko - Personal address, for example:
Evergreen terrace 123 - Email address of individuals, for example:
rivelro@test-mail.com - Telephone number of individuals, for example:
636-555-3226 - Driver's license number
- National ID number
- Employer identification number
- Bank account information: account IDs, routing numbers, SWIFT IDs
- Payment card number
- Gender, for example:
Female, Male, Nonbinary - Ethnicity, for example:
Berber, Italian, Japanese, Latino, Ukrainian - Usernames, ID number of third parties
- Passport number, for example:
AA1001111 - Marital status, for example:
Single, Divorced - Number of allowances or exemptions
- Dependent names
- Vehicle identifiers (VIN, license plates, etc.)
- Any other unique identifying number, characteristic or code of an individual that could identify an individual consumer, family, or device over time or across services
Can I resell the Document AI API?
No, you are not permitted to resell Document AI service. You can still integrate Document AI into applications of independent value.
How can customers control Google Cloud} support access to their documents or data?
All Document AI parsers support access transparency and access approvals. By default, Google support wouldn't have access to any of customer data or applications. In the situation where access is required from the Google support team, customers can use the Access Approvals process to authorize access to data or applications. This process starts with the creation of a ticket in the Google support portal. The customer then receive a notification (usually email) and an option to authorize or deny access.
Google also offers a service called Access Transparency which gives customer visibility into all the tasks that Google support performs while they have access to the system.