Google Cloud Storage: projected connector

What you can do today

Copy extracts to local files or an S3-compatible store read by a shipped connector.

Whatever route you choose, the export and every row-level step stay inside your network. You can evaluate the whole workflow now with the synthetic demo.

Capability matrix

Google Cloud Storage does not ship yet, so no capability is verified. The column shows what the design plans; plans are not commitments.

How the connector is designed to prove read-only access

Designed: a service account with only roles/storage.objectViewer on the bucket.

Design: the same file-set connector as S3 and Azure (Parquet/CSV, declared table names).

What crosses the boundary

Connectors run inside the agent in your network. Only metadata, aggregates and evidence reach DataNivra Cloud:

• Schema, table and column names and data types (for file sets, operator-declared or opaque table names — never data-derived file names).
• Aggregates such as row-count estimates, null and distinct ratios; counts from 1 to 10 are reported as 10 (small-cell protection).
• Classification findings (which column looks like which kind of sensitive data) and relationship metadata.
• Evidence metadata: checksums, gate outcomes, engine and policy versions, and templated error codes.

Never sent:

• Any cell value, row, sample, minimum/maximum or top-k value — masked or not.
• Credentials, connection strings or resolved secret values: DataNivra stores only the secret reference.
• Free text copied from your data, or exception messages that contain values.

See the customer-resident architecture and how to verify these claims yourself.

Request this connector

We prioritise connectors by demand, engineering effort and strategic fit. Telling us that Google Cloud Storage matters to you is counted; it does not commit a delivery date.