company-logo company-logo-mini

Privacy Policy

Download
Cloudaware provides SaaS (Software as a Service) CMDB to customers. CMDB gathers cloud infrastructure metadata that a customer leverages. Cloudaware has recommended security policies for accessing resources in a cloud provider system. These cloud access policies are specifically designed to provide Cloudaware with access to describe a customer cloud infrastructure without giving access to the business data.

Cloudaware operates as a container application inside Salesforce's app engine and is subject to all Salesforce security controls. The Cloudaware role is limited to updating, deleting, and inserting new data into CMDB. There are no algorithms or automated batch export jobs that export a customer's data outside of the Salesforce instance where Cloudaware is hosted. In addition, the Cloudaware internal security policy explicitly forbids exporting the customer data outside of the customer’s Salesforce instance. In order to provide our customers with hands-on support, technical account managers associated with a customer account have access to a customer's Cloudaware instance.

Cloudaware processes and stores customer data on Salesforce's app engine infrastructure. Many of Salesforce's SOC2 controls regarding data backup, DR, BCP, access control, and auditing apply directly to Cloudaware. More information about compliance certifications are available here: https://compliance.salesforce.com/en

Salesforce performs its own security and audit process to vet vendors whose applications are offered via Salesforce's app store. More details about this process are available here: https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/security_review_overview.htm

Additional helpful documentation: https://developer.salesforce.com/docs/atlas.en-us.securityImplGuide.meta/securityImplGuide/salesforce_security_guide.html


Handling of Google User Data

The following describes how the Cloudaware MCP server accesses, uses, stores, and shares Google user data in compliance with the Google API Services User Data Policy and Google APIs Terms of Service. Google user data refers to information obtained via Google APIs, such as authentication details and dataset content in Google BigQuery.

  1. Data Accessed
    The Cloudaware MCP server accesses the following specific types of Google user data via the https://www.googleapis.com/auth/bigquery scope:

    • User's email address (for authentication and account association).
    • Data from Google BigQuery datasets, specifically the SObjects dataset in your configured Export Project, which contains metadata and data from your Cloudaware CMDB (e.g., object types, fields, relationships, and query results).

  2. Data Usage
    We use, process, and handle this Google user data solely to provide the MCP server's core functionality: enabling secure discovery and querying of Cloudaware datasets stored in Google BigQuery. This includes programmatic access via JSON-RPC interfaces for tools like search_types, search_fields, get_relationship_graph, and execute_query. No data is used for marketing, advertising, or unrelated purposes.

  3. Data Sharing
    We do not share Google user data with any third parties, except as necessary to operate the service (e.g., storing data in Google BigQuery, which is managed by Google) or as required by law. Any such sharing is limited to the purpose of data storage and querying, with no transfer for commercial gain.

  4. Data Storage & Protection
    The Cloudaware MCP server is stateless and does not store any Google user data. All data resides in your Google BigQuery project, secured by Google's infrastructure-level protections, including encryption at rest and in transit, access controls, and compliance with standards like SOC 2. Access is restricted to what is necessary for service delivery.

  5. Data Retention & Deletion
    The Cloudaware MCP server does not retain any Google user data, as it is stateless. All data resides in your own Google Cloud Project, where retention is governed by your project's settings or as required by applicable laws. Users manage and delete their data directly through the Google BigQuery console or APIs. For assistance or questions, contact our support team at support@cloudaware.com.


Last Updated November 14, 2025