Product News

Census officially SOC 2 Type 2 compliant | Census

Sylvain Giuliani
Sylvain Giuliani June 25, 2021

Syl is the Head of Growth & Operations at Census. He's a revenue leader and mentor with a decade of experience building go-to-market strategies for developer tools. San Francisco, California, United States

Customer data security is more important than ever, and a security-by-design approach like Census' ensures the bridge is as safe as the endpoints (the data warehouse and operational systems like Salesforce or Hubspot.)

That's why we're excited to announce that as of June 7th, we became the first operational analytics platform to achieve SOC 2 Type 2 compliance to ensure best-in-class security, confidentiality, and availability.

Meeting the SOC 2 Type 2 standard demonstrates our data-bridging technology delivers the same customer data security as the business application endpoints it supports.

What this means for our customers

AICPA SOC 2 defines the criteria for managing customer data based on the five trust principles: security, availability, processing integrity, confidentiality, and privacy. We've always built security first, but now our customers can rest easy knowing that our internal controls, systems, policies, and procedures all align toward this high standard.

"We trust Census for reverse ETL because it's clear that they share our obsession with designing, building and operating secure data infrastructure. This new SOC 2 certification demonstrates the strength of that commitment." - Jeff Ronaldi, GTM operations manager at LogDNA

SOC 2 Type 2 reports specifically detail operational effectiveness for service organizations. This demonstrates that we use secure means of proactively publishing customer data from the data repository to third-party applications such as Salesforce, HubSpot, Marketo, and Zendesk. With SOC 2 Type 2 compliance, our customers can feel certain their data is secure through the last mile of their data stack.

"We built Census to be secure by design. Before we wrote a single line of code, we asked ourselves how can we protect and secure our customers' data by not having to store it? This made passing the SOC 2 certification process easier because security has, and always will be, part of our software design process." - Bradley Buda, co-founder and head of security at Census

With Census, our users can maintain a single, accurate view of customer data throughout their organization. Unlike most business applications, which have to retrieve customer data, we proactively populate commonly used business applications with data stored in a cloud data warehouse.

As a reverse ETL solution, we automatically extract, validate, and send data to the applications that need it, ensuring customers can work with one common source of truth from which they can manage customer interactions and operations.

Best of all, Census integrates with most marketing, sales, and customer success applications without requiring custom code or engineering favors. 🙌

So what's next for security for Census? While we're incredibly proud of our SOC 2 Type 2 compliance, our work to maintain the highest-quality security standard doesn't stop here.  Our auditors will continue to ensure that the controls and policies we've adopted meet this standard across our entire organization. And this compliance is just one part of a long list of things we do--and have done since day one--to protect your data, including:

  • Our secure by design approach to systems architecture,
  • Practicing the Software Development Lifecycle (SDLC),
  • Regular third-party penetration testing,
  • Automated vulnerability scanning,
  • and much more.

If you're an existing Census customer, you can contact your customer success manager or ping us in your dedicated Slack channel to see our SOC 2 Type 2 audit report. If you're trialing Census, your point of contact can provide it to you with an NDA.

Thanks for trusting us with your business and data, and we look forward to continuing to build with it in mind.

Related articles

Product News
Sync data 100x faster on Snowflake with Census Live Syncs
Sync data 100x faster on Snowflake with Census Live Syncs

For years, working with high-quality data in real time was an elusive goal for data teams. Two hurdles blocked real-time data activation on Snowflake from becoming a reality: Lack of low-latency data flows and transformation pipelines The compute cost of running queries at high frequency in order to provide real-time insights Today, we’re solving both of those challenges by partnering with Snowflake to support our real-time Live Syncs, which can be 100 times faster and 100 times cheaper to operate than traditional Reverse ETL. You can create a Live Sync using any Snowflake table (including Dynamic Tables) as a source, and sync data to over 200 business tools within seconds. We’re proud to offer the fastest Reverse ETL platform on the planet, and the only one capable of real-time activation with Snowflake. 👉 Luke Ambrosetti discusses Live Sync architecture in-depth on Snowflake’s Medium blog here. Real-Time Composable CDP with Snowflake Developed alongside Snowflake’s product team, we’re excited to enable the fastest-ever data activation on Snowflake. Today marks a massive paradigm shift in how quickly companies can leverage their first-party data to stay ahead of their competition. In the past, businesses had to implement their real-time use cases outside their Data Cloud by building a separate fast path, through hosted custom infrastructure and event buses, or piles of if-this-then-that no-code hacks — all with painful limitations such as lack of scalability, data silos, and low adaptability. Census Live Syncs were born to tear down the latency barrier that previously prevented companies from centralizing these integrations with all of their others. Census Live Syncs and Snowflake now combine to offer real-time CDP capabilities without having to abandon the Data Cloud. This Composable CDP approach transforms the Data Cloud infrastructure that companies already have into an engine that drives business growth and revenue, delivering huge cost savings and data-driven decisions without complex engineering. Together we’re enabling marketing and business teams to interact with customers at the moment of intent, deliver the most personalized recommendations, and update AI models with the freshest insights. Doing the Math: 100x Faster and 100x Cheaper There are two primary ways to use Census Live Syncs — through Snowflake Dynamic Tables, or directly through Snowflake Streams. Near real time: Dynamic Tables have a target lag of minimum 1 minute (as of March 2024). Real time: Live Syncs can operate off a Snowflake Stream directly to achieve true real-time activation in single-digit seconds. Using a real-world example, one of our customers was looking for real-time activation to personalize in-app content immediately. They replaced their previous hourly process with Census Live Syncs, achieving an end-to-end latency of <1 minute. They observed that Live Syncs are 144 times cheaper and 150 times faster than their previous Reverse ETL process. It’s rare to offer customers multiple orders of magnitude of improvement as part of a product release, but we did the math. Continuous Syncs (traditional Reverse ETL) Census Live Syncs Improvement Cost 24 hours = 24 Snowflake credits. 24 * $2 * 30 = $1440/month ⅙ of a credit per day. ⅙ * $2 * 30 = $10/month 144x Speed Transformation hourly job + 15 minutes for ETL = 75 minutes on average 30 seconds on average 150x Cost The previous method of lowest latency Reverse ETL, called Continuous Syncs, required a Snowflake compute platform to be live 24/7 in order to continuously detect changes. This was expensive and also wasteful for datasets that don’t change often. Assuming that one Snowflake credit is on average $2, traditional Reverse ETL costs 24 credits * $2 * 30 days = $1440 per month. Using Snowflake’s Streams to detect changes offers a huge saving in credits to detect changes, just 1/6th of a single credit in equivalent cost, lowering the cost to $10 per month. Speed Real-time activation also requires ETL and transformation workflows to be low latency. In this example, our customer needed real-time activation of an event that occurs 10 times per day. First, we reduced their ETL processing time to 1 second with our HTTP Request source. On the activation side, Live Syncs activate data with subsecond latency. 1 second HTTP Live Sync + 1 minute Dynamic Table refresh + 1 second Census Snowflake Live Sync = 1 minute end-to-end latency. This process can be even faster when using Live Syncs with a Snowflake Stream. For this customer, using Census Live Syncs on Snowflake was 144x cheaper and 150x faster than their previous Reverse ETL process How Live Syncs work It’s easy to set up a real-time workflow with Snowflake as a source in three steps:

Best Practices
How Retail Brands Should Implement Real-Time Data Platforms To Drive Revenue
How Retail Brands Should Implement Real-Time Data Platforms To Drive Revenue

Remember when the days of "Dear [First Name]" emails felt like cutting-edge personalization?

Product News
Why Census Embedded?
Why Census Embedded?

Last November, we shipped a new product: Census Embedded. It's a massive expansion of our footprint in the world of data. As I'll lay out here, it's a natural evolution of our platform in service of our mission and it's poised to help a lot of people get access to more great quality data.