Additional Terms: Databases (GCP — Cloud SQL)

Effective Date: April 16, 2026
Cloud Provider: Google Cloud Platform
GCP Service: Cloud SQL for PostgreSQL
Document ID: QUOME-LEGAL-DB-GCP-001

These Additional Terms govern your use of the Quome Databases service ("Databases") when provisioned on Google Cloud Platform. These terms supplement the Terms of Service.

1. Service Description

Databases enables you to provision, manage, and scale managed PostgreSQL instances on Google Cloud SQL within your GCP project under the BYOSA model. Quome handles provisioning, configuration, connection management (via Cloud SQL Auth Proxy sidecars), backup scheduling, and extension management on your behalf.

2. Infrastructure Ownership

2.1 Customer-Owned Resources

• Cloud SQL instances and replicas
• Database users, schemas, tables, and all stored data
• Automated and on-demand backups (stored in your GCP project)
• Private IP networking and VPC peering configurations
• Cloud SQL Auth Proxy connections

2.2 Quome-Managed Configuration

• Instance provisioning (tier, region, HA configuration)
• Connection credential generation and rotation
• Backup schedule configuration
• Extension enablement and management
• Row-level security (RLS) policy configuration
• Column-level encryption configuration (CMEK)

3. Customer Responsibilities

3.1 Data Management

You are solely responsible for:

(a) All data stored in your Cloud SQL instances, including ensuring that data complies with Applicable Law;

(b) Database schema design, query performance, and data integrity;

(c) Application-level data validation and sanitization;

(d) Data backup verification — while Quome configures automated backups, you should periodically verify that backups can be restored successfully;

(e) Data retention and deletion in compliance with your legal obligations.

3.2 Access Control

You are responsible for managing database user accounts and permissions within your Cloud SQL instances. Quome's delegate service account has administrative access for provisioning and management purposes; you should not modify or revoke this access while using the Service.

3.3 Sensitive Data

If your database stores regulated data (PHI, PCI cardholder data, etc.):

(a) You must enable encryption at rest using Customer-Managed Encryption Keys (CMEK) through the Quome platform;

(b) You must enforce SSL/TLS for all database connections;

(c) You must configure private IP networking (no public IP) for the Cloud SQL instance;

(d) You must maintain a BAA with both Quome and Google Cloud if storing PHI.

4. Service Limits and Pricing

Databases are subject to Google Cloud SQL quotas, limits, and pricing. Cloud SQL pricing is billed directly by Google Cloud to your GCP billing account. Quome does not mark up or resell cloud infrastructure costs.

Key limits to be aware of:

5. Data Handling

5.1 Database Content

All database content (tables, rows, indexes, stored procedures) resides exclusively in your GCP project. Quome's control plane never reads, stores, or processes the content of your database tables.

5.2 Query Execution

Quome provides a query interface for convenience. Queries are executed directly against your Cloud SQL instance through the delegated connection. Query text may be transiently processed through Quome's control plane for delivery but is not logged or stored beyond the active session, except:

(a) Query execution metadata (timestamp, duration, rows affected, error status) may be logged for audit and debugging purposes;

(b) Query text is never included in audit logs.

5.3 Connection Credentials

Database connection credentials are generated by Quome and stored in Google Secret Manager within your GCP project. Quome's control plane stores only a reference to the secret name, not the credential values.

6. Backups and Recovery

6.1 Automated Backups

Quome configures automated daily backups through Cloud SQL's built-in backup mechanism. Backups are stored in your GCP project and are subject to Google Cloud's backup retention policies and your configured retention period.

6.2 Point-in-Time Recovery

Point-in-time recovery (PITR) is available for Cloud SQL instances with binary logging enabled. Quome does not guarantee the availability or completeness of PITR.

6.3 Backup Responsibility

QUOME DOES NOT GUARANTEE BACKUP INTEGRITY OR RECOVERABILITY. YOU ARE SOLELY RESPONSIBLE FOR VERIFYING THAT YOUR BACKUPS ARE COMPLETE AND RESTORABLE. QUOME RECOMMENDS PERIODIC RESTORATION TESTING.

7. Termination Effects

Upon termination:

(a) Cloud SQL instances continue to run in your GCP project — Quome does not delete your databases;

(b) Connection credentials in your Secret Manager remain accessible to you;

(c) Automated backup schedules configured through Quome will continue operating via Cloud SQL's native scheduling;

(d) You retain full control and can manage instances through the GCP Console.

Cloud Provider Reference

AWS (RDS for PostgreSQL) and Azure (Azure Database for PostgreSQL) Additional Terms will be published when those providers reach general availability.