Data Storage
How we store your data
We store the data you sync using Census, sometimes for the lifetime of your Census workspace, including:
CSV datasets
Entity Resolution datasets
...plus AI Columns, Enrichment Columns, and Warehouse Writeback logs for all of these datasets
Snapshots of the data you sync using Basic Sync Engine
Sync Tracking logs of the data you sync
Temporary files used to load and unload data
This data is stored in cloud-based object storage providers. Census provides object storage locations in multiple clouds in the US and the EU that you can use to store this data, and your Census organization is configured to use these locations by default. You can also add your own object storage locations to Census.
Census-provided object storage
New Census organizations are configured to use Census-provided object storage by default. Census manages object storage locations in multiple public clouds, including AWS (S3), GCP (GCS), and Azure (Blob Storage). This includes managing credentials with narrow permissions and short lifetimes, encrypting data at rest and in transit, automatically removing old data once it is no longer in use, and ensuring your workspace is always storing data in the correct region (US or EU). This approach is secure and is used by the vast majority of Census customers.
Customer-provided object storage
You can also add your own object storage locations and configure Census to default to these locations on a per-organization, per-workspace, or per-connection basis. Note that some data warehouses are only compatible with specific object storage providers. If a compatible customer-provided storage location is not available, Census will default to using compatible Census-provided storage.
When you bring your own object storage, you are responsible for managing the retention of data in the object storage location, and for ensuring the object storage is located in an appropriate region for your requirements.
Last updated
Was this helpful?