Google terms of service violations and Trusted Cloud resources
Google treats policy and Terms of Service (ToS) violations very seriously in order to protect users, resources, and data. At the same time at Google we understand the value of users' Trusted Cloud by S3NS resources and we have provided safeguards and recovery mechanisms for legitimate users that temporarily lose access to their Trusted Cloud resources due to ToS violations.
This page describes how ToS violations may affect access to your Trusted Cloud resources and provides best practices to ensure a quick recovery.
Suspended vs orphaned Project resources
A Project resource or user can be suspended by Google due to ToS violations. If the user is the sole owner of a Project resource, that Project will also be suspended. When this happens, existing workloads are shut down, and users lose access to the suspended Project resource. Project owners will receive an email notification informing them of the suspension, and how to appeal the suspension.
A Project resource becomes orphaned if it does not have an owner, regardless of whether they are active or suspended. This might come about if the Google accounts belonging to all owners or users associated with the Project resource are deleted. A Project resource isn't considered orphaned if the owners are suspended.
Orphaned Project resources are inaccessible. If you want to recover an orphaned project, reach out to Google support. A Project resource that is orphaned will immediately be marked for deletion unless one of the following criteria is met:
- It has some API activity that is reflected in the logs.
- It is associated with a Google Workspace customer domain.
- It has a live App Engine app.
- It has any active or future Variable Term Quota.
- It is linked to a Cloud Billing account.
- It is owned by an Organization resource resource.
Projects that are marked for deletion are not usable, and will be fully deleted after approximately 30 days. Some resources, such as Cloud Storage resources, are deleted much sooner. For more information about the project deletion process, see Creating and Managing Projects.
How to avoid orphaned projects
In order to prevent a project from becoming orphaned, we recommend that more than one owner be associated with the project at all times.
If a project belongs to an Organization resource, then it will always have at least the Organization as an owner and as such will not be orphaned. The Organization administrator has full control over each project in the Organization. To eliminate the risk of a Project resource becoming orphaned, we recommend obtaining an Organization resource and migrating all production projects under it.
Effect of ToS violations
Trusted Cloud account suspension
In certain circumstances when a Trusted Cloud user is consistently violating ToS or Trusted Cloud Acceptable Use Policy (AUP) through their projects, their access to Trusted Cloud may be suspended. When that happens, the developer will not be able to access their Cloud projects. They will continue to have access to other Google services like Gmail.
When a Trusted Cloud account is suspended and the developer has at least one active project, they will get an email informing them about the project being suspended. The developer can go to the Console, fill out the form and reach out to Google to resolve the issue.
Trusted Cloud project suspension
Trusted Cloud projects may be suspended due to violations of the Trusted Cloud by S3NS ToS, including the Trusted Cloud Acceptable Use Policy (Trusted Cloud by S3NS AUP). When activities that violate the Trusted Cloud AUP or ToS are detected in a project, the project owner has an obligation to fix the violation immediately. If the violation is not fixed, Google may take action to suspend the project. It is important that Trusted Cloud developers check the project owner email account regularly. If Google suspends a Trusted Cloud project then all the associated Trusted Cloud workloads will be suspended as well. The owner of a suspended project will receive a notification email from google-cloud-compliance@google.com with resources to appeal.
If a suspended Project resource has at least one owner, whether active or suspended, it is not considered orphaned and will not marked be for deletion. However, a Project resource that has been suspended for nine months will be marked for deletion even if it is not orphaned.
Cloud Billing account suspension
Trusted Cloud Cloud Billing accounts may be suspended due to violations of Trusted Cloud ToS, missed payments, or for suspected fraud. If a Cloud Billing account is suspended then all Trusted Cloud resources attached to that Cloud Billing account are suspended as well.
If your Cloud Billing account remains invalid for a protracted period, some resources might be removed from the projects associated with your account. Removed resources are not recoverable. See the Resolve Cloud Billing issues page for more information.
To recover a suspended Cloud Billing account, owners can use one of these options:
Submit documents or request a verification code: Use Google payments center to see if you need to submit documents or get a verification code.
Make a manual payment: In the Trusted Cloud console, sign in to the Payment overview page for your Cloud Billing account, and click Make a payment.
Learn about making manual payments to your Cloud Billing account.
You might need to manually restart services that were shut down while the Cloud Billing account was suspended. See Restarting Trusted Cloud services for information on restarting your services.
Cloud resources linked to a suspended Cloud Billing account are not considered orphaned, as long as they have at least one active owner.