The only Reverse ETL platform that doesn’t store your data
Unlike other Reverse ETL platforms, Census was designed from day one to run inside your data warehouse. Our unique “low touch” sync architecture leverages your data warehouse’s own execution engine to perform sensitive operations, meaning that validation, transformation, and state tracking all happen without your data ever touching Census's servers. This ensures speed and security and makes Census “secure by default” against many common attacks.
Census is the only major Reverse ETL platform that does not store a second copy of your data. We perform most of the “logic” for determining what records need to be synced — and how to match those records to your existing data — within your own warehouse.
Least privileges needed for handling data
Census does not require superuser access to your data warehouse, and will request the fewest OAuth scopes needed for your SaaS applications (subject to SaaS provider support). Connections between your data warehouse and shared resources such as S3 buckets are performed using minimum privilege STS credentials with short expiration times.
SOC 2/HIPAA Compliance
Safeguarding our customers’ personal data is our fundamental responsibility. Census is the first Reverse ETL platform to obtain a SOC 2 certification, and we regularly audit our policies and procedures to ensure compliance with ongoing HIPAA and SOC 2 requirements.
Request our SOC 2 report →
EU Data Locality
Customers can choose to keep all their data within the EU throughout the duration of a Census sync, hosted in Frankfurt (AWS eu-central-1). We never store your data, but your selected region determines where data is processed during your Census syncs.
Data encrypted in transit & at rest
If your data does transit through Census's servers, it is encrypted in transit and securely removed the moment it reaches the ultimate destination. Census uses recent TLS versions for all connections between systems: from your browser to our application, from our servers to your data warehouse or SaaS application, and internally between our own services and databases. We do not use self-signed certificates and we regularly audit TLS versions and ciphersuites to avoid any newly discovered weaknesses. Census encrypts its own databases and blob storage at rest and applies an additional layer of asymmetric encryption to protect our core application secrets, like OAuth credentials and API keys.
GDPR and CCPA Compliance
Census is fully compliant with GDPR regulations that ensure the privacy, protection, and security of personal information. We continuously evaluate our practices to prioritize and mitigate risks, and we are transparent about how customer data is collected, processed and stored. We have a Data Process Addendum available.
Request our DPA →
SAML SSO
We seamlessly support over 10,000 data consumers with enterprise-grade SAML 2.0 SSO, which makes signing in with your existing identity provider easy. You can sign in with:
- Okta
- OneLogin
- PingIdentity
- ADFS
- WorkOS
- Or any of dozens of other SAML 2.0 IdPs